Grammatical fixes in gawk manual v.3.1.8

[Peter Axon]

Got a patch file for the gawk info manual for version 3.1.8. Just some
grammatical fixes.

Following is the patch file: gawk.texi.patch

--- doc/gawk.texi       2010-04-20 18:41:01.000000000 +1000
+++ doc/gawk-new.texi   2010-12-02 13:01:52.000000000 +1100
@@ -12779,7 +12779,7 @@
 The @var{regexp} argument may be either a regexp constant
 (@samp{/@dots{}/}) or a string constant (@var{"@dots{}"}).
 In the latter case, the string is treated as a regexp to be matched.
address@hidden Regexps}, for a
+See @ref{Computed Regexps}, for a
 discussion of the difference between the two forms, and the
 implications for writing your program correctly.
 
@@ -12934,7 +12934,7 @@
 string.
 @value{DARKCORNER}
 The POSIX standard allows this as well.
address@hidden Regexps}, for a
+See @xref{Computed Regexps}, for a
 discussion of the difference between using a string constant or a regexp 
constant,
 and the implications for writing your program correctly.
 
@@ -13003,7 +13003,7 @@
 The @var{regexp} argument may be either a regexp constant
 (@samp{/@dots{}/}) or a string constant (@var{"@dots{}"}).
 In the latter case, the string is treated as a regexp to be matched.
address@hidden Regexps}, for a
+See @ref{Computed Regexps}, for a
 discussion of the difference between the two forms, and the
 implications for writing your program correctly.
 
@@ -27243,7 +27243,7 @@
 @cindex address@hidden data-driven
 @command{awk} manages the reading of data for you, as well as the
 breaking it up into records and fields.  Your program's job is to
-tell @command{awk} what to with the data.  You do this by describing
+tell @command{awk} what to do with the data.  You do this by describing
 @dfn{patterns} in the data to look for, and @dfn{actions} to execute
 when those patterns are seen.  This @dfn{data-driven} nature of
 @command{awk} programs usually makes them both easier to write