Documentation now matches UI copy

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md
index 495ec099111..8b2ce425cf5 100644
--- a/doc/ci/caching/index.md
+++ b/doc/ci/caching/index.md
@@ -29,7 +29,7 @@ needed to compile the project:
   Cache was designed to be used to speed up invocations of subsequent runs of a
   given job, by keeping things like dependencies (e.g., npm packages, Go vendor
   packages, etc.) so they don't have to be re-fetched from the public internet.
-  While the cache can be abused to pass intermediate build results between 
+  While the cache can be abused to pass intermediate build results between
   stages, there may be cases where artifacts are a better fit.
 - `artifacts`: **Use for stage results that will be passed between stages.**
   Artifacts were designed to upload some compiled/generated bits of the build,
@@ -40,10 +40,10 @@ needed to compile the project:
   comply to this rule trigger an unintuitive and illogical error message (an
   enhancement is discussed at
   [https://gitlab.com/gitlab-org/gitlab-ce/issues/15530](https://gitlab.com/gitlab-org/gitlab-ce/issues/15530)
-  ). Artifacts need to be uploaded to the GitLab instance (not only the GitLab 
-  runner) before the next stage job(s) can start, so you need to evaluate 
-  carefully whether your bandwidth allows you to profit from parallelization 
-  with stages and shared artifacts before investing time in changes to the 
+  ). Artifacts need to be uploaded to the GitLab instance (not only the GitLab
+  runner) before the next stage job(s) can start, so you need to evaluate
+  carefully whether your bandwidth allows you to profit from parallelization
+  with stages and shared artifacts before investing time in changes to the
   setup.
 
 
@@ -90,7 +90,7 @@ cache, when declaring `cache` in your jobs, use one or a mix of the following:
   that will be only available to a particular project.
 - [Use a `key`](../yaml/README.md#cache-key) that fits your workflow (e.g.,
   different caches on each branch). For that, you can take advantage of the
-  [CI/CD predefined variables](../variables/README.md#predefined-variables-environment-variables).
+  [CI/CD predefined variables](../variables/README.md#predefined-environment-variables).
 
 TIP: **Tip:**
 Using the same Runner for your pipeline, is the most simple and efficient way to