1.1 --- a/cut.en.ms	Fri Oct 02 07:01:20 2015 +0200
     1.2 +++ b/cut.en.ms	Fri Oct 02 07:19:08 2015 +0200
     1.3 @@ -1,6 +1,6 @@
     1.4  .so macros
     1.5  .lc_ctype en_US.utf8
     1.6 -.pl -4v
     1.7 +.pl -3v
     1.8  
     1.9  .TL
    1.10  Cut out selected fields of each line of a file
    1.11 @@ -9,7 +9,7 @@
    1.12  ..
    1.13  .FS
    1.14  2015-05.
    1.15 -This text is in the public domain (CC0).
    1.16 +This text is part of the public domain (CC0).
    1.17  It is available online:
    1.18  .I http://marmaro.de/docs/
    1.19  .FE
    1.20 @@ -102,7 +102,7 @@
    1.21  .CE
    1.22  .LP
    1.23  (The values to the command line switches may be appended directly
    1.24 -to them or separated by whitespace.)
    1.25 +to them or separated by white\%space.)
    1.26  .PP
    1.27  The field mode is suited for simple tabular data, like the
    1.28  password file. Beyond that, it soon reaches its limits. The typical
    1.29 @@ -233,6 +233,7 @@
    1.30  appeared in all relevant standards. POSIX.2 specified cut for
    1.31  the first time in its modern form (with \f(CW-b\fP) in 1992.
    1.32  
    1.33 +.pl -1v
    1.34  .SH
    1.35  Multi-byte support
    1.36  .LP
    1.37 @@ -246,7 +247,7 @@
    1.38  Then there are implementations that have \f(CW-b\fP, but
    1.39  treat it as an alias for \f(CW-c\fP only. These
    1.40  implementations work correctly for single-byte encodings
    1.41 -(e.g. US-ASCII, Latin1) but for multi-byte encodings (e.g.
    1.42 +(e.g. US-ASCII, Latin1) but for multi-byte en\%codings (e.g.
    1.43  UTF-8) their \f(CW-c\fP behaves like \f(CW-b\fP (and
    1.44  \f(CW-n\fP is ignored). Finally, there are implementations
    1.45  that implement \f(CW-c\fP and \f(CW-b\fP in a POSIX-compliant