diff --git a/components/cache.rst b/components/cache.rst
index d728f4455e0..1e0508b653a 100644
--- a/components/cache.rst
+++ b/components/cache.rst
@@ -10,8 +10,9 @@ The Cache Component
 
     The Cache component provides an extended `PSR-6`_ implementation as well as
     a `PSR-16`_ "Simple Cache" implementation for adding cache to your applications.
-    It is designed to have a low overhead and it ships with ready to use adapters
-    for the most common caching backends.
+    It is designed for performance and resiliency, and ships with ready to use
+    adapters for the most common caching backends, including proxies for adapting
+    from/to `Doctrine Cache`_.
 
 .. versionadded:: 3.3
     The PSR-16 "Simple Cache" implementation was introduced in Symfony 3.3.
@@ -192,4 +193,4 @@ Advanced Usage (PSR-6)
 
 .. _`PSR-6`: http://www.php-fig.org/psr/psr-6/
 .. _`PSR-16`: http://www.php-fig.org/psr/psr-16/
-.. _Packagist: https://packagist.org/packages/symfony/cache
+.. _Doctrine Cache: https://www.doctrine-project.org/projects/cache.html
diff --git a/components/cache/adapters/pdo_doctrine_dbal_adapter.rst b/components/cache/adapters/pdo_doctrine_dbal_adapter.rst
index 3a2f5b9425c..6ba9eb8f0b4 100644
--- a/components/cache/adapters/pdo_doctrine_dbal_adapter.rst
+++ b/components/cache/adapters/pdo_doctrine_dbal_adapter.rst
@@ -31,7 +31,7 @@ third, and forth parameters::
         // until the database table is truncated or its rows are otherwise deleted)
         $defaultLifetime = 0,
 
-        // an array of options for configuring the database connection
+        // an array of options for configuring the database table and connection
         $options = array()
     );
 
diff --git a/components/cache/cache_invalidation.rst b/components/cache/cache_invalidation.rst
index df1b1f3b893..f600a3ba83b 100644
--- a/components/cache/cache_invalidation.rst
+++ b/components/cache/cache_invalidation.rst
@@ -12,7 +12,7 @@ several cached items, keeping them in sync can be difficult.
 
 The Symfony Cache component provides two mechanisms to help solving this problem:
 
-* :ref:`Tags based invalidation <cache-component-tags>` for managing data dependencies;
+* :ref:`Tags-based invalidation <cache-component-tags>` for managing data dependencies;
 * :ref:`Expiration based invalidation <cache-component-expiration>` for time related dependencies.
 
 .. _cache-component-tags:
@@ -21,9 +21,9 @@ Using Cache Tags
 ----------------
 
 .. versionadded:: 3.2
-    Tags based invalidation was introduced in Symfony 3.2.
+    Tags-based invalidation was introduced in Symfony 3.2.
 
-To benefit from tags based invalidation, you need to attach the proper tags to
+To benefit from tags-based invalidation, you need to attach the proper tags to
 each cached item. Each tag is a plain string identifier that you can use at any
 time to trigger the removal of all items associated with this tag.
 
diff --git a/components/cache/cache_pools.rst b/components/cache/cache_pools.rst
index 0629487ff53..158f0e660c3 100644
--- a/components/cache/cache_pools.rst
+++ b/components/cache/cache_pools.rst
@@ -179,7 +179,7 @@ allowing manual removal of stale cache items::
 
 The :ref:`ChainAdapter <component-cache-chain-adapter>` implementation does not directly
 contain any pruning logic itself. Instead, when calling the chain adapter's
-:method:`Symfony\\Component\\Cache\\ChainAdapter::prune` method, the call is delegated to all
+:method:`Symfony\\Component\\Cache\\Adapter\\ChainAdapter::prune` method, the call is delegated to all
 its compatible cache adapters (and those that do not implement ``PruneableInterface`` are
 silently ignored)::