Tweak and reword release notes

diff --git a/doc/notes/notes-9.16.3.rst b/doc/notes/notes-9.16.3.rst
index ae2f353f8f1ed1b72113363900c3444527aa3091..92d18cc647b14cb122689870cdfec928db3f1b05 100644 (file)
--- a/doc/notes/notes-9.16.3.rst
+++ b/doc/notes/notes-9.16.3.rst
@@ -14,15 +14,15 @@ Notes for BIND 9.16.3
 Known Issues
 ~~~~~~~~~~~~
 
--  BIND crashes on startup when linked against libuv 1.36. This issue is
-   related to recvmmsg() support in libuv which was first included in
-   libuv 1.35. The problem was addressed in libuv 1.37, but the relevant
-   libuv code change requires a special flag to be set during library
-   initialization in order for recvmmsg() support to be enabled. This
-   BIND release sets that special flag when required, so recvmmsg()
-   support is now enabled when BIND is compiled against either libuv
-   1.35 or libuv >= 1.37; libuv 1.36 is still not usable with BIND. [GL
-   #1761] [GL #1797]
+-  BIND crashes on startup when linked against libuv 1.36. This issue
+   is related to ``recvmmsg()`` support in libuv, which was first
+   included in libuv 1.35. The problem was addressed in libuv 1.37, but
+   the relevant libuv code change requires a special flag to be set
+   during library initialization in order for ``recvmmsg()`` support to
+   be enabled. This BIND release sets that special flag when required,
+   so ``recvmmsg()`` support is now enabled when BIND is compiled
+   against either libuv 1.35 or libuv 1.37+; libuv 1.36 is still not
+   usable with BIND. [GL #1761] [GL #1797]
 
 Feature Changes
 ~~~~~~~~~~~~~~~
@@ -63,8 +63,8 @@ Bug Fixes
 
 -  When running on a system with support for Linux capabilities,
    ``named`` drops root privileges very soon after system startup. This
-   was causing a spurious log message, "unable to set effective uid to
-   0: Operation not permitted", which has now been silenced. [GL #1042]
+   was causing a spurious log message, ``unable to set effective uid to
+   0: Operation not permitted``, which has now been silenced. [GL #1042]
    [GL #1090]
 
 -  When ``named-checkconf`` was run, it would sometimes incorrectly set

diff --git a/doc/notes/notes-9.16.4.rst b/doc/notes/notes-9.16.4.rst
index 4b7955a769a4c521a846fba07c24885c9c915760..748633a4bf8385cd5ea6b99e457cd27d0370f7c2 100644 (file)
--- a/doc/notes/notes-9.16.4.rst
+++ b/doc/notes/notes-9.16.4.rst
@@ -29,38 +29,39 @@ New Features
    Docs`_. Release notes are no longer available as a separate document
    accompanying a release. [GL #83]
 
--  ``named`` and ``named-checkzone`` now reject master zones that
-   have a DS RRset at the zone apex.  Attempts to add DS records
-   at the zone apex via UPDATE will be logged but otherwise ignored.
-   DS records belong in the parent zone, not at the zone apex. [GL #1798]
+-  ``named`` and ``named-checkzone`` now reject master zones that have a
+   DS RRset at the zone apex. Attempts to add DS records at the zone
+   apex via UPDATE will be logged but otherwise ignored. DS records
+   belong in the parent zone, not at the zone apex. [GL #1798]
 
 -  ``dig`` and other tools can now print the Extended DNS Error (EDE)
-   option when it appears in a request or response. [GL #1834]
+   option when it appears in a request or a response. [GL #1835]
 
 Feature Changes
 ~~~~~~~~~~~~~~~
 
--  The default value of ``max-stale-ttl`` has changed from 1 week to 12 hours.
-   This option controls how long named retains expired RRsets in cache as a
-   potential mitigation mechanism, should there be a problem with one or more
-   domains.  Note that cache content retention is independent of whether or not
-   stale answers will be used in response to client queries
-   (``stale-answer-enable yes|no`` and ``rndc serve-stale on|off``).  Serving of
-   stale answers when the authoritative servers are not responding must be
-   explicitly enabled, whereas the retention of expired cache content takes
-   place automatically on all versions of BIND that have this feature available.
-   [GL #1877]
-
-   .. warning:
-       This change may be significant for administrators who expect that stale
-       cache content will be automatically retained for up to 1 week.  Add
-       option ``max-stale-ttl 1w;`` to named.conf to keep the previous behavior
-       of named.
-
--  listen-on-v6 { any; } creates separate sockets for all interfaces,
-   while previously it created one socket on systems conforming to
-   :rfc:`3493` and :rfc:`3542`, this change was introduced in 9.16.0
-   but accudently ommited from documentation.
+-  The default value of ``max-stale-ttl`` has changed from 1 week to 12
+   hours. This option controls how long ``named`` retains expired RRsets
+   in cache as a potential mitigation mechanism, should there be a
+   problem with one or more domains. Note that cache content retention
+   is independent of whether stale answers are used in response to
+   client queries (``stale-answer-enable yes|no`` and ``rndc serve-stale
+   on|off``). Serving of stale answers when the authoritative servers
+   are not responding must be explicitly enabled, whereas the retention
+   of expired cache content takes place automatically on all versions of
+   BIND 9 that have this feature available. [GL #1877]
+
+   .. warning::
+       This change may be significant for administrators who expect that
+       stale cache content will be automatically retained for up to 1
+       week. Add option ``max-stale-ttl 1w;`` to ``named.conf`` to keep
+       the previous behavior of ``named``.
+
+-  ``listen-on-v6 { any; }`` creates a separate socket for each
+   interface. Previously, just one socket was created on systems
+   conforming to :rfc:`3493` and :rfc:`3542`. This change was introduced
+   in BIND 9.16.0, but it was accidentally omitted from documentation.
+   [GL #1782]
 
 Bug Fixes
 ~~~~~~~~~
@@ -80,23 +81,24 @@ Bug Fixes
 -  A possible deadlock in ``lib/isc/unix/socket.c`` was fixed.
    [GL #1859]
 
--  Missing mutex and conditional destruction in netmgr code leads to a memory
-   leak on BSD systems. [GL #1893].
+-  Previously, ``named`` did not destroy some mutexes and conditional
+   variables in netmgr code, which caused a memory leak on FreeBSD. This
+   has been fixed. [GL #1893]
 
--  Fix a data race in resolver.c:formerr() that could lead to assertion
-   failure. [GL #1808]
+-  A data race in ``lib/dns/resolver.c:log_formerr()`` that could lead
+   to an assertion failure was fixed. [GL #1808]
 
 -  Previously, ``provide-ixfr no;`` failed to return up-to-date
    responses when the serial number was greater than or equal to the
    current serial number. [GL #1714]
 
--  Fix a bug in dnssec-policy keymgr where the check if a key has a
-   successor would return a false positive if any other key in the
-   keyring has a successor. [GL #1845]
+-  A bug in dnssec-policy keymgr was fixed, where the check for the
+   existence of a given key's successor would incorrectly return
+   ``true`` if any other key in the keyring had a successor. [GL #1845]
 
--  With dnssec-policy, when creating a successor key, the goal state of
-   the current active key (the predecessor) was not changed and thus was
-   never is removed from the zone. [GL #1846]
+-  With dnssec-policy, when creating a successor key, the "goal" state
+   of the current active key (the predecessor) was not changed and thus
+   never removed from the zone. [GL #1846]
 
 - ``named-checkconf -p`` could include spurious text in
   ``server-addresses`` statements due to an uninitialized DSCP value.