@@ -84,7 +84,7 @@ Along the way, the cache will store each response that is deemed "cacheable"
84
84
the cache sends the cached response to the client, ignoring your application
85
85
entirely.
86
86
87
- This type of cache is knows as an HTTP gateway cache and many exist such
87
+ This type of cache is known as a HTTP gateway cache and many exist such
88
88
as `Varnish `_, `Squid in reverse proxy mode `_, and the Symfony2 reverse proxy.
89
89
90
90
.. index ::
@@ -140,7 +140,7 @@ application comes with a pre-configured caching kernel (``AppCache``) that
140
140
wraps the default one (``AppKernel ``). The caching Kernel *is * the reverse
141
141
proxy.
142
142
143
- To enabling caching, modify the code of a front controller to use the caching
143
+ To enable caching, modify the code of a front controller to use the caching
144
144
kernel::
145
145
146
146
// web/app.php
@@ -636,7 +636,7 @@ exposing a simple and efficient pattern::
636
636
{
637
637
// Get the minimum information to compute
638
638
// the ETag or the Last-Modified value
639
- // (based on the Request, data are retrieved from
639
+ // (based on the Request, data is retrieved from
640
640
// a database or a key-value store for instance)
641
641
$article = // ...
642
642
@@ -717,7 +717,7 @@ Expiration and Validation
717
717
You can of course use both validation and expiration within the same ``Response ``.
718
718
As expiration wins over validation, you can easily benefit from the best of
719
719
both worlds. In other words, by using both expiration and validation, you
720
- can instruct the cache to server the cached content, while checking back
720
+ can instruct the cache to serve the cached content, while checking back
721
721
at some interval (the expiration) to verify that the content is still valid.
722
722
723
723
.. index ::
0 commit comments