diff --git a/doc/gawk.info b/doc/gawk.info
index 877f50d..35eddeb 100644
--- a/doc/gawk.info
+++ b/doc/gawk.info
@@ -9905,7 +9905,7 @@ internal implementation of arrays and will vary from one version of
    Often, though, you may wish to do something simple, such as
 "traverse the array by comparing the indices in ascending order," or
 "traverse the array by on comparing the values in descending order."
-`gawk' provides two mechanims which give you this control.
+`gawk' provides two mechanisms which give you this control.
 
    * Set `PROCINFO["sorted_in"]' to one of a set of predefined values.
      We describe this now.
@@ -13730,7 +13730,7 @@ specific field position and can be used for this purpose:
      }
 
    The first field in each entry of the password file is the user's
-login name, and the fields are seperated by colons.  Each record
+login name, and the fields are separated by colons.  Each record
 defines a subarray, with each field as an element in the subarray.
 Running the program produces the following output:
 
@@ -20127,14 +20127,14 @@ inclusive.  Ordering was based on the numeric value of each character
 in the machine's native character set.  Thus, on ASCII-based systems,
 `[a-z]' matched all the lowercase letters, and only the lowercase
 letters, since the numeric values for the letters from `a' through `z'
-were contigous.  (On an EBCDIC system, the range `[a-z]' includes
+were contiguous.  (On an EBCDIC system, the range `[a-z]' includes
 additional, non-alphabetic characters as well.)
 
    Almost all introductory Unix literature explained range expressions
 as working in this fashion, and in particular, would teach that the
 "correct" way to match lowercase letters was with `[a-z]', and that
-`[A-Z]' was the the "correct" way to match uppercase letters.  And
-indeed, this was true.
+`[A-Z]' was the "correct" way to match uppercase letters.  And indeed,
+this was true.
 
    The 1993 POSIX standard introduced the idea of locales (*note
 Locales::).  Since many locales include other letters besides the plain
diff --git a/doc/gawk.texi b/doc/gawk.texi
index 9cd4b74..79e968f 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -13415,7 +13415,7 @@ and will vary from one version of @command{awk} to the next.
 Often, though, you may wish to do something simple, such as
 ``traverse the array by comparing the indices in ascending order,''
 or ``traverse the array by on comparing the values in descending order.''
address@hidden provides two mechanims which give you this control.
address@hidden provides two mechanisms which give you this control.
 
 @itemize @bullet
 @item
@@ -18455,7 +18455,7 @@ END @{
 @end example
 
 The first field in each entry of the password file is the user's login name,
-and the fields are seperated by colons.
+and the fields are separated by colons.
 Each record defines a subarray,
 with each field as an element in the subarray.
 Running the program produces the
@@ -27011,13 +27011,13 @@ inclusive.  Ordering was based on the numeric value of each character
 in the machine's native character set.  Thus, on ASCII-based systems,
 @code{[a-z]} matched all the lowercase letters, and only the lowercase
 letters, since the numeric values for the letters from @samp{a} through
address@hidden were contigous.  (On an EBCDIC system, the range @samp{[a-z]}
address@hidden were contiguous.  (On an EBCDIC system, the range @samp{[a-z]}
 includes additional, non-alphabetic characters as well.)
 
 Almost all introductory Unix literature explained range expressions
 as working in this fashion, and in particular, would teach that the
 ``correct'' way to match lowercase letters was with @samp{[a-z]}, and
-that @samp{[A-Z]} was the the ``correct'' way to match uppercase letters.
+that @samp{[A-Z]} was the ``correct'' way to match uppercase letters.
 And indeed, this was true.
 
 The 1993 POSIX standard introduced the idea of locales (@pxref{Locales}).