aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/ChangeLog1
-rw-r--r--doc/gawkinet.info14
-rw-r--r--doc/gawkinet.texi2
3 files changed, 9 insertions, 8 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog
index 042f28f8..89b39459 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -3,6 +3,7 @@
* gawktexi.in: Fix a spelling error.
* wordlist, wordlist2, wordlist3: Remove words that spell
now recognizes as real words.
+ * gawkinet.texi: Fix a spelling error.
2020-09-18 Arnold D. Robbins <arnold@skeeve.com>
diff --git a/doc/gawkinet.info b/doc/gawkinet.info
index 4de7cf0a..626048fa 100644
--- a/doc/gawkinet.info
+++ b/doc/gawkinet.info
@@ -2894,7 +2894,7 @@ variables. The following conventions are used:
Now it's clear what happens to the 'Label' parameter of the function
'migrate()'. It is copied into 'MOBVAR["Label"]' and travels alongside
-the other data. Since travelling takes place via HTTP, records must be
+the other data. Since traveling takes place via HTTP, records must be
separated with '"\r\n"' in 'RS' and 'ORS' as usual. The code assembly
for migration takes place in three steps:
@@ -4394,12 +4394,12 @@ Node: STATIST104830
Ref: STATIST-Footnote-1117982
Node: MAZE118427
Node: MOBAGWHO124634
-Ref: MOBAGWHO-Footnote-1138652
-Node: STOXPRED138707
-Node: PROTBASE152995
-Node: Links166111
-Node: GNU Free Documentation License169544
-Node: Index194664
+Ref: MOBAGWHO-Footnote-1138651
+Node: STOXPRED138706
+Node: PROTBASE152994
+Node: Links166110
+Node: GNU Free Documentation License169543
+Node: Index194663

End Tag Table
diff --git a/doc/gawkinet.texi b/doc/gawkinet.texi
index 91c222be..2bb22d93 100644
--- a/doc/gawkinet.texi
+++ b/doc/gawkinet.texi
@@ -3507,7 +3507,7 @@ takes part in migration has to be an element of this array.
Now it's clear what happens to the @code{Label} parameter of the
function @code{migrate()}. It is copied into @code{MOBVAR["Label"]} and
-travels alongside the other data. Since travelling takes place via HTTP,
+travels alongside the other data. Since traveling takes place via HTTP,
records must be separated with @code{"\r\n"} in @code{RS} and
@code{ORS} as usual. The code assembly for migration takes place in
three steps: