[master] 3ae6077 Spelling
Federico G. Schwindt
fgsch at lodoss.net
Thu Jun 26 19:48:03 CEST 2014
Author: Federico G. Schwindt <fgsch at lodoss.net>
Date: Thu Jun 26 18:30:13 2014 +0100
diff --git a/doc/sphinx/tutorial/peculiarities.rst b/doc/sphinx/tutorial/peculiarities.rst
index 45f2f25..085edfd 100644
@@ -3,7 +3,7 @@ Peculiarities
There are a couple of things that are different with Varnish Cache, as
-opposed to other programs. One thing you've already seen - VCL. In this section we provide a very quick tour of other pecularities you need to know about to get the most out of Varnish.
+opposed to other programs. One thing you've already seen - VCL. In this section we provide a very quick tour of other peculiarities you need to know about to get the most out of Varnish.
diff --git a/doc/sphinx/users-guide/command-line.rst b/doc/sphinx/users-guide/command-line.rst
index aa8c5be..854fb32 100644
@@ -36,7 +36,7 @@ Here are some examples::
-.. XXX:brief explanation of some of the more comples examples perhaps? benc
+.. XXX:brief explanation of some of the more complex examples perhaps? benc
If your webserver runs on the same machine, you will have to move
it to another port number first.
diff --git a/doc/sphinx/users-guide/compression.rst b/doc/sphinx/users-guide/compression.rst
index cb95619..bff1ebb 100644
@@ -9,7 +9,7 @@ encoding. *Before* 3.0, Varnish would never compress objects.
In Varnish 4.0 compression defaults to "on", meaning that it tries to
be smart and do the sensible thing.
-.. XXX:Heavy refactoring to VArnish 4 above. benc
+.. XXX:Heavy refactoring to Varnish 4 above. benc
If you don't want Varnish tampering with the encoding you can disable
compression all together by setting the parameter 'http_gzip_support' to
@@ -40,7 +40,7 @@ You can make Varnish compress content before storing it in cache in
Please make sure that you don't try to compress content that is
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 that will ususally not be the most sensible thing to do.
+setting 'do_gunzip' to true but that will usually not be the most sensible thing to do.
Generally, Varnish doesn't use much CPU so it might make more sense to
have Varnish spend CPU cycles compressing content than doing it in
your web- or application servers, which are more likely to be
@@ -71,5 +71,5 @@ the page while delivering it.
A random outburst
-Poul-Henning Kamp has written :ref:`phk_gzip` which talks abit more about how the
+Poul-Henning Kamp has written :ref:`phk_gzip` which talks a bit more about how the
diff --git a/doc/sphinx/users-guide/devicedetection.rst b/doc/sphinx/users-guide/devicedetection.rst
index 2a0cb21..9138816 100644
@@ -68,7 +68,7 @@ VCL::
# req.http.X-UA-Device is copied by Varnish into bereq.http.X-UA-Device
- # so, this is a bit conterintuitive. The backend creates content based on
+ # so, this is a bit counterintuitive. The backend creates content based on
# the normalized User-Agent, but we use Vary on X-UA-Device so Varnish will
# use the same cached object for all U-As that map to the same X-UA-Device.
@@ -101,7 +101,7 @@ VCL::
Example 2: Normalize the User-Agent string
-Another way of signaling the device type is to override or normalize the
+Another way of signalling the device type is to override or normalize the
'User-Agent' header sent to the backend.
diff --git a/doc/sphinx/users-guide/intro.rst b/doc/sphinx/users-guide/intro.rst
index f9c5587..927292a 100644
@@ -65,7 +65,7 @@ simple to do simple things with::
The CLI interface allows you to compile and load new VCL programs
-at any time, and you can switch betweem the loaded VCL programs
+at any time, and you can switch between the loaded VCL programs
instantly, without restarting the child process and without missing
a single HTTP request.
diff --git a/doc/sphinx/users-guide/operation-logging.rst b/doc/sphinx/users-guide/operation-logging.rst
index 4bfdca0..4dfa40f 100644
@@ -51,7 +51,7 @@ session. Lines with the same number are coming from the same session
and are being handled by the same thread. The second column is the
*tag* of the log message. All log entries are tagged with a tag
indicating what sort of activity is being logged. Tags starting with
-'Rx' indicate Varnish is recieving data and 'Tx' indicates sending data.
+'Rx' indicate Varnish is receiving data and 'Tx' indicates sending data.
The third column tell us whether this is is data coming or going to
the client ('c') or to/from the backend ('b'). The forth column is the
More information about the varnish-commit