Tweak and reword release notes

diff --git a/doc/notes/notes-9.18.33.rst b/doc/notes/notes-9.18.33.rst
index e9ce35377e265438b0eeef96685a58bad9a388c2..0ace1f944511f14cbeef7d0d21a8641314c3803a 100644 (file)
--- a/doc/notes/notes-9.18.33.rst
+++ b/doc/notes/notes-9.18.33.rst
@@ -15,34 +15,40 @@ Notes for BIND 9.18.33
 Security Fixes
 ~~~~~~~~~~~~~~
 
-- [CVE-2024-12705] DNS-over-HTTP(s) flooding fixes.
+- DNS-over-HTTPS flooding fixes. :cve:`2024-12705`
 
-  Fix DNS-over-HTTP(S) implementation issues that arise under heavy
+  Fix DNS-over-HTTPS implementation issues that arise under heavy
   query load. Optimize resource usage for :iscman:`named` instances that
-  accept queries over DNS-over-HTTP(S).
+  accept queries over DNS-over-HTTPS.
 
-  Previously, :iscman:`named` would process all incoming HTTP/2 data at
+  Previously, :iscman:`named` processed all incoming HTTP/2 data at
   once, which could overwhelm the server, especially when dealing with
-  clients that send requests but don't wait for responses. That has been
+  clients that sent requests but did not wait for responses. That has been
   fixed. Now, :iscman:`named` handles HTTP/2 data in smaller chunks and
   throttles reading until the remote side reads the response data. It
   also throttles clients that send too many requests at once.
 
-  Additionally, :iscman:`named` now carefully processes data sent by
-  some clients, which can be considered "flooding." It logs these
-  clients and drops connections from them. :gl:`#4795`
+  In addition, :iscman:`named` now evaluates excessive streams opened by
+  clients that include no DNS data, which is considered "flooding." It
+  logs these clients and drops connections from them. :gl:`#4795`
 
-  In some cases, :iscman:`named` could leave DNS-over-HTTP(S)
-  connections in the `CLOSE_WAIT` state indefinitely. That also has been
-  fixed. ISC would like to thank JF Billaud for thoroughly investigating
-  the issue and verifying the fix. :gl:`#5083` :gl:`#4795` :gl:`#5083`
+  In some cases, :iscman:`named` could leave DNS-over-HTTPS
+  connections in the `CLOSE_WAIT` state indefinitely. That has also been
+  fixed. :gl:`#5083`
 
-- [CVE-2024-11187] Limit the additional processing for large RDATA sets.
+  ISC would like to thank Jean-François Billaud for his assistance with
+  investigating this issue.
+
+- Limit additional section processing for large RDATA sets.
+  :cve:`2024-11187`
 
   When answering queries, don't add data to the additional section if
   the answer has more than 13 names in the RDATA. This limits the number
   of lookups into the database(s) during a single client query, reducing
-  query processing load. :gl:`#5034`
+  the query-processing load. :gl:`#5034`
+
+  ISC would like to thank Toshifumi Sakaguchi for bringing this
+  vulnerability to our attention.
 
 New Features
 ~~~~~~~~~~~~
@@ -50,42 +56,42 @@ New Features
 - Add a new option to configure the maximum number of outgoing queries
   per client request.
 
-  The configuration option 'max-query-count' sets how many outgoing
-  queries per client request is allowed. The existing
-  'max-recursion-queries' is the number of permissible queries for a
+  The configuration option :any:`max-query-count` sets how many outgoing
+  queries per client request are allowed. The existing
+  :any:`max-recursion-queries` value is the number of permissible queries for a
   single name and is reset on every CNAME redirection. This new option
   is a global limit on the client request. The default is 200.
 
-  This allows us to send a bit more queries while looking up a single
-  name. The default for 'max-recursion-queries' is changed from 32 to
-  50. :gl:`#4980`  :gl:`#4921`
+  The default for :any:`max-recursion-queries` is changed from 32 to
+  50. This allows :any:`named` to send a few more queries
+  while looking up a single name. :gl:`#4980` :gl:`#4921`
 
 Bug Fixes
 ~~~~~~~~~
 
-- Fix nsupdate hang when processing a large update.
+- Fix :iscman:`nsupdate` hang when processing a large update.
 
-  To mitigate DNS flood attacks over a single TCP connection, we
-  throttle the connection when the other side does not read the data.
-  Throttling should only occur on server-side sockets, but erroneously
-  also happened for nsupdate, which acts as a client. When nsupdate
-  started throttling the connection, it never attempts to read again.
-  This has been fixed.   :gl:`#4910`
+  To mitigate DNS flood attacks over a single TCP connection, throttle
+  the connection when the other side does not read the data. Throttling
+  should only occur on server-side sockets, but erroneously also
+  happened for :iscman:`nsupdate`, which acts as a client. When
+  :iscman:`nsupdate` started throttling the connection, it never
+  attempted to read again. This has been fixed. :gl:`#4910`
 
 - Fix possible assertion failure when reloading server while processing
-  updates.
+  update policy rules. :gl:`#5006`
 
-  :gl:`#5006`
+- Fix :iscman:`dnssec-signzone` signing non-DNSKEY RRsets with revoked keys.
 
-- Fix dnssec-signzone signing non-DNSKEY RRsets with revoked keys.
-
-  `dnssec-signzone` was using revoked keys for signing RRsets other than
+  :any:`dnssec-signzone` was using revoked keys for signing RRsets other than
   DNSKEY.  This has been corrected. :gl:`#5070`
 
-- Unknown directive in resolv.conf not handled properly.
+- Fix improper handling of unknown directives in ``resolv.conf``.
+
+  The line after an unknown directive in ``resolv.conf`` could accidentally be
+  skipped, potentially affecting :iscman:`dig`, :iscman:`host`,
+  :iscman:`nslookup`, :iscman:`nsupdate`, or :iscman:`delv`. This has been
+  fixed. :gl:`#5084`
 
-  The line after an unknown directive in resolv.conf could accidentally
-  be skipped, potentially affecting dig, host, nslookup, nsupdate, or
-  delv. This has been fixed. :gl:`#5084`