Remove copy paste error on zone-max-ttl

The "zone-max-ttl" option inside a "dnssec-policy" is not used to cap
the TTLs in a zone, only yo calculate key rollover timings.

(cherry picked from commit 4e3ba8169652e3e0423d176aa59d8686e95e014a)

diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst
index a7030ee32e85f7d8012d82922a0e74eb23e424a4..a455609b101b3ea13eebc6b1707c980d7b9ba18f 100644 (file)
--- a/doc/arm/reference.rst
+++ b/doc/arm/reference.rst
@@ -5019,10 +5019,7 @@ The following options can be specified in a ``dnssec-policy`` statement:
 
   ``max-zone-ttl``
     Like the ``max-zone-ttl`` zone option, this specifies the maximum
-    permissible TTL value, in seconds, for the zone.  When loading a
-    zone file using a ``masterfile-format`` of ``text`` or ``raw``, any
-    record encountered with a TTL higher than ``max-zone-ttl`` is capped
-    at the maximum permissible TTL value.
+    permissible TTL value, in seconds, for the zone.
 
     This is needed in DNSSEC-maintained zones because when rolling to a
     new DNSKEY, the old key needs to remain available until RRSIG