Re: Grammatical fixes in gawk manual v.3.1.8

[Peter Axon]

Thanks to the advice of Ralf and Karl here is a resubmission of the
previously posted patch.

The first two hunks change @ref to @xref so that `See' appears in the
output which makes the sentences start correctly.

The second hunk is the insertion of a missing word.

Hope this is some help.

== Patch Follows ==

--- gawk.texi.orig      Tue Apr 20 18:41:01 2010
+++ gawk.texi   Fri Dec  3 10:03:12 2010
@@ -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
address@hidden Regexps}, for a
 discussion of the difference between the two forms, 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
address@hidden 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