gbranden pushed a commit to branch master
in repository groff.

commit 8465cde3972f52a96637d991343b96d13cf3a431
Author: G. Branden Robinson <[email protected]>
AuthorDate: Mon Apr 13 13:47:20 2026 -0500

    [doc,man]: Favor present tense over future.
---
 doc/groff.texi.in    | 40 +++++++++++++++++++++++++++++-----------
 man/groff_diff.7.man | 18 +++++++++++-------
 2 files changed, 40 insertions(+), 18 deletions(-)

diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index 9b5456589..cfe962c13 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -13543,8 +13543,11 @@ Initially, no characters have this property.
 
 In contrast to values 2 and@tie{}4, the values 128, 256, and 512 work
 pairwise.  If, for example, the left character has value 512, and the
-right character 128, no break will be automatically inserted between
-them.  If we use value@tie{}6 instead for the left character, a break
+right character 128,
+GNU
+@command{troff} @c GNU
+does not insert a break between them.
+If we use value@tie{}6 instead for the left character, a break
 after the character can't be suppressed since the neighboring character
 on the right doesn't get examined.
 @endDefreq
@@ -15666,11 +15669,23 @@ request.
 @cindex uppercasing a string (@code{stringup})
 @cindex lowercasing a string (@code{stringdown})
 @cindex down-casing a string (@code{stringdown})
-Alter the string named @var{str} by replacing each of its bytes with its
-lowercase (@code{stringdown}) or uppercase (@code{stringup}) version (if
-one exists).  Special characters in the string will often transform in
-the expected way due to the regular naming convention for accented
-characters.  When they do not, use substrings and/or catenation.
+Alter the string named
+@var{str}
+by replacing each of its bytes with its
+lowercase
+(@code{stringdown})
+or uppercase
+(@code{stringup})
+version
+(if one exists).
+GNU
+@command{troff}'s @c GNU
+built-in special characters often transform in the expected way
+due to the regular naming convention
+for accented characters.@footnote{See
+@cite{groff_char@r{(7)}.}}
+When they do not,
+use substrings and/or catenation.
 
 @Example
 .ds resume R\['e]sum\['e]\"
@@ -17122,10 +17137,13 @@ use @code{\E} to keep @samp{..} from ending a macro 
definition
 prematurely.  If the multiplicity of backslashes complicates
 maintenance, use end macros.
 
-@code{\E} is also convenient to define strings containing escape
-sequences that need to work when used in copy mode (for example, as
-macro arguments), or which will be interpolated at varying macro nesting
-depths.  We might define strings to begin and end superscripting
+@code{\E}
+is also convenient to define strings containing escape sequences that
+need to work when used in copy mode
+(for example,
+as macro arguments),
+or that are interpolated at varying macro nesting depths.
+We might define strings to begin and end superscripting
 as follows.@footnote{These are lightly adapted from the @code{groff}
 implementation of the @file{ms} macros.}
 
diff --git a/man/groff_diff.7.man b/man/groff_diff.7.man
index a59b80709..1fb1f48ca 100644
--- a/man/groff_diff.7.man
+++ b/man/groff_diff.7.man
@@ -549,7 +549,9 @@ If,
 for example,
 the left character has value 512,
 and the right character 128,
-no break will be automatically inserted between them.
+GNU
+.I troff \" GNU
+does not insert a break between them.
 .
 If we use value\~6 instead for the left character,
 a break after the character can't be suppressed since the neighboring
@@ -1224,7 +1226,7 @@ It is also convenient to define strings containing escape 
sequences that
 need to work when used in copy mode
 (for example,
 as macro arguments),
-or that will be interpolated at varying macro nesting depths.
+or that are interpolated at varying macro nesting depths.
 .
 .
 .TP
@@ -4493,11 +4495,13 @@ or uppercase
 version
 (if one exists).
 .
-Special characters
-(see
-.MR groff_char @MAN7EXT@ )
-will often transform in the expected way due to the regular naming
-convention for accented characters.
+GNU
+.IR troff 's \" GNU
+built-in special characters often transform in the expected way
+due to the regular naming convention for accented characters.
+.
+See
+.MR groff_char @MAN7EXT@ .
 .
 When they do not,
 use substrings and/or catenation.

_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit

Reply via email to