Skip to content

Commit a0e0dcd

Browse files
committed
Merge branch '4.4' into 5.0
* 4.4: Misc wording/grammar improvements
2 parents 7fdb608 + d7a620f commit a0e0dcd

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

cache.rst

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@
44
Cache
55
=====
66

7-
Using cache is a great way of making your application run quicker. The Symfony cache
8-
component is shipped with many adapters to different storages. Every adapter is
7+
Using a cache is a great way of making your application run quicker. The Symfony cache
8+
component ships with many adapters to different storages. Every adapter is
99
developed for high performance.
1010

1111
The following example shows a typical usage of the cache::
@@ -27,7 +27,7 @@ The following example shows a typical usage of the cache::
2727
// ... and to remove the cache key
2828
$pool->delete('my_cache_key');
2929

30-
Symfony supports the Cache Contracts, PSR-6/16 and Doctrine Cache interfaces.
30+
Symfony supports Cache Contracts, PSR-6/16 and Doctrine Cache interfaces.
3131
You can read more about these at the :doc:`component documentation </components/cache>`.
3232

3333
.. _cache-configuration-with-frameworkbundle:
@@ -42,9 +42,9 @@ of:
4242
This is a service that you will interact with. Each pool will always have
4343
its own namespace and cache items. There is never a conflict between pools.
4444
**Adapter**
45-
An adapter is a *template* that you use to create Pools.
45+
An adapter is a *template* that you use to create pools.
4646
**Provider**
47-
A provider is a service that some adapters are using to connect to the storage.
47+
A provider is a service that some adapters use to connect to the storage.
4848
Redis and Memcached are example of such adapters. If a DSN is used as the
4949
provider then a service is automatically created.
5050

@@ -104,7 +104,7 @@ The Cache component comes with a series of adapters pre-configured:
104104
* :doc:`cache.adapter.redis </components/cache/adapters/redis_adapter>`
105105

106106
Some of these adapters could be configured via shortcuts. Using these shortcuts
107-
will create pool with service id of ``cache.[type]``
107+
will create pools with service IDs that follow the pattern ``cache.[type]``.
108108

109109
.. configuration-block::
110110

@@ -298,13 +298,13 @@ You can also create more customized pools:
298298
],
299299
]);
300300
301-
Each pool manages a set of independent cache keys: keys of different pools
301+
Each pool manages a set of independent cache keys: keys from different pools
302302
*never* collide, even if they share the same backend. This is achieved by prefixing
303303
keys with a namespace that's generated by hashing the name of the pool, the name
304304
of the compiled container class and a :ref:`configurable seed<reference-cache-prefix-seed>`
305305
that defaults to the project directory.
306306

307-
Each custom pool becomes a service where the service id is the name of the pool
307+
Each custom pool becomes a service whose service ID is the name of the pool
308308
(e.g. ``custom_thing.cache``). An autowiring alias is also created for each pool
309309
using the camel case version of its name - e.g. ``custom_thing.cache`` can be
310310
injected automatically by naming the argument ``$customThingCache`` and type-hinting it
@@ -330,7 +330,7 @@ Custom Provider Options
330330

331331
Some providers have specific options that can be configured. The
332332
:doc:`RedisAdapter </components/cache/adapters/redis_adapter>` allows you to
333-
create providers with option ``timeout``, ``retry_interval``. etc. To use these
333+
create providers with the options ``timeout``, ``retry_interval``. etc. To use these
334334
options with non-default values you need to create your own ``\Redis`` provider
335335
and use that when configuring the pool.
336336

@@ -422,7 +422,7 @@ item in a cache chain, Symfony stores it in all pools sequentially. When
422422
retrieving an item, Symfony tries to get it from the first pool. If it's not
423423
found, it tries the next pools until the item is found or an exception is thrown.
424424
Because of this behavior, it's recommended to define the adapters in the chain
425-
in order from the fastest to the slowest.
425+
in order from fastest to slowest.
426426

427427
If an error happens when storing an item in a pool, Symfony stores it in the
428428
other pools and no exception is thrown. Later, when the item is retrieved,
@@ -486,9 +486,9 @@ Using Cache Tags
486486
----------------
487487

488488
In applications with many cache keys it could be useful to organize the data stored
489-
to be able to invalidate the cache more efficient. One way to achieve that is to
489+
to be able to invalidate the cache more efficiently. One way to achieve that is to
490490
use cache tags. One or more tags could be added to the cache item. All items with
491-
the same key could be invalidate with one function call::
491+
the same key could be invalidated with one function call::
492492

493493
use Symfony\Contracts\Cache\ItemInterface;
494494
use Symfony\Contracts\Cache\TagAwareCacheInterface;
@@ -636,14 +636,14 @@ Clearing the Cache
636636

637637
To clear the cache you can use the ``bin/console cache:pool:clear [pool]`` command.
638638
That will remove all the entries from your storage and you will have to recalculate
639-
all values. You can also group your pools into "cache clearers". There are 3 cache
639+
all the values. You can also group your pools into "cache clearers". There are 3 cache
640640
clearers by default:
641641

642642
* ``cache.global_clearer``
643643
* ``cache.system_clearer``
644644
* ``cache.app_clearer``
645645

646-
The global clearer clears all the cache in every pool. The system cache clearer
646+
The global clearer clears all the cache items in every pool. The system cache clearer
647647
is used in the ``bin/console cache:clear`` command. The app clearer is the default
648648
clearer.
649649

0 commit comments

Comments
 (0)