More doc fixes.

4 files changed, 209 insertions, 206 deletions

diff --git a/doc/ChangeLog b/doc/ChangeLog
index e1c3c210..3444a542 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,7 @@
+2014-09-30         Arnold D. Robbins     <arnold@skeeve.com>
+
+	* gawktexi.in: More fixes after reading through the MS.
+
 2014-09-29         Arnold D. Robbins     <arnold@skeeve.com>
 
 	* gawktexi.in: More fixes after reading through the MS.
diff --git a/doc/gawk.info b/doc/gawk.info
index 058d1100..398fbb61 100644
--- a/doc/gawk.info
+++ b/doc/gawk.info
@@ -26963,7 +26963,7 @@ This appendix provides instructions for installing `gawk' on the
 various platforms that are supported by the developers.  The primary
 developer supports GNU/Linux (and Unix), whereas the other ports are
 contributed.  *Note Bugs::, for the electronic mail addresses of the
-people who did the respective ports.
+people who maintain the respective ports.
 
 * Menu:
 
@@ -27253,12 +27253,12 @@ Unix-derived systems, GNU/Linux, BSD-based systems, and the Cygwin
 environment for MS-Windows.
 
    After you have extracted the `gawk' distribution, `cd' to
-`gawk-4.1.2'.  Like most GNU software, `gawk' is configured
-automatically for your system by running the `configure' program.  This
-program is a Bourne shell script that is generated automatically using
-GNU Autoconf.  (The Autoconf software is described fully starting with
-*note (Autoconf)Top:: autoconf,Autoconf--Generating Automatic
-Configuration Scripts.)
+`gawk-4.1.2'.  As with most GNU software, you configure `gawk' for your
+system by running the `configure' program.  This program is a Bourne
+shell script that is generated automatically using GNU Autoconf.  (The
+Autoconf software is described fully starting with *note
+(Autoconf)Top:: autoconf,Autoconf--Generating Automatic Configuration
+Scripts.)
 
    To configure `gawk', simply run `configure':
 
@@ -27321,8 +27321,8 @@ command line when compiling `gawk' from scratch, including:
      User-modified::) has no effect on the running `awk' program.
 
      When used with GCC's automatic dead-code-elimination, this option
-     cuts almost 200K bytes off the size of the `gawk' executable on
-     GNU/Linux x86 systems.  Results on other systems and with other
+     cuts almost 23K bytes off the size of the `gawk' executable on
+     GNU/Linux x86_64 systems.  Results on other systems and with other
      compilers are likely to vary.  Using this option may bring you
      some slight performance improvement.
 
@@ -27408,10 +27408,10 @@ File: gawk.info,  Node: PC Installation,  Next: VMS Installation,  Up: Non-Unix
 B.3.1 Installation on PC Operating Systems
 ------------------------------------------
 
-This minor node covers installation and usage of `gawk' on x86 machines
-running MS-DOS, any version of MS-Windows, or OS/2.  In this minor
-node, the term "Windows32" refers to any of Microsoft
-Windows-95/98/ME/NT/2000/XP/Vista/7/8.
+This minor node covers installation and usage of `gawk' on Intel
+architecture machines running MS-DOS, any version of MS-Windows, or
+OS/2.  In this minor node, the term "Windows32" refers to any of
+Microsoft Windows-95/98/ME/NT/2000/XP/Vista/7/8.
 
    The limitations of MS-DOS (and MS-DOS shells under the other
 operating systems) has meant that various "DOS extenders" are often
@@ -27496,7 +27496,7 @@ MS-DOS and Windows32 versions.  A list of targets is printed if the
 `gawk' using the DJGPP tools, enter `make djgpp'.  (The DJGPP tools
 needed for the build may be found at
 `ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/'.)  To build a native
-MS-Windows binary of `gawk', type `make mingw32'.
+MS-Windows binary of `gawk' using the MinGW tools, type `make mingw32'.
 
    The 32 bit EMX version of `gawk' works "out of the box" under OS/2.
 However, it is highly recommended to use GCC 2.95.3 for the compilation.
@@ -27588,8 +27588,8 @@ Networking::).  EMX (OS/2 only) supports at least the `|&' operator.
    The MS-DOS and MS-Windows versions of `gawk' search for program
 files as described in *note AWKPATH Variable::.  However, semicolons
 (rather than colons) separate elements in the `AWKPATH' variable.  If
-`AWKPATH' is not set or is empty, then the default search path for
-MS-Windows and MS-DOS versions is `.;c:/lib/awk;c:/gnu/lib/awk'.
+`AWKPATH' is not set or is empty, then the default search path is
+`.;c:/lib/awk;c:/gnu/lib/awk'.
 
    The search path for OS/2 (32 bit, EMX) is determined by the prefix
 directory (most likely `/usr' or `c:/usr') that has been specified as
@@ -27613,10 +27613,10 @@ programs) silently translate end-of-line `\r\n' to `\n' on input and
 `\n' to `\r\n' on output.  A special `BINMODE' variable (c.e.)  allows
 control over these translations and is interpreted as follows:
 
-   * If `BINMODE' is `"r"', or one, then binary mode is set on read
+   * If `BINMODE' is `"r"' or one, then binary mode is set on read
      (i.e., no translations on reads).
 
-   * If `BINMODE' is `"w"', or two, then binary mode is set on write
+   * If `BINMODE' is `"w"' or two, then binary mode is set on write
      (i.e., no translations on writes).
 
    * If `BINMODE' is `"rw"' or `"wr"' or three, binary mode is set for
