fix lint errors

Author: rosieyohannan

docs/guides/modules/ROOT/partials/pipelines-and-triggers/custom-webhook-setup.adoc

@@ -2,7 +2,7 @@ include::ROOT:partial$app-navigation/steps-to-project-settings.adoc[]
 . Select **Project Setup** in the sidebar.
 . If there is already a GitHub App pipeline set up that you want to trigger with your custom webhook, proceed to the **Triggers** step below (step 5).  If not, select btn:[Add Pipeline]. You can find guidance on setting up a pipeline in the xref:orchestrate:pipelines.adoc#add-or-edit-a-pipeline[Pipelines overview and setup] page.
 +
-NOTE: If you have not installed the CircleCI GitHub App into your GitHub organization you will be prompted to do so. Installing the GitHub App is a one-time step that can be done by an organization admin. Once installed, further GitHub App pipelines can be set up without this installation step. For a detailed guide to using both OAuth and GitHub App integrations, see the xref:integration:using-the-circleci-github-app-in-an-oauth-org.adoc[Using the CircleCI GitHub App in an OAuth organization] page. If you run into an issue when installing the CircleCI GitHub App (for example, the App looks installed on GitHub, but does not show up on CircleCI), submit a request through link:https://forms.gle/aaVERZNNvzsDLJJ46[this form].
+NOTE: If you have not installed the CircleCI GitHub App into your GitHub organization you will be prompted to do so. Installing the GitHub App is a one-time step that can be done by an organization admin. Once installed, further GitHub App pipelines can be set up without this installation step. For a detailed guide to using both OAuth and GitHub App integrations, see the xref:integration:using-the-circleci-github-app-in-an-oauth-org.adoc[Using the CircleCI GitHub App in an OAuth organization] page. If you run into issues when installing the GitHub App, for example, App looks installed on GitHub, but does not show up on CircleCI, submit a request through link:https://forms.gle/aaVERZNNvzsDLJJ46[this form].
 . Select btn:[Custom webhook +] at the bottom of the pipeline box.
 . Enter a descriptive name for the webhook event.
 . Enter the name of the event source for the trigger. For example, if you are setting up a custom webhook to run pipelines on events from Datadog, enter "Datadog" here.

docs/guides/modules/ROOT/partials/troubleshoot/pipelines-troubleshoot-snip.adoc

@@ -67,7 +67,7 @@ my-user/couchdb:1.6.1
 [#best-practice-for-specifying-image-versions]
 === What is the best practice for specifying image versions?
 
-It is best practice *not* to use the `latest` tag for specifying image versions. It is also best practice to use a specific version and tag, for example `cimg/ruby:3.0.4-browsers`, to pin down the image and prevent upstream changes to your containers when the underlying base distribution changes. For example, specifying only `cimg/ruby:3.0.4` could result in unexpected changes from `browsers` to `node`. For more context, refer to xref:guides:execution-managed:using-docker.adoc#docker-image-best-practices[Docker image best practices], and xref:guides:execution-managed:circleci-images.adoc#best-practices[CircleCI image best practices].
+It is best practice *not* to use the `latest` tag for specifying image versions. It is also best practice to use a specific version and tag, for example `cimg/ruby:3.0.4-browsers`. Using a specific version and tag pins down the image and prevents upstream changes to your containers when the underlying base distribution changes. For example, specifying only `cimg/ruby:3.0.4` could result in unexpected changes from `browsers` to `node`. For more context, refer to xref:guides:execution-managed:using-docker.adoc#docker-image-best-practices[Docker image best practices], and xref:guides:execution-managed:circleci-images.adoc#best-practices[CircleCI image best practices].
 
 [#set-the-timezone-in-docker-images]
 === How can I set the timezone in Docker images?

docs/guides/modules/getting-started/pages/create-project.adoc

@@ -163,7 +163,7 @@ image::guides:ROOT:create-project/authorize-bitbucket-data-center.png[Choose a r
 
 CircleCI uses the specified `.circleci/config.yml` file to run your pipeline. You can see the output on the pipelines page. To make changes to your pipeline, edit the `.circleci/config.yml` file in your repository.
 
-Through creating a project and connecting your code you have set up your pipeline and a trigger. The default trigger runs your pipeline when a change is committed to your code. You can create more triggers at menu:Project settings[Project Setup] if your project integrates with GitHub, or at menu:Project settings[Triggers] if it integrates with Gitlab or Bitbucket. For more information, see the xref:orchestrate:set-up-triggers.adoc[Set up triggers] page.
+Through creating a project and connecting your code you have set up your pipeline and a trigger. The default trigger runs your pipeline when a change is committed to your code. You can create more triggers at menu:Project settings[Project Setup] if your project integrates with GitHub, or at menu:Project settings[Triggers] if it integrates with GitLab or Bitbucket. For more information, see the xref:orchestrate:set-up-triggers.adoc[Set up triggers] page.
 
 [#set-up-a-project]
 === Set up a project

docs/guides/modules/orchestrate/pages/set-up-multiple-configuration-files-for-a-project.adoc

@@ -49,7 +49,7 @@ include::ROOT:partial$app-navigation/steps-to-project-settings.adoc[]
 +
 . Select btn:[Add Pipeline].
 +
-NOTE: If you have not installed the CircleCI GitHub App into your GitHub organization you will be prompted to do so. Installing the GitHub App is a one-time step that can be done by an organization admin. Once installed, further GitHub App pipelines can be setup without this installation step. For a guide to using both OAuth and GitHub App integrations, see the xref:integration:using-the-circleci-github-app-in-an-oauth-org.adoc[Using the CircleCI GitHub App in an OAuth organization] page. If you run into an issue when installing the CircleCI GitHub App (for example, App looks installed on GitHub, but does not show up on CircleCI), submit a request through link:https://forms.gle/aaVERZNNvzsDLJJ46[this form].
+NOTE: If you have not installed the CircleCI GitHub App into your GitHub organization you will be prompted to do so. Installing the GitHub App is a one-time step that can be done by an organization admin. Once installed, further GitHub App pipelines can be setup without this installation step. For a guide to using both OAuth and GitHub App integrations, see the xref:integration:using-the-circleci-github-app-in-an-oauth-org.adoc[Using the CircleCI GitHub App in an OAuth organization] page. If you run into issues when installing the GitHub App, for example, App looks installed on GitHub, but does not show up on CircleCI, submit a request through link:https://forms.gle/aaVERZNNvzsDLJJ46[this form].
 . Complete the required form fields:
 ** Give your pipeline a descriptive name.
 ** Under *Config Source* select the repository where the config file is stored. This can be the same repository as your code or a different repository.