Edit reference.rst to indicate that the TSIG session key is automatically created...

(cherry picked from commit 79920cea70e267eb15395bafb734a3bd0eba1ca3)

diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml
index d44ef39605fef62129dd85694b776a84307d6861..02fc0380e1d60df71555fb1ad5dafb618fd09884 100644 (file)
--- a/doc/arm/Bv9ARM-book.xml
+++ b/doc/arm/Bv9ARM-book.xml
@@ -12512,9 +12512,8 @@ example.com. NS ns2.example.net.
              A pre-defined <command>update-policy</command> rule can be
              switched on with the command
              <command>update-policy local;</command>.
-             Using this in a zone causes
-             <command>named</command> to generate a TSIG session key
-             when starting up and store it in a file; this key can then
+             <command>named</command> automatically generates a TSIG session
+             key when starting and stores it in a file; this key can then
              be used by local clients to update the zone while
              <command>named</command> is running.
              By default, the session key is stored in the file