diff --git a/docs/features/caching.rst b/docs/features/caching.rst
index 8e70bc3a..fd780b1e 100644
--- a/docs/features/caching.rst
+++ b/docs/features/caching.rst
@@ -1,21 +1,34 @@
-Caching
-=======
-
-Ocelot supports some very rudimentary caching at the moment provider by
-the `CacheManager `_ project. This is an amazing project
-that is solving a lot of caching problems. I would reccomend using this package to
-cache with Ocelot. If you look at the example `here `_ you can see how the cache manager is setup and then passed into the Ocelot
-AddOcelotOutputCaching configuration method. You can use any settings supported by
-the CacheManager package and just pass them in.
-
-Anyway Ocelot currently supports caching on the URL of the downstream service
-and setting a TTL in seconds to expire the cache. You can also clear the cache for a region
-by calling Ocelot's administration API.
-
-In order to use caching on a route in your ReRoute configuration add this setting.
-
-.. code-block:: json
-
- "FileCacheOptions": { "TtlSeconds": 15, "Region": "somename" }
-
-In this example ttl seconds is set to 15 which means the cache will expire after 15 seconds.
+Caching
+=======
+
+Ocelot supports some very rudimentary caching at the moment provider by
+the `CacheManager `_ project. This is an amazing project
+that is solving a lot of caching problems. I would reccomend using this package to
+cache with Ocelot.
+
+The following example shows how to add CacheManager to Ocelot so that you can do output caching. The first thing you need to do is add the following to your ConfigureServices..
+
+.. code-block:: csharp
+
+ s.AddOcelot()
+ .AddCacheManager(x =>
+ {
+ x.WithDictionaryHandle();
+ })
+
+In order to use caching on a route in your ReRoute configuration add this setting.
+
+.. code-block:: json
+
+ "FileCacheOptions": { "TtlSeconds": 15, "Region": "somename" }
+
+In this example ttl seconds is set to 15 which means the cache will expire after 15 seconds.
+
+If you look at the example `here `_ you can see how the cache manager is setup and then passed into the Ocelot
+AddOcelotOutputCaching configuration method. You can use any settings supported by
+the CacheManager package and just pass them in.
+
+Anyway Ocelot currently supports caching on the URL of the downstream service
+and setting a TTL in seconds to expire the cache. You can also clear the cache for a region
+by calling Ocelot's administration API.
+