summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndy Allan <gitlab@gravitystorm.co.uk>2019-05-17 09:55:16 +0000
committerAndy Allan <gitlab@gravitystorm.co.uk>2019-05-17 09:55:16 +0000
commit89ef857dbe32e9349e30ebb6f083d74895b752fd (patch)
tree7bb48e299b8786e6f947864ee4194b8a1f8c4a5c
parentf2cb5220112f1f7fe4c29c4b07998f77a67291a2 (diff)
downloadgitlab-ce-89ef857dbe32e9349e30ebb6f083d74895b752fd.tar.gz
Remove stray full stop from the middle of the sentence
-rw-r--r--doc/ci/caching/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md
index 3f72fe3e9eb..d703e106e76 100644
--- a/doc/ci/caching/index.md
+++ b/doc/ci/caching/index.md
@@ -100,7 +100,7 @@ From the perspective of the Runner, in order for cache to work effectively, one
of the following must be true:
- Use a single Runner for all your jobs.
-- Use multiple Runners (in autoscale mode or not) that use.
+- Use multiple Runners (in autoscale mode or not) that use
[distributed caching](https://docs.gitlab.com/runner/configuration/autoscale.html#distributed-runners-caching),
where the cache is stored in S3 buckets (like shared Runners on GitLab.com).
- Use multiple Runners (not in autoscale mode) of the same architecture that