Typo patrol - again

doc/sphinx/tutorial/purging.rst

@@ -16,11 +16,11 @@ bans. First, let me explain the HTTP purges.
 HTTP Purges
 ~~~~~~~~~~~
 
-An HTTP purge is similar to a HTTP GET request, except that the
+An HTTP purge is similar to an HTTP GET request, except that the
 *method* is PURGE. Actually you can call the method whatever you'd
 like, but most people refer to this as purging. Squid supports the
 same mechanism. In order to support purging in Varnish you need the
-following VCL in place:::
+following VCL in place::
 
   acl purge {
 	  "localhost";
@@ -61,7 +61,7 @@ corresponding subroutine is called. In vcl_hit the object that is
 stored in cache is available and we can set the TTL.
 
 So for vg.no to invalidate their front page they would call out to
-Varnish like this:::
+Varnish like this::
 
   PURGE / HTTP/1.0
   Host: vg.no
@@ -69,7 +69,7 @@ Varnish like this:::
 And Varnish would then discard the front page. If there are several
 variants of the same URL in the cache however, only the matching
 variant will be purged. To purge a gzip variant of the same page the
-request would have to look like this:::
+request would have to look like this::
 
   PURGE / HTTP/1.0
   Host: vg.no
@@ -85,7 +85,7 @@ have.
 
 Support for bans is built into Varnish and available in the CLI
 interface. For VG to ban every png object belonging on vg.no they could
-issue:::
+issue::
 
   purge req.http.host == "vg.no" && req.http.url ~ "\.png$"
 
@@ -96,7 +96,7 @@ deliver it. An object is only checked against newer bans. If you have
 a lot of objects with long TTL in your cache you should be aware of a
 potential performance impact of having many bans.
 
-You can also add bans to Varnish via HTTP. Doing so requires a bit of VCL.::
+You can also add bans to Varnish via HTTP. Doing so requires a bit of VCL::
 
   sub vcl_recv {
 	  if (req.request == "BAN") {
@@ -108,12 +108,11 @@ You can also add bans to Varnish via HTTP. Doing so requires a bit of VCL.::
 		        "&& req.url == " req.url);
 
 		  # Throw a synthetic page so the
-                  # request wont go to the backend.
+                  # request won't go to the backend.
 		  error 200 "Ban added"
 	  }
   }
 
-This VCL sniplet enables Varnish to handle a HTTP BAN method. Adding a
+This VCL sniplet enables Varnish to handle an HTTP BAN method, adding a
 ban on the URL, including the host part.
 
-