typos in the gawk manual

[Ralf Wildenhues]

Hello there,

The patch below (against the gawk-stable CVS) fixes some typos and
spacings in the gawk and gawkinet manuals.  Note the typo in the GFDL
seems not to be present in the upstream version.

Cheers,
Ralf

doc/ChangeLog:
2006-11-07  Ralf Wildenhues  <address@hidden>

        * gawk.texi: Fix some typos.
        * gawkinet.texi: Likewise.

Index: doc/gawk.texi
===================================================================
RCS file: /cvsroot/gawk/gawk-stable/doc/gawk.texi,v
retrieving revision 1.5
diff -u -r1.5 gawk.texi
--- doc/gawk.texi       15 Sep 2006 13:49:28 -0000      1.5
+++ doc/gawk.texi       8 Nov 2006 06:26:28 -0000
@@ -281,7 +281,7 @@
                                    operating systems.
 * Notes::                          Notes about @command{gawk} extensions and
                                    possible future work.
-* Basic Concepts::                 A very quick intoduction to programming
+* Basic Concepts::                 A very quick introduction to programming
                                    concepts.
 * Glossary::                       An explanation of some unfamiliar terms.
 * Copying::                        Your right to copy and distribute
@@ -930,7 +930,7 @@
 @node Names
 @section A Rose by Any Other Name
 
address@hidden @command{awk}, new vs. old
address@hidden @command{awk}, new vs.@: old
 The @command{awk} language has evolved over the years. Full details are
 provided in @ref{Language History}.
 The language described in this @value{DOCUMENT}
@@ -1559,7 +1559,7 @@
 the end of the input files.
 
 @cindex @command{awk}, uses for
address@hidden programming address@hidden data-driven vs. procedural
address@hidden programming address@hidden data-driven vs.@: procedural
 @cindex @command{awk} programs
 Programs in @command{awk} are different from programs in most other languages,
 because @command{awk} programs are @dfn{data-driven}; that is, you describe
@@ -1926,8 +1926,8 @@
 when reading it at a later time.
 
 @cindex quoting
