Revert "Describe VMODs as VCL modules"

This reverts commit c2070784, we'll
stick to varnish modules. I also updated a commented-out occurrence
of "VCL modules" in params.h, we can probably get rid of these
comments.

doc/sphinx/reference/vcl.rst

@@ -174,7 +174,7 @@ To include a VCL file in another file use the include keyword::
 Import statement
 ----------------
 
-The ``import`` statement is used to load VCL modules (VMODs.)
+The ``import`` statement is used to load Varnish Modules (VMODs.)
 
 Example::
 

doc/sphinx/reference/vmod.rst

 .. _ref-vmod:
 
-%%%%%%%%%%%%%%%%%%
-VMOD - VCL Modules
-%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%
+VMOD - Varnish Modules
+%%%%%%%%%%%%%%%%%%%%%%
 
 For all you can do in VCL, there are things you can not do.
 Look an IP number up in a database file for instance.

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

@@ -120,9 +120,9 @@ You can also group several backend into a group of backends. These
 groups are called directors. This will give you increased performance
 and resilience.
 
-You can define several backends and group them together in a director.
-This requires you to load a VMOD, a VCL module, and then to call certain
-actions in `vcl_init`.::
+You can define several backends and group them together in a
+director. This requires you to load a VMOD, a Varnish module, and then to
+call certain actions in `vcl_init`.::
 
 
     import directors;    # load the directors

include/tbl/params.h

@@ -1473,7 +1473,7 @@ PARAM(
 	/* units */	NULL,
 	/* flags */	0,
 	/* s-text */
-	"Directory where VCL modules are to be found.",
+	"Directory where Varnish modules are to be found.",
 	/* l-text */	"",
 	/* func */	NULL
 )