nope, here users_vcl _was_ the right reference

doc/sphinx/users-guide/index.rst

@@ -20,7 +20,7 @@ following the major interfaces to Varnish as a service:
 respect to storage, sockets, security and how you can control and
 communicate with Varnish once it is running.
 
-:ref:`vcl(7)` is about getting Varnish to handle the
+:ref:`users_vcl` is about getting Varnish to handle the
 HTTP requests the way you want, what to cache, how to cache it,
 modifying HTTP headers etc. etc.
 

doc/sphinx/users-guide/intro.rst

@@ -73,7 +73,7 @@ VCL code can be extended using external modules, called VMODs or
 even by inline C-code if you are brave, so in terms of what Varnish
 can do for your HTTP traffic, there really is no limit.
 
-:ref:`vcl(7)` describes VCL and what it can do in great detail.
+:ref:`users_vcl` describes VCL and what it can do in great detail.
 
 Varnish uses a segment of shared memory to report and log its activities and
 status. For each HTTP request, a number of very detailed records will

doc/sphinx/users-guide/vcl.rst

-.. _vcl(7):
+
+.. _users_vcl:
 
 VCL - Varnish Configuration Language
 ------------------------------------