fix spelling errors

Author: dbu

doc/proxy-clients.rst

@@ -179,7 +179,7 @@ You need to pass the following options to the Fastly client:
 * ``service_identifier``: Identifier for your Fastly service account.
 * ``authentication_token``: User token for authentication against Fastly APIs.
 * NB: To be able to clear all cache(``->clear()``), you'll need a token for user with Fastly "Engineer permissions".
-* ``soft_purge`` (default: true): Boolean for doing soft purges or not on tag & url purging.
+* ``soft_purge`` (default: true): Boolean for doing soft purges or not on tag & URL purging.
   Soft purges expires the cache unlike hard purge (removal), and allow grace/stale handling within Fastly VCL.
 
 Additionally, you can specify the request factory used to build the
@@ -364,7 +364,7 @@ All other interfaces, ``PurgeCapable``, ``RefreshCapable``, ``BanCapable``, ``Ta
 and ``ClearCapable`` extend this ``ProxyClient``. So each client implements at least
 one of the :ref:`invalidation methods <invalidation methods>` depending on
 the proxy server’s abilities. To interact with a proxy client directly, refer to
-the phpdoc on the interfaces.
+the documentation comments on the interfaces.
 
 The ``ProxyClient`` has one method: ``flush()``. After collecting
 invalidation requests, ``flush()`` needs to be called to actually send the

doc/spelling_word_list.txt

@@ -1,9 +1,12 @@
 admin
+Analytics
 backend
 cacheable
 config
 css
 Fastly
+getter
+getters
 hostname
 hostnames
 http
@@ -28,3 +31,4 @@ Vcl
 inline
 Noop
 xkey
+ykey

doc/varnish-configuration.rst

@@ -14,9 +14,9 @@ To invalidate cached objects in Varnish, begin by adding an `ACL`_ (for Varnish
 3 see `ACL for Varnish 3`_) to your Varnish configuration. This ACL determines
 which IPs are allowed to issue invalidation requests. To use the provided
 configuration fragments, this ACL has to be named ``invalidators``. The most
-simple ACL, valid for all Varnish versions from 3 onwards, looks as follows:
+simple ACL, valid for Varnish version 3 or better, looks as follows:
 
-.. code-block:: varnish4
+.. code-block:: varnish3
 
     # /etc/varnish/your_varnish.vcl
 
@@ -419,7 +419,7 @@ The custom TTL header is removed before sending the response to the client.
     enabled for Varnish 3 by default. Check for the ``vcc_allow_inline_c``
     setting.
     If you are using Varnish 4 or newer, you are using the
-    ``varnish/fos_custom_ttl.vcl`` which uses a vmod function instead of inline C.
+    ``varnish/fos_custom_ttl.vcl`` which uses a Varnish function instead of inline C.
 
 .. _varnish_debugging: