[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 14/50: [docs]: Fix content and style nits.
From: |
G. Branden Robinson |
Subject: |
[groff] 14/50: [docs]: Fix content and style nits. |
Date: |
Sat, 21 May 2022 12:17:24 -0400 (EDT) |
gbranden pushed a commit to branch master
in repository groff.
commit a2cc5648854b5207d0a2f0fd87f74052b2ceface
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Tue May 17 18:05:22 2022 -0500
[docs]: Fix content and style nits.
* It is the end of input that causes a break, not the end of a file.
* Tighten wording.
---
doc/groff.texi | 13 ++++++-------
man/roff.7.man | 5 ++---
2 files changed, 8 insertions(+), 10 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index f0898e59..e512e193 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -5373,7 +5373,7 @@ traditions have accrued in service of these goals.
@itemize @bullet
@item
-Break input lines after sentence-ending punctuation to ease their
+Follow sentence endings in input with newlines to ease their
recognition (@pxref{Sentences}). It is frequently convenient to break
after colons and semicolons as well, as these typically precede
independent clauses. Consider breaking after commas; they often occur
@@ -5556,12 +5556,11 @@ start a new one, and reset the drawing position to one
vee below the
page top again; this is a @dfn{page break}.
When the last line of input text is also the last output line that can
-fit on the page, the break caused by the end of the input file will also
-break the page, producing a useless blank one. Macro packages keep
-users from having to confront this difficulty by setting ``traps''
-(@pxref{Traps}); moreover, all but the simplest page layouts tend to
-have headers and footers, or at least bear vertical margins larger than
-one vee.
+fit on the page, the break caused by the end of input will also break
+the page, producing a useless blank one. Macro packages keep users from
+having to confront this difficulty by setting ``traps'' (@pxref{Traps});
+moreover, all but the simplest page layouts tend to have headers and
+footers, or at least bear vertical margins larger than one vee.
@codequotebacktick off
diff --git a/man/roff.7.man b/man/roff.7.man
index 82d277e2..7bf53b04 100644
--- a/man/roff.7.man
+++ b/man/roff.7.man
@@ -489,8 +489,7 @@ this is a
.P
When the last line of input text is also the last output line that can
fit on the page,
-the break caused by the end of the input file
-will also break the page,
+the break caused by the end of input will also break the page,
producing a useless blank one.
.
Macro packages keep users from having
@@ -2028,7 +2027,7 @@ Several traditions have accrued in service of these goals.
.
.
.IP \[bu] 2n
-Break input lines after sentence-ending punctuation to ease their
+Follow sentence endings in input with newlines to ease their
recognition.
.\" Texinfo: (@pxref{Sentences}).
It is frequently convenient to break after colons and semicolons as
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 14/50: [docs]: Fix content and style nits.,
G. Branden Robinson <=