[groff] 04/09: doc/groff.texi: Fix omission.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 59ce7aada0da48baf9489a7907abfeba1750bbfc
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Mon Aug 9 19:22:29 2021 +1000

    doc/groff.texi: Fix omission.
    
    My deliberate sacrifice of a hostage to fortune in commit 85f96663, 31
    July, had the desired effect, forcing my brain to disgorge a
    counterexample to the generalization I made.
    
    (Translation: a control character is also recognized in the first
    argument to the `nop` request.)
---
 doc/groff.texi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index dfb369d..a54390b 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -4937,9 +4937,9 @@ languages, with an exception already noted several times 
in passing.
 A @dfn{request} is an instruction to the formatter that occurs after a
 control character.  A @dfn{control character} must occur at the
 beginning of an input line to be recognized.@footnote{A control
-character is also expected in arguments to the @code{if}, @code{ie},
-@code{el}, and @code{while} requests.}  The regular control character
-has a counterpart, the @dfn{no-break control character}, which
+character can also occur in arguments to @code{if}, @code{ie},
+@code{el}, @code{nop}, and @code{while} requests.}  The regular control
+character has a counterpart, the @dfn{no-break control character}, which
 suppresses the break that is implied by some requests.  The default
 control characters are the dot (@code{.}) and the neutral apostrophe
 (@code{'}), the latter being the no-break control character.  These