final tweaks

Author: xabbuh

cache/esi.rst

@@ -6,8 +6,8 @@ Working with Edge Side Includes
 ===============================
 
 Gateway caches are a great way to make your website perform better. But they
-have one limitation: they can only cache whole pages. If you can't cache
-whole pages or if parts of a page has "more" dynamic parts, you are out of
+have one limitation: they can only cache whole pages. If your pages contain
+dynamic sections, such as the user name or a shopping cart, you are out of
 luck. Fortunately, Symfony provides a solution for these cases, based on a
 technology called `ESI`_, or Edge Side Includes. Akamai wrote this specification
 almost 10 years ago and it allows specific parts of a page to have a different
@@ -33,7 +33,7 @@ as this is the only useful one outside of Akamai context:
 
 .. note::
 
-    Notice from the example that each ESI tag has a fully-qualified URL.
+    Notice from the example that each ESI tag requires a fully-qualified URL.
     An ESI tag represents a page fragment that can be fetched via the given
     URL.
 

cache/expiration.rst

@@ -4,10 +4,10 @@
 HTTP Cache Expiration
 =====================
 
-The `expiration model`_ is the more efficient and straightforward of the two
+The `expiration model`_ is the most efficient and straightforward of the two
 caching models and should be used whenever possible. When a response is cached
-with an expiration, the cache will store the response and return it directly
-without hitting the application until it expires.
+with an expiration, the cache returns it directly without hitting the application
+until the cached response expires.
 
 The expiration model can be accomplished using one of two, nearly identical,
 HTTP headers: ``Expires`` or ``Cache-Control``.

cache/validation.rst

@@ -78,9 +78,9 @@ To see a simple implementation, generate the ETag as the md5 of the content::
     }
 
 The :method:`Symfony\\Component\\HttpFoundation\\Response::isNotModified`
-method compares the ``If-None-Match`` sent with the ``Request`` with the
-``ETag`` header set on the ``Response``. If the two match, the method
-automatically sets the ``Response`` status code to 304.
+method compares the ``If-None-Match`` header with the ``ETag`` response header.
+If the two match, the method automatically sets the ``Response`` status code
+to 304.
 
 .. note::
 
@@ -156,9 +156,9 @@ header value::
     }
 
 The :method:`Symfony\\Component\\HttpFoundation\\Response::isNotModified`
-method compares the ``If-Modified-Since`` header sent by the request with
-the ``Last-Modified`` header set on the response. If they are equivalent,
-the ``Response`` will be set to a 304 status code.
+method compares the ``If-Modified-Since`` header with the ``Last-Modified``
+response header. If they are equivalent, the ``Response`` will be set to a
+304 status code.
 
 .. note::
 

http_cache.rst

@@ -71,14 +71,14 @@ Symfony Reverse Proxy
 ~~~~~~~~~~~~~~~~~~~~~
 
 Symfony comes with a reverse proxy (i.e. gateway cache) written in PHP.
-:ref:`It's not as robust as other reverse proxy caches like Varnish <http-cache-symfony-versus-varnish>`,
+:ref:`It's not a fully-featured reverse proxy cache like Varnish <http-cache-symfony-versus-varnish>`,
 but is a great way to start.
 
 .. tip::
 
     For details on setting up Varnish, see :doc:`/cache/varnish`.
 
-Enabling the is easy: each application comes with a caching kernel (``AppCache``)
+Enabling the proxy is easy: each application comes with a caching kernel (``AppCache``)
 that wraps the default one (``AppKernel``). The caching Kernel *is* the reverse
 proxy.