aboutsummaryrefslogtreecommitdiffstats
path: root/doc/gawktexi.in
diff options
context:
space:
mode:
authorArnold D. Robbins <arnold@skeeve.com>2015-05-16 22:51:21 +0300
committerArnold D. Robbins <arnold@skeeve.com>2015-05-16 22:51:21 +0300
commitb6963495dffd0bc11e2007b9854ad34d14b0b29c (patch)
tree5ae0816d4cb3f10f885a370e9570ab43d3c51a05 /doc/gawktexi.in
parent00f67c740d3e60bedc57b4a0481451156fe6823e (diff)
parent744df5938d55ce8b21db883a4c14730137e3db82 (diff)
downloadegawk-b6963495dffd0bc11e2007b9854ad34d14b0b29c.tar.gz
egawk-b6963495dffd0bc11e2007b9854ad34d14b0b29c.tar.bz2
egawk-b6963495dffd0bc11e2007b9854ad34d14b0b29c.zip
Merge branch 'gawk-4.1-stable'
Diffstat (limited to 'doc/gawktexi.in')
-rw-r--r--doc/gawktexi.in4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/gawktexi.in b/doc/gawktexi.in
index 2610a74b..903152d9 100644
--- a/doc/gawktexi.in
+++ b/doc/gawktexi.in
@@ -13863,8 +13863,8 @@ The current version of BWK @command{awk} and @command{mawk}
also support @code{nextfile}. However, they don't allow the
@code{nextfile} statement inside function bodies (@pxref{User-defined}).
@command{gawk} does; a @code{nextfile} inside a function body reads the
-next record and starts processing it with the first rule in the program,
-just as any other @code{nextfile} statement.
+first record from the next file and starts processing it with the first
+rule in the program, just as any other @code{nextfile} statement.
@node Exit Statement
@subsection The @code{exit} Statement