Tweak and reword release notes

diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst
index 6987411f95848596ef7258a5ddb52b41292ef542..a5d3204c21987858c118619a62b9ed1acc580400 100644 (file)
--- a/doc/notes/notes-current.rst
+++ b/doc/notes/notes-current.rst
@@ -24,10 +24,10 @@ Known Issues
 New Features
 ~~~~~~~~~~~~
 
-- New ``rndc`` command ``rndc dnssec -checkds`` to tell ``named``
-  that a DS record for a given zone or key has been published or withdrawn
-  from the parent. Replaces the time-based ``parent-registration-delay``
-  configuration option. [GL #1613]
+- Add a new ``rndc`` command, ``rndc dnssec -checkds``, which signals to
+  ``named`` that a DS record for a given zone or key has been published
+  or withdrawn from the parent. This command replaces the time-based
+  ``parent-registration-delay`` configuration option. [GL #1613]
 
 - Log when ``named`` adds a CDS/CDNSKEY to the zone. [GL #1748]
 
@@ -42,30 +42,32 @@ Removed Features
 Feature Changes
 ~~~~~~~~~~~~~~~
 
-- Previously, using ``dig +bufsize=0`` had the side effect of disabling EDNS,
-  and there was no way to test the remote server's behavior when it had received
-  a packet with EDNS0 buffer size set to ``0``. This is no longer the case;
-  ``dig +bufsize=0`` now sends a DNS message with EDNS version 0 and buffer size
-  set to ``0``. To disable EDNS, use ``dig +noedns``. [GL #2054]
+- Previously, using ``dig +bufsize=0`` had the side effect of disabling
+  EDNS, and there was no way to test the remote server's behavior when
+  it had received a packet with EDNS0 buffer size set to 0. This is no
+  longer the case; ``dig +bufsize=0`` now sends a DNS message with EDNS
+  version 0 and buffer size set to 0. To disable EDNS, use ``dig
+  +noedns``. [GL #2054]
 
 Bug Fixes
 ~~~~~~~~~
 
-- In rare circumstances, named would exit with assertion failure when the number
-  of nodes stored in the red-black-tree exceeds the maximum allowed size of the
-  internal hashtable.  [GL #2104]
-
-- Silence spurious system log messages for EPROTO(71) error code that has been
-  seen on older operating systems where unhandled ICMPv6 errors result in a
-  generic protocol error being returned instead of the more specific error code.
-  [GL #1928]
-
-- With query minimization enabled, named failed to resolve ip6.arpa. names
-  that had more labels before the IPv6 part. For example, when named
-  implemented query minimization on a name like
-  ``A.B.1.2.3.4.(...).ip6.arpa.``, it stopped at the left-most IPv6 label, i.e.
-  ``1.2.3.4.(...).ip6.arpa.`` without considering the extra labels ``A.B``.
-  That caused a query loop when resolving the name: if named received
-  NXDOMAIN answers, then the same query was repeatedly sent until the number
-  of queries sent reached the value in the ``max-recursion-queries``
-  configuration option. [GL #1847]
+- In rare circumstances, ``named`` would exit with an assertion failure
+  when the number of nodes stored in the red-black tree exceeded the
+  maximum allowed size of the internal hash table. [GL #2104]
+
+- Silence spurious system log messages for an EPROTO(71) error code that
+  was seen on older operating systems, where unhandled ICMPv6 errors
+  resulted in a generic protocol error being returned instead of a more
+  specific error code. [GL #1928]
+
+- With query name minimization enabled, ``named`` failed to resolve
+  ``ip6.arpa.`` names that had extra labels to the left of the IPv6
+  part. For example, when ``named`` attempted query name minimization on
+  a name like ``A.B.1.2.3.4.(...).ip6.arpa.``, it stopped at the
+  leftmost IPv6 label, i.e. ``1.2.3.4.(...).ip6.arpa.``, without
+  considering the extra labels (``A.B``). That caused a query loop when
+  resolving the name: if ``named`` received NXDOMAIN answers, then the
+  same query was repeatedly sent until the number of queries sent
+  reached the value of the ``max-recursion-queries`` configuration
+  option. [GL #1847]