fix spelling errors

Author: dbu

Resources/doc/reference/annotations.rst

@@ -49,7 +49,7 @@ See :doc:`/features/invalidation` for more information.
 ``@InvalidateRoute``
 --------------------
 
-Like InvalidatePath annotations, you can use php attributes instead if you are using PHP 8
+Like InvalidatePath annotations, you can use PHP attributes instead if you are using PHP 8
 Invalidate a route with parameters::
 
     use FOS\HttpCacheBundle\Configuration\InvalidateRoute;
@@ -99,7 +99,7 @@ HTTP header (``X-Cache-Tags``, by default).
 Any non-safe request to the ``editAction`` that returns a successful response
 will trigger invalidation of both the ``news`` and the ``news-123`` tags.
 
-Like InvalidatePath annotations, you can use php attributes instead if you are using PHP 8
+Like InvalidatePath annotations, you can use PHP attributes instead if you are using PHP 8
 
 Set/invalidate a tag::
 

Resources/doc/reference/configuration/proxy-client.rst

@@ -81,13 +81,13 @@ inconsistent caches.
 
 **type**: ``string``
 
-Json encoded servers array as string. The servers array has the same specs as ``http.servers``.
+JSON encoded servers array as string. The servers array has the same specs as ``http.servers``.
 
 Use this option only when using a variable amount of proxy servers that shall be defined via
 environment variable. Otherwise use the regular ``http.servers`` option.
 
 Usage:
-* fos_http_cache.yaml: ``servers_from_jsonenv: '%env(json:VARNISH_SERVERS)%'``
+* ``fos_http_cache.yaml``: ``servers_from_jsonenv: '%env(json:VARNISH_SERVERS)%'``
 * environment definition: ``VARNISH_SERVERS='["123.123.123.1:6060","123.123.123.2"]'``
 
 

Resources/doc/reference/configuration/tags.rst

@@ -64,11 +64,11 @@ section of the tag configuration and ``@tag`` :ref:`annotations<tag>`.
 By default, the generated response header will not be split into multiple headers.
 This means that depending on the amount of tags generated in your application the
 value of that header might become pretty long. This again might cause issues with
-your webserver which usually come with a pre-defined maximum header value length and
-will throw an exception if you exceed this. Using this configuration key you can
+your web server, as it usually has a default maximum header length and will reject
+the request if the header exceeds this value. Using this configuration key, you can
 configure a maximum length **in bytes** which will split your value into multiple
-headers. Note that you might update your proxy configuration because it needs
-to be able to handle multiple headers instead of just one.
+headers. Note that you might have to update your proxy configuration because it
+needs to be able to handle multiple headers instead of just one.
 
 .. code-block:: yaml
 
@@ -79,7 +79,7 @@ to be able to handle multiple headers instead of just one.
 
 .. note::
 
-    4096 bytes is generally a good choice because it seems like most webservers have
+    4096 bytes is generally a good choice because it seems like most web servers have
     a maximum value of 4 KB configured.
 
 ``strict``

Resources/doc/spelling_word_list.txt

@@ -8,15 +8,18 @@ cacheable
 ETag
 friendsofsymfony
 github
+hardcoded
 hostname
 invalidations
 invalidator
 javascript
+JSON
 login
 logout
 lookup
 lookups
 matcher
+md
 mistyped
 multi
 nginx
@@ -31,5 +34,6 @@ symfony
 subdomains
 templating
 TTL
+vmod
 xkey
 yaml