diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md
index 6a7b60c2ba5b9b81bdfde0030782a3ff770c98e3..6b8e7fa2ad555e2cb5558fc8fe2c965d7859ac98 100644
--- a/doc/ci/caching/index.md
+++ b/doc/ci/caching/index.md
@@ -491,8 +491,8 @@ job B:
 To fix that, use different `keys` for each job.
 
 In another case, let's assume you have more than one Runners assigned to your
-project, but the distributed cache is not enabled. We want the second time the
-pipeline is run, `job A` and `job B` to re-use their cache (which in this case
+project, but the distributed cache is not enabled. The second time the
+pipeline is run, we want `job A` and `job B` to re-use their cache (which in this case
 will be different):
 
 ```yaml
@@ -518,7 +518,7 @@ job B:
 ```
 
 In that case, even if the `key` is different (no fear of overwriting), you
-might experience the cached files to "get cleaned" before each stage if the
+might experience that the cached files "get cleaned" before each stage if the
 jobs run on different Runners in the subsequent pipelines.
 
 ## Clearing the cache