Automatic merge of gitlab-org/gitlab-ce master

doc/ci/yaml/README.md

@@ -2073,8 +2073,8 @@ include:
     file: /templates/docker-workflow.yml
 ```
 
-The `/templates/docker-workflow.yml` present in `/group/my-project` includes two local files
-of the `/group/my-project`:
+The `/templates/docker-workflow.yml` present in `group/my-project` includes two local files
+of the `group/my-project`:
 
 ```yaml
 include:
@@ -2082,14 +2082,14 @@ include:
   - local: : /templates/docker-testing.yml
 ```
 
-Our `/templates/docker-build.yml` present in `/group/my-project` adds a `docker-build` job:
+Our `/templates/docker-build.yml` present in `group/my-project` adds a `docker-build` job:
 
 ```yaml
 docker-build:
   script: docker build -t my-image .
 ```
 
-Our second `/templates/docker-test.yml` present in `/group/my-project` adds a `docker-test` job:
+Our second `/templates/docker-test.yml` present in `group/my-project` adds a `docker-test` job:
 
 ```yaml
 docker-test:
@@ -2487,9 +2487,9 @@ This can only be used when `custom_build_dir` is enabled in the [Runner's
 configuration](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscustom_build_dir-section).
 This is the default configuration for `docker` and `kubernetes` executor.
 
-By default, GitLab Runner clones the repository in a unique subpath of the 
-`$CI_BUILDS_DIR` directory. However, your project might require the code in a 
-specific directory (Go projects, for example). In that case, you can specify 
+By default, GitLab Runner clones the repository in a unique subpath of the
+`$CI_BUILDS_DIR` directory. However, your project might require the code in a
+specific directory (Go projects, for example). In that case, you can specify
 the `GIT_CLONE_PATH` variable to tell the Runner in which directory to clone the
 repository: