More man page cleanups (grammatical nits, etc.)

1 files changed, 17 insertions, 19 deletions

diff --git a/setxkbmap.man b/setxkbmap.man
index 290501d..48f49c6 100644
--- a/setxkbmap.man
+++ b/setxkbmap.man
@@ -1,7 +1,7 @@
 .\"
 .\" $XFree86: xc/programs/setxkbmap/setxkbmap.man,v 3.6 2003/01/20 04:15:08 dawes Exp $
 .\"
-.TH SETXKBMAP 1 __xorgversion__
+.TH SETXKBMAP __appmansuffix__ __xorgversion__
 .SH NAME
 setxkbmap
 \- set the keyboard using the X Keyboard Extension
@@ -76,19 +76,19 @@ Specifies the name of an option to determine the components which make up
 the keyboard description;  multiple options may be specified, one per
 \fI-option\fP flag. Note that
 .B setxkbmap
-summarize options specified in the command
-line with options was set before (saved in root window properties). If you
-want only specified options will be set use the \fI-option\fP flag with
-an empty argument first.
+adds options specified in the command line to the options that were set 
+before (as saved in root window properties). If you want to replace all
+previously specified options, use the \fI-option\fP flag with an empty 
+argument first.
 .TP 8
 .B \-print
 With this option the \fBsetxkbmap\fP just prints component names in a format
-acceptable by an \fBxkbcomp\fP (an XKB keymap compiler) and exits. The option
-can be used for tests instead of a verbose option and in case when one need
+acceptable by \fBxkbcomp\fP (an XKB keymap compiler) and exits. The option
+can be used for tests instead of a verbose option and in cases when one needs
 to run both the \fBsetxkbmap\fP and the \fBxkbcomp\fP in chain (see below).
 .TP 8
 .B \-rules \fIfile\fP
-Specifies the name of the rules file used to resolve the request layout
+Specifies the name of the rules file used to resolve the requested layout
 and model to a set of component names.
 .TP 8
 .B \-symbols \fIname\fP
@@ -114,26 +114,24 @@ If no level is specified, each \fI-v\fP or \fI-verbose\fP flag raises the
 level by 1.
 .SH USING WITH xkbcomp
 If you have an Xserver and a client shell running on different computers and
-XKB configuration files sets on those machines are different you can get
+XKB configuration files on those machines are different you can get
 problems specifying a keyboard map by model, layout, options names.
-The thing is the \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
+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
 compose a complete keyboard map using files which the server has.
 Thus if the sets of files differ significantly the names that the
 \fBsetxkbmap\fP generates can be unacceptable on the server side.  You can
-solve this problem running the \fBxkbcomp\fP on the client side too.
-With the \fI-print\fP option \fBsetxkbmap\fP just prints the files names
+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, a command
+directly to the \fBxkbcomp\fP input. For example, the command
 
 \fBsetxkbmap us -print | xkbcomp - $DISPLAY\fP
 
-makes both step on the same (client) machine and loads a keyboard map into
+makes both steps run on the same (client) machine and loads a keyboard map into
 the server.
-.ig
 .SH SEE ALSO
-keyboards(1)
-..
+xkbcomp(__appmansuffix__)
 .SH FILES
 .I __xkbconfigroot__