summaryrefslogtreecommitdiff
path: root/doc/ci/quick_start
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axilleas@axilleas.me>2015-11-05 22:49:57 +0200
committerAchilleas Pipinellis <axilleas@axilleas.me>2015-12-01 08:58:09 +0200
commit2c30d11e80a4bb4112d01be7e1fbe51a321b3beb (patch)
tree3e4ce4bed2435f4e7b72a997aac7d54211a3ff26 /doc/ci/quick_start
parent5f6117c0aa391a6e9c96493ca01a8a23eb40f0cd (diff)
downloadgitlab-ce-2c30d11e80a4bb4112d01be7e1fbe51a321b3beb.tar.gz
Clean up intro
Diffstat (limited to 'doc/ci/quick_start')
-rw-r--r--doc/ci/quick_start/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/quick_start/README.md b/doc/ci/quick_start/README.md
index 74626c8f8a4..92dad2be3e8 100644
--- a/doc/ci/quick_start/README.md
+++ b/doc/ci/quick_start/README.md
@@ -16,8 +16,8 @@ In brief, the steps needed to have a working CI can be summed up to:
1. Configure a Runner
From there on, on every push to your git repository the build will be
-automagically started by the Runner and will appear under the project's
-`/builds` page.
+automagically started by the runner and will appear under the project's `/builds`
+page.
Now, let's break it down to pieces and work on solving the GitLab CI puzzle.