summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Milonakis <michail.milonakis@gmail.com>2016-02-18 16:07:13 +0200
committerMike Milonakis <michail.milonakis@gmail.com>2016-02-18 16:07:13 +0200
commitcbc73ccdf8c5be2e2f0ca38afa5e9c195a15c003 (patch)
tree55891cd9724cdf25bb0034f4d91128f81a72a411
parenta4ffdf922da488b2f04e81f5fc29243413e42cd3 (diff)
downloadgitlab-ce-cbc73ccdf8c5be2e2f0ca38afa5e9c195a15c003.tar.gz
Typo fix in README.md
-rw-r--r--doc/ci/quick_start/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/quick_start/README.md b/doc/ci/quick_start/README.md
index ae7b760fa67..50554d8ee3d 100644
--- a/doc/ci/quick_start/README.md
+++ b/doc/ci/quick_start/README.md
@@ -124,7 +124,7 @@ In GitLab, Runners run the builds that you define in `.gitlab-ci.yml`.
A Runner can be a virtual machine, a VPS, a bare-metal machine, a docker
container or even a cluster of containers. GitLab and the Runners communicate
through an API, so the only needed requirement is that the machine on which the
-Runner is configured to has Internet access.
+Runner is configured to have Internet access.
A Runner can be specific to a certain project or serve multiple projects in
GitLab. If it serves all projects it's called a _Shared Runner_.