Tweak and reword release notes

doc/notes/notes-9.20.12.rst

@@ -15,22 +15,26 @@ Notes for BIND 9.20.12
 New Features
 ~~~~~~~~~~~~
 
-- Support for parsing the DSYNC record has been added.
+- Support for parsing DSYNC records has been added.
 
-  :gl:`#5440`
+  These records are used for discovering the receiver endpoint for DNS
+  notification messages. For more information, see
+  `draft-ietf-dnsop-generalized-notify-09`_. :gl:`#5440`
+
+.. _`draft-ietf-dnsop-generalized-notify-09`: https://datatracker.ietf.org/doc/draft-ietf-dnsop-generalized-notify/09/
 
 Feature Changes
 ~~~~~~~~~~~~~~~
 
-- Add deprecation warnings for RSASHA1, RSASHA1-NSEC3SHA1 and DS digest
+- Add deprecation warnings for RSASHA1, RSASHA1-NSEC3SHA1, and DS digest
   type 1.
 
   RSASHA1 and RSASHA1-NSEC-SHA1 DNSKEY algorithms have been deprecated
   by the IETF and should no longer be used for DNSSEC. DS digest type 1
-  (SHA1) has also been deprecated. Validators are now expected to treat
+  (SHA1) has also been deprecated in BIND 9. Validators are now expected to treat
   these algorithms and digest as unknown, resulting in some zones being
   treated as insecure when they were previously treated as secure.
-  Warnings have been added to named and tools when these algorithms and
+  Warnings have been added to :iscman:`named` and tools when these algorithms and
   this digest are being used for signing.
 
   Zones signed with RSASHA1 or RSASHA1-NSEC-SHA1 should be migrated to a
@@ -38,60 +42,57 @@ Feature Changes
 
   Zones with DS or CDS records with digest type 1 (SHA1) should be
   updated to use a different digest type (e.g. SHA256) and the digest
-  type 1 records should be removed.
-
-  Related to #5358
+  type 1 records should be removed. :gl:`#5358`
 
 Bug Fixes
 ~~~~~~~~~
 
 - Stale RRsets in a CNAME chain were not always refreshed.
 
-  With serve-stale enabled, a CNAME chain that contains a stale RRset,
-  the refresh query doesn't always properly refresh the stale RRsets.
+  Previously, with serve-stale enabled and a CNAME chain that contained a stale RRset,
+  the refresh query didn't always properly refresh the stale RRsets.
   This has been fixed. :gl:`#5243`
 
 - Add RPZ extended DNS error for zones with a CNAME override policy
   configured.
 
-  When the zone is configured with a CNAME override policy, or the
-  response policy zone contains a wildcard CNAME, the extended DNS error
+  Previously, when the zone was configured with a CNAME override policy, or the
+  response policy zone contained a wildcard CNAME, the extended DNS error
   code was not added. This has been fixed. :gl:`#5342`
 
-- Fix dig issues.
+- Fix :iscman:`dig` issues.
 
-  When used with the ``+keepopen`` option with a TCP connection,
-  iscman:`dig` could terminate unexpectedly in rare situations.
-  Additionally, iscman:`dig` could hang and fail to shutdown properly
+  When used with the ``+keepopen`` option,
+  :iscman:`dig` could terminate unexpectedly in rare situations.
+  Additionally, :iscman:`dig` could hang and fail to shutdown properly
   when interrupted during a query. These have been fixed. :gl:`#5381`
 
-- Log dropped or slipped responses in the query-errors category.
+- Log dropped or slipped responses in the ``query-errors`` category.
 
-  Responses which were dropped or slipped because of RRL (Response Rate
-  Limiting) were logged in the ``rate-limit`` category instead of the
-  ``query-errors`` category, as documented in ARM. This has been fixed.
+  Responses which were dropped or slipped because of Response Rate
+  Limiting (RRL) were logged in the ``rate-limit`` category instead of the
+  ``query-errors`` category, as documented in the ARM. This has been fixed.
   :gl:`#5388`
 
-- Synth-from-dnssec was not working in some scenarios.
+- :any:`synth-from-dnssec` was not working in some scenarios.
 
   Aggressive use of DNSSEC-Validated cache with NSEC was not working in
-  scenarios when no parent NSEC was not in cache.  This has been fixed.
+  scenarios when no parent NSEC was in cache.  This has been fixed.
   :gl:`#5422`
 
 - Clean enough memory when adding new ADB names/entries under memory
   pressure.
 
-  The ADB memory cleaning is opportunistic even when we are under memory
-  pressure (in the overmem condition).  Split the opportunistic LRU
-  cleaning and overmem cleaning and make the overmem cleaning always
-  cleanup double of the newly allocated adbname/adbentry to ensure we
-  never allocate more memory than the assigned limit.
+  The ADB memory cleaning is opportunistic even when BIND is under memory
+  pressure (in the overmem condition).  :iscman:`named` now ensures that the assigned memory
+  limit is not exceeded by releasing twice the amount of memory
+  allocated for each new ADB name/entry when under memory pressure.
+  :gl:`!10637`
 
 - Prevent spurious validation failures.
 
   Under rare circumstances, validation could fail if multiple clients
-  simultaneously iterated the same set of signatures.
-
-  References #3014
+  simultaneously iterated the same set of DNSSEC signatures. This has
+  been fixed. :gl:`#3014`