[groff] 01/05: [docs]: Recast definition of "break".

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 06c6eaf5b2ea94e6aac4feeeae573a8cc901ae73
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Tue May 30 15:13:27 2023 -0500

    [docs]: Recast definition of "break".
---
 doc/groff.texi | 19 +++++++++----------
 man/roff.7.man |  8 ++++----
 2 files changed, 13 insertions(+), 14 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index c9c6201e5..b81194d9d 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -5158,16 +5158,15 @@ several parameters that can prevent it in certain 
circumstances.
 @cindex line break, output
 @cindex output line break
 
-Once an output line has been filled, whether or not hyphenation has
-occurred on that line, the next word read from the input will be placed
-on a different output line; this is called a @dfn{break}.  In this
-manual and in @code{roff} discussions generally, a ``break'' if not
-further qualified always refers to the termination of an output line.
-When the formatter is filling text, it introduces breaks automatically
-to keep output lines from exceeding the configured line length.  After
-an automatic break, GNU @code{troff} adjusts the line if applicable (see
-below), and then resumes collecting and filling text on the next output
-line.
+Once an output line is full, the next word (or remainder of a hyphenated
+one) is placed on a different output line; this is called a @dfn{break}.
+In this manual and in @code{roff} discussions generally, a ``break'' if
+not further qualified always refers to the termination of an output
+line.  When the formatter is filling text, it introduces breaks
+automatically to keep output lines from exceeding the configured line
+length.  After an automatic break, GNU @code{troff} adjusts the line if
+applicable (see below), and then resumes collecting and filling text on
+the next output line.
 
 Sometimes, a line cannot be broken automatically.  This usually does
 not happen with natural language text unless the output line length has
diff --git a/man/roff.7.man b/man/roff.7.man
index 2c389fbe4..846cb7562 100644
--- a/man/roff.7.man
+++ b/man/roff.7.man
@@ -256,10 +256,10 @@ in certain circumstances.
 .
 .
 .P
-Once an output line has been filled,
-whether or not hyphenation has occurred on that line,
-the next word read from the input will be placed on a different output
-line;
+Once an output line is full,
+the next word
+(or remainder of a hyphenated one)
+is placed on a different output line;
 this is called a
 .I break.
 .