Reference cleanup.

doc/sphinx/users-guide/cookies.rst

@@ -90,6 +90,7 @@ Cookies coming from the backend
 
 If your backend server sets a cookie using the Set-Cookie header
 Varnish will not cache the page in the default configuration.  A
-hit-for-pass object (see :ref:`users-guide-vcl_fetch_actions`) is created.
+hit-for-pass 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

 
-.. vcl-built-in-subs_
+.. _vcl-built-in-subs:
 
 Built in subroutines
 --------------------

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

@@ -13,7 +13,7 @@ matches certain criteria::
     }
   }
 
-.. XXX ref hit-for-pass
+
 
 We also remove any Set-Cookie headers in order to avoid a hit-for-pass
-object to be created.
+object to be created. See :ref:`user-guide-vcl_actions`.

doc/sphinx/users-guide/vcl-syntax.rst

@@ -88,4 +88,5 @@ To call a subroutine, use the call keyword followed by the subroutine's name:
 
 call pipe_if_local;
 
-Varnish has quite a few built in subroutines that are called for each transaction as it flows through Varnish. See :ref:`vcl-built-in-subs`.
+Varnish has quite a few built in subroutines that are called for each
+transaction as it flows through Varnish. See :ref:`vcl-built-in-subs`.