Final touches for the quick start quide

doc/ci/quick_start/README.md

@@ -16,7 +16,7 @@ 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
+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.
@@ -120,6 +120,8 @@ Notice that there are two jobs pending which are named after what we wrote in
 `.gitlab-ci.yml`. The red triangle indicates that there is no Runner configured
 yet for these builds.
 
+The next step is to configure a Runner so that it picks the pending jobs.
+
 ## 2. Configuring a Runner
 
 In GitLab, Runners run the builds that you define in `.gitlab-ci.yml`.
@@ -136,8 +138,8 @@ Find more information about different Runners in the
 
 You can find whether any Runners are assigned to your project by going to
 **Settings** -> **Runners**.
-
 Setting up a Runner is easy and straightforward. The official Runner supported
+
 by GitLab is written in Go and can be found at
 <https://gitlab.com/gitlab-org/gitlab-ci-multi-runner>.