[master] 78ab678f3 Another rewording for req.ttl in the 6.1 release notes.

[Geoff Simmons]

commit 78ab678f3372c964a664a3a519af3e567b4022cd
Author: Geoff Simmons <geoff at uplex.de>
Date:   Mon Sep 17 10:48:39 2018 +0200

    Another rewording for req.ttl in the 6.1 release notes.

diff --git a/doc/sphinx/whats-new/upgrading-6.1.rst b/doc/sphinx/whats-new/upgrading-6.1.rst
index 3a0f8452a..0f175b10f 100644
--- a/doc/sphinx/whats-new/upgrading-6.1.rst
+++ b/doc/sphinx/whats-new/upgrading-6.1.rst
@@ -50,12 +50,12 @@ since there are use cases that cannot be solved without it. Similarly,
 ``req.ttl`` used to be deprecated and is now fully supported again.
 
 ``req.ttl`` and ``req.grace`` limit the ttl and grace times that are
-permitted for the current request. If ``req.ttl`` is set, it requires
-cache objects to have that minimum remaining ttl to be considered
-fresh. Likewise, ``req.grace`` sets an upper bound on the time an
-object has spent in grace to be considered eligible for grace mode
-(which is to deliver this object and fetch a fresh copy in the
-background).
+permitted for the current request. If ``req.ttl`` is set, then cache
+objects are considered fresh (and may be cache hits) only if their
+remaining ttl is less than or equal to ``req.ttl``. Likewise,
+``req.grace`` sets an upper bound on the time an object has spent in
+grace to be considered eligible for grace mode (which is to deliver
+this object and fetch a fresh copy in the background).
 
 A common application is to set shorter TTLs when the backend is known
 to be healthy, so that responses are fresher when all is well. But if