Reorder release notes

diff --git a/doc/notes/notes-9.16.6.rst b/doc/notes/notes-9.16.6.rst
index ce08e450e3289ea377a0de362064f422da6deb9d..6d08db0e09a1b2effaa9e01e41791b746217ca64 100644 (file)
--- a/doc/notes/notes-9.16.6.rst
+++ b/doc/notes/notes-9.16.6.rst
@@ -79,20 +79,6 @@ Bug Fixes
   rules that were loaded from RPZ zones which appeared later in the
   ``response-policy`` statement. This has been fixed. [GL #1619]
 
-- Addressed an error in recursive clients stats reporting which could
-  cause underflow, and even negative statistics. There were occasions
-  when an incoming query could trigger a prefetch for some eligible
-  RRset, and if the prefetch code were executed before recursion, no
-  increment in recursive clients stats would take place. Conversely,
-  when processing the answers, if the recursion code were executed
-  before the prefetch, the same counter would be decremented without a
-  matching increment. [GL #1719]
-
-- The introduction of KASP support inadvertently caused the second field
-  of ``sig-validity-interval`` to always be calculated in hours, even in
-  cases when it should have been calculated in days. This has been
-  fixed. (Thanks to Tony Finch.) [GL !3735]
-
 - The IPv6 Duplicate Address Detection (DAD) mechanism could
   inadvertently prevent ``named`` from binding to new IPv6 interfaces,
   by causing multiple route socket messages to be sent for each IPv6
@@ -108,5 +94,19 @@ Bug Fixes
   to ``bind()`` to each IPv6 address again if the first ``bind()`` call
   for that address failed with ``EADDRNOTAVAIL``. [GL #2038]
 
+- Addressed an error in recursive clients stats reporting which could
+  cause underflow, and even negative statistics. There were occasions
+  when an incoming query could trigger a prefetch for some eligible
+  RRset, and if the prefetch code were executed before recursion, no
+  increment in recursive clients stats would take place. Conversely,
+  when processing the answers, if the recursion code were executed
+  before the prefetch, the same counter would be decremented without a
+  matching increment. [GL #1719]
+
+- The introduction of KASP support inadvertently caused the second field
+  of ``sig-validity-interval`` to always be calculated in hours, even in
+  cases when it should have been calculated in days. This has been
+  fixed. (Thanks to Tony Finch.) [GL !3735]
+
 - LMDB locking code was revised to make ``rndc reconfig`` work properly
   on FreeBSD and with LMDB >= 0.9.26. [GL #1976]