@@ -27683,7 +27683,7 @@ same as for a Unix system:
      tar -xvpzf gawk-4.1.2.tar.gz
      cd gawk-4.1.2
      ./configure
-     make
+     make && make check
 
    When compared to GNU/Linux on the same system, the `configure' step
 on Cygwin takes considerably longer.  However, it does finish, and then
@@ -27706,8 +27706,8 @@ translation of `"\r\n"', since it won't.
 
 File: gawk.info,  Node: VMS Installation,  Prev: PC Installation,  Up: Non-Unix Installation
 
-B.3.2 How to Compile and Install `gawk' on Vax/VMS and OpenVMS
---------------------------------------------------------------
+B.3.2 Compiling and Installing `gawk' on Vax/VMS and OpenVMS
+------------------------------------------------------------
 
 This node describes how to compile and install `gawk' under VMS.  The
 older designation "VMS" is used throughout to refer to OpenVMS.
@@ -27898,12 +27898,12 @@ If any other dash-type options (or multiple parameters such as data
 files to process) are present, there is no ambiguity and `--' can be
 omitted.
 
-   The `exit' value is a Unix-style value and is encoded to a VMS exit
+   The `exit' value is a Unix-style value and is encoded into a VMS exit
 status value when the program exits.
 
    The VMS severity bits will be set based on the `exit' value.  A
 failure is indicated by 1 and VMS sets the `ERROR' status.  A fatal
-error is indicated by 2 and VMS will set the `FATAL' status.  All other
+error is indicated by 2 and VMS sets the `FATAL' status.  All other
 values will have the `SUCCESS' status.  The exit value is encoded to
 comply with VMS coding standards and will have the `C_FACILITY_NO' of
 `0x350000' with the constant `0xA000' added to the number shifted over
@@ -27916,9 +27916,9 @@ by 3 bits to make room for the severity codes.
 A C program that uses `exec()' to call `gawk' will get the original
 Unix-style exit value.
 
-   Older versions of `gawk' treated a Unix exit code 0 as 1, a failure
-as 2, a fatal error as 4, and passed all the other numbers through.
-This violated the VMS exit status coding requirements.
+   Older versions of `gawk' for VMS treated a Unix exit code 0 as 1, a
+failure as 2, a fatal error as 4, and passed all the other numbers
+through.  This violated the VMS exit status coding requirements.
 
    VAX/VMS floating point uses unbiased rounding. *Note Round
 Function::.
@@ -27949,8 +27949,8 @@ reorganized to supply individual PCSI packages for each component.  See
    The normal build procedure for `gawk' produces a program that is
 suitable for use with GNV.
 
-   The `vms/gawk_build_steps.txt' in the source documents the procedure
-for building a VMS PCSI kit that is compatible with GNV.
+   The `vms/gawk_build_steps.txt' in the distribution documents the
+procedure for building a VMS PCSI kit that is compatible with GNV.
 
 
 File: gawk.info,  Node: VMS Old Gawk,  Prev: VMS GNV,  Up: VMS Installation
@@ -27979,11 +27979,11 @@ B.4 Reporting Problems and Bugs
 please report it to the developers; we cannot promise to do anything
 but we might well want to fix it.
 
-   Before reporting a bug, make sure you have actually found a real bug.
-Carefully reread the documentation and see if it really says you can do
-what you're trying to do.  If it's not clear whether you should be able
-to do something or not, report that too; it's a bug in the
-documentation!
+   Before reporting a bug, please make sure you have actually found a
+real bug.  Carefully reread the documentation and see if it really says
+you can do what you're trying to do.  If it's not clear whether you
+should be able to do something or not, report that too; it's a bug in
+the documentation!
 
    Before reporting a bug or trying to fix it yourself, try to isolate
 it to the smallest possible `awk' program and input data file that
@@ -27999,17 +27999,17 @@ get this information with the command `gawk --version'.
    Once you have a precise problem, send email to <bug-gawk@gnu.org>.
 
    The `gawk' maintainers subscribe to this address and thus they will
-receive your bug report.  If necessary, the primary maintainer can be
-reached directly at <arnold@skeeve.com>.  The bug reporting address is
-preferred since the email list is archived at the GNU Project.  _All
-email should be in English. This is the only language understood in
-common by all the maintainers._
+receive your bug report.  Although you can send mail to the maintainers
+directly, the bug reporting address is preferred since the email list
+is archived at the GNU Project.  _All email must be in English. This is
+the only language understood in common by all the maintainers._
 
      CAUTION: Do _not_ try to report bugs in `gawk' by posting to the
      Usenet/Internet newsgroup `comp.lang.awk'.  While the `gawk'
      developers do occasionally read this newsgroup, there is no
      guarantee that we will see your posting.  The steps described
-     above are the official recognized ways for reporting bugs.  Really.
+     above are the only official recognized way for reporting bugs.
+     Really.
 
      NOTE: Many distributions of GNU/Linux and the various BSD-based
      operating systems have their own bug reporting systems.  If you
@@ -28018,25 +28018,26 @@ common by all the maintainers._
 
      This is for two reasons.  First, while some distributions forward
      bug reports "upstream" to the GNU mailing list, many don't, so
-     there is a good chance that the `gawk'  maintainer won't even see
+     there is a good chance that the `gawk'  maintainers won't even see
      the bug report!  Second, mail to the GNU list is archived, and
      having everything at the GNU project keeps things self-contained
-     and not dependant on other web sites.
+     and not dependant on other organizations.
 
    Non-bug suggestions are always welcome as well.  If you have
 questions about things that are unclear in the documentation or are
