Update docs in spots to use the hit-for-miss and -pass terminology.

doc/sphinx/users-guide/increasing-your-hitrate.rst

@@ -220,7 +220,7 @@ Cookies coming from the backend
 
 If your backend server sets a cookie using the 'Set-Cookie' header
 Varnish will not cache the page when using the default configuration.
-A `hit-for-pass` object (see :ref:`user-guide-vcl_actions`) is
+A `hit-for-miss` object (see :ref:`user-guide-vcl_actions`) is
 created.  So, if the backend server acts silly and sets unwanted
 cookies just unset the 'Set-Cookie' header and all should be fine.
 

doc/sphinx/users-guide/vcl-built-in-subs.rst

@@ -178,10 +178,17 @@ The `vcl_hash` subroutine may only terminate with calling ``return(lookup)``:
     Look up the object in cache.
     Control passes to :ref:`vcl_purge` when coming from a ``purge``
     return in `vcl_recv`.
-    Otherwise control passes to :ref:`vcl_hit`, :ref:`vcl_miss` or
-    :ref:`vcl_pass` if the cache lookup result was a hit, a miss or hit
-    on a hit-for-pass object (object with ``obj.uncacheable ==
-    true``), respectively.
+    Otherwise control passes to the next subroutine depending on the result of
+    the cache lookup:
+
+    * a hit: pass to :ref:`vcl_hit`
+
+    * a miss or a hit on a hit-for-miss object (an object with
+      ``obj.uncacheable == true``): pass to :ref:`vcl_miss`
+
+    * a hit on a hit-for-pass object (for which ``pass(DURATION)`` had been
+      previously returned from ``vcl_backend_response``): pass to
+      :ref:`vcl_pass`
 
 .. _vcl_purge:
 

doc/sphinx/users-guide/vcl-example-manipulating-responses.rst

@@ -15,5 +15,5 @@ matches certain criteria::
 
 
 
-We also remove any Set-Cookie headers in order to avoid a `hit-for-pass`
-object to be created. See :ref:`user-guide-vcl_actions`.
+We also remove any Set-Cookie headers in order to avoid creation of a
+`hit-for-miss` object. See :ref:`user-guide-vcl_actions`.