Lots of fixes

Author: Nyholm

cache.rst

@@ -2,8 +2,8 @@ Cache
 =====
 
 Using cache is a great way of making you application run quicker. The Symfony cache
-component is shipped with many adapters to cache storages that all are developed
-for high performance.
+component is shipped with many adapters to different storages. Every adapter is
+developed for high performance.
 
 Basic uses of the cache looks like this.
 
@@ -16,11 +16,13 @@ Basic uses of the cache looks like this.
         $item->expiresAfter(3600);
 
         // Do some HTTP request or heavy computations
-        $computedValue = ...;
+        $computedValue = 'foobar';
 
         return $computedValue;
     });
 
+    echo $value; // 'foobar'
+
     $pool->delete('some_key');
 
 
@@ -31,10 +33,11 @@ these at the :ref:`component documentation <component-cache>`.
 Configuring Cache with SymfonyFrameworkBundle
 ---------------------------------------------
 
-When configuring the the cache component there are a few concepts you should know:
+When configuring the the cache component there are a few concepts you should know
+of:
 
 **Pool**
-    This is a service that you will interact with. Each pool will always has
+    This is a service that you will interact with. Each pool will always have
     its own namespace and cache items. There is never a conflict between pools.
 **Adapter**
     An adapter is a *template* that you use to create Pools.
@@ -43,8 +46,8 @@ When configuring the the cache component there are a few concepts you should kno
 
 There are two pools that are always enabled by default. They are ``cache.app`` and
 ``cache.system``. The system cache is use for things like annotations, serializer,
-and validation. The ```cache.app`` is used in your code. You can configure witch
-adapters (templates) they use by using the ``app`` and ``system`` key like:
+and validation. The ```cache.app`` is used in your code. You can configure which
+adapter (template) they use by using the ``app`` and ``system`` key like:
 
 .. code-block:: yaml
 
@@ -56,17 +59,19 @@ adapters (templates) they use by using the ``app`` and ``system`` key like:
 The Cache component comes with a series of adapters already created:
 
 - :ref:`cache.adapter.apcu <component-cache-apcu-adapter>`
-- :ref:`cache.adapter.chain <component-cache-chain-adapter>`
+- :ref:`ChainAdapter <component-cache-chain-adapter>`
 - :ref:`cache.adapter.doctrine <component-cache-doctrine-adapter>`
 - :ref:`cache.adapter.filesystem <component-cache-filesystem-adapter>`
 - :ref:`cache.adapter.memcached <component-cache-memcached-adapter>`
 - :ref:`cache.adapter.pdo <component-cache-pdo-doctrine-dbal-adapter>`
-- :ref:`cache.adapter.array <component-cache-php-array-adapter>`
-- :ref:`cache.adapter.file <component-cache-php-files-adapter>`
-- :ref:`cache.adapter.proxy <component-cache-proxy-adapter>`
+- :ref:`PHPArrayAdapter <component-cache-php-array-adapter>`
+- :ref:`PHPFileAdapter <component-cache-php-files-adapter>`
+- :ref:`ProxyAdapter <component-cache-proxy-adapter>`
 - :ref:`cache.adapter.redis <component-cache-redis-adapter>`
 - cache.adapter.psr6
 - cache.adapter.system
+- NullAdapter
+- cache.adapter.array
 
 Some of these adapters could be configured via shortcuts:
 
@@ -83,7 +88,7 @@ Some of these adapters could be configured via shortcuts:
             default_pdo_provider: 'doctrine.dbal.default_connection'
 
 Using the *providers* above, they will configure the adapters and create pools (services)
-with names:
+with service ids:
 
 - ``cache.doctrine``
 - ``cache.psr6``
@@ -111,9 +116,9 @@ You can also create more customized pools. All you need is an adapter
                     provider: 'memcached://user:password@example.com'
 
 The configuration above will create 3 services: ``my_cache_pool``, ``cache.acme``
-and ``cache.foobar``.  The ``my_cache_pool`` pool is using the :ref:`ArrayAdapter <component-cache-php-array-adapter>`
+and ``cache.foobar``.  The ``my_cache_pool`` pool is using the ArrayAdapter
 and the other two are using the :ref:`MemcachedAdapter <component-cache-memcached-adapter>`.
-Pool ``cache.acme`` is using the Memcached server on localhost and ``cache.foobar``
+The ``cache.acme`` pool is using the Memcached server on localhost and ``cache.foobar``
 is using the Memcached server at example.com.
 
 For advanced configurations it could sometimes be useful to use a pool as an adapter.
@@ -169,12 +174,19 @@ case we have to recalculate the value.
 Clearing the Cache
 ------------------
 
-When the ``bin/console cache:clear`` command is executed it will use
+To clear the cache you can use the ``bin/console cache:pool:clear [pool]`` command.
+That will remove all the entries from your storage and you wil have to recalcuate
+all values. You can also group your pools into "cache clearers". There 3 cache clearer
+by default:
+
+* cache.global_clearer
+* cache.system_clearer
+* cache.app_clearer
 
-Only the system cached is cleared..
+The global clearer clears all the cache in every pool. The system cache clearer
+is used in the ``bin/console cache:clear`` command. The app clearer is the default
+clearer.
 
-cache.system_clearer
-cache.default_clearer
-cache.app_clearer
+.. code-block:: terminal
 
-cache.global_clearer
+    $ bin/console cache:pool:clear cache.app_clearer