Skip to content

Commit ab10035

Browse files
committed
minor #3505 replace Akamaï with Akamai (xabbuh)
This PR was merged into the 2.3 branch. Discussion ---------- replace Akamaï with Akamai | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | all | Fixed tickets | #3502 Commits ------- fb276b8 replace Akamaï with Akamai
2 parents e385d28 + fb276b8 commit ab10035

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

book/http_cache.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -795,13 +795,13 @@ Gateway caches are a great way to make your website perform better. But they
795795
have one limitation: they can only cache whole pages. If you can't cache
796796
whole pages or if parts of a page has "more" dynamic parts, you are out of
797797
luck. Fortunately, Symfony2 provides a solution for these cases, based on a
798-
technology called `ESI`_, or Edge Side Includes. Akamaï wrote this specification
798+
technology called `ESI`_, or Edge Side Includes. Akamai wrote this specification
799799
almost 10 years ago, and it allows specific parts of a page to have a different
800800
caching strategy than the main page.
801801

802802
The ESI specification describes tags you can embed in your pages to communicate
803803
with the gateway cache. Only one tag is implemented in Symfony2, ``include``,
804-
as this is the only useful one outside of Akamaï context:
804+
as this is the only useful one outside of Akamai context:
805805

806806
.. code-block:: html
807807

@@ -936,7 +936,7 @@ used ``render``.
936936

937937
.. note::
938938

939-
Symfony2 detects if a gateway cache supports ESI via another Akamaï
939+
Symfony2 detects if a gateway cache supports ESI via another Akamai
940940
specification that is supported out of the box by the Symfony2 reverse
941941
proxy.
942942

cookbook/cache/varnish.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ As seen previously, Symfony2 is smart enough to detect whether it talks to a
1919
reverse proxy that understands ESI or not. It works out of the box when you
2020
use the Symfony2 reverse proxy, but you need a special configuration to make
2121
it work with Varnish. Thankfully, Symfony2 relies on yet another standard
22-
written by Akamaï (`Edge Architecture`_), so the configuration tips in this
22+
written by Akamai (`Edge Architecture`_), so the configuration tips in this
2323
chapter can be useful even if you don't use Symfony2.
2424

2525
.. note::

0 commit comments

Comments
 (0)