gbranden pushed a commit to branch master
in repository groff.
commit 71941b196ee2382cb82bccb4ab603c21ec7c3c83
Author: G. Branden Robinson <[email protected]>
AuthorDate: Tue Apr 28 09:51:11 2026 -0500
doc/groff.texi.in: Fix style and markup nits.
* Promote an inline, backward reference out of parentheses.
* Break input lines in places convenient for roffing and diffing.
---
doc/groff.texi.in | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index ef54996ad..e346fe0f2 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -6819,13 +6819,19 @@ Several traditions have accrued in service of these
goals.
@itemize @bullet
@item
Follow sentence endings in the input with newlines to ease their
-recognition (@pxref{Sentences}). It is frequently convenient to end
-text lines after colons and semicolons as well, as these typically
-precede independent clauses. Consider doing so after commas; they often
-occur in lists that become easy to scan when itemized by line, or
-constitute supplements to the sentence that are added, deleted, or
-updated to clarify it. Parenthetical and quoted phrases are also good
-candidates for placement on text lines by themselves.
+recognition;
+recall @ref{Sentences}.
+It is frequently convenient to end text lines after colons
+and semicolons as well,
+as these typically precede independent clauses.
+Consider doing so after commas;
+they often occur in lists that become easy to scan
+when itemized by line,
+or constitute supplements to the sentence that are added,
+deleted,
+or updated to clarify it.
+Parenthetical and quoted phrases
+are also good candidates for placement on text lines by themselves.
@item
Set your text editor's line length to 72 characters or
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
