Add missing raw tags

teesloane · teesloane · commit d2684231bf26 · 2019-08-21T14:51:08.000-04:00
diff --git a/jekyll/_cci2/caching.md b/jekyll/_cci2/caching.md
@@ -134,9 +134,9 @@ Because the second key is less specific than the first, it is more likely that t
 
 Let's walk through how the above cache keys are used in more detail:
 
-Each line in the `keys:` list all manage _one cache_ (each line does **not** correspond to it's own cache). The list of keys (`v1-npm-deps-{{ checksum "package-lock.json" }}` and `v1-npm-deps-`), in this example, represent a **single** cache. When it comes time to restore the cache, CircleCI first validates the cache based on the first (and most specific) key, and then steps through the other keys looking for any other cache-key changes. 
+Each line in the `keys:` list all manage _one cache_ (each line does **not** correspond to it's own cache). The list of keys {% raw %}(`v1-npm-deps-{{ checksum "package-lock.json" }}`{% endraw %} and `v1-npm-deps-`), in this example, represent a **single** cache. When it comes time to restore the cache, CircleCI first validates the cache based on the first (and most specific) key, and then steps through the other keys looking for any other cache-key changes. 
 
-Here, the first key concatenates the checksum  of `package-lock.json` file into the string `v1-npm-deps-`; if this file was to change in your commit, CircleCI would see a new cache-key. 
+https://github.com/circleci/circleci-docs/issues/3650aere, the first key concatenates the checksum  of `package-lock.json` file into the string `v1-npm-deps-`; if this file was to change in your commit, CircleCI would see a new cache-key. 
 
 The next key does not have a dynamic component to it, it simply is a static string: `v1-npm-deps-`. If you would like to invalidate your cache manually, you can bump `v1` to `v2` in your `config.yml` file. In this case, you would now have a new cache key `v2-npm-deps`, which will trigger the storing of a new cache.
 
