NEWS + doc about TTL: forgotten minor tweaks

diff --git a/NEWS b/NEWS
index f93929e403e16e174fa79773b192b9fababf6a8e..b9d3894d90138d4f819740effa123e090ac4373c 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,10 +1,10 @@
-Knot Resolver 5.x.y (202y-mm-dd)
+Knot Resolver 5.6.0 (202y-mm-dd)
 ================================
 
 Improvements
 ------------
-- cache.max_ttl(): lower the default from six days to one day (!1323)
-  and apply both limits to the first uncached answer already
+- cache.max_ttl(): lower the default from six days to one day
+  and apply both limits to the first uncached answer already (!1323 #127)
 - depend on jemalloc, preferably, to improve memory usage (!1353)
 - no longer accept DNS messages with trailing data (!1365)
 - policy.STUB: avoid applying aggressive DNSSEC denial proofs (!1364)

diff --git a/daemon/bindings/cache.rst b/daemon/bindings/cache.rst
index fe614bf963a0e3a2d6babbb21524a0280931b08b..36114d226b65b32537d21f43def1ab569e57c9db 100644 (file)
--- a/daemon/bindings/cache.rst
+++ b/daemon/bindings/cache.rst
@@ -227,7 +227,7 @@ Configuration reference
 
   :return: current maximum TTL
 
-  Get or set maximum TTL bound applied to all received records.
+  Get or set upper TTL bound applied to all received records.
 
   .. note:: The `ttl` value must be in range `(min_ttl, 2147483647)`.
 
@@ -246,10 +246,10 @@ Configuration reference
 
   .. KR_CACHE_DEFAULT_TTL_MIN ^^
 
-  :return: current maximum TTL
+  :return: current minimum TTL
 
-  Get or set minimum TTL bound applied to all received records.
-  Forcing TTL higher than specified violates DNS standards, so use it with care.
+  Get or set lower TTL bound applied to all received records.
+  Forcing TTL higher than specified violates DNS standards, so use higher values with care.
   TTL still won't be extended beyond expiration of the corresponding DNSSEC signature.
 
   .. note:: The `ttl` value must be in range `<0, max_ttl)`.