Update formatted docs.rel-0-6-1lg3d-rel-0-7-0lg3d-baseXORG-6_8_0

1 files changed, 11 insertions, 12 deletions

diff --git a/README.enhancing b/README.enhancing
index 9993584..a8456e8 100644
--- a/README.enhancing
+++ b/README.enhancing
@@ -124,7 +124,7 @@ modifiers.  <ENTER> key, for instance, usually doesn't depend on any modi-
 fiers so it its row has only one column defined.
 
 Note that in XKB there is no prior assumption that certain modifiers are
-bound to certain columns. By editing proper files (see keytypes (section 4.2,
+bound to certain columns. By editing proper files (see refnam (section 4.2,
 page 1)) this mapping can be changed as well.
 
 Unlike the original X protocol the XKB approach is far more flexible. It is
@@ -132,12 +132,12 @@ comfortable to add one additional XKB term - group. You can think of a group
 as of a vector of columns per each keycode (naturally the dimension of this
 vector may differ for different keycodes). What is it good for? The group is
 not very useful unless you intend to use more than one logically different
-set of symbols (like more than one alphabet) defined in a single mapping ta-
-ble. But then, the group has a natural meaning - each symbol set has its own
-group and changing it means selecting a different one.  XKB approach allows
-up to four different groups. The columns inside each group are called (shift)
-levels. The X server knows the current group and reports it together with
-modifier set and with a keycode in key events.
+set of symbols (like more than one alphabet) defined in a single mapping
+table. But then, the group has a natural meaning - each symbol set has its
+own group and changing it means selecting a different one.  XKB approach
+allows up to four different groups. The columns inside each group are called
+(shift) levels. The X server knows the current group and reports it together
+with modifier set and with a keycode in key events.
 
 To sum it up:
 
@@ -223,9 +223,9 @@ altering what may be needed.
 
 The differences in the number of columns (shift levels) are caused by a dif-
 ferent types of keys (see the types definition in section basics).  Most key-
-codes have implicitly set the keytype in the included "pc/latin" file to
-"FOUR_LEVEL_ALPHABETIC". The only exception is <RALT> keycode which is
-explicitly set "TWO_LEVEL" keytype.
+codes have implicitly set the keytype in the included 'pc/latin' file to
+'FOUR_LEVEL_ALPHABETIC'. The only exception is <RALT> keycode which is
+explicitly set 'TWO_LEVEL' keytype.
 
 All those names refer to pre-defined shift level schemes. Usually you can
 choose a suitable shift level scheme from default types scheme list in proper
@@ -505,6 +505,5 @@ rules file described above the .lst file could look like:
 
 And that should be it. Enjoy creating your own xkb mapping.
 
-     Generated from Id: XKB-Enhancing.sgml,v 1.1.10.2 eich Exp $
-
 
+$XdotOrg$