Spelling fixes.

Submitted by:	 Federico G. Schwindt

Thanks!

doc/sphinx/reference/varnish-cli.rst

@@ -81,7 +81,7 @@ backend.list
 
 backend.set_health matcher state
       Sets the health state on a specific backend. This is useful if
-      you want to take a certain backend out of sirculations.
+      you want to take a certain backend out of circulation.
 
 ban   *field operator argument* [&& field operator argument [...]]
       Immediately invalidate all documents matching the ban

doc/sphinx/reference/vcl.rst

@@ -483,7 +483,7 @@ vcl_fetch
 
   hit_for_pass 
     Pass in fetch. Passes the object without caching it. This will
-    create a socalled hit_for_pass object which has the side effect
+    create a so-called hit_for_pass object which has the side effect
     that the decision not to cache will be cached. This is to allow
     would-be uncachable requests to be passed to the backend at the
     same time. The same logic is not necessary in vcl_recv because
@@ -545,7 +545,7 @@ default code.
 
 Multiple subroutines
 ~~~~~~~~~~~~~~~~~~~~
-If multiple subroutines with the the name of one of the builtin
+If multiple subroutines with the name of one of the builtin
 ones are defined, they are concatenated in the order in which they
 appear in the source.
 The default versions distributed with Varnish will be implicitly

doc/sphinx/reference/vmod.rst

@@ -34,7 +34,7 @@ The vmod.vcc file
 
 The interface between your VMOD and the VCL compiler ("VCC") and the
 VCL runtime ("VRT") is defined in the vmod.vcc file which a python
-script called "vmod.py" turns into thaumathurgically challenged C
+script called "vmod.py" turns into thaumaturgically challenged C
 data structures that does all the hard work.
 
 The std VMODs vmod.vcc file looks somewhat like this::