[groff] 08/46: [docs]: Sync "Registers" and "Strings" sections.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 1e39a21c46aff535777411d44998cf4c98794952
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Fri Dec 2 02:49:36 2022 -0600

    [docs]: Sync "Registers" and "Strings" sections.
    
    ...between our Texinfo manual and groff(7).
---
 doc/groff.texi  | 11 +++++++----
 man/groff.7.man | 30 +++++++++++++++++++-----------
 2 files changed, 26 insertions(+), 15 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index cad2afd71..9eccfefb6 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -7259,13 +7259,15 @@ the call of its end macro.
 
 @c =====================================================================
 
+@c BEGIN Keep (roughly) parallel with subsection "Registers" of
+@c groff(7).
 @node Registers, Manipulating Filling and Adjustment, Formatter Instructions, 
gtroff Reference
 @section Registers
 @cindex registers
 
-Numeric variables in GNU @code{troff} are called @dfn{registers}.  Many
-built-in registers exist, supplying anything from the date to details of
-formatting parameters.  You can also define your own.
+In the @code{roff} language, numbers can be stored in @dfn{registers}.
+Many built-in registers exist, supplying anything from the date to
+details of formatting parameters.  You can also define your own.
 @xref{Identifiers}, for information on constructing a valid name for a
 register.
 
@@ -7420,6 +7422,7 @@ suppression of warnings.
 To remove a register alias, call @code{rr} on its name.  A register's
 contents do not become inaccessible until it has no more names.
 @endDefreq
+@c END Keep (roughly) parallel with subsection "Registers" of groff(7).
 
 @c ---------------------------------------------------------------------
 
@@ -11998,7 +12001,7 @@ string-valued register @samp{.M}; it is associated with 
the environment
 @section Strings
 @cindex strings
 
-GNU @code{troff} has string variables primarily for user convenience.
+GNU @code{troff} supports strings primarily for user convenience.
 Conventionally, if a macro definition needs only to interpolate text,
 without invoking any requests or calling any other macros, a string is
 defined instead.  Only one string is predefined by the language.
diff --git a/man/groff.7.man b/man/groff.7.man
index 83d851496..5aebe5ff5 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -5149,20 +5149,27 @@ the effect of a newline.
 .SH Registers
 .\" ====================================================================
 .
-Most registers store numeric values
-(see section \[lq]Numeric expressions\[rq] above),
-but some interpolate text;
-see subsection \[lq]Read-only registers\[rq] below.
+.\" BEGIN Keep (roughly) parallel with groff.texi node "Registers".
+In the
+.I roff
+language,
+numbers can be stored in
+.I registers.
 .
-Each register has a name.
+Many built-in registers exist,
+supplying anything from the date to details of formatting parameters.
 .
-A register is defined and assigned with the
-.request .nr
+You can also define your own.
+.
+See section \[lq]Identifiers\[rq] above for information on constructing
+a valid name for a register.
+.
+.
+.P
+Define registers and update their values with the
+.B nr
 request or the
-.esc R
-escape sequence;
-its value is interpolated with the
-.esc n
+.B \[rs]R
 escape sequence.
 .
 .
@@ -5207,6 +5214,7 @@ Bear in mind that the symbols
 are
 .I not
 part of the register name.
+.\" END Keep (roughly) parallel with groff.texi node "Registers".
 .
 .
 .\" ====================================================================