[groff] 02/04: Fix style nit.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 9d55caaff752e175c2998465c50eaddb2ca55c2f
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Thu Jul 16 22:02:27 2020 +1000

    Fix style nit.
    
    groff documentation seems to prefer "name space" over "namespace", and
    most occurrences of the latter are my doing, so replace them with the
    former.
---
 doc/groff.texi       | 8 ++++----
 man/groff_diff.7.man | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index 840ff58..ae34cec 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -9535,7 +9535,7 @@ character).
 .class [quotes] ' \[rs] \[dq] \[oq] \[cq] \[lq] \[rq]
 @endExample
 
-Since class and glyph names share the same namespace, it is recommended
+Since class and glyph names share the same name space, it is recommended
 to start and end the class name with @code{[} and @code{]},
 respectively, to avoid collisions with existing character names defined
 by GNU @code{troff} or the user (with @code{char} and related requests).
@@ -14489,9 +14489,9 @@ 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 namespace of @acronym{AT&T} @code{troff} is confining and
+register name space of @acronym{AT&T} @code{troff} is confining and
 mnemonically challenging; you may wish to use the more capacious
-namespace of GNU @code{troff}.  However, attempting @samp{.nr
+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
@@ -14512,7 +14512,7 @@ at the beginning of your file, followed by
 
 @noindent
 at the end.  As in the C language, we all have to share one big
-namespace, so choose a register name that is unlikely to collide with
+name space, so choose a register name that is unlikely to collide with
 other uses.
 
 @endDefreq
diff --git a/man/groff_diff.7.man b/man/groff_diff.7.man
index 30d9e5d..cd01ecc 100644
--- a/man/groff_diff.7.man
+++ b/man/groff_diff.7.man
@@ -1429,7 +1429,7 @@ is a character
 .RE
 .
 .IP
-Since class and glyph names share the same namespace,
+Since class and glyph names share the same name space,
 it is recommended to start and end the class name with
 .RB \[lq] [ \[rq]
 and
@@ -4426,12 +4426,12 @@ layers of inclusion.
 You cannot use the same register name everywhere or you risk
 \[lq]clobbering\[rq] the value from a preceding or enclosing context.
 .
-The two-character register namespace of
+The two-character register name space of
 .RI AT&T\~ troff
 is confining and mnemonically challenging;
 you may wish to use
 .IR groff 's
-more capacious namespace.
+more capacious name space.
 .
 However,
 attempting
@@ -4468,7 +4468,7 @@ followed by
 at the end.
 .
 As in the C language,
-we all have to share one big namespace,
+we all have to share one big name space,
 so choose a register name that is unlikely to collide with other uses.
 .
 .P