groff-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 11/23: [docs]: Tighten wording.


From: G. Branden Robinson
Subject: [groff] 11/23: [docs]: Tighten wording.
Date: Mon, 21 Mar 2022 03:44:55 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit fcd10fdfcae57fa2282b24c48e159a0e33bc26f2
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Mon Mar 21 01:58:43 2022 +1100

    [docs]: Tighten wording.
---
 doc/groff.texi | 14 +++++++-------
 man/roff.7.man |  5 ++---
 2 files changed, 9 insertions(+), 10 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index a804739b..f58ac3b6 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -5360,13 +5360,13 @@ greater code point coverage.}
 @cindex conventions for input
 
 Since GNU @code{troff} fills text automatically, it is common practice
-in @code{roff} languages to not attempt careful visual composition of
-text in input files: it is the esthetic appeal of the formatted output
-that matters.  Therefore, @code{roff} input should be arranged such that
-it is easy for authors and maintainers to compose and develop the
-document, understand the syntax of @code{roff} requests, macro calls,
-and preprocessor languages used, and predict the behavior of the
-formatter.  Several traditions have accrued in service of these goals.
+in @code{roff} languages to avoid visual composition of text in input
+files: the esthetic appeal of the formatted output is what matters.
+Therefore, @code{roff} input should be arranged such that it is easy for
+authors and maintainers to compose and develop the document, understand
+the syntax of @code{roff} requests, macro calls, and preprocessor
+languages used, and predict the behavior of the formatter.  Several
+traditions have accrued in service of these goals.
 
 @itemize @bullet
 @item
diff --git a/man/roff.7.man b/man/roff.7.man
index 11d6b224..8df8c505 100644
--- a/man/roff.7.man
+++ b/man/roff.7.man
@@ -1995,9 +1995,8 @@ Since
 fills text automatically,
 it is common practice in
 .I roff
-languages to not attempt careful visual composition of text in input
-files:
-it is the esthetic appeal of the formatted output that matters.
+languages to avoid visual composition of text in input files:
+the esthetic appeal of the formatted output is what matters.
 .
 Therefore,
 .I roff



reply via email to

[Prev in Thread] Current Thread [Next in Thread]