Tweak and reword release notes

diff --git a/doc/notes/notes-9.16.36.rst b/doc/notes/notes-9.16.36.rst
index 7479d59b1018858d033e44b2495e62e7e3e9ae57..677ce8091f0b1896c27a0aa0ef34426f1f9f3dee 100644 (file)
--- a/doc/notes/notes-9.16.36.rst
+++ b/doc/notes/notes-9.16.36.rst
@@ -15,8 +15,9 @@ Notes for BIND 9.16.36
 Feature Changes
 ~~~~~~~~~~~~~~~
 
-- The option ``auto-dnssec`` is deprecated and will be removed in 9.19.
-  Please migrate to ``dnssec-policy``. :gl:`#3667`
+- The ``auto-dnssec`` option has been deprecated and will be removed in
+  a future BIND 9.19.x release. Please migrate to ``dnssec-policy``.
+  :gl:`#3667`
 
 Bug Fixes
 ~~~~~~~~~
@@ -26,18 +27,19 @@ Bug Fixes
   :iscman:`named-checkzone` tool from superfluously logging this message
   in non-debug mode. :gl:`#3707`
 
-- When a catalog zone is removed from the configuration, in some
-  cases a dangling pointer could cause a :iscman:`named` process
-  crash. This has been fixed. :gl:`#3683`
+- When a catalog zone was removed from the configuration, in some cases
+  a dangling pointer could cause the :iscman:`named` process to crash.
+  This has been fixed. :gl:`#3683`
 
-- The ``named`` would wait for some outstanding recursing queries
-  to finish before shutting down.  This has been fixed.  :gl:`#3183`
-
-- When a zone is deleted from a server, an key management objects related to
-  that zone would be kept in the memory and released only at the server
-  shutdown.  This could lead to constantly increasing memory usage for servers
-  with a high zone churn. :gl:`#3727`
+- In certain cases, :iscman:`named` waited for the resolution of
+  outstanding recursive queries to finish before shutting down. This was
+  unintended and has been fixed. :gl:`#3183`
 
+- When a zone was deleted from a server, a key management object related
+  to that zone was inadvertently kept in memory and only released upon
+  shutdown. This could lead to constantly increasing memory use on
+  servers with a high rate of changes affecting the set of zones being
+  served. This has been fixed. :gl:`#3727`
 
 Known Issues
 ~~~~~~~~~~~~