[master] 8e2d5ac Typos
Federico G. Schwindt
fgsch at lodoss.net
Tue Jul 7 13:29:11 CEST 2015
commit 8e2d5ac61f0e8cdfc0650c718abf13f148772b64
Author: Federico G. Schwindt <fgsch at lodoss.net>
Date: Tue Jul 7 12:26:35 2015 +0100
Typos
Partially from minusf via github
diff --git a/doc/sphinx/users-guide/run_security.rst b/doc/sphinx/users-guide/run_security.rst
index e34b0a7..5b9dfad 100644
--- a/doc/sphinx/users-guide/run_security.rst
+++ b/doc/sphinx/users-guide/run_security.rst
@@ -45,9 +45,9 @@ The important decisions to make are:
CLI interface access
^^^^^^^^^^^^^^^^^^^^
-The command line interface can be accessed three ways.
+The command line interface can be accessed in three ways.
-`Varnishd` can be told til listen and offer CLI connections
+`Varnishd` can be told to listen and offer CLI connections
on a TCP socket. You can bind the socket to pretty
much anything the kernel will accept::
@@ -227,12 +227,12 @@ HTTP requests
-------------
We have gone to great lengths to make Varnish resistant to anything
-coming in throught the socket where HTTP requests are received, and
+coming in through the socket where HTTP requests are received, and
you should, generally speaking, not need to protect it any further.
The caveat is that since VCL is a programming language which lets you
decide exactly what to do with HTTP requests, you can also decide
-to do stupid and potentially dangerous things with them, including opening youself up
+to do stupid and potentially dangerous things with them, including opening yourself up
to various kinds of attacks and subversive activities.
If you have "administrative" HTTP requests, for instance PURGE
More information about the varnish-commit
mailing list