Spelling

doc/sphinx/users-guide/compression.rst

@@ -36,7 +36,7 @@ vcl_fetch by setting do_gzip to true, like this::
   }
 
 Please make sure that you don't try to compress content that is
-incompressable, like jpgs, gifs and mp3. You'll only waste CPU
+uncompressable, like jpgs, gifs and mp3. You'll only waste CPU
 cycles. You can also uncompress objects before storing it in memory by
 setting do_gunzip to *true* but I have no idea why anybody would want
 to do that.

doc/sphinx/users-guide/devicedetection.rst

@@ -28,7 +28,7 @@ Setting this header can be as simple as::
    }
 
 There are different commercial and free offerings in doing grouping and
-identifiying clients in further detail than this. For a basic and community
+identifying clients in further detail than this. For a basic and community
 based regular expression set, see
 https://github.com/varnish/varnish-devicedetect/ .
 

doc/sphinx/users-guide/intro.rst

@@ -99,9 +99,9 @@ and facilities Varnish offers.
 Finally, Murphys Law must be contended with: Things will go wrong, and
 more likely than not, they will do so at zero-zero-dark O'clock. Most
 likely during a hurricane, when your phones battery is flat and your
-wife had prepared a intimate evening to celebrate your aniversary.
+wife had prepared a intimate evening to celebrate your anniversary.
 
-Yes, we've all been there, havn't we?
+Yes, we've all been there, haven't we?
 
 When things go wrong :ref:`users_trouble` will hopefully be of some help.
 

doc/sphinx/users-guide/params.rst

@@ -5,7 +5,7 @@ Parameters
 
 Varnish Cache has a set of parameter that affect its behaviour and
 performance. Most of these parameters can be set on the Varnish
-command line (through varnishadm) useing the param.set keyword.
+command line (through varnishadm) using the param.set keyword.
 
 Some parameters can, for security purposes be read only using the "-r"
 command line switch to varnishd.

doc/sphinx/users-guide/run_security.rst

@@ -9,7 +9,7 @@ this chapter:  We have protected Varnish as well as we can from
 anything which can come in through HTTP socket.
 
 If parts of your web infrastructure are outsourced or otherwise
-partitioned along adminitrative lines, you need to think about
+partitioned along administrative lines, you need to think about
 security.
 
 Varnish provides four levels of authority, roughly related to

doc/sphinx/users-guide/vcl-example-manipulating-responses.rst

@@ -3,7 +3,7 @@
 Altering the backend response
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Here we override the TTL of a object comming from the backend if it
+Here we override the TTL of a object coming from the backend if it
 matches certain criteria::
 
   sub vcl_fetch {

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

@@ -3,7 +3,7 @@ VCL Examples
 ------------
 
 These are a short collection of examples that showcase some of the
-capabilites of the VCL language.
+capabilities of the VCL language.
 
 .. toctree::
 

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

@@ -3,7 +3,7 @@ Hashing
 
 Internally, when Varnish stores content in it's store it uses a hash
 key to find the object again. In the default setup this key is
-calculated based on the content of the *Host* header or the IP adress
+calculated based on the content of the *Host* header or the IP address
 of the server and the URL.
 
 Behold the default vcl::
@@ -19,8 +19,8 @@ Behold the default vcl::
  }
 
 As you can see it first chucks in req.url then req.http.host if it
-exsists. It is worth pointing out that Varnish doesn't lowercase the
-hostname or the URL before hashing it so in thery having Varnish.org/
+exists. It is worth pointing out that Varnish doesn't lowercase the
+hostname or the URL before hashing it so in theory having Varnish.org/
 and varnish.org/ would result in different cache entries. Browers
 however, tend to lowercase hostnames.
 

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

@@ -15,7 +15,7 @@ In VCL, there several important objects.
 
 *beresp*
  The backend respons object. It contains the headers of the object 
- comming from the backend. Most of the work you do in vcl_fetch you 
+ coming from the backend. Most of the work you do in vcl_fetch you 
  do on the beresp object.
 
 *resp*

doc/sphinx/users-guide/vcl.rst

@@ -16,7 +16,7 @@ the request is being handled by altering the VCL code. You can direct
 certain requests to certains backends, you can alter the requests and
 the responses or have Varnish take various actions depending on
 arbitrary properties of the request or the response. This makes
-Varnish an extremly powerful HTTP processor, not just for caching.
+Varnish an extremely powerful HTTP processor, not just for caching.
 
 Varnish translates VCL into binary code which is then executed when
 requests arrive. The performance impact of VCL is negligible.