From: Michał Kępień <michal@isc.org>
Date: Thu, 7 Jul 2022 14:34:14 +0000 (+0200)
Subject: Tweak and reword release notes
X-Git-Tag: v9.18.5~2^2~3
X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=9eb6e06f57b34770e42c2045a007337a717f3a48;p=thirdparty%2Fbind9.git

Tweak and reword release notes
---

diff --git a/doc/notes/notes-9.18.5.rst b/doc/notes/notes-9.18.5.rst
index 1eac3620fe0..b594e135f66 100644
--- a/doc/notes/notes-9.18.5.rst
+++ b/doc/notes/notes-9.18.5.rst
@@ -15,24 +15,27 @@ Notes for BIND 9.18.5
 Feature Changes
 ~~~~~~~~~~~~~~~
 
-- The :option:`dnssec-signzone -H` default value has been changed to 0 additional
-  NSEC3 iterations. This change aligns the :iscman:`dnssec-signzone` default with
-  the default used by the :ref:`dnssec-policy <dnssec_policy_grammar>` feature.
-  At the same time, documentation about NSEC3 has been aligned with
-  `Best Current Practice
-  <https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-nsec3-guidance-10>`__.
-  :gl:`#3395`
+- The :option:`dnssec-signzone -H` default value has been changed to 0
+  additional NSEC3 iterations. This change aligns the
+  :iscman:`dnssec-signzone` default with the default used by the
+  :any:`dnssec-policy` feature. At the same
+  time, documentation about NSEC3 has been aligned with the `Best
+  Current Practice`_. :gl:`#3395`
+
+.. _Best Current Practice: https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-nsec3-guidance-10
 
 Bug Fixes
 ~~~~~~~~~
 
-- It was possible for a catalog zone consumer to process a catalog zone member
-  zone when there was a configured pre-existing forward-only forward zone with
-  the same name. This has been fixed. :gl:`#2506`.
+- It was possible for a catalog zone consumer to process a catalog zone
+  member zone when there was a configured pre-existing forward-only
+  forward zone with the same name. This has been fixed. :gl:`#2506`
 
-- Fix the assertion failure caused by TCP connection closing between the
-  connect (or accept) and the read from the socket. :gl:`#3400`
+- An assertion failure caused by a TCP connection closing between a
+  connect (or accept) and a read from a socket has been fixed.
+  :gl:`#3400`
 
-- When grafting on non-delegated namespace, synth-from-dnssec could incorrectly
-  synthesise non-existance of records within the grafted in namespace using
-  NSEC records from higher zones. :gl:`#3402`
+- When grafting non-delegated namespace onto delegated namespace,
+  :any:`synth-from-dnssec` could incorrectly synthesize non-existence of
+  records within the non-delegated namespace using NSEC records from
+  higher zones. :gl:`#3402`