[groff] 11/47: [docs]: Make slight clarification.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit f8f4e8ea07ab55fa41e2576e452b50b63d10937a
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Wed Jan 5 21:23:54 2022 +1100

    [docs]: Make slight clarification.
---
 doc/groff.texi       | 24 ++++++++++++------------
 man/groff_diff.7.man |  2 +-
 2 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index 6313e60d..03d60327 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -468,7 +468,7 @@ developing GNU and promoting software freedom.''
 @title groff
 @subtitle The GNU implementation of @code{troff}
 @subtitle Edition 1.23.0
-@subtitle November 2021
+@subtitle January 2022
 @author by Trent A.@tie{}Fisher
 @author and Werner Lemberg
 
@@ -15929,17 +15929,17 @@ When writing macro packages or documents that use GNU 
@code{troff}
 features and which may be mixed with other packages or documents that do
 not---common scenarios include serial processing of man pages or use of
 the @code{so} or @code{mso} requests---you may desire correct operation
-regardless of compatibility mode in the surrounding context.  It may
-occur to you to save the existing value of @samp{\n(.C} into a register,
-say, @samp{_C}, at the beginning of your file, turn compatibility mode
-off with @samp{.cp 0}, then restore it from that register at the end
-with @samp{.cp \n(_C}.  At the same time, a modular design of a document
-or macro package may lead you to multiple layers of inclusion.  You
-cannot use the same register name everywhere or you risk ``clobbering''
-the value from a preceding or enclosing context.  The two-character
-register name space of @acronym{AT&T} @code{troff} is confining and
-mnemonically challenging; you may wish to use the more capacious
-name space of GNU @code{troff}.  However, attempting @samp{.nr
+regardless of compatibility mode enablement in the surrounding context.
+It may occur to you to save the existing value of @samp{\n(.C} into a
+register, say, @samp{_C}, at the beginning of your file, turn
+compatibility mode off with @samp{.cp 0}, then restore it from that
+register at the end with @samp{.cp \n(_C}.  At the same time, a modular
+design of a document or macro package may lead you to multiple layers of
+inclusion.  You cannot use the same register name everywhere or you risk
+``clobbering'' the value from a preceding or enclosing context.  The
+two-character register name space of @acronym{AT&T} @code{troff} is
+confining and mnemonically challenging; you may wish to use the more
+capacious name space of GNU @code{troff}.  However, attempting @samp{.nr
 _my_saved_C \n(.C} will not work in compatibility mode; the register
 name is too long.  ``This is exactly what @code{do} is for,'' you think,
 @samp{.do nr _my_saved_C \n(.C}.  The foregoing will always save zero to
diff --git a/man/groff_diff.7.man b/man/groff_diff.7.man
index dda325a0..f73683fc 100644
--- a/man/groff_diff.7.man
+++ b/man/groff_diff.7.man
@@ -4808,7 +4808,7 @@ of the
 or
 .B .mso
 requests\[em]you may desire correct operation regardless of
-compatibility mode in the surrounding context.
+compatibility mode enablement in the surrounding context.
 .
 It may occur to you to save the existing value of
 .B \[rs]n(.C