Fix trailing whitespace in docs

These pages contained trailing whitespace somewhere; this merge
request removes the trailing whitespace.

doc/administration/gitaly/troubleshooting.md

@@ -226,8 +226,8 @@ update the secrets file on the Gitaly server to match the Gitaly client, then
 ### Repository pushes fail with a `deny updating a hidden ref` error
 
 Due to [a change](https://gitlab.com/gitlab-org/gitaly/-/merge_requests/3426)
-introduced in GitLab 13.12, Gitaly has read-only, internal GitLab references that users are not 
-permitted to update. If you attempt to update internal references with `git push --mirror`, Git 
+introduced in GitLab 13.12, Gitaly has read-only, internal GitLab references that users are not
+permitted to update. If you attempt to update internal references with `git push --mirror`, Git
 returns the rejection error, `deny updating a hidden ref`.
 
 The following references are read-only:
@@ -243,7 +243,7 @@ To mirror-push branches and tags only, and avoid attempting to mirror-push prote
 git push origin +refs/heads/*:refs/heads/* +refs/tags/*:refs/tags/*
 ```
 
-Any other namespaces that the admin wants to push can be included there as well via additional patterns. 
+Any other namespaces that the admin wants to push can be included there as well via additional patterns.
 
 ### Command line tools cannot connect to Gitaly
 

doc/administration/pages/index.md

@@ -1266,7 +1266,7 @@ Alternatively, run the CI pipelines of those projects that contain a `pages` job
 
 ## 404 or 500 error when accessing GitLab Pages in a Geo setup
 
-Pages sites are only available on the primary Geo site, while the codebase of the project is available on all sites. 
+Pages sites are only available on the primary Geo site, while the codebase of the project is available on all sites.
 
 If you try to access a Pages page on a secondary site, you will get a 404 or 500 HTTP code depending on the access control.
 

doc/administration/postgresql/replication_and_failover.md

@@ -183,7 +183,7 @@ Few things to remember about the service itself:
 
 - The service runs as the same system account as the database
   - In the package, this is by default `gitlab-psql`
-- If you use a non-default user account for PgBouncer service (by default `pgbouncer`), you need to specify this username. 
+- If you use a non-default user account for PgBouncer service (by default `pgbouncer`), you need to specify this username.
 - Passwords are stored in the following locations:
   - `/etc/gitlab/gitlab.rb`: hashed, and in plain text
   - `/var/opt/gitlab/pgbouncer/pg_auth`: hashed

doc/administration/troubleshooting/log_parsing.md

@@ -55,7 +55,7 @@ zcat @400000006026b71d1a7af804.s | (head -1; tail -1) | jq '.time'
 zcat some_json.log.25.gz | (head -1; tail -1) | jq '.time'
 ```
 
-#### Get activity for correlation ID across multiple JSON logs in chronological order 
+#### Get activity for correlation ID across multiple JSON logs in chronological order
 
 ```shell
 grep -hR <correlationID> | jq -c -R 'fromjson?' | jq -C -s 'sort_by(.time)'  | less -R

doc/api/oauth2.md

@@ -84,8 +84,8 @@ Before starting the flow, generate the `STATE`, the `CODE_VERIFIER` and the `COD
   `CODE_VERIFIER`
   - The SHA256 hash must be in binary format before encoding.
   - In Ruby, you can set that up with `Base64.urlsafe_encode64(Digest::SHA256.digest(CODE_VERIFIER), padding: false)`.
-  - For reference, a `CODE_VERIFIER` string of `ks02i3jdikdo2k0dkfodf3m39rjfjsdk0wk349rj3jrhf` when hashed 
-    and encoded using the Ruby snippet above produces a `CODE_CHALLENGE` string 
+  - For reference, a `CODE_VERIFIER` string of `ks02i3jdikdo2k0dkfodf3m39rjfjsdk0wk349rj3jrhf` when hashed
+    and encoded using the Ruby snippet above produces a `CODE_CHALLENGE` string
     of `2i0WFA-0AerkjQm4X4oDEhqA17QIAKNjXpagHBXmO_U`.
 
 1. Request authorization code. To do that, you should redirect the user to the
@@ -138,7 +138,7 @@ Before starting the flow, generate the `STATE`, the `CODE_VERIFIER` and the `COD
    ```
 
    Example response:
-   
+
    ```json
    {
      "access_token": "c97d1fe52119f38c7f67f0a14db68d60caa35ddc86fd12401718b649dcfa9c68",

doc/ci/ci_cd_for_external_repos/github_integration.md

@@ -29,7 +29,7 @@ repositories:
 
 1. In GitHub, create a token:
    1. Open <https://github.com/settings/tokens/new>.
-   1. Create a **Personal Access Token**. 
+   1. Create a **Personal Access Token**.
    1. Enter a **Token description** and update the scope to allow
       `repo` and `admin:repo_hook` so that GitLab can access your project,
       update commit statuses, and create a web hook to notify GitLab of new commits.
@@ -57,7 +57,7 @@ To manually enable GitLab CI/CD for your repository:
 
 1. In GitHub, create a token:
    1. Open <https://github.com/settings/tokens/new>.
-   1. Create a **Personal Access Token**. 
+   1. Create a **Personal Access Token**.
    1. Enter a **Token description** and update the scope to allow
       `repo` so that GitLab can access your project and update commit statuses.
 1. In GitLab, create a project:

doc/ci/runners/build_cloud/macos/environment.md

@@ -4,12 +4,12 @@ group: Runner
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# VM instances and images for Build Cloud for macOS 
+# VM instances and images for Build Cloud for macOS
 
 When you use the Build Cloud for macOS:
 
-- Each of your jobs runs in a newly provisioned VM, which is dedicated to the specific job. 
-- The VM is active only for the duration of the job and immediately deleted. 
+- Each of your jobs runs in a newly provisioned VM, which is dedicated to the specific job.
+- The VM is active only for the duration of the job and immediately deleted.
 
 ## VM types
 

doc/ci/runners/build_cloud/macos_build_cloud.md

@@ -12,7 +12,7 @@ of all the capabilities of the GitLab single DevOps platform and not have to man
 build environment.
 
 Build Cloud runners for macOS are in [Beta](https://about.gitlab.com/handbook/product/gitlab-the-product/#beta)
-and shouldn't be relied upon for mission-critical production jobs. 
+and shouldn't be relied upon for mission-critical production jobs.
 
 ## Quickstart
 

doc/ci/yaml/index.md

@@ -430,7 +430,7 @@ In `include` sections in your `.gitlab-ci.yml` file, you can use:
 - [Project variables](../variables/index.md#add-a-cicd-variable-to-a-project)
 - [Group variables](../variables/index.md#add-a-cicd-variable-to-a-group)
 - [Instance variables](../variables/index.md#add-a-cicd-variable-to-an-instance)
-- Project [predefined variables](../variables/predefined_variables.md).   
+- Project [predefined variables](../variables/predefined_variables.md).
 
 ```yaml
 include:

doc/development/api_graphql_styleguide.md

@@ -941,7 +941,7 @@ end
 ```
 
 While you can use the same resolver class in two different places,
-such as in two different fields where the same object is exposed, 
+such as in two different fields where the same object is exposed,
 you should never re-use resolver objects directly. Resolvers have a complex life-cycle, with
 authorization, readiness and resolution orchestrated by the framework, and at
 each stage [lazy values](#laziness) can be returned to take advantage of batching

doc/development/experiment_guide/index.md

@@ -12,8 +12,8 @@ Experiments are run as an A/B/n test, and are behind an [experiment feature flag
 
 ## Experiment rollout issue
 
-Each experiment should have an [experiment rollout](https://gitlab.com/groups/gitlab-org/-/boards/1352542) issue to track the experiment from rollout through to cleanup and removal. 
-The rollout issue is similar to a feature flag rollout issue, and is also used to track the status of an experiment. 
+Each experiment should have an [experiment rollout](https://gitlab.com/groups/gitlab-org/-/boards/1352542) issue to track the experiment from rollout through to cleanup and removal.
+The rollout issue is similar to a feature flag rollout issue, and is also used to track the status of an experiment.
 When an experiment is deployed, the due date of the issue should be set (this depends on the experiment but can be up to a few weeks in the future).
 After the deadline, the issue needs to be resolved and either:
 
@@ -46,7 +46,7 @@ For more information, see [Implementing an A/B/n experiment using GLEX](gitlab_e
 
 There are still some longer running experiments using the [`Exerimentation Module`](experimentation.md).
 
-Both approaches use [experiment](../feature_flags/index.md#experiment-type) feature flags. 
+Both approaches use [experiment](../feature_flags/index.md#experiment-type) feature flags.
 `GLEX` is the preferred option for new experiments.
 
 ### Add new icons and illustrations for experiments

doc/development/i18n/externalization.md

@@ -137,7 +137,7 @@ The `~/locale` module exports the following key functions for externalization:
 - `s__()` (namespaced double underscore parenthesis)
 - `__()` Mark content for translation (note the double underscore).
 - `s__()` Mark namespaced content for translation
-- `n__()` Mark pluralized content for translation 
+- `n__()` Mark pluralized content for translation
 
 ```javascript
 import { __, s__, n__ } from '~/locale';

doc/install/aws/eks_clusters_aws.md

@@ -29,7 +29,7 @@ Using the EKS Quick Start or `eksctl` enables the following when building an EKS
 - It can deploy high value-add items to the cluster, including:
   - A bastion host to keep the cluster endpoint private and possible perform performance testing.
   - Prometheus and Grafana for monitoring.
-- EKS Autoscaler for automatic K8s Node scaling. 
+- EKS Autoscaler for automatic K8s Node scaling.
 - 2 or 3 Availability Zones (AZ) spread for balance between High Availability (HA) and cost control.
 - Ability to specify spot compute.
 

doc/install/aws/gitlab_hybrid_on_aws.md

@@ -115,7 +115,7 @@ Some services, such as log aggregation, outbound email are not specified by GitL
 
 - [3K AutoScale GPT Test Results](https://gitlab.com/gitlab-com/alliances/aws/implementation-patterns/gitlab-cloud-native-hybrid-on-eks/-/blob/master/gitlab-alliances-testing/3K/3k-QuickStart-AutoScale-ARM-RDS-Cache_v13-12-3-ee_2021-07-23_194200/3k-QuickStart-AutoScale-ARM-RDS-Cache_v13-12-3-ee_2021-07-23_194200_results.txt)
 
- **Deploy Now** 
+ **Deploy Now**
  Deploy Now links leverage the AWS Quick Start automation and only prepopulate the number of instances and instance types for the Quick Start based on the Bill of Meterials below. You must provide appropriate input for all other parameters by following the guidance in the [Quick Start documentation's Deployment steps](https://aws-quickstart.github.io/quickstart-eks-gitlab/#_deployment_steps) section.
 
 - **Deploy Now: AWS Quick Start for 2 AZs**
@@ -215,7 +215,7 @@ If EKS node autoscaling is employed, it is likely that your average loading will
 - [5K Full Scale GPT Test Results](https://gitlab.com/gitlab-com/alliances/aws/implementation-patterns/gitlab-cloud-native-hybrid-on-eks/-/blob/master/gitlab-alliances-testing/5K/5k-QuickStart-ARM-RDS-Redis_v13-12-3-ee_2021-07-23_140128/5k-QuickStart-ARM-RDS-Redis_v13-12-3-ee_2021-07-23_140128_results.txt)
 - [5K AutoScale from 25% GPT Test Results](https://gitlab.com/gitlab-com/alliances/aws/implementation-patterns/gitlab-cloud-native-hybrid-on-eks/-/blob/master/gitlab-alliances-testing/5K/5k-QuickStart-AutoScale-From-25Percent-ARM-RDS-Redis_v13-12-3-ee_2021-07-24_102717/5k-QuickStart-AutoScale-From-25Percent-ARM-RDS-Redis_v13-12-3-ee_2021-07-24_102717_results.txt)
 
-**Deploy Now** 
+**Deploy Now**
 
 Deploy Now links leverage the AWS Quick Start automation and only prepopulate the number of instances and instance types for the Quick Start based on the Bill of Meterials below. You must provide appropriate input for all other parameters by following the guidance in the [Quick Start documentation's Deployment steps](https://aws-quickstart.github.io/quickstart-eks-gitlab/#_deployment_steps) section.
 
@@ -266,7 +266,7 @@ If EKS node autoscaling is employed, it is likely that your average loading will
 - [10K Full Scale GPT Test Results](https://gitlab.com/gitlab-com/alliances/aws/implementation-patterns/gitlab-cloud-native-hybrid-on-eks/-/blob/master/gitlab-alliances-testing/10K/GL-CloudNative-10k-RDS-Graviton_v13-12-3-ee_2021-07-08_194647/GL-CloudNative-10k-RDS-Graviton_v13-12-3-ee_2021-07-08_194647_results.txt)
 - [10K AutoScale GPT Test Results](https://gitlab.com/gitlab-com/alliances/aws/implementation-patterns/gitlab-cloud-native-hybrid-on-eks/-/blob/master/gitlab-alliances-testing/10K/GL-CloudNative-10k-AutoScaling-Test_v13-12-3-ee_2021-07-09_115139/GL-CloudNative-10k-AutoScaling-Test_v13-12-3-ee_2021-07-09_115139_results.txt)
 
-**Deploy Now** 
+**Deploy Now**
 
 Deploy Now links leverage the AWS Quick Start automation and only prepopulate the number of instances and instance types for the Quick Start based on the Bill of Meterials below. You must provide appropriate input for all other parameters by following the guidance in the [Quick Start documentation's Deployment steps](https://aws-quickstart.github.io/quickstart-eks-gitlab/#_deployment_steps) section.
 
@@ -316,7 +316,7 @@ If EKS node autoscaling is employed, it is likely that your average loading will
 - [50K Full Scale GPT Test Results](https://gitlab.com/gitlab-com/alliances/aws/implementation-patterns/gitlab-cloud-native-hybrid-on-eks/-/blob/master/gitlab-alliances-testing/50K/50k-Fixed-Scale-Test_v13-12-3-ee_2021-08-13_172819/50k-Fixed-Scale-Test_v13-12-3-ee_2021-08-13_172819_results.txt)
 - [50K AutoScale GPT Test Results](https://gitlab.com/gitlab-com/alliances/aws/implementation-patterns/gitlab-cloud-native-hybrid-on-eks/-/blob/master/gitlab-alliances-testing/50K/50k-AutoScale-Test_v13-12-3-ee_2021-08-13_192633/50k-AutoScale-Test_v13-12-3-ee_2021-08-13_192633.txt)
 
-**Deploy Now** 
+**Deploy Now**
 
 Deploy Now links leverage the AWS Quick Start automation and only prepopulate the number of instances and instance types for the Quick Start based on the Bill of Meterials below. You must provide appropriate input for all other parameters by following the guidance in the [Quick Start documentation's Deployment steps](https://aws-quickstart.github.io/quickstart-eks-gitlab/#_deployment_steps) section.
 

doc/install/aws/gitlab_sre_for_aws.md

@@ -48,7 +48,7 @@ Background:
 - When not using provisioned EBS IO, EBS volume size determines the IO level, so provisioning volumes that are much larger than needed can be the least expensive way to improve EBS IO.
 - Only use nitro instance types due to higher IO and EBS optimization.
 - Use Amazon Linux 2 to ensure the best disk and memory optimizations (for example, ENA network adapters and drivers).
-- If GitLab backup scripts are used, they need a temporary space location large enough to hold 2 times the current size of the Git File system. If that will be done on Gitaly servers, separate volumes should be used. 
+- If GitLab backup scripts are used, they need a temporary space location large enough to hold 2 times the current size of the Git File system. If that will be done on Gitaly servers, separate volumes should be used.
 
 ### Gitaly HA in EKS quick start
 

doc/install/aws/index.md

@@ -53,7 +53,7 @@ Testing-backed architectural qualification is a fundamental concept behind imple
 Implementation patterns enable platform-specific terminology, best practice architecture, and platform-specific build manifests:
 
 - Implementation patterns are more vendor specific. For instance, advising specific compute instances / VMs / nodes instead of vCPUs or other generalized measures.
-- Implementation patterns are oriented to implementing good architecture for the vendor in view. 
+- Implementation patterns are oriented to implementing good architecture for the vendor in view.
 - Implementation patterns are written to an audience who is familiar with building on the infrastructure that the implementation pattern targets. For example, if the implementation pattern is for GCP, the specific terminology of GCP is used - including using the specific names for PaaS services.
 - Implementation patterns can test and qualify if the versions of PaaS available are compatible with GitLab (for example, PostgreSQL, Redis, etc.).
 

doc/topics/autodevops/stages.md

@@ -696,7 +696,7 @@ To use Auto Monitoring:
 
 1. [Install and configure the Auto DevOps requirements](requirements.md).
 1. [Enable Auto DevOps](index.md#enable-or-disable-auto-devops), if you haven't done already.
-1. On the left sidebar, select **CI/CD > Pipelines**. 
+1. On the left sidebar, select **CI/CD > Pipelines**.
 1. Select **Run pipeline**.
 1. After the pipeline finishes successfully, open the
    [monitoring dashboard for a deployed environment](../../ci/environments/index.md#monitor-environments)

doc/user/admin_area/license.md

@@ -167,7 +167,7 @@ your license. However, if you have 111, you must purchase more users before you
 
 ### There is a connectivity issue
 
-In GitLab 14.1 and later, to activate your subscription, your GitLab instance must be connected to the internet. 
+In GitLab 14.1 and later, to activate your subscription, your GitLab instance must be connected to the internet.
 
 If you have an offline or airgapped environment, you can [upload a license file](license.md#activate-gitlab-ee-with-a-license-file) instead.
 

doc/user/admin_area/moderate_users.md

@@ -199,7 +199,7 @@ Users can also be activated using the [GitLab API](../../api/users.md#activate-u
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/327353) in GitLab 14.2.
 
-GitLab administrators can ban and unban users. Banned users are blocked, and their issues are hidden. 
+GitLab administrators can ban and unban users. Banned users are blocked, and their issues are hidden.
 The banned user's comments are still displayed. Hiding a banned user's comments is [tracked in this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/327356).
 
 ### Ban a user

doc/user/application_security/dependency_list/index.md

@@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/10075) in GitLab Ultimate 12.0.
 
 Use the dependency list to review your project's dependencies and key
-details about those dependencies, including their known vulnerabilities. It is a collection of dependencies in your project, including existing and new findings. 
+details about those dependencies, including their known vulnerabilities. It is a collection of dependencies in your project, including existing and new findings.
 
 To see the dependency list, go to your project and select **Security & Compliance > Dependency List**.
 

doc/user/clusters/migrating_from_gma_to_project_template.md

@@ -14,7 +14,7 @@ some recorded videos with [live examples](#live-examples).
 1. Familiarize yourself with the [management project template](management_project_template.md).
 1. Create a [new project](../project/working_with_projects.md#create-a-project), either:
    - From a template, selecting the **GitLab Cluster Management** project template.
-   - Importing the project from the URL `https://gitlab.com/gitlab-org/project-templates/cluster-management.git`. This 
+   - Importing the project from the URL `https://gitlab.com/gitlab-org/project-templates/cluster-management.git`. This
      is useful if you are using GitLab Self-Managed and you want to use the latest version of the template.
 
    This is your cluster management project.

doc/user/compliance/license_compliance/index.md

@@ -249,7 +249,7 @@ generate a key store file, see the
 
 License Compliance uses Java 8 by default. You can specify a different Java version using `LM_JAVA_VERSION`.
 
-`LM_JAVA_VERSION` only accepts versions: 8, 11, 14, 15. 
+`LM_JAVA_VERSION` only accepts versions: 8, 11, 14, 15.
 
 ### Selecting the version of Python
 

doc/user/project/settings/import_export.md

@@ -219,7 +219,7 @@ GitLab.com may have [different settings](../../gitlab_com/index.md#importexport)
 
 ## Troubleshooting
 
-### Import workaround for large repositories 
+### Import workaround for large repositories
 
 [Maximum import size limitations](#import-the-project)
 can prevent an import from being successful.
@@ -227,7 +227,7 @@ If changing the import limits is not possible,
 the following local workflow can be used to temporarily
 reduce the repository size for another import attempt.
 
-1. Create a temporary working directory from the export: 
+1. Create a temporary working directory from the export:
 
     ```shell
     EXPORT=<filename-without-extension>

doc/user/project/settings/project_access_tokens.md

@@ -25,7 +25,7 @@ Project access tokens:
   should:
   - Review their security and compliance policies with regards to
     [user self-enrollment](../../admin_area/settings/sign_up_restrictions.md#disable-new-sign-ups).
-  - Consider [disabling project access tokens](#enable-or-disable-project-access-token-creation) to 
+  - Consider [disabling project access tokens](#enable-or-disable-project-access-token-creation) to
     lower potential abuse.
 - Are also supported on GitLab SaaS Premium and above (excluding [trial licenses](https://about.gitlab.com/free-trial/).)