Update formatted docs.XORG-6_8_2XORG-6_8-branch

2 files changed, 8 insertions, 8 deletions

diff --git a/README.config b/README.config
index 135675a..cf4d670 100644
--- a/README.config
+++ b/README.config
@@ -6,7 +6,7 @@
 
                                   Abstract
 
-     This document describes how to configure X11R6.8.1 XKB from a
+     This document describes how to configure X11R6.8.2 XKB from a
      user's point a few. It converts basic configuration syntax and
      gives also a few examples.
 
diff --git a/README.enhancing b/README.enhancing
index a8456e8..e1e64fc 100644
--- a/README.enhancing
+++ b/README.enhancing
@@ -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
-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.
+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.
 
 To sum it up:
 
@@ -506,4 +506,4 @@ rules file described above the .lst file could look like:
 And that should be it. Enjoy creating your own xkb mapping.
 
 
-$XdotOrg$
+$XdotOrg: $