[4.0] 9f9d069 Squash more sphinx warnings

[Lasse Karstensen]

commit 9f9d0690b37962aa9188f23ef7204568a034b5f3
Author: Lasse Karstensen <lkarsten at varnish-software.com>
Date:   Thu Mar 20 16:06:45 2014 +0100

    Squash more sphinx warnings

diff --git a/doc/sphinx/users-guide/vcl-backends.rst b/doc/sphinx/users-guide/vcl-backends.rst
index 77347c4..a51e4f6 100644
--- a/doc/sphinx/users-guide/vcl-backends.rst
+++ b/doc/sphinx/users-guide/vcl-backends.rst
@@ -205,6 +205,7 @@ initial
 
 
 .. XXX: Where and why? benc
+
 Now we define the 'director'::
 
     import directors;
@@ -214,6 +215,7 @@ Now we define the 'director'::
         { .backend = server2; }
     }
 
+
 You use this director just as you would use any other director or
 backend. Varnish will not send traffic to hosts that are marked as
 unhealthy. Varnish can also serve stale content if all the backends are
diff --git a/doc/sphinx/users-guide/vcl-syntax.rst b/doc/sphinx/users-guide/vcl-syntax.rst
index f0b427f..d4acdd7 100644
--- a/doc/sphinx/users-guide/vcl-syntax.rst
+++ b/doc/sphinx/users-guide/vcl-syntax.rst
@@ -98,8 +98,7 @@ 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. These builtin subroutines are all named vcl_*. Your own subroutines cannot start their name with vcl_.
+transaction as it flows through Varnish. These builtin subroutines are all
+named `vcl_*`. Your own subroutines cannot start their name with `vcl\_`.
 
 .. XXX:looks as bit funky as red text? benc
-
-See :ref:`vcl-built-in-subs`.