Fixing a small mistake in the man page -- s/comp/map/.

And seizing the opportunity to tweak some of the wording.

Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

1 files changed, 7 insertions, 7 deletions

diff --git a/man/setxkbmap.man b/man/setxkbmap.man
index cf23d6f..926b6f7 100644
--- a/man/setxkbmap.man
+++ b/man/setxkbmap.man
@@ -121,18 +121,18 @@ level by 1.
 Prints the program's version number.
 .SH USING WITH xkbcomp
 If you have an Xserver and a client shell running on different computers and
-XKB configuration files on those machines are different you can get
-problems specifying a keyboard map by model, layout, options names.
-This is because \fBsetxkbcomp\fP converts these names to names of XKB
-configuration files according to files that are on the client side computer,
-then it sends the file names to the server where the \fBxkbcomp\fP has to
+some XKB configuration files on those machines are different, you can get
+problems specifying a keyboard map by model, layout, and options names.
+This is because \fBsetxkbmap\fP converts its arguments to names of XKB
+configuration files according to files that are on the client-side computer,
+then sends these file names to the server where \fBxkbcomp\fP has to
 compose a complete keyboard map using files which the server has.
-Thus if the sets of files differ significantly the names that the
+Thus if the sets of files differ in some way, the names that
 \fBsetxkbmap\fP generates can be unacceptable on the server side.  You can
 solve this problem by running the \fBxkbcomp\fP on the client side too.
 With the \fI-print\fP option \fBsetxkbmap\fP just prints the file names
 in an appropriate format to its stdout and this output can be piped
-directly to the \fBxkbcomp\fP input. For example, the command
+directly to the \fBxkbcomp\fP input.  For example, the command
 
 \fBsetxkbmap us -print | xkbcomp - $DISPLAY\fP