summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDylan Griffith <dyl.griffith@gmail.com>2018-05-08 11:11:48 +0200
committerDylan Griffith <dyl.griffith@gmail.com>2018-05-08 11:11:48 +0200
commita7ca7a315be8c940f6b88fd2a5636304608172d9 (patch)
tree2a3364190b79e62cb7343aa6981393fd74e649f3
parentd9ea1b88b7a8d5a07a7fd0ab3cc83ff4e786c2c1 (diff)
downloadgitlab-ce-10244-ux-improvements-for-group-runners-ce.tar.gz
Capitalize runner in a couple more places10244-ux-improvements-for-group-runners-ce
-rw-r--r--doc/ci/runners/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/runners/README.md b/doc/ci/runners/README.md
index ec1b6fa1dcb..703a7f030ed 100644
--- a/doc/ci/runners/README.md
+++ b/doc/ci/runners/README.md
@@ -33,7 +33,7 @@ are:
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
- and would like all projects to have access to a set of runners. Group Runners
+ and would like all projects to have access to a set of Runners. Group Runners
process jobs using a [FIFO] queue.
A Runner that is specific only runs for the specified project(s). A shared Runner
@@ -132,7 +132,7 @@ To enable/disable a Runner in your project:
> **Note**:
Consider that if you don't lock your specific Runner to a specific project, any
-user with Master role in you project can assign your runner to another arbitrary
+user with Master role in you project can assign your Runner to another arbitrary
project without requiring your authorization, so use it with caution.
An admin can enable/disable a specific Runner for projects: