Tweak and reword release notes

diff --git a/doc/notes/notes-9.16.35.rst b/doc/notes/notes-9.16.35.rst
index 2cfbf671c963942a0435e46c821cf2a6c7d4445b..8c4dc5d7455202a918c5539513ae3a5128579869 100644 (file)
--- a/doc/notes/notes-9.16.35.rst
+++ b/doc/notes/notes-9.16.35.rst
@@ -15,25 +15,29 @@ Notes for BIND 9.16.35
 Bug Fixes
 ~~~~~~~~~
 
-- The RecursClients statistics counter could overflow in certain resolution
-  scenarios. This has been fixed. :gl:`#3584`
-
-- BIND would fail to start on Solaris-based systems with hundreds of CPUs. This
-  has been fixed. ISC would like to thank Stacey Marshall from Oracle for
-  bringing this problem to our attention. :gl:`#3563`
-
-- In certain resolution scenarios quotas could be erroneously reached for
-  servers, including the configured forwarders, resulting in SERVFAIL answers
-  sent to the clients. This has been fixed. :gl:`#3598`
-
-- When having Internet connectivity issues during the initial startup of
-  ``named``, BIND resolver with ``dnssec-validation`` set to ``auto`` could
-  enter into a state where it would not recover without stopping ``named``,
-  manually deleting ``managed-keys.bind`` and ``managed-keys.bind.jnl`` files,
-  and starting ``named`` again. :gl:`#2895`
-
-- Fixed a crash that happens when you reconfigure a ``dnssec-policy``
-  zone that uses NSEC3 to enable ``inline-signing``. :gl:`#3591`
+- The statistics counter representing the current number of clients
+  awaiting recursive resolution results (``RecursClients``) could
+  overflow in certain resolution scenarios. This has been fixed.
+  :gl:`#3584`
+
+- Previously, BIND failed to start on Solaris-based systems with
+  hundreds of CPUs. This has been fixed. :gl:`#3563`
+
+- In certain resolution scenarios, quotas could be erroneously reached
+  for servers, including any configured forwarders, resulting in
+  SERVFAIL answers being sent to clients. This has been fixed.
+  :gl:`#3598`
+
+- Previously, if Internet connectivity issues were experienced during
+  the initial startup of :iscman:`named`, a BIND resolver with
+  ``dnssec-validation`` set to ``auto`` could enter into a state where
+  it would not recover without stopping :iscman:`named`, manually
+  deleting the ``managed-keys.bind`` and ``managed-keys.bind.jnl``
+  files, and starting :iscman:`named` again. This has been fixed.
+  :gl:`#2895`
+
+- A crash was fixed that happened when a ``dnssec-policy`` zone that
+  used NSEC3 was reconfigured to enable ``inline-signing``. :gl:`#3591`
 
 Known Issues
 ~~~~~~~~~~~~