address@hidden single quote (@code{'}), vs. apostrophe
address@hidden @code{'} (single quote), vs. apostrophe
address@hidden single quote (@code{'}), vs.@: apostrophe
address@hidden @code{'} (single quote), vs.@: apostrophe
 @strong{Caution:} As mentioned in
 @ref{One-shot},
 you can enclose small to medium programs in single quotes, in order to keep
@@ -3663,7 +3663,7 @@
 ASCII characters, which also provides a number of characters suitable
 for use with European languages.
 
-As of @command{gawk} 3.1.4, the case equivalencies are fully
+As of @command{gawk} 3.1.4, the case equivalences are fully
 locale-aware.  They are based on the C @code{<ctype.h>} facilities,
 such as @code{isalpha()} and @code{toupper()}.
 
@@ -3751,7 +3751,7 @@
 on the right.  This is true of any string-valued expression (such as
 @code{digits_regexp}, shown previously), not just string constants.
 
address@hidden regexp constants, slashes vs. quotes
address@hidden regexp constants, slashes vs.@: quotes
 @cindex @code{\} (backslash), regexp constants
 @cindex backslash (@code{\}), regexp constants
 @cindex @code{"} (double quote), regexp constants
@@ -3767,9 +3767,9 @@
 second one so that the string actually contains the
 two characters @samp{\} and @samp{*}.
 
address@hidden troubleshooting, regexp constants vs. string constants
address@hidden regexp constants, vs. string constants
address@hidden string constants, vs. regexp constants
address@hidden troubleshooting, regexp constants vs.@: string constants
address@hidden regexp constants, vs.@: string constants
address@hidden string constants, vs.@: regexp constants
 Given that you can use both regexp and string constants to describe
 regular expressions, which should you use?  The answer is ``regexp
 constants,'' for several reasons:
@@ -4840,7 +4840,7 @@
 separator occurs when processing the Unix system password file.
 On many Unix systems, each user has a separate entry in the system password
 file, one line per user.  The information in these lines is separated
-by colons.  The first field is the user's logon name and the second is
+by colons.  The first field is the user's login name and the second is
 the user's (encrypted or shadow) password.  A password file entry might look
 like this:
 
@@ -5185,7 +5185,7 @@
 Another way to separate fields is to
 put each field on a separate line: to do this, just set the
 variable @code{FS} to the string @code{"\n"}.  (This single
-character seperator matches a single newline.)
+character separator matches a single newline.)
 A practical example of a @value{DF} organized this way might be a mailing
 list, where each entry is separated by blank lines.  Consider a mailing
 list in a file named @file{addresses}, which looks like this:
@@ -6220,7 +6220,7 @@
 @cindex @command{gawk}, format-control characters
 @quotation NOTE
 When using the integer format-control letters for values that are
-outside the range of the widest C integer type, @command{gawk} switches to the
+outside the range of the widest C integer type, @command{gawk} switches to
 the @samp{%g} format specifier. If @option{--lint} is provided on the
 command line (@pxref{Options}), @command{gawk}
 warns about this.  Other versions of @command{awk} may print invalid
@@ -6313,7 +6313,7 @@
 value to print.
 
 @item '
-A single quote or apostrohe character is a POSIX extension to ISO C.
+A single quote or apostrophe character is a POSIX extension to ISO C.
 It indicates that the integer part of a floating point value, or the
 entire part of an integer decimal value, should have a thousands-separator
 character in it.  This only works in locales that support such characters.
@@ -7767,8 +7767,8 @@
 
 @cindex POSIX @command{awk}, @code{OFMT} variable and
 @cindex @code{OFMT} variable
address@hidden portability, new @command{awk} vs. old @command{awk}
address@hidden @command{awk}, new vs. old, @code{OFMT} variable
address@hidden portability, new @command{awk} vs.@: old @command{awk}
address@hidden @command{awk}, new vs.@: old, @code{OFMT} variable
 Prior to the POSIX standard, @command{awk} used the value
 of @code{OFMT} for converting numbers to strings.  @code{OFMT}
 specifies the output format to use when printing numbers with @code{print}.
@@ -8726,9 +8726,9 @@
 @print{} false
 @end example
 
address@hidden comparison expressions, string vs. regexp
address@hidden @cindex string comparison vs. regexp comparison
address@hidden @cindex regexp comparison vs. string comparison
address@hidden comparison expressions, string vs.@: regexp
address@hidden @cindex string comparison vs.@: regexp comparison
address@hidden @cindex regexp comparison vs.@: string comparison
 @noindent
 the result is @samp{false} because both @code{$1} and @code{$2}
 are user input.  They are numeric strings---therefore both have
@@ -12705,7 +12705,7 @@
 default is to use and alter @address@hidden that this means
 that the record will first be regenerated using the value of @code{OFS} if
 any fields have been changed, and that the fields will be updated
-after the substituion, even if the operation is a ``no-op'' such
+after the substitution, even if the operation is a ``no-op'' such
 as @samp{sub(/^/, "")}.}
 For example:
 
@@ -13118,7 +13118,7 @@
 @ref{table-sub-proposed}.
 
 @float Table,table-sub-proposed
address@hidden rules for sub and backslash}
address@hidden rules for sub and backslash}
 @tex
 \vbox{\bigskip
 % This table has lots of &'s and \'s, so unspecialize them.
@@ -13431,7 +13431,7 @@
 @c fakenode --- for prepinfo
 @subheading Advanced Notes: Interactive Versus Noninteractive Buffering
 @cindex advanced features, buffering
address@hidden buffering, interactive vs. noninteractive
address@hidden buffering, interactive vs.@: noninteractive
 
 As a side point, buffering issues can be even more confusing, depending
 upon whether your program is @dfn{interactive}, i.e., communicating
@@ -15247,7 +15247,7 @@
 at runtime,
 it cannot change the argument order in the call to @code{printf}.
 
-To solve this problem, @code{printf} format specificiers may have
+To solve this problem, @code{printf} format specifiers may have
 an additional optional element, which we call a @dfn{positional specifier}.
 For example:
 
@@ -15287,7 +15287,7 @@
 @quotation NOTE
 When using @samp{*} with a positional specifier, the @samp{*}
 comes first, then the integer position, and then the @samp{$}.
-This is somewhat counterintutive.
+This is somewhat counterintuitive.
 @end quotation
 
 @cindex @code{printf} statement, positional specifiers, mixing with regular 
formats
@@ -17308,7 +17308,7 @@
 
 @cindex @code{nextfile} user-defined function
 This initial version has a subtle problem.
-If the same @value{DF} is listed @emph{twice} on the commandline,
+If the same @value{DF} is listed @emph{twice} on the command line,
 one right after the other
 or even with just a variable assignment between them,
 this code skips right through the file a second time, even though
@@ -17468,7 +17468,7 @@
 the correct numeric value for each hexadecimal digit.
 
 Finally, if the string matches the (rather complicated) regex for a
-regular decimal integer or floating-point numer, the computation
+regular decimal integer or floating-point number, the computation
 @samp{ret = str + 0} lets @command{awk} convert the value to a
 number.
 
@@ -17682,7 +17682,7 @@
 @cindex functions, library, Cliff random numbers
 
 The Cliff random number
address@hidden@uref{http://mathworld.wolfram.com/CliffRandomNumberGenerator.hmtl}}
address@hidden@uref{http://mathworld.wolfram.com/CliffRandomNumberGenerator.html}}
 is a very simple random number generator that ``passes the noise sphere test
 for randomness by showing no structure.''
 It is easily programmed, in less than 10 lines of @command{awk} code:
@@ -19239,7 +19239,7 @@
 we cast it to @code{long} for all cases.)
 
 @item Group Member List
-A comma-separated list of usernames.  These users are members of the group.
+A comma-separated list of user names.  These users are members of the group.
 Modern Unix systems allow users to be members of several groups
 simultaneously.  If your system does, then there are elements
 @code{"group1"} through @code{"address@hidden"} in @code{PROCINFO}
@@ -19259,7 +19259,7 @@
 The group's numeric group ID number; this number should be unique within the 
file.
 
 @item Group member list @tab
-A comma-separated list of usernames.  These users are members of the group.
+A comma-separated list of user names.  These users are members of the group.
 Modern Unix systems allow users to be members of several groups
 simultaneously.  If your system does, then there are elements
 @code{"group1"} through @code{"address@hidden"} in @code{PROCINFO}
@@ -19369,7 +19369,7 @@
 The group information is stored is several associative arrays.
 The arrays are indexed by group name (@address@hidden), by group ID number
 (@address@hidden), and by position in the database (@address@hidden).
-There is an additional array indexed by username (@address@hidden),
+There is an additional array indexed by user name (@address@hidden),
 which is a space-separated list of groups to which each user belongs.
 
 Unlike the user database, it is possible to have multiple records in the
@@ -19382,7 +19382,7 @@
 @end example
 
 For this reason, @code{_gr_init} looks to see if a group name or
-group ID number is already seen.  If it is, then the usernames are
+group ID number is already seen.  If it is, then the user names are
 simply concatenated onto the previous list of users.  (There is actually a
 subtle problem with the code just presented.  Suppose that
 the first time there were no names. This code adds the names with
@@ -19430,7 +19430,7 @@
 
 @cindex @code{getgruser} function (C library)
 The @code{getgruser} function does not have a C counterpart. It takes a
-username and returns the list of groups that have the user as a member:
+user name and returns the list of groups that have the user as a member:
 
 @cindex @code{getgruser} function, user-defined
 @example
@@ -22337,7 +22337,7 @@
     shift
 fi
 
-# A literal newline, so that program text is formmatted correctly
+# A literal newline, so that program text is formatted correctly
 n='
 '
 
@@ -23019,7 +23019,7 @@
 @appendixsec Extensions in @command{gawk} Not in POSIX @command{awk}
 
 @ignore
-I've tried to follow this general order, esp. for the 3.0 and 3.1 sections:
+I've tried to follow this general order, esp.@: for the 3.0 and 3.1 sections:
        variables
        special files
        language changes (e.g., hex constants)
@@ -28403,7 +28403,7 @@
 translations of some or all Invariant Sections in addition to the
 original versions of these Invariant Sections.  You may include a
 translation of this License, and all the license notices in the
-Document, and any Warrany Disclaimers, provided that you also include
+Document, and any Warranty Disclaimers, provided that you also include
 the original English version of this License and the original versions
 of those notices and disclaimers.  In case of a disagreement between
 the translation and the original version of this License or a notice
Index: doc/gawkinet.texi
===================================================================
RCS file: /cvsroot/gawk/gawk-stable/doc/gawkinet.texi,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 gawkinet.texi
--- doc/gawkinet.texi   11 Aug 2006 12:05:48 -0000      1.1.1.1
+++ doc/gawkinet.texi   8 Nov 2006 06:26:29 -0000
@@ -152,7 +152,7 @@
 
 @menu
 * Preface::                          About this document.
-* Introduction::                     About networkiing.
+* Introduction::                     About networking.
 * Using Networking::                 Some examples.
 * Some Applications and Techniques:: More extended examples.
 * Links::                            Where to find the stuff mentioned in this
@@ -240,7 +240,7 @@
 @node Introduction, Using Networking, Preface, Top
 @chapter Networking Concepts
 
-This @value{CHAPTER} provides a (necessarily) brief intoduction to
+This @value{CHAPTER} provides a (necessarily) brief introduction to
 computer networking concepts.  For many applications of @command{gawk}
 to TCP/IP networking, we hope that this is enough.  For more
 advanced tasks, you will need deeper background, and it may be necessary
@@ -1008,7 +1008,7 @@
 @ignore
 @multitable {1234567890123} {1234567890123} 
{123456789012345678901234567890123456789012}
 @item Service @strong{name} @tab Service @strong{number}
address@hidden echo @tab 7/tcp @tab echo sends back each line it receivces
address@hidden echo @tab 7/tcp @tab echo sends back each line it receives
 @item echo @tab 7/udp @tab echo is good for testing purposes
 @item discard @tab 9/tcp @tab discard behaves like @file{/dev/null}
 @item discard @tab 9/udp @tab discard just throws away each line
@@ -1071,7 +1071,7 @@
 flavor of Microsoft Windows usually do @emph{not} support these services.
 Nevertheless, it @emph{is} possible to do networking with @command{gawk} on
 Microsoft
address@hidden prefered to ignore the TCP/IP
address@hidden preferred to ignore the TCP/IP
 family of protocols until 1995. Then came the rise of the Netscape browser
 as a landmark ``killer application.'' Microsoft added TCP/IP support and
 their own browser to Microsoft Windows 95 at the last minute. They even 
back-ported
@@ -4476,7 +4476,7 @@
 can ignore. Then there are some comments about the query having been
 filtered to avoid spuriously high scores. After this, there is a reference
 to the paper that describes the software being used for searching the data
-base. After a repitition of the original query's description we find the
+base. After a repetition of the original query's description we find the
 list of significant alignments:
 
 @smallexample
@@ -4497,7 +4497,7 @@
 But the value 0.20 (20%) means that the probability of an accidental match
 is rather high (20%) in all cases and should be taken into account.
 You may wonder what the first column means. It is a key to the specific
-database in which this occurence was found.  The unique sequence identifiers
+database in which this occurrence was found.  The unique sequence identifiers
 reported in the search results can be used as sequence retrieval keys
 via the NCBI server. The syntax of sequence header lines used by the NCBI
 BLAST server depends on the database from which each sequence was obtained.
@@ -4581,7 +4581,7 @@
 
 @item
 While Waterman's book can explain to you the algorithms employed internally
-in the database search engines, most practicioners prefer to approach
+in the database search engines, most practitioners prefer to approach
 the subject differently. The applied side of Computational Biology is
 called Bioinformatics, and emphasizes the tools available for day-to-day
 work as well as how to actually @emph{use} them. One of the very few affordable
@@ -5092,7 +5092,7 @@
 translations of some or all Invariant Sections in addition to the
 original versions of these Invariant Sections.  You may include a
 translation of this License, and all the license notices in the
-Document, and any Warrany Disclaimers, provided that you also include
+Document, and any Warranty Disclaimers, provided that you also include
 the original English version of this License and the original versions
 of those notices and disclaimers.  In case of a disagreement between
 the translation and the original version of this License or a notice