From a7ca7a315be8c940f6b88fd2a5636304608172d9 Mon Sep 17 00:00:00 2001 From: Dylan Griffith Date: Tue, 8 May 2018 11:11:48 +0200 Subject: Capitalize runner in a couple more places --- doc/ci/runners/README.md | 4 ++-- 1 file 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: -- cgit v1.2.3