[groff] 03/10: NEWS: Tweak formatting.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 87bf0ca06a64aa02052b587ba62e065dab77714b
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Tue Jul 11 14:17:21 2023 -0500

    NEWS: Tweak formatting.
    
    * Put a blank line after section headings.
    * Wrap lines at 72 columns per the editor aids at the end of the file.
---
 NEWS | 22 ++++++++++++----------
 1 file changed, 12 insertions(+), 10 deletions(-)

diff --git a/NEWS b/NEWS
index 8d697f3c1..410931c6e 100644
--- a/NEWS
+++ b/NEWS
@@ -12,6 +12,7 @@ VERSION next
 
 troff
 -----
+
 o In nroff mode (in other words, when producing output for terminal
   devices), the formatter now reports warning diagnostics regarding
   certain output problems using units of lines instead of inches (or the
@@ -69,16 +70,17 @@ o Spanish language input documents are now supported, 
including
   hyphenation patterns from the hyph-utf8 project and localized strings
   for the man, ms, me, mm, and mom packages.  Thanks to Eloi Monta��s.
 
-o If groff programs have their current time overridden by the SOURCE_DATE_EPOCH
-  environment variable, then that time is always displayed in UTC.  That
-  environment variable is normally only set when specifically requesting build
-  systems to produce reproducible output, and it is useful for reproducibility
-  test harnesses to vary the TZ environment variable and ensure that it does
-  not affect the output of the build; those harnesses have no way to set TZ=UTC
-  only for groff programs.  People setting SOURCE_DATE_EPOCH are likely to be
-  more in the "system programmer" camp as described in the release notes for
-  1.23.0, so it is easier to defend time-zone-invariant output to them.  In all
-  other cases, the current time remains displayed in local time.
+o If groff programs have their current time overridden by the
+  SOURCE_DATE_EPOCH environment variable, then that time is always
+  displayed in UTC.  That environment variable is normally only set when
+  specifically requesting build systems to produce reproducible output,
+  and it is useful for reproducibility test harnesses to vary the TZ
+  environment variable and ensure that it does not affect the output of
+  the build; those harnesses have no way to set TZ=UTC only for groff
+  programs.  People setting SOURCE_DATE_EPOCH are likely to be more in
+  the "system programmer" camp as described in the release notes for
+  1.23.0, so it is easier to defend time-zone-invariant output to them.
+  In all other cases, the current time remains displayed in local time.
 
 
 VERSION 1.23.0