summaryrefslogtreecommitdiff
path: root/doc/ci/runners
diff options
context:
space:
mode:
authorMarcel Amirault <ravlen@gmail.com>2018-09-19 16:03:00 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2018-09-21 16:29:14 +0200
commit109cfd951d0763d72cf0f9b72f45a4a58af76ad1 (patch)
tree98e374609326f00fd8e37c20652ab3d334226d28 /doc/ci/runners
parenta4a7c5316ca9700ec88c24da6b737f47b5cfc61e (diff)
downloadgitlab-ce-109cfd951d0763d72cf0f9b72f45a4a58af76ad1.tar.gz
Correct grammar (setup to set-up) in Docs
Diffstat (limited to 'doc/ci/runners')
-rw-r--r--doc/ci/runners/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ci/runners/README.md b/doc/ci/runners/README.md
index 7859d2ec631..83e0fa34ad6 100644
--- a/doc/ci/runners/README.md
+++ b/doc/ci/runners/README.md
@@ -29,7 +29,7 @@ are:
- **Specific Runners** are useful for jobs that have special requirements or for
projects with a specific demand. If a job has certain requirements, you can set
up the specific Runner with this in mind, while not having to do this for all
- Runners. For example, if you want to deploy a certain project, you can setup
+ Runners. For example, if you want to deploy a certain project, you can set up
a specific Runner to have the right credentials for this. The [usage of tags](#using-tags)
may be useful in this case. Specific Runners process jobs using a [FIFO] queue.
- **Group Runners** are useful when you have multiple projects under one group
@@ -222,7 +222,7 @@ should keep in mind.
### Using tags
-You must setup a Runner to be able to run all the different types of jobs
+You must set up a Runner to be able to run all the different types of jobs
that it may encounter on the projects it's shared over. This would be
problematic for large amounts of projects, if it wasn't for tags.
@@ -298,7 +298,7 @@ and using more secure [Runner Executors](https://docs.gitlab.com/runner/executor
### Forks
Whenever a project is forked, it copies the settings of the jobs that relate
-to it. This means that if you have shared Runners setup for a project and
+to it. This means that if you have shared Runners set up for a project and
someone forks that project, the shared Runners will also serve jobs of this
project.