aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorArnold D. Robbins <arnold@skeeve.com>2018-11-02 12:09:43 +0200
committerArnold D. Robbins <arnold@skeeve.com>2018-11-02 12:09:43 +0200
commit153ba49632aa30feaa4ad61b3d2ce2cc9c2fa441 (patch)
treed56d4e968732c789a9dc79c2f7df1a783afb5495
parentba62ad36edf69ede39194e7e970a3edc1cbe9b47 (diff)
downloadegawk-153ba49632aa30feaa4ad61b3d2ce2cc9c2fa441.tar.gz
egawk-153ba49632aa30feaa4ad61b3d2ce2cc9c2fa441.tar.bz2
egawk-153ba49632aa30feaa4ad61b3d2ce2cc9c2fa441.zip
Small doc fixes.
-rw-r--r--doc/ChangeLog7
-rw-r--r--doc/gawk.info70
-rw-r--r--doc/gawk.texi3
-rw-r--r--doc/gawktexi.in3
4 files changed, 45 insertions, 38 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog
index b0099dba..fd940c75 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,8 @@
+2018-11-02 Arnold D. Robbins <arnold@skeeve.com>
+
+ * gawktexi.in): Small typo fixes. Thanks to Antonio
+ Giovanni Colombo for pointing them out.
+
2018-10-30 Arnold D. Robbins <arnold@skeeve.com>
* gawktexi.in (Arrays of Arrays): Typo fix in code. Thanks to Alto Tom
@@ -53,7 +58,7 @@
* gawktexi.in (Two-way I/O): Fix some typos.
* gawkworkflow.texi (Configuring git): Correct some
- command usages. Thanks to Antonio Columbo for the fix.
+ command usages. Thanks to Antonio Colombo for the fix.
2018-07-31 Ralph Corderoy <ralph@inputplus.co.uk>
diff --git a/doc/gawk.info b/doc/gawk.info
index 785d71ab..3f5bca3c 100644
--- a/doc/gawk.info
+++ b/doc/gawk.info
@@ -1126,7 +1126,7 @@ in *note Sample Programs::, should be of interest.
material for those who are completely unfamiliar with computer
programming.
- The *note Glossary::, defines most, if not all, of the
+ - The *note Glossary::, defines most, if not all, of the
significant terms used throughout the Info file. If you find
terms that you aren't familiar with, try looking them up here.
@@ -29820,7 +29820,7 @@ maintainer no longer does. Thus it's virtually guaranteed that he will
_not_ see your posting.
Similarly, posting bug reports or questions in web forums (such as
-Stack Overflow (https://stackoverflow.com/)) may get you an answser, but
+Stack Overflow (https://stackoverflow.com/)) may get you an answer, but
it won't be from the 'gawk' maintainers, who do not spend their time in
web forums. The steps described here are the only officially recognized
way for reporting bugs. Really.
@@ -36660,38 +36660,38 @@ Node: VMS Old Gawk1198854
Node: Bugs1199325
Node: Bug address1199988
Node: Usenet1202970
-Node: Maintainers1203975
-Node: Other Versions1205236
-Node: Installation summary1211794
-Node: Notes1212996
-Node: Compatibility Mode1213790
-Node: Additions1214572
-Node: Accessing The Source1215497
-Node: Adding Code1216934
-Node: New Ports1223153
-Node: Derived Files1227641
-Ref: Derived Files-Footnote-11233287
-Ref: Derived Files-Footnote-21233322
-Ref: Derived Files-Footnote-31233920
-Node: Future Extensions1234034
-Node: Implementation Limitations1234692
-Node: Extension Design1235875
-Node: Old Extension Problems1237019
-Ref: Old Extension Problems-Footnote-11238537
-Node: Extension New Mechanism Goals1238594
-Ref: Extension New Mechanism Goals-Footnote-11241958
-Node: Extension Other Design Decisions1242147
-Node: Extension Future Growth1244260
-Node: Notes summary1245096
-Node: Basic Concepts1246271
-Node: Basic High Level1246952
-Ref: figure-general-flow1247234
-Ref: figure-process-flow1247919
-Ref: Basic High Level-Footnote-11251220
-Node: Basic Data Typing1251405
-Node: Glossary1254733
-Node: Copying1286571
-Node: GNU Free Documentation License1324114
-Node: Index1349234
+Node: Maintainers1203974
+Node: Other Versions1205235
+Node: Installation summary1211793
+Node: Notes1212995
+Node: Compatibility Mode1213789
+Node: Additions1214571
+Node: Accessing The Source1215496
+Node: Adding Code1216933
+Node: New Ports1223152
+Node: Derived Files1227640
+Ref: Derived Files-Footnote-11233286
+Ref: Derived Files-Footnote-21233321
+Ref: Derived Files-Footnote-31233919
+Node: Future Extensions1234033
+Node: Implementation Limitations1234691
+Node: Extension Design1235874
+Node: Old Extension Problems1237018
+Ref: Old Extension Problems-Footnote-11238536
+Node: Extension New Mechanism Goals1238593
+Ref: Extension New Mechanism Goals-Footnote-11241957
+Node: Extension Other Design Decisions1242146
+Node: Extension Future Growth1244259
+Node: Notes summary1245095
+Node: Basic Concepts1246270
+Node: Basic High Level1246951
+Ref: figure-general-flow1247233
+Ref: figure-process-flow1247918
+Ref: Basic High Level-Footnote-11251219
+Node: Basic Data Typing1251404
+Node: Glossary1254732
+Node: Copying1286570
+Node: GNU Free Documentation License1324113
+Node: Index1349233

End Tag Table
diff --git a/doc/gawk.texi b/doc/gawk.texi
index df46d3a1..e643f1ed 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -1769,6 +1769,7 @@ and some possible future directions for @command{gawk} development.
provides some very cursory background material for those who
are completely unfamiliar with computer programming.
+@item
The @ref{Glossary}, defines most, if not all, of the significant terms used
throughout the @value{DOCUMENT}. If you find terms that you aren't familiar with,
try looking them up here.
@@ -40580,7 +40581,7 @@ that he will @emph{not} see your posting.
Similarly, posting bug reports or questions in web forums (such
as @uref{https://stackoverflow.com/, Stack Overflow}) may get you
-an answser, but it won't be from the @command{gawk} maintainers,
+an answer, but it won't be from the @command{gawk} maintainers,
who do not spend their time in web forums. The steps described here are
the only officially recognized way for reporting bugs. Really.
diff --git a/doc/gawktexi.in b/doc/gawktexi.in
index 5a950afa..e7959d83 100644
--- a/doc/gawktexi.in
+++ b/doc/gawktexi.in
@@ -1736,6 +1736,7 @@ and some possible future directions for @command{gawk} development.
provides some very cursory background material for those who
are completely unfamiliar with computer programming.
+@item
The @ref{Glossary}, defines most, if not all, of the significant terms used
throughout the @value{DOCUMENT}. If you find terms that you aren't familiar with,
try looking them up here.
@@ -39554,7 +39555,7 @@ that he will @emph{not} see your posting.
Similarly, posting bug reports or questions in web forums (such
as @uref{https://stackoverflow.com/, Stack Overflow}) may get you
-an answser, but it won't be from the @command{gawk} maintainers,
+an answer, but it won't be from the @command{gawk} maintainers,
who do not spend their time in web forums. The steps described here are
the only officially recognized way for reporting bugs. Really.