[master] 5e3e98f Correct article

Lasse Karstensen lkarsten at varnish-software.com
Thu Mar 20 13:30:25 CET 2014


commit 5e3e98f054309e34ccbef67bd030acf22369f388
Author: Lasse Karstensen <lkarsten at varnish-software.com>
Date:   Thu Mar 20 13:30:22 2014 +0100

    Correct article

diff --git a/doc/sphinx/glossary/index.rst b/doc/sphinx/glossary/index.rst
index 3da5af3..574156b 100644
--- a/doc/sphinx/glossary/index.rst
+++ b/doc/sphinx/glossary/index.rst
@@ -34,11 +34,11 @@ Varnish Glossary
    backend
 	The HTTP server varnishd is caching for.  This can be
 	any sort of device that handles HTTP requests, including, but
-	not limited to: a webserver, a CMS, a load-balancer 
+	not limited to: a webserver, a CMS, a load-balancer
 	another varnishd, etc.
 
    client
-	The program which sends varnishd a HTTP request, typically
+	The program which sends varnishd an HTTP request, typically
 	a browser, but do not forget to think about spiders, robots
 	script-kiddies and criminals.
 
@@ -65,13 +65,13 @@ Varnish Glossary
    .. comment: "components of traffic ---------------------------------"
 
    header
-	A HTTP protocol header, like "Accept-Encoding:".
+	An HTTP protocol header, like "Accept-Encoding:".
 
    request
 	What the client sends to varnishd and varnishd sends to the backend.
 
    response
-	What the backend returns to varnishd and varnishd returns to 
+	What the backend returns to varnishd and varnishd returns to
 	the client.  When the response is stored in varnishd's cache,
 	we call it an object.
 
diff --git a/doc/sphinx/users-guide/increasing-your-hitrate.rst b/doc/sphinx/users-guide/increasing-your-hitrate.rst
index 2f22e3c..4be147f 100644
--- a/doc/sphinx/users-guide/increasing-your-hitrate.rst
+++ b/doc/sphinx/users-guide/increasing-your-hitrate.rst
@@ -48,7 +48,7 @@ Tool: lwp-request
 ~~~~~~~~~~~~~~~~~
 
 `lwp-request` is tool that is a part of The World-Wide Web library for Perl. It's a
-couple of really basic programs that can execute a HTTP request and
+couple of really basic programs that can execute an HTTP request and
 show you the result. We mostly use the two programs, ``GET`` and ``HEAD``.
 
 vg.no was the first site to use Varnish and the people running Varnish
diff --git a/doc/sphinx/users-guide/purging.rst b/doc/sphinx/users-guide/purging.rst
index 214fe81..c0e8381 100644
--- a/doc/sphinx/users-guide/purging.rst
+++ b/doc/sphinx/users-guide/purging.rst
@@ -21,7 +21,7 @@ A *purge* is what happens when you pick out an object from the cache
 and discard it along with its variants. Usually a purge is invoked
 through HTTP with the method `PURGE`.
 
-A 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, for example, supports the
 same mechanism. In order to support purging in Varnish you need the
diff --git a/doc/sphinx/users-guide/run_cli.rst b/doc/sphinx/users-guide/run_cli.rst
index 3e75ac5..40c6b4e 100644
--- a/doc/sphinx/users-guide/run_cli.rst
+++ b/doc/sphinx/users-guide/run_cli.rst
@@ -116,7 +116,7 @@ but they are banned from delivery.
 
 Instead of checking each and every cached object right away, we
 test each object against the regular expression only if and when
-a HTTP request asks for it.
+an HTTP request asks for it.
 
 Banning stuff is much cheaper than restarting Varnish to get rid
 of wronly cached content.
diff --git a/doc/sphinx/users-guide/run_security.rst b/doc/sphinx/users-guide/run_security.rst
index 7607cfc..5fe3890 100644
--- a/doc/sphinx/users-guide/run_security.rst
+++ b/doc/sphinx/users-guide/run_security.rst
@@ -6,7 +6,7 @@ Security first
 If you are the only person involved in running Varnish, or if all
 the people involved are trusted to the same degree, you can skip
 this chapter. We have protected Varnish as well as we can from
-anything which can come in through a HTTP socket.
+anything which can come in through an HTTP socket.
 
 If parts of your web infrastructure are outsourced or otherwise
 partitioned along administrative lines, you need to think about



More information about the varnish-commit mailing list