Skip to content

Commit b24ccc3

Browse files
committed
Merge branch '3.4' into 4.3
* 3.4: Simply update the ESI initial specs date (dated 2001) fix some more typos
2 parents fe75e60 + 35efe0f commit b24ccc3

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

components/property_access.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ Using Getters
112112
~~~~~~~~~~~~~
113113

114114
The ``getValue()`` method also supports reading using getters. The method will
115-
be created using common naming conventions for getters. It transform the
115+
be created using common naming conventions for getters. It transforms the
116116
property name to camelCase (``first_name`` becomes ``FirstName``) and prefixes
117117
it with ``get``. So the actual method becomes ``getFirstName()``::
118118

configuration/micro_kernel_trait.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -331,6 +331,6 @@ As before you can use the :doc:`Symfony Local Web Server
331331
cd public/
332332
$ symfony server:start
333333
334-
Then see page in browser:
334+
Then visit the page in your browser:
335335

336336
http://localhost:8000/random/10

http_cache/esi.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ have one limitation: they can only cache whole pages. If your pages contain
1212
dynamic sections, such as the user name or a shopping cart, you are out of
1313
luck. Fortunately, Symfony provides a solution for these cases, based on a
1414
technology called `ESI`_, or Edge Side Includes. Akamai wrote this specification
15-
almost 10 years ago and it allows specific parts of a page to have a different
15+
in 2001 and it allows specific parts of a page to have a different
1616
caching strategy than the main page.
1717

1818
The ESI specification describes tags you can embed in your pages to communicate

0 commit comments

Comments
 (0)