Fixes doc issues and typos

app/views/projects/blob/viewers/_route_map.html.haml

@@ -6,4 +6,4 @@
   This Route Map is invalid:
   = viewer.validation_message
 
-= link_to 'Learn more', help_page_path('ci/environments/index.md', anchor: 'going-from-source-files-to-public-pages')
+= link_to 'Learn more', help_page_path('ci/environments/index.md', anchor: 'go-from-source-files-to-public-pages')

app/views/projects/blob/viewers/_route_map_loading.html.haml

 = loading_icon(css_class: "gl-vertical-align-text-bottom gl-mr-1")
 Validating Route Map…
 
-= link_to 'Learn more', help_page_path('ci/environments/index.md', anchor: 'going-from-source-files-to-public-pages')
+= link_to 'Learn more', help_page_path('ci/environments/index.md', anchor: 'go-from-source-files-to-public-pages')

app/views/projects/feature_flags/edit.html.haml

@@ -9,5 +9,5 @@
                       feature_flags_path: project_feature_flags_path(@project),
                       environments_endpoint: search_project_environments_path(@project, format: :json),
                       strategy_type_docs_page_path: help_page_path('operations/feature_flags', anchor: 'feature-flag-strategies'),
-                      environments_scope_docs_path: help_page_path('ci/environments/index.md', anchor: 'scoping-environments-with-specs'),
+                      environments_scope_docs_path: help_page_path('ci/environments/index.md', anchor: 'scope-environments-with-specs'),
                       feature_flag_issues_endpoint: feature_flag_issues_links_endpoint(@project, @feature_flag, current_user) } }

app/views/projects/feature_flags/new.html.haml

@@ -10,5 +10,5 @@
                      user_callout_id: UserCalloutsHelper::FEATURE_FLAGS_NEW_VERSION,
                      show_user_callout: show_feature_flags_new_version?.to_s,
                      strategy_type_docs_page_path: help_page_path('operations/feature_flags', anchor: 'feature-flag-strategies'),
-                     environments_scope_docs_path: help_page_path('ci/environments/index.md', anchor: 'scoping-environments-with-specs'),
+                     environments_scope_docs_path: help_page_path('ci/environments/index.md', anchor: 'scope-environments-with-specs'),
                      project_id: @project.id } }

doc/api/environments.md

@@ -236,7 +236,7 @@ curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" "https://git
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/296625) in GitLab 14.2.
 
 It schedules for deletion multiple environments that have already been
