Copy-edit multi-project pipeline docs

doc/ci/multi_project_pipelines.md

@@ -53,7 +53,7 @@ in a different project.
 
 In GitLab 11.8, GitLab provides a new CI/CD configuration syntax to make this
 task easier, and avoid needing GitLab Runner for triggering cross-project
-pipelines.
+pipelines. The following illustrates configuring a bridge job:
 
 ```yaml
 rspec:
@@ -86,14 +86,14 @@ GitLab does not support status attribution yet, however adding first-class
 
 NOTE: **Note:**
 "Bridge" jobs do not support every configuration entry that a user can use
-in the case of regular jobs. "Bridge" jobs will not to be picked by a runner,
+in the case of regular jobs. "Bridge" jobs will not to be picked by a Runner,
 thus there is no point in adding support for `script`, for example. If a user
-tries to used unsupported configuration syntax, YAML validation will fail upon
+tries to use unsupported configuration syntax, YAML validation will fail upon
 pipeline creation.
 
 ### Specifying a downstream pipeline branch
 
-It is possible to specify a branch name that a downstream pipeline will use.
+It is possible to specify a branch name that a downstream pipeline will use:
 
 ```yaml
 rspec:

doc/ci/yaml/README.md

@@ -1539,12 +1539,13 @@ test:
 from `trigger` definition is started by GitLab, a downstream pipeline gets
 created.
 
-Learm more about [multi-project pipelines](../multi_project_pipelines.html#creating-cross-project-pipelines-from-gitlab-ci-yml).
-
-Example:
+Learm more about [multi-project pipelines](../multi_project_pipelines.md#creating-cross-project-pipelines-from-gitlab-ci-yml).
 
 ### Simple `trigger` syntax
 
+The most simple way to configure a downstream trigger to use `trigger` keyword
+with a full path to a downstream project:
+
 ```yaml
 rspec:
   stage: test
@@ -1557,6 +1558,9 @@ staging:
 
 ### Complex `trigger` syntax
 
+It is possible to configure a branch name that GitLab will use to create
+a downstream pipeline with:
+
 ```yaml
 rspec:
   stage: test