fix more lint errors

Author: rosieyohannan

docs/guides/modules/integration/pages/gitlab-integration.adoc

@@ -8,7 +8,7 @@ This page walks you through integrating a GitLab project with CircleCI. The sect
 [#overview]
 == What is GitLab CI/CD?
 
-GitLab CI/CD allows you to build, test (continuous integration) and deploy (continuous deployment, continuous delivery) your projects each time a developer pushes a change to the codebase, and/or when a merge request is created. As an alternative, you can integrate with CircleCI to manage your CI/CD pipelines. If you use GitLab (SaaS or Self-managed) for version control and code storage, GitLab CI/CD is enabled for your project by default.
+GitLab CI/CD allows you to build, test and deploy your projects each time a developer pushes a change to the codebase, and/or when a merge request is created. As an alternative, you can integrate with CircleCI to manage your CI/CD pipelines. If you use GitLab (SaaS or Self-managed) for version control and code storage, GitLab CI/CD is enabled for your project by default.
 
 Integrate with CircleCI to access features for automated software delivery:
 
@@ -51,7 +51,7 @@ You can choose a sample `.circleci/config.yml` to best fit your project from a v
 
 The first two options (**Fastest** and **Faster**) automatically trigger a pipeline once you create the project.
 --
-GitLab Self-Managed::
+GitLab self-managed::
 +
 --
 NOTE: **Remove GitLab CI/CD config** You should remove the `.gitlab-ci.yml` file from projects you integrate with CircleCI. This prevents you from having CI/CD builds happening in both systems. There is an option to _disable_ GitLab CI/CD for a project in the GitLab UI but using this is **not recommended**.
@@ -92,13 +92,13 @@ image::guides:ROOT:gl-sm-create-project.png[Create a new project in a self-manag
 
 . Copy and paste the SSH host key from your self-managed instance into **known_hosts**. Select **Connect**.
 +
-NOTE: If you are using both CircleCI's Bitbucket Data Center and GitLab Self-Managed integrations, there is a known bug in the menu:Organization Settings[Integrations] section of the CircleCI web app. Adding a `known_hosts` to one integration will populate the `known_hosts`  for the other integration. To use both Bitbucket Data Center and GitLab Self-Managed integrations within the same CircleCI organization, add both respective `known_hosts` values to the one input field separated by a new line.
+NOTE: If you are using both CircleCI's Bitbucket Data Center and GitLab self-managed integrations, there is a known bug in the menu:Organization Settings[Integrations] section of the CircleCI web app. Adding a `known_hosts` to one integration will populate the `known_hosts`  for the other integration. To use both Bitbucket Data Center and GitLab self-managed integrations within the same CircleCI organization, add both respective `known_hosts` values to the one input field separated by a new line.
 
 . Once your account is successfully authorized, select the repository for your CircleCI project, and enter a project name.
 
 . Finally, select **Create Project**. You will then be redirected to the newly-created project's Pipelines page.
 
-The express CircleCI configuration setup is not currently available for GitLab Self-managed projects. You will need to add a `.circleci/config.yml` file in your repository if it has not yet been set up. If the repository you selected already contains a `.circleci/config.yml`, you will need to save a commit in the repository to see your pipeline on the dashboard.
+The express CircleCI configuration setup is not currently available for GitLab self-managed projects. You will need to add a `.circleci/config.yml` file in your repository if it has not yet been set up. If the repository you selected already contains a `.circleci/config.yml`, you will need to save a commit in the repository to see your pipeline on the dashboard.
 --
 ====
 
@@ -127,7 +127,7 @@ When you create a new project using the **Fastest** (use an existing `config.yml
 
 If you use the **Fast** config setup, the pipeline is not triggered until you save the `.circleci/config.yml` by clicking the **Commit and Run** button in the web app.
 --
-GitLab Self-Managed::
+GitLab self-managed::
 +
 --
 If you have not already done so, add a `.circleci` directory to the root of the repository, then add a `config.yml` file in that directory.
@@ -226,7 +226,7 @@ Add or remove users, and manage user roles for the organization as well as user
 [#organization-settings-integrations]
 === Integrations (GitLab self-managed only)
 
-For GitLab Self-managed organizations, you may connect additional self-managed instances to be integrated with your organization.
+For GitLab self-managed organizations, you may connect additional self-managed instances to be integrated with your organization.
 
 . Navigate to **Integrations** within **Organization Settings** to add a new instance.
 +
@@ -241,7 +241,7 @@ For GitLab.com, account integrations can be managed under your xref:#user-accoun
 [#establish the authenticity of an SSH host]
 ==== Establish the authenticity of an SSH host
 
-For GitLab self-managed instances, it is necessary to add the SSH host keys to a "known hosts" file (`~/.ssh/known_hosts`) so that CircleCI can verify that the host it is connecting to is authentic. The **known_hosts** input stores your instance's public host keys so CircleCI jobs can verify the remote host's identity when checking out code.
+For GitLab self-managed instances, you need to add the SSH host keys to a "known hosts" file (`~/.ssh/known_hosts`). This enables CircleCI to verify that the host it is connecting to is authentic. The **known_hosts** input stores your instance's public host keys so CircleCI jobs can verify the remote host's identity when checking out code.
 
 SSH keys for remote servers can be fetched by running `ssh-keyscan <host>`, for example, `ssh-keyscan test-gitlab.circleci.com`.
 

docs/guides/modules/orchestrate/pages/github-trigger-event-options.adoc

@@ -23,7 +23,7 @@ When you create or set up a project in CircleCI you will set up your first pipel
 
 include::ROOT:partial$tips/check-github-type-org.adoc[]
 
-If your CircleCI organization is integrated with GitHub only through the **GitHub App** (see tip above), you will see trigger options when creating a project in the CircleCI web app, and you have the option to change the trigger options for your first trigger. You can also set up additional triggers during project creation, or setup/edit later in your menu:Project settings[Project Setup].
+If your CircleCI organization is integrated with GitHub only through the **GitHub App**, you will see trigger options when creating a project in the CircleCI web app. You have the option to change the trigger options for your first trigger when setting the project up. You can also set up additional triggers during project creation, or setup/edit later in your menu:Project settings[Project Setup].
 
 .Trigger options during project creation
 image::guides:ROOT:triggers/create-project-run-on.png[Create a project trigger and access trigger options]
@@ -95,7 +95,7 @@ All pipelines triggered by link:https://docs.github.com/en/webhooks/webhook-even
 * `pipeline.event.github.pull_request.head.ref`: the name of the *head* branch of the PR - that is the branch containing the changes to be merged.
 * `pipeline.event.github.pull_request.draft`: a boolean value indicating whether the pull request is a draft.
 +
-**Usage example**: To trigger a pipeline on _PR opened or pushed to, default branch and tag pushes_, but ensure that it never runs if the event is associated with a PR that is marked as draft, use the following filter.
+**Example**: To trigger a pipeline on `PR opened or pushed to, default branch and tag pushes`, and ensure that it never runs if the event is associated with a draft PR, use the following:
 +
 [,yaml]
 ----
@@ -113,7 +113,7 @@ workflows:
 
 * `pipeline.event.github.pull_request.title`: the title of the pull request.
 * `pipeline.event.github.pull_request.number`: the numeric identifier of the pull request.
-* `pipeline.event.github.pull_request.merged`: a boolean that indicates whether the PR was merged or not. 
+* `pipeline.event.github.pull_request.merged`: a boolean that indicates whether the PR was merged or not.
 
 These values are extracted directly from the GitHub event payload. The part after prefix `pipeline.event.github.*` matches the corresponding field in the pull request event structure described in link:https://docs.github.com/en/webhooks/webhook-events-and-payloads#pull_request[the GitHub docs].
 
@@ -142,7 +142,7 @@ include::guides:ROOT:partial$app-navigation/steps-to-project-settings.adoc[]
 .Trigger options under Project settings
 image::guides:ROOT:triggers/select-when-to-run.png[Set a trigger option for a project trigger]
 .
-** Select the *Event Source* repository from the dropdown. This defaults to the config source repository. If you change it to a repository that does not match the pipeline's config or checkout source, you will be prompted to specify a fixed branch to be used respectively for fetching config and checking out code. 
+** Select the *Event Source* repository from the dropdown. This defaults to the config source repository. If you change it to a repository that does not match the pipeline's checkout source, you can specify a branch to be used for fetching config and code checkout.
 . Select btn:[Save].
 
 To verify your trigger is set up correctly, trigger an event (open a PR) from your repository.
@@ -153,7 +153,12 @@ To verify your trigger is set up correctly, trigger an event (open a PR) from yo
 
 No, different trigger event options cannot be combined in a single trigger. However, you can create multiple triggers for the same pipeline that listen for events from the same repository, with each trigger using a different trigger event option.
 
-For example, by having one trigger with the trigger option "PR opened" and a second trigger with the trigger option "PR merged", your pipeline will trigger whenever a PR is opened or merged.
+For example, by having the following:
+
+* One trigger with the trigger option "PR opened"
+* One trigger with the trigger option "PR merged"
+
+Your pipeline will trigger whenever a PR is opened or merged.
 
 == Next steps
 

docs/guides/modules/orchestrate/pages/set-up-triggers.adoc

@@ -17,7 +17,7 @@ NOTE: **Using CircleCI server?** The Pipeline and Trigger pages under Project Se
 
 The pipeline and trigger options and features available to you depend on how your code is integrated and where it is stored. For a feature availability overview, see the xref:integration:version-control-system-integration-overview.adoc[VCS integration overview] page.
 
-There are broadly three types of triggers:
+Triggers are available in the following types:
 
 * VCS triggers.
 * Custom webhooks used for triggering pipelines from external services.