-[stopped](../ci/environments/index.md#stopping-an-environment) and
+[stopped](../ci/environments/index.md#stop-an-environment) and
 are [in the review app folder](../ci/review_apps/index.md).
 The actual deletion is performed after 1 week from the time of execution.
 

doc/ci/environments/index.md

@@ -356,12 +356,12 @@ For example:
 
 ![Environment URLs in merge request](../img/environments_link_url_mr.png)
 
-#### Going from source files to public pages
+#### Go from source files to public pages
 
 With GitLab [Route Maps](../review_apps/index.md#route-maps), you can go directly
 from source files to public pages in the environment set for Review Apps.
 
-### Stopping an environment
+### Stop an environment
 
 When you stop an environment:
 
@@ -491,7 +491,7 @@ The `auto_stop_in` setting is overwritten and the environment remains active unt
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/20620) in GitLab 12.10.
 
-You can delete [stopped environments](#stopping-an-environment) in the GitLab UI or by using
+You can delete [stopped environments](#stop-an-environment) in the GitLab UI or by using
 [the API](../../api/environments.md#delete-an-environment).
 
 To delete a stopped environment in the GitLab UI:
@@ -525,7 +525,7 @@ build:
     url: https://staging.example.com
 ```
 
-This gives you access to [environment-scoped variables](#scoping-environments-with-specs),
+This gives you access to [environment-scoped variables](#scope-environments-with-specs),
 and can be used to [protect builds from unauthorized access](protected_environments.md).
 
 ### Group similar environments
@@ -608,7 +608,7 @@ GitLab Auto Rollback is turned off by default. To turn it on:
 1. Select the checkbox for **Enable automatic rollbacks**.
 1. Select **Save changes**.
 
-### Monitoring environments
+### Monitor environments
 
 To monitor the behavior of your app as it runs in each environment,
 enable [Prometheus for monitoring system and response metrics](../../user/project/integrations/prometheus.md).
@@ -627,7 +627,7 @@ It may take a minute or two for data to appear after initial deployment.
 
 ![Monitoring dashboard](../img/environments_monitoring.png)
 
-#### Embedding metrics in GitLab Flavored Markdown
+#### Embed metrics in GitLab Flavored Markdown
 
 Metric charts can be embedded in GitLab Flavored Markdown. See [Embedding Metrics in GitLab Flavored Markdown](../../operations/metrics/embed.md) for more details.
 
@@ -680,7 +680,7 @@ fetch line:
 fetch = +refs/environments/*:refs/remotes/origin/environments/*
 ```
 
-### Scoping environments with specs
+### Scope environments with specs
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/2112) in [GitLab Premium](https://about.gitlab.com/pricing/) 9.4.
 > - [Environment scoping for CI/CD variables was moved to all tiers](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/30779) in GitLab 12.2.

doc/ci/environments/protected_environments.md

@@ -122,7 +122,7 @@ access to a protected environment through any of these methods:
 If the user also has push or merge access to the branch deployed on production,
 they have the following privileges:
 
-- [Stopping an environment](index.md#stopping-an-environment).
+- [Stop an environment](index.md#stop-an-environment).
 - [Delete a stopped environment](index.md#delete-a-stopped-environment).
 - [Create an environment terminal](index.md#web-terminals).
 
@@ -215,7 +215,7 @@ configured:
 - Operators should be assigned the [maintainer role](../../user/permissions.md)
   (or above) to the top-level group. They can maintain CI/CD configurations for
   the higher environments (such as production) in the group-level settings page,
-  wnich includes group-level protected environments,
+  which includes group-level protected environments,
   [group-level runners](../runners/runners_scope.md#group-runners),
   [group-level clusters](../../user/group/clusters/index.md), etc. Those
   configurations are inherited to the child projects as read-only entries.
@@ -232,9 +232,9 @@ configured:
     cannot override it.
   - [Project-level protected environments](#protecting-environments) can be
     combined with the group-level setting. If both group-level and project-level
-    environment configurations exist, the user must be allowed in **both**
-    rulesets in order to run a deployment job.
-  - Within a project or a sub-group of the top-level group, developers can be
+    environment configurations exist, to run a deployment job, the user must be allowed in **both**
+    rulesets.
+  - In a project or a subgroup of the top-level group, developers can be
     safely assigned the Maintainer role to tune their lower environments (such
     as `testing`).
 

doc/ci/migration/jenkins.md

@@ -16,7 +16,7 @@ The following list of recommended steps was created after observing organization
 that were able to quickly complete this migration:
 
 1. Start by reading the GitLab CI/CD [Quick Start Guide](../quick_start/index.md) and [important product differences](#important-product-differences).
-1. Learn the importance of [managing the organizational transition](#managing-the-organizational-transition).
+1. Learn the importance of [managing the organizational transition](#manage-organizational-transition).
 1. [Add runners](../runners/index.md) to your GitLab instance.
 1. Educate and enable your developers to independently perform the following steps in their projects:
    1. Review the [Quick Start Guide](../quick_start/index.md) and [Pipeline Configuration Reference](../yaml/index.md).
@@ -39,7 +39,7 @@ to GitLab!
 If you have questions that are not answered here, the [GitLab community forum](https://forum.gitlab.com/)
 can be a great resource.
 
-## Managing the organizational transition
+## Manage organizational transition
 
 An important part of transitioning from Jenkins to GitLab is the cultural and organizational
 changes that comes with the move, and successfully managing them. There are a few
@@ -89,13 +89,13 @@ There are some high level differences between the products worth mentioning:
   permissions), and then any project can use them. This central project could also
   contain scripts or other reusable code.
 - You can also use the [`extends` keyword](../yaml/index.md#extends) to reuse configuration
-  within a single pipeline configuration.
-- All jobs within a single stage always run in parallel, and all stages run in sequence. We are planning
+  in a single pipeline configuration.
+- All jobs in a single stage always run in parallel, and all stages run in sequence. We are planning
   to allow certain jobs to break this sequencing as needed with our [directed acyclic graph](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/47063)
   feature.
 - The [`parallel`](../yaml/index.md#parallel) keyword can automatically parallelize tasks,
   like tests that support parallelization.
-- Normally all jobs within a single stage run in parallel, and all stages run in sequence.
+- Normally all jobs in a single stage run in parallel, and all stages run in sequence.
   There are different [pipeline architectures](../pipelines/pipeline_architectures.md)
   that allow you to change this behavior.
 - The new [`rules` syntax](../yaml/index.md#rules) is the recommended method of
@@ -104,7 +104,7 @@ There are some high level differences between the products worth mentioning:
   fresh environment in each job. Passing artifacts between jobs is controlled using the
   [`artifacts`](../yaml/index.md#artifacts) and [`dependencies`](../yaml/index.md#dependencies)
   keywords. When finished, use the planned [Workspaces](https://gitlab.com/gitlab-org/gitlab/-/issues/29265)
-  feature to more easily persist a common workspace between serial jobs.
+  feature to persist a common workspace between serial jobs.
 - The `.gitlab-ci.yml` file is checked in to the root of your repository, much like a Jenkinsfile, but
   is in the YAML format (see [complete reference](../yaml/index.md)) instead of a Groovy DSL. It's most
   analogous to the declarative Jenkinsfile format.
@@ -122,7 +122,7 @@ There are some high level differences between the products worth mentioning:
 ## Agents vs. runners
 
 Both Jenkins agents and GitLab runners are the hosts that run jobs. To convert the
-Jenkins agent, simply uninstall it and then [install and register the runner](../runners/index.md).
+Jenkins agent, uninstall it and then [install and register the runner](../runners/index.md).
 Runners do not require much overhead, so you can size them similarly to the Jenkins
 agents you were using.
 
@@ -215,7 +215,7 @@ be used by all projects in the group. An instance administrator can set a group
 the source for [instance project templates](../../user/group/custom_project_templates.md),
 which can be used by projects in that instance.
 
-## Converting a declarative Jenkinsfile
+## Convert a declarative Jenkinsfile
 
 A declarative Jenkinsfile contains "Sections" and "Directives" which are used to control the behavior of your
 pipelines. There are equivalents for all of these in GitLab, which we've documented below.

doc/ci/pipelines/index.md

@@ -94,7 +94,7 @@ This table lists the refspecs injected for each pipeline type:
 The refs `refs/heads/<name>` and `refs/tags/<name>` exist in your
 project repository. GitLab generates the special ref `refs/pipelines/<id>` during a
 running pipeline job. This ref can be created even after the associated branch or tag has been
-deleted. It's therefore useful in some features such as [automatically stopping an environment](../environments/index.md#stopping-an-environment),
+deleted. It's therefore useful in some features such as [automatically stopping an environment](../environments/index.md#stop-an-environment),
 and [merge trains](../pipelines/merge_trains.md)
 that might run pipelines after branch deletion.
 

doc/ci/review_apps/index.md

@@ -60,7 +60,7 @@ The process of configuring Review Apps is as follows:
 1. Set up a job in `.gitlab-ci.yml` that uses the [predefined CI/CD variable](../variables/index.md) `${CI_COMMIT_REF_NAME}`
    to create dynamic environments and restrict it to run only on branches.
    Alternatively, you can get a YML template for this job by [enabling review apps](#enable-review-apps-button) for your project.
-1. Optionally, set a job that [manually stops](../environments/index.md#stopping-an-environment) the Review Apps.
+1. Optionally, set a job that [manually stops](../environments/index.md#stop-an-environment) the Review Apps.
 
 ### Enable Review Apps button
 

doc/ci/variables/index.md

@@ -649,7 +649,7 @@ the environment scope of a variable. GitLab does this by
 [defining which environments and corresponding jobs](../environments/index.md)
 the variable can be available for.
 
-To learn more about scoping environments, see [Scoping environments with specs](../environments/index.md#scoping-environments-with-specs).
+To learn more about scoping environments, see [Scoping environments with specs](../environments/index.md#scope-environments-with-specs).
 
 To learn more about ensuring CI/CD variables are only exposed in pipelines running from protected
 branches or tags, see [Protect a CI/CD Variable](#protect-a-cicd-variable).

doc/ci/yaml/index.md

@@ -2214,7 +2214,7 @@ it is set to `manual`, so it needs a [manual action](#whenmanual) from
 the GitLab UI to run.
 
 Also in the example, `GIT_STRATEGY` is set to `none`. If the
-`stop_review_app` job is [automatically triggered](../environments/index.md#stopping-an-environment),
+`stop_review_app` job is [automatically triggered](../environments/index.md#stop-an-environment),
 the runner won't try to check out the code after the branch is deleted.
 
 The example also overwrites global variables. If your `stop` `environment` job depends

doc/operations/metrics/dashboards/settings.md

@@ -46,7 +46,7 @@ existing external dashboards:
 1. Click **Save changes**.
 
 GitLab displays a **View full dashboard** button in the top right corner of your
-[monitoring dashboard](../../../ci/environments/index.md#monitoring-environments)
+[monitoring dashboard](../../../ci/environments/index.md#monitor-environments)
 which opens the URL you provided:
 
 ![External Dashboard Link](img/external_dashboard_link.png)

doc/operations/metrics/index.md

@@ -117,7 +117,7 @@ Custom metrics can be monitored by adding them on the monitoring dashboard page.
 After saving them, they display on the environment metrics dashboard provided that either:
 
 - A [connected Kubernetes cluster](../../user/project/clusters/add_remove_clusters.md)
-  with the matching [environment scope](../../ci/environments/index.md#scoping-environments-with-specs) is used and
+  with the matching [environment scope](../../ci/environments/index.md#scope-environments-with-specs) is used and
   [Prometheus installed on the cluster](../../user/project/integrations/prometheus.md#enabling-prometheus-integration).
 - Prometheus is [manually configured](../../user/project/integrations/prometheus.md#manual-configuration-of-prometheus).
 

doc/topics/autodevops/customize.md

@@ -342,7 +342,7 @@ You must define environment-scoped CI/CD variables for `POSTGRES_ENABLED` and
 `DATABASE_URL` in your project's CI/CD settings:
 
 1. Disable the built-in PostgreSQL installation for the required environments using
-   environment-scoped [CI/CD variables](../../ci/environments/index.md#scoping-environments-with-specs).
+   environment-scoped [CI/CD variables](../../ci/environments/index.md#scope-environments-with-specs).
    For this use case, it's likely that only `production` must be added to this
    list. The built-in PostgreSQL setup for Review Apps and staging is sufficient.
 

doc/topics/autodevops/quick_start_guide.md

@@ -242,7 +242,7 @@ you to common environment tasks:
 - **Re-deploy to environment** (**{repeat}**) - For more information, see
   [Retrying and rolling back](../../ci/environments/index.md#retry-or-roll-back-a-deployment)
 - **Stop environment** (**{stop}**) - For more information, see
-  [Stopping an environment](../../ci/environments/index.md#stopping-an-environment)
+  [Stopping an environment](../../ci/environments/index.md#stop-an-environment)
 
 GitLab displays the [Deploy Board](../../user/project/deploy_boards.md) below the
 environment's information, with squares representing pods in your

doc/topics/autodevops/stages.md

@@ -696,7 +696,7 @@ To use Auto Monitoring:
 1. [Enable Auto DevOps](index.md#enable-or-disable-auto-devops), if you haven't done already.
 1. Navigate to your project's **{rocket}** **CI/CD > Pipelines** and click **Run pipeline**.
 1. After the pipeline finishes successfully, open the
-   [monitoring dashboard for a deployed environment](../../ci/environments/index.md#monitoring-environments)
+   [monitoring dashboard for a deployed environment](../../ci/environments/index.md#monitor-environments)
    to view the metrics of your deployed application. To view the metrics of the
    whole Kubernetes cluster, navigate to **Operations > Metrics**.
 

doc/topics/autodevops/upgrading_auto_deploy_dependencies.md

@@ -117,7 +117,7 @@ If your Auto DevOps project has an active environment that was deployed with the
 1. Deploy your environment as usual. This deployment uses Helm v3.
 1. If the deployment succeeds, you can safely run `<environment-name>:helm-2to3:cleanup`.
    This deletes all Helm v2 release data from the namespace.
-1. Remove the `MIGRATE_HELM_2TO3` CI/CD variable or set it to `false`. You can do this one environment at a time using [environment scopes](../../ci/environments/index.md#scoping-environments-with-specs).
+1. Remove the `MIGRATE_HELM_2TO3` CI/CD variable or set it to `false`. You can do this one environment at a time using [environment scopes](../../ci/environments/index.md#scope-environments-with-specs).
 
 #### In-Cluster PostgreSQL Channel 2
 

doc/topics/autodevops/upgrading_postgresql.md

@@ -175,7 +175,7 @@ deleted, you can choose to retain the [persistent volume](#retain-persistent-vol
 
 NOTE:
 You can also
-[scope](../../ci/environments/index.md#scoping-environments-with-specs) the
+[scope](../../ci/environments/index.md#scope-environments-with-specs) the
 `AUTO_DEVOPS_POSTGRES_CHANNEL`, `AUTO_DEVOPS_POSTGRES_DELETE_V1` and
 `POSTGRES_VERSION` variables to specific environments, e.g. `staging`.
 
@@ -190,7 +190,7 @@ higher*. This is the
    minimum PostgreSQL version supported by Auto DevOps. See also the list of
    [tags available](https://hub.docker.com/r/bitnami/postgresql/tags).
 1. Set `PRODUCTION_REPLICAS` to `0`. For other environments, use
-   `REPLICAS` with an [environment scope](../../ci/environments/index.md#scoping-environments-with-specs).
+   `REPLICAS` with an [environment scope](../../ci/environments/index.md#scope-environments-with-specs).
 1. If you have set the `DB_INITIALIZE` or `DB_MIGRATE` variables, either
    remove the variables, or rename the variables temporarily to
    `XDB_INITIALIZE` or the `XDB_MIGRATE` to effectively disable them.

doc/user/instance/clusters/index.md

@@ -28,7 +28,7 @@ GitLab tries to match clusters in the following order:
 - Instance-level clusters.
 
 To be selected, the cluster must be enabled and
-match the [environment selector](../../../ci/environments/index.md#scoping-environments-with-specs).
+match the [environment selector](../../../ci/environments/index.md#scope-environments-with-specs).
 
 ## Cluster environments **(PREMIUM)**
 

doc/user/project/integrations/prometheus.md

@@ -109,7 +109,7 @@ can use only one:
   [Cluster precedence](../../instance/clusters/index.md#cluster-precedence).
 - If you have managed Prometheus applications installed on multiple Kubernetes
   clusters at the **same** level, the Prometheus application of a cluster with a
-  matching [environment scope](../../../ci/environments/index.md#scoping-environments-with-specs) is used.
+  matching [environment scope](../../../ci/environments/index.md#scope-environments-with-specs) is used.
 
 ## Determining the performance impact of a merge