Add latest changes from gitlab-org/gitlab@13-1-stable-ee

1 files changed, 5 insertions, 2 deletions

diff --git a/doc/ci/quick_start/README.md b/doc/ci/quick_start/README.md
index a14cfcfa9ed..25469570603 100644
--- a/doc/ci/quick_start/README.md
+++ b/doc/ci/quick_start/README.md
@@ -1,4 +1,7 @@
 ---
+stage: Verify
+group: Continuous Integration
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
 type: reference
 ---
 
@@ -165,7 +168,7 @@ The next step is to configure a Runner so that it picks the pending jobs.
 ## Configuring a Runner
 
 In GitLab, Runners run the jobs that you define in `.gitlab-ci.yml`. A Runner
-can be a virtual machine, a VPS, a bare-metal machine, a docker container or
+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 requirement is that the Runner's machine has network access to the
 GitLab server.
@@ -184,7 +187,7 @@ can be found at <https://docs.gitlab.com/runner/>.
 In order to have a functional Runner you need to follow two steps:
 
 1. [Install it](https://docs.gitlab.com/runner/install/)
-1. [Configure it](../runners/README.md#registering-a-specific-runner)
+1. [Configure it](https://docs.gitlab.com/runner/configuration/)
 
 Follow the links above to set up your own Runner or use a Shared Runner as
 described in the next section.