summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVitali Tatarintev <vtatarintev@gitlab.com>2019-08-13 17:45:32 +0200
committerVitali Tatarintev <vtatarintev@gitlab.com>2019-08-13 17:46:04 +0200
commit5ebff84683361e6514d5d6d9e82ff60f495ec631 (patch)
tree05b2e4d27c138f2d2f60398fd269a01f9ed0b2db
parent6fd2cef0461bfba50fb1d1346c12a47053ec344f (diff)
downloadgitlab-ce-fix-spelling-in-ci-runners-readme.tar.gz
Change spelling of "timeouted" to "timed out"fix-spelling-in-ci-runners-readme
-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 c3678fc948e..8474d4ef66e 100644
--- a/doc/ci/runners/README.md
+++ b/doc/ci/runners/README.md
@@ -319,21 +319,21 @@ How this feature will work:
1. You set the _maximum job timeout_ for a Runner to 24 hours
1. You set the _CI/CD Timeout_ for a project to **2 hours**
1. You start a job
-1. The job, if running longer, will be timeouted after **2 hours**
+1. The job, if running longer, will be timed out after **2 hours**
**Example 2 - Runner timeout not configured**
1. You remove the _maximum job timeout_ configuration from a Runner
1. You set the _CI/CD Timeout_ for a project to **2 hours**
1. You start a job
-1. The job, if running longer, will be timeouted after **2 hours**
+1. The job, if running longer, will be timed out after **2 hours**
**Example 3 - Runner timeout smaller than project timeout**
1. You set the _maximum job timeout_ for a Runner to **30 minutes**
1. You set the _CI/CD Timeout_ for a project to 2 hours
1. You start a job
-1. The job, if running longer, will be timeouted after **30 minutes**
+1. The job, if running longer, will be timed out after **30 minutes**
### Be careful with sensitive information