[groff] 16/26: NEWS: Tweak.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit df8dbb28a4901bf20f4601e2b9e9e80e8d57bc1b
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sat May 14 23:56:56 2022 -0500

    NEWS: Tweak.
    
    * Put section headings in sentence case.
    * Move Latin-1-encoded \[oq] item to a new, general "Output drivers"
      section, since it no longer applies only to grotty.
---
 NEWS | 43 +++++++++++++++++++++++--------------------
 1 file changed, 23 insertions(+), 20 deletions(-)

diff --git a/NEWS b/NEWS
index 7708e6d3..8b96af54 100644
--- a/NEWS
+++ b/NEWS
@@ -103,7 +103,7 @@ groff
 o The -I option now implies -g (run the grn(1) preprocessor), and
   supplies grn an -M option with the argument to -I.
 
-Macro Packages
+Macro packages
 --------------
 
 o English localization has been split into a dedicated macro file,
@@ -345,6 +345,24 @@ o The "safer.tmac" file has been dropped from the 
distribution.  It was
   can create an empty file of this name in groff's macro file search
   path (see troff(1)) or consider migrating to man-db man(1).
 
+Output drivers
+--------------
+
+o On output devices using the Latin-1 character encoding ("groff -T
+  latin1" and the X11 devices) the special character escape sequence
+  \[oq] (opening quote) is now rendered as code point 0x27 (apostrophe)
+  instead of 0x60 (grave accent).  The ISO 8859/ECMA-94 Latin character
+  sets do not define any glyphs for directional ("typographer's")
+  quotation marks, but the apostrophe is depicted in the defining
+  standard as a neutral (vertical) glyph, whereas the grave accent 0x60
+  and acute accent 0xB4 are mirror-symmetric diacritical marks.
+
+  This change has no effect on _input_ conventions for roff source
+  documents.  You can still get directional single quotes on UTF-8,
+  PostScript, PDF, and other output devices supporting them by typing
+  sequences like `this' in the input (character remapping with 'char'
+  requests and similar notwithstanding).
+
 gropdf
 ------
 
@@ -362,21 +380,6 @@ o A new device control command, "link", generates OSC 8 
hyperlinks.
   This means that groff documents can produce clickable links in the
   terminal window for emulators that support such escape sequences.
 
-o On output devices using the Latin-1 character encoding ("groff -T
-  latin1" and the X11 devices) the special character escape sequence
-  \[oq] (opening quote) is now rendered as code point 0x27 (apostrophe)
-  instead of 0x60 (grave accent).  The ISO 8859/ECMA-94 Latin character
-  sets do not define any glyphs for directional ("typographer's")
-  quotation marks, but the apostrophe is depicted in the defining
-  standard as a neutral (vertical) glyph, whereas the grave accent 0x60
-  and acute accent 0xB4 are mirror-symmetric diacritical marks.
-
-  This change has no effect on _input_ conventions for roff source
-  documents.  You can still get directional single quotes on UTF-8,
-  PostScript, PDF, and other output devices supporting them by typing
-  sequences like `this' in the input (character remapping with 'char'
-  requests and similar notwithstanding).
-
 o The "sgr" device control command, which dynamically configured support
   for ISO 6429/ECMA-48 SGR escape sequences (and restored traditional
   overstriking behavior if disabled), has been removed.  It took effect
@@ -442,15 +445,15 @@ o The 'configure' option --with-doc that was introduced 
in version
   formats, so in contrast to the documentation, the option not only
   affected which output formats were generated, but also restricted the
   documentation content the user would get in erratic and surprising
-  ways.  The option was also ill-designed in so far as the "examples"
+  ways.  The option was also ill-designed insofar as the "examples"
   keyword did not represent an output format.  Some example files were
   controlled by the "examples" keyword alone, some by the respective
   format keywords alone, and some by a combination of both.  The
   implementation of the option was full of bugs, but few, if any, of
   these bugs were ever reported by users, giving the impression that
-  few, if any, users ever attempted to use the option, and those who
-  did likely remained unaware that doing so deprived them of parts of
-  the content of the documentation.  Experience has demonstrated that
+  few, if any, users ever attempted to use the option, and those who did
+  likely remained unaware that doing so deprived them of parts of the
+  content of the documentation.  Experience has demonstrated that
   properly maintaining and testing the option exceeds the amount of
   effort the GNU troff team is able to invest.  Finally, GNU standards
   contain no recommendation to support this option, and indeed, few, if