-just obscure features, ask me; I will try to help you out, although I
-may not have the time to fix the problem.  You can send me electronic
-mail at the Internet address noted previously.
+just obscure features, ask on the bug list; we will try to help you out
+if we can.
 
    If you find bugs in one of the non-Unix ports of `gawk', please send
-an electronic mail message to the person who maintains that port.  They
-are named in the following list, as well as in the `README' file in the
-`gawk' distribution.  Information in the `README' file should be
-considered authoritative if it conflicts with this Info file.
+an electronic mail message to the bug list, with a copy to the person
+who maintains that port.  They are named in the following list, as well
+as in the `README' file in the `gawk' distribution.  Information in the
+`README' file should be considered authoritative if it conflicts with
+this Info file.
 
-   The people maintaining the non-Unix ports of `gawk' are as follows:
+   The people maintaining the various `gawk' ports are:
 
+Unix and POSIX systems  Arnold Robbins, <arnold@skeeve.com>.
 MS-DOS with DJGPP       Scott Deifik, <scottd.mail@sbcglobal.net>.
 MS-Windows with MinGW   Eli Zaretskii, <eliz@gnu.org>.
 OS/2                    Andreas Buening, <andreas.buening@nexgo.de>.
@@ -28128,9 +28129,9 @@ Unix `awk'
 `pawk'
      Nelson H.F. Beebe at the University of Utah has modified BWK `awk'
      to provide timing and profiling information.  It is different from
-     `gawk' with the `--profile' option.  (*note Profiling::), in that
-     it uses CPU-based profiling, not line-count profiling.  You may
-     find it at either
+     `gawk' with the `--profile' option (*note Profiling::), in that it
+     uses CPU-based profiling, not line-count profiling.  You may find
+     it at either
      `ftp://ftp.math.utah.edu/pub/pawk/pawk-20030606.tar.gz' or
      `http://www.math.utah.edu/pub/pawk/pawk-20030606.tar.gz'.
 
@@ -28146,11 +28147,11 @@ Busybox Awk
 The OpenSolaris POSIX `awk'
      The versions of `awk' in `/usr/xpg4/bin' and `/usr/xpg6/bin' on
      Solaris are more-or-less POSIX-compliant.  They are based on the
-     `awk' from Mortice Kern Systems for PCs.  This author was able to
-     make this code compile and work under GNU/Linux with 1-2 hours of
-     work.  Making it more generally portable (using GNU Autoconf
-     and/or Automake) would take more work, and this has not been done,
-     at least to our knowledge.
+     `awk' from Mortice Kern Systems for PCs.  We were able to make
+     this code compile and work under GNU/Linux with 1-2 hours of work.
+     Making it more generally portable (using GNU Autoconf and/or
+     Automake) would take more work, and this has not been done, at
+     least to our knowledge.
 
      The source code used to be available from the OpenSolaris web site.
      However, that project was ended and the web site shut down.
@@ -31801,7 +31802,7 @@ Index
 * common extensions, RS as a regexp:     gawk split records.  (line   6)
 * common extensions, single character fields: Single Character Fields.
                                                               (line   6)
-* comp.lang.awk newsgroup:               Bugs.                (line  39)
+* comp.lang.awk newsgroup:               Bugs.                (line  38)
 * comparison expressions:                Typing and Comparison.
                                                               (line   9)
 * comparison expressions, as patterns:   Expression Patterns. (line  14)
@@ -33543,7 +33544,7 @@ Index
 * RLENGTH variable:                      Auto-set.            (line 251)
 * RLENGTH variable, match() function and: String Functions.   (line 227)
 * Robbins, Arnold <1>:                   Future Extensions.   (line   6)
-* Robbins, Arnold <2>:                   Bugs.                (line  32)
+* Robbins, Arnold <2>:                   Bugs.                (line  71)
 * Robbins, Arnold <3>:                   Contributors.        (line 144)
 * Robbins, Arnold <4>:                   General Data Types.  (line   6)
 * Robbins, Arnold <5>:                   Alarm Program.       (line   6)
@@ -34600,64 +34601,64 @@ Ref: Ranges and Locales-Footnote-31075147
 Node: Contributors1075368
 Node: History summary1080908
 Node: Installation1082277
-Node: Gawk Distribution1083228
-Node: Getting1083712
-Node: Extracting1084536
-Node: Distribution contents1086178
-Node: Unix Installation1091895
-Node: Quick Installation1092512
-Node: Additional Configuration Options1094954
-Node: Configuration Philosophy1096692
-Node: Non-Unix Installation1099043
-Node: PC Installation1099501
-Node: PC Binary Installation1100812
-Node: PC Compiling1102660
-Ref: PC Compiling-Footnote-11105659
-Node: PC Testing1105764
-Node: PC Using1106940
-Node: Cygwin1111092
-Node: MSYS1111901
-Node: VMS Installation1112399
-Node: VMS Compilation1113195
-Ref: VMS Compilation-Footnote-11114417
-Node: VMS Dynamic Extensions1114475
-Node: VMS Installation Details1115848
-Node: VMS Running1118100
-Node: VMS GNV1120934
-Node: VMS Old Gawk1121657
-Node: Bugs1122127
-Node: Other Versions1126131
-Node: Installation summary1132355
-Node: Notes1133411
-Node: Compatibility Mode1134276
-Node: Additions1135058
-Node: Accessing The Source1135983
-Node: Adding Code1137419
-Node: New Ports1143591
-Node: Derived Files1148072
-Ref: Derived Files-Footnote-11153547
-Ref: Derived Files-Footnote-21153581
-Ref: Derived Files-Footnote-31154177
-Node: Future Extensions1154291
-Node: Implementation Limitations1154897
-Node: Extension Design1156145
-Node: Old Extension Problems1157299
-Ref: Old Extension Problems-Footnote-11158816
-Node: Extension New Mechanism Goals1158873
-Ref: Extension New Mechanism Goals-Footnote-11162233
-Node: Extension Other Design Decisions1162422
-Node: Extension Future Growth1164530
-Node: Old Extension Mechanism1165366
-Node: Notes summary1167128
-Node: Basic Concepts1168314
-Node: Basic High Level1168995
-Ref: figure-general-flow1169267
-Ref: figure-process-flow1169866
-Ref: Basic High Level-Footnote-11173095
-Node: Basic Data Typing1173280
-Node: Glossary1176608
-Node: Copying1201766
-Node: GNU Free Documentation License1239322
-Node: Index1264458
+Node: Gawk Distribution1083233
+Node: Getting1083717
+Node: Extracting1084541
+Node: Distribution contents1086183
+Node: Unix Installation1091900
+Node: Quick Installation1092517
+Node: Additional Configuration Options1094948
+Node: Configuration Philosophy1096688
+Node: Non-Unix Installation1099039
+Node: PC Installation1099497
+Node: PC Binary Installation1100823
+Node: PC Compiling1102671
+Ref: PC Compiling-Footnote-11105692
+Node: PC Testing1105797
+Node: PC Using1106973
+Node: Cygwin1111088
+Node: MSYS1111911
+Node: VMS Installation1112409
+Node: VMS Compilation1113201
+Ref: VMS Compilation-Footnote-11114423
+Node: VMS Dynamic Extensions1114481
+Node: VMS Installation Details1115854
+Node: VMS Running1118106
+Node: VMS GNV1120947
+Node: VMS Old Gawk1121676
+Node: Bugs1122146
+Node: Other Versions1126110
+Node: Installation summary1132323
+Node: Notes1133379
+Node: Compatibility Mode1134244
+Node: Additions1135026
+Node: Accessing The Source1135951
+Node: Adding Code1137387
+Node: New Ports1143559
+Node: Derived Files1148040
+Ref: Derived Files-Footnote-11153515
+Ref: Derived Files-Footnote-21153549
+Ref: Derived Files-Footnote-31154145
+Node: Future Extensions1154259
+Node: Implementation Limitations1154865
+Node: Extension Design1156113
+Node: Old Extension Problems1157267
+Ref: Old Extension Problems-Footnote-11158784
+Node: Extension New Mechanism Goals1158841
+Ref: Extension New Mechanism Goals-Footnote-11162201
+Node: Extension Other Design Decisions1162390
+Node: Extension Future Growth1164498
+Node: Old Extension Mechanism1165334
+Node: Notes summary1167096
+Node: Basic Concepts1168282
+Node: Basic High Level1168963
+Ref: figure-general-flow1169235
+Ref: figure-process-flow1169834
+Ref: Basic High Level-Footnote-11173063
+Node: Basic Data Typing1173248
+Node: Glossary1176576
+Node: Copying1201734
+Node: GNU Free Documentation License1239290
+Node: Index1264426
 
 End Tag Table
diff --git a/doc/gawk.texi b/doc/gawk.texi
index 513dea3a..8040e06e 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -36688,7 +36688,7 @@ various platforms that are supported by the developers.  The primary
 developer supports GNU/Linux (and Unix), whereas the other ports are
 contributed.
 @xref{Bugs},
-for the electronic mail addresses of the people who did
+for the electronic mail addresses of the people who maintain
 the respective ports.
 
 @menu
@@ -37007,11 +37007,10 @@ Unix-derived systems, GNU/Linux, BSD-based systems, and the Cygwin
 environment for MS-Windows.
 
 After you have extracted the @command{gawk} distribution, @command{cd}
-to @file{gawk-@value{VERSION}.@value{PATCHLEVEL}}.  Like most GNU software,
-@command{gawk} is configured
-automatically for your system by running the @command{configure} program.
-This program is a Bourne shell script that is generated automatically using
-GNU Autoconf.
+to @file{gawk-@value{VERSION}.@value{PATCHLEVEL}}.  As with most GNU
+software, you configure @command{gawk} for your system by running the
+@command{configure} program.  This program is a Bourne shell script that
+is generated automatically using GNU Autoconf.
 @ifnotinfo
 (The Autoconf software is
 described fully in
@@ -37106,8 +37105,8 @@ Similarly, setting the @code{LINT} variable
 has no effect on the running @command{awk} program.
 
 When used with GCC's automatic dead-code-elimination, this option
-cuts almost 200K bytes off the size of the @command{gawk}
-executable on GNU/Linux x86 systems.  Results on other systems and
+cuts almost 23K bytes off the size of the @command{gawk}
+executable on GNU/Linux x86_64 systems.  Results on other systems and
 with other compilers are likely to vary.
 Using this option may bring you some slight performance improvement.
 
@@ -37200,7 +37199,8 @@ various non-Unix systems.
 
 @cindex PC operating systems@comma{} @command{gawk} on, installing
 @cindex operating systems, PC@comma{} @command{gawk} on, installing
-This @value{SECTION} covers installation and usage of @command{gawk} on x86 machines
+This @value{SECTION} covers installation and usage of @command{gawk}
+on Intel architecture machines
 @ifclear FOR_PRINT
 running MS-DOS, any version of MS-Windows, or OS/2.
 @end ifclear
@@ -37302,7 +37302,8 @@ MS-DOS and Windows32 versions.  A list of targets is printed if the
 build @command{gawk} using the DJGPP tools, enter @samp{make djgpp}.
 (The DJGPP tools needed for the build may be found at
 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/}.)  To build a
-native MS-Windows binary of @command{gawk}, type @samp{make mingw32}.
+native MS-Windows binary of @command{gawk} using the MinGW tools,
+type @samp{make mingw32}.
 
 @ifclear FOR_PRINT
 @cindex compiling @command{gawk} with EMX for OS/2
@@ -37432,8 +37433,7 @@ The MS-DOS and MS-Windows versions of @command{gawk} search for
 program files as described in @ref{AWKPATH Variable}.  However,
 semicolons (rather than colons) separate elements in the @env{AWKPATH}
 variable.  If @env{AWKPATH} is not set or is empty, then the default
-search path for MS-Windows and MS-DOS versions is
-@samp{@w{.;c:/lib/awk;c:/gnu/lib/awk}}.
+search path is @samp{@w{.;c:/lib/awk;c:/gnu/lib/awk}}.
 
 @ifclear FOR_PRINT
 @cindex @command{gawk}, OS/2 version of
@@ -37478,12 +37478,12 @@ allows control over these translations and is interpreted as follows:
 
 @itemize @value{BULLET}
 @item
-If @code{BINMODE} is @code{"r"}, or one,
+If @code{BINMODE} is @code{"r"} or one,
 then
 binary mode is set on read (i.e., no translations on reads).
 
 @item
-If @code{BINMODE} is @code{"w"}, or two,
+If @code{BINMODE} is @code{"w"} or two,
 then
 binary mode is set on write (i.e., no translations on writes).
 
@@ -37571,7 +37571,7 @@ same as for a Unix system:
 tar -xvpzf gawk-@value{VERSION}.@value{PATCHLEVEL}.tar.gz
 cd gawk-@value{VERSION}.@value{PATCHLEVEL}
 ./configure
-make
+make && make check
 @end example
 
 When compared to GNU/Linux on the same system, the @samp{configure}
@@ -37590,7 +37590,7 @@ been ported to MS-Windows that expect @command{gawk} to do automatic
 translation of @code{"\r\n"}, since it won't.
 
 @node VMS Installation
-@appendixsubsec How to Compile and Install @command{gawk} on Vax/VMS and OpenVMS
+@appendixsubsec Compiling and Installing @command{gawk} on Vax/VMS and OpenVMS
 
 @c based on material from Pat Rankin <rankin@eql.caltech.edu>
 @c now rankin@pactechdata.com
@@ -37807,12 +37807,12 @@ other dash-type options (or multiple parameters such as @value{DF}s to
 process) are present, there is no ambiguity and @option{--} can be omitted.
 
 @cindex exit status, of VMS
-The @code{exit} value is a Unix-style value and is encoded to a VMS exit
+The @code{exit} value is a Unix-style value and is encoded into a VMS exit
 status value when the program exits.
 
 The VMS severity bits will be set based on the @code{exit} value.
 A failure is indicated by 1 and VMS sets the @code{ERROR} status.
-A fatal error is indicated by 2 and VMS will set the @code{FATAL} status.
+A fatal error is indicated by 2 and VMS sets the @code{FATAL} status.
 All other values will have the @code{SUCCESS} status.  The exit value is
 encoded to comply with VMS coding standards and will have the
 @code{C_FACILITY_NO} of @code{0x350000} with the constant @code{0xA000}
@@ -37828,7 +37828,7 @@ unix_status = (vms_status .and. &x7f8) / 8
 A C program that uses @code{exec()} to call @command{gawk} will get the original
 Unix-style exit value.
 
-Older versions of @command{gawk} treated a Unix exit code 0 as 1, a failure
+Older versions of @command{gawk} for VMS treated a Unix exit code 0 as 1, a failure
 as 2, a fatal error as 4, and passed all the other numbers through.
 This violated the VMS exit status coding requirements.
 
@@ -37862,7 +37862,7 @@ See @w{@uref{https://sourceforge.net/p/gnv/wiki/InstallingGNVPackages/}.}
 The normal build procedure for @command{gawk} produces a program that
 is suitable for use with GNV.
 
-The @file{vms/gawk_build_steps.txt} in the source documents the procedure
+The @file{vms/gawk_build_steps.txt} in the distribution documents the procedure
 for building a VMS PCSI kit that is compatible with GNV.
 
 @ignore
@@ -37935,7 +37935,7 @@ If you have problems with @command{gawk} or think that you have found a bug,
 please report it to the developers; we cannot promise to do anything
 but we might well want to fix it.
 
-Before reporting a bug, make sure you have actually found a real bug.
+Before reporting a bug, please make sure you have actually found a real bug.
 Carefully reread the documentation and see if it really says you can do
 what you're trying to do.  If it's not clear whether you should be able
 to do something or not, report that too; it's a bug in the documentation!
@@ -37957,14 +37957,12 @@ You can get this information with the command @samp{gawk --version}.
 Once you have a precise problem, send email to
 @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org}.
 
-@cindex Robbins, Arnold
 The @command{gawk} maintainers subscribe to this address and
 thus they will receive your bug report.
-If necessary, the primary maintainer can be reached directly at
-@EMAIL{arnold@@skeeve.com,arnold at skeeve dot com}.
-The bug reporting address is preferred since the
+Although you can send mail to the maintainers directly,
+the bug reporting address is preferred since the
 email list is archived at the GNU Project.
-@emph{All email should be in English. This is the only language
+@emph{All email must be in English. This is the only language
 understood in common by all the maintainers.}
 
 @cindex @code{comp.lang.awk} newsgroup
@@ -37973,7 +37971,7 @@ Do @emph{not} try to report bugs in @command{gawk} by
 posting to the Usenet/Internet newsgroup @code{comp.lang.awk}.
 While the @command{gawk} developers do occasionally read this newsgroup,
 there is no guarantee that we will see your posting.  The steps described
-above are the official recognized ways for reporting bugs.
+above are the only official recognized way for reporting bugs.
 Really.
 @end quotation
 
@@ -37985,34 +37983,35 @@ bug reporting system, @emph{please} also send a copy to
 
 This is for two reasons.  First, while some distributions forward
 bug reports ``upstream'' to the GNU mailing list, many don't, so there is a good
-chance that the @command{gawk}  maintainer won't even see the bug report!  Second,
+chance that the @command{gawk}  maintainers won't even see the bug report!  Second,
 mail to the GNU list is archived, and having everything at the GNU project
-keeps things self-contained and not dependant on other web sites.
+keeps things self-contained and not dependant on other organizations.
 @end quotation
 
 Non-bug suggestions are always welcome as well.  If you have questions
 about things that are unclear in the documentation or are just obscure
-features, ask me; I will try to help you out, although I
-may not have the time to fix the problem.  You can send me electronic
-mail at the Internet address noted previously.
+features, ask on the bug list; we will try to help you out if we can.
 
-If you find bugs in one of the non-Unix ports of @command{gawk}, please send
-an electronic mail message to the person who maintains that port.  They
-are named in the following list, as well as in the @file{README} file in the @command{gawk}
-distribution.  Information in the @file{README} file should be considered
-authoritative if it conflicts with this @value{DOCUMENT}.
+If you find bugs in one of the non-Unix ports of @command{gawk}, please
+send an electronic mail message to the bug list, with a copy to the
+person who maintains that port.  They are named in the following list,
+as well as in the @file{README} file in the @command{gawk} distribution.
+Information in the @file{README} file should be considered authoritative
+if it conflicts with this @value{DOCUMENT}.
 
-The people maintaining the non-Unix ports of @command{gawk} are
-as follows:
+The people maintaining the various @command{gawk} ports are:
 
 @c put the index entries outside the table, for docbook
-@cindex Deifik, Scott
-@cindex Zaretskii, Eli
 @cindex Buening, Andreas
-@cindex Rankin, Pat
+@cindex Deifik, Scott
 @cindex Malmberg, John
 @cindex Pitts, Dave
+@cindex Rankin, Pat
+@cindex Robbins, Arnold
+@cindex Zaretskii, Eli
 @multitable {MS-Windows with MinGW} {123456789012345678901234567890123456789001234567890}
+@item Unix and POSIX systems @tab Arnold Robbins, @EMAIL{arnold@@skeeve.com,arnold at skeeve dot com}.
+
 @item MS-DOS with DJGPP @tab Scott Deifik, @EMAIL{scottd.mail@@sbcglobal.net,scottd dot mail at sbcglobal dot net}.
 
 @item MS-Windows with MinGW @tab Eli Zaretskii, @EMAIL{eliz@@gnu.org,eliz at gnu dot org}.
@@ -38165,7 +38164,7 @@ since approximately 2003.
 @item @command{pawk}
 Nelson H.F.@: Beebe at the University of Utah has modified
 BWK @command{awk} to provide timing and profiling information.
-It is different from @command{gawk} with the @option{--profile} option.
+It is different from @command{gawk} with the @option{--profile} option
 (@pxref{Profiling}),
 in that it uses CPU-based profiling, not line-count
 profiling.  You may find it at either
@@ -38190,7 +38189,7 @@ information, see the @uref{http://busybox.net, project's home page}.
 The versions of @command{awk} in @file{/usr/xpg4/bin} and
 @file{/usr/xpg6/bin} on Solaris are more-or-less POSIX-compliant.
 They are based on the @command{awk} from Mortice Kern Systems for PCs.
-This author was able to make this code compile and work under GNU/Linux
+We were able to make this code compile and work under GNU/Linux
 with 1--2 hours of work.  Making it more generally portable (using
 GNU Autoconf and/or Automake) would take more work, and this
 has not been done, at least to our knowledge.
diff --git a/doc/gawktexi.in b/doc/gawktexi.in
index 6e4c9567..3b2214df 100644
--- a/doc/gawktexi.in
+++ b/doc/gawktexi.in
@@ -35785,7 +35785,7 @@ various platforms that are supported by the developers.  The primary
 developer supports GNU/Linux (and Unix), whereas the other ports are
 contributed.
 @xref{Bugs},
-for the electronic mail addresses of the people who did
+for the electronic mail addresses of the people who maintain
 the respective ports.
 
 @menu
@@ -36104,11 +36104,10 @@ Unix-derived systems, GNU/Linux, BSD-based systems, and the Cygwin
 environment for MS-Windows.
 
 After you have extracted the @command{gawk} distribution, @command{cd}
-to @file{gawk-@value{VERSION}.@value{PATCHLEVEL}}.  Like most GNU software,
-@command{gawk} is configured
-automatically for your system by running the @command{configure} program.
-This program is a Bourne shell script that is generated automatically using
-GNU Autoconf.
+to @file{gawk-@value{VERSION}.@value{PATCHLEVEL}}.  As with most GNU
+software, you configure @command{gawk} for your system by running the
+@command{configure} program.  This program is a Bourne shell script that
+is generated automatically using GNU Autoconf.
 @ifnotinfo
 (The Autoconf software is
 described fully in
@@ -36203,8 +36202,8 @@ Similarly, setting the @code{LINT} variable
 has no effect on the running @command{awk} program.
 
 When used with GCC's automatic dead-code-elimination, this option
-cuts almost 200K bytes off the size of the @command{gawk}
-executable on GNU/Linux x86 systems.  Results on other systems and
+cuts almost 23K bytes off the size of the @command{gawk}
+executable on GNU/Linux x86_64 systems.  Results on other systems and
 with other compilers are likely to vary.
 Using this option may bring you some slight performance improvement.
 
@@ -36297,7 +36296,8 @@ various non-Unix systems.
 
 @cindex PC operating systems@comma{} @command{gawk} on, installing
 @cindex operating systems, PC@comma{} @command{gawk} on, installing
-This @value{SECTION} covers installation and usage of @command{gawk} on x86 machines
+This @value{SECTION} covers installation and usage of @command{gawk}
+on Intel architecture machines
 @ifclear FOR_PRINT
 running MS-DOS, any version of MS-Windows, or OS/2.
 @end ifclear
@@ -36399,7 +36399,8 @@ MS-DOS and Windows32 versions.  A list of targets is printed if the
 build @command{gawk} using the DJGPP tools, enter @samp{make djgpp}.
 (The DJGPP tools needed for the build may be found at
 @uref{ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/}.)  To build a
-native MS-Windows binary of @command{gawk}, type @samp{make mingw32}.
+native MS-Windows binary of @command{gawk} using the MinGW tools,
+type @samp{make mingw32}.
 
 @ifclear FOR_PRINT
 @cindex compiling @command{gawk} with EMX for OS/2
@@ -36529,8 +36530,7 @@ The MS-DOS and MS-Windows versions of @command{gawk} search for
 program files as described in @ref{AWKPATH Variable}.  However,
 semicolons (rather than colons) separate elements in the @env{AWKPATH}
 variable.  If @env{AWKPATH} is not set or is empty, then the default
-search path for MS-Windows and MS-DOS versions is
-@samp{@w{.;c:/lib/awk;c:/gnu/lib/awk}}.
+search path is @samp{@w{.;c:/lib/awk;c:/gnu/lib/awk}}.
 
 @ifclear FOR_PRINT
 @cindex @command{gawk}, OS/2 version of
@@ -36575,12 +36575,12 @@ allows control over these translations and is interpreted as follows:
 
 @itemize @value{BULLET}
 @item
-If @code{BINMODE} is @code{"r"}, or one,
+If @code{BINMODE} is @code{"r"} or one,
 then
 binary mode is set on read (i.e., no translations on reads).
 
 @item
-If @code{BINMODE} is @code{"w"}, or two,
+If @code{BINMODE} is @code{"w"} or two,
 then
 binary mode is set on write (i.e., no translations on writes).
 
@@ -36668,7 +36668,7 @@ same as for a Unix system:
 tar -xvpzf gawk-@value{VERSION}.@value{PATCHLEVEL}.tar.gz
 cd gawk-@value{VERSION}.@value{PATCHLEVEL}
 ./configure
-make
+make && make check
 @end example
 
 When compared to GNU/Linux on the same system, the @samp{configure}
@@ -36687,7 +36687,7 @@ been ported to MS-Windows that expect @command{gawk} to do automatic
 translation of @code{"\r\n"}, since it won't.
 
 @node VMS Installation
-@appendixsubsec How to Compile and Install @command{gawk} on Vax/VMS and OpenVMS
+@appendixsubsec Compiling and Installing @command{gawk} on Vax/VMS and OpenVMS
 
 @c based on material from Pat Rankin <rankin@eql.caltech.edu>
 @c now rankin@pactechdata.com
@@ -36904,12 +36904,12 @@ other dash-type options (or multiple parameters such as @value{DF}s to
 process) are present, there is no ambiguity and @option{--} can be omitted.
 
 @cindex exit status, of VMS
-The @code{exit} value is a Unix-style value and is encoded to a VMS exit
+The @code{exit} value is a Unix-style value and is encoded into a VMS exit
 status value when the program exits.
 
 The VMS severity bits will be set based on the @code{exit} value.
 A failure is indicated by 1 and VMS sets the @code{ERROR} status.
-A fatal error is indicated by 2 and VMS will set the @code{FATAL} status.
+A fatal error is indicated by 2 and VMS sets the @code{FATAL} status.
 All other values will have the @code{SUCCESS} status.  The exit value is
 encoded to comply with VMS coding standards and will have the
 @code{C_FACILITY_NO} of @code{0x350000} with the constant @code{0xA000}
@@ -36925,7 +36925,7 @@ unix_status = (vms_status .and. &x7f8) / 8
 A C program that uses @code{exec()} to call @command{gawk} will get the original
 Unix-style exit value.
 
-Older versions of @command{gawk} treated a Unix exit code 0 as 1, a failure
+Older versions of @command{gawk} for VMS treated a Unix exit code 0 as 1, a failure
 as 2, a fatal error as 4, and passed all the other numbers through.
 This violated the VMS exit status coding requirements.
 
@@ -36959,7 +36959,7 @@ See @w{@uref{https://sourceforge.net/p/gnv/wiki/InstallingGNVPackages/}.}
 The normal build procedure for @command{gawk} produces a program that
 is suitable for use with GNV.
 
-The @file{vms/gawk_build_steps.txt} in the source documents the procedure
+The @file{vms/gawk_build_steps.txt} in the distribution documents the procedure
 for building a VMS PCSI kit that is compatible with GNV.
 
 @ignore
@@ -37032,7 +37032,7 @@ If you have problems with @command{gawk} or think that you have found a bug,
 please report it to the developers; we cannot promise to do anything
 but we might well want to fix it.
 
-Before reporting a bug, make sure you have actually found a real bug.
+Before reporting a bug, please make sure you have actually found a real bug.
 Carefully reread the documentation and see if it really says you can do
 what you're trying to do.  If it's not clear whether you should be able
 to do something or not, report that too; it's a bug in the documentation!
@@ -37054,14 +37054,12 @@ You can get this information with the command @samp{gawk --version}.
 Once you have a precise problem, send email to
 @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org}.
 
-@cindex Robbins, Arnold
 The @command{gawk} maintainers subscribe to this address and
 thus they will receive your bug report.
-If necessary, the primary maintainer can be reached directly at
-@EMAIL{arnold@@skeeve.com,arnold at skeeve dot com}.
-The bug reporting address is preferred since the
+Although you can send mail to the maintainers directly,
+the bug reporting address is preferred since the
 email list is archived at the GNU Project.
-@emph{All email should be in English. This is the only language
+@emph{All email must be in English. This is the only language
 understood in common by all the maintainers.}
 
 @cindex @code{comp.lang.awk} newsgroup
@@ -37070,7 +37068,7 @@ Do @emph{not} try to report bugs in @command{gawk} by
 posting to the Usenet/Internet newsgroup @code{comp.lang.awk}.
 While the @command{gawk} developers do occasionally read this newsgroup,
 there is no guarantee that we will see your posting.  The steps described
-above are the official recognized ways for reporting bugs.
+above are the only official recognized way for reporting bugs.
 Really.
 @end quotation
 
@@ -37082,34 +37080,35 @@ bug reporting system, @emph{please} also send a copy to
 
 This is for two reasons.  First, while some distributions forward
 bug reports ``upstream'' to the GNU mailing list, many don't, so there is a good
-chance that the @command{gawk}  maintainer won't even see the bug report!  Second,
+chance that the @command{gawk}  maintainers won't even see the bug report!  Second,
 mail to the GNU list is archived, and having everything at the GNU project
-keeps things self-contained and not dependant on other web sites.
+keeps things self-contained and not dependant on other organizations.
 @end quotation
 
 Non-bug suggestions are always welcome as well.  If you have questions
 about things that are unclear in the documentation or are just obscure
-features, ask me; I will try to help you out, although I
-may not have the time to fix the problem.  You can send me electronic
-mail at the Internet address noted previously.
+features, ask on the bug list; we will try to help you out if we can.
 
-If you find bugs in one of the non-Unix ports of @command{gawk}, please send
-an electronic mail message to the person who maintains that port.  They
-are named in the following list, as well as in the @file{README} file in the @command{gawk}
-distribution.  Information in the @file{README} file should be considered
-authoritative if it conflicts with this @value{DOCUMENT}.
+If you find bugs in one of the non-Unix ports of @command{gawk}, please
+send an electronic mail message to the bug list, with a copy to the
+person who maintains that port.  They are named in the following list,
+as well as in the @file{README} file in the @command{gawk} distribution.
+Information in the @file{README} file should be considered authoritative
+if it conflicts with this @value{DOCUMENT}.
 
-The people maintaining the non-Unix ports of @command{gawk} are
-as follows:
+The people maintaining the various @command{gawk} ports are:
 
 @c put the index entries outside the table, for docbook
-@cindex Deifik, Scott
-@cindex Zaretskii, Eli
 @cindex Buening, Andreas
-@cindex Rankin, Pat
+@cindex Deifik, Scott
 @cindex Malmberg, John
 @cindex Pitts, Dave
+@cindex Rankin, Pat
+@cindex Robbins, Arnold
+@cindex Zaretskii, Eli
 @multitable {MS-Windows with MinGW} {123456789012345678901234567890123456789001234567890}
+@item Unix and POSIX systems @tab Arnold Robbins, @EMAIL{arnold@@skeeve.com,arnold at skeeve dot com}.
+
 @item MS-DOS with DJGPP @tab Scott Deifik, @EMAIL{scottd.mail@@sbcglobal.net,scottd dot mail at sbcglobal dot net}.
 
 @item MS-Windows with MinGW @tab Eli Zaretskii, @EMAIL{eliz@@gnu.org,eliz at gnu dot org}.
@@ -37262,7 +37261,7 @@ since approximately 2003.
 @item @command{pawk}
 Nelson H.F.@: Beebe at the University of Utah has modified
 BWK @command{awk} to provide timing and profiling information.
-It is different from @command{gawk} with the @option{--profile} option.
+It is different from @command{gawk} with the @option{--profile} option
 (@pxref{Profiling}),
 in that it uses CPU-based profiling, not line-count
 profiling.  You may find it at either
@@ -37287,7 +37286,7 @@ information, see the @uref{http://busybox.net, project's home page}.
 The versions of @command{awk} in @file{/usr/xpg4/bin} and
 @file{/usr/xpg6/bin} on Solaris are more-or-less POSIX-compliant.
 They are based on the @command{awk} from Mortice Kern Systems for PCs.
-This author was able to make this code compile and work under GNU/Linux
+We were able to make this code compile and work under GNU/Linux
 with 1--2 hours of work.  Making it more generally portable (using
 GNU Autoconf and/or Automake) would take more work, and this
 has not been done, at least to our knowledge.