Merge branch 'docs-whitespace-cleanup' into 'master'

EOL whitespace cleanup in docs

See merge request gitlab-org/gitlab!55957

doc/administration/geo/glossary.md

@@ -23,7 +23,7 @@ these definitions yet.
 |---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------|
 | Node                      | An individual server that runs GitLab either with a specific role or as a whole (e.g. a Rails application node). In a cloud context this can be a specific machine type.                 | GitLab       | instance, server                                |
 | Site                      | One or a collection of nodes running a single GitLab application. A site can be single-node or multi-node.                                                                             | GitLab       | deployment, installation instance               |
-| Single-node site          | A specific configuration of GitLab that uses exactly one node.                                                                                                                     | GitLab       | single-server, single-instance 
+| Single-node site          | A specific configuration of GitLab that uses exactly one node.                                                                                                                     | GitLab       | single-server, single-instance
 | Multi-node site           | A specific configuration of GitLab that uses more than one node.                                                                                                                   | GitLab       | multi-server, multi-instance, high availability |
 | Primary site              | A GitLab site that is configured to be read and writable. There can only be a single primary site.                                                                                     | Geo-specific | Geo deployment, Primary node                    |
 | Secondary site(s)         | GitLab site that is configured to be read-only. There can be one or more secondary sites.                                                                                              | Geo-specific | Geo deployment, Secondary node                  |

doc/administration/maintenance_mode/index.md

@@ -172,7 +172,7 @@ You can monitor queues and disable jobs in **Admin Area > Monitoring > Backgroun
 
 [Incident management](../../operations/incident_management/index.md) functions will be limited. The creation of [alerts](../../operations/incident_management/alerts.md) and [incidents](../../operations/incident_management/incidents.md#incident-creation) will be paused entirely. Notifications and paging on alerts and incidents will therefore be disabled.
 
-### Feature flags 
+### Feature flags
 
 - [Development feature flags](../../development/feature_flags/index.md) cannot be turned on or off through the API, but can be toggled through the Rails console.
 - [The feature flag service](../../operations/feature_flags.md) will respond to feature flag checks but feature flags cannot be toggled

doc/administration/repository_storage_paths.md

@@ -83,7 +83,7 @@ For [backups](../raketasks/backup_restore.md) to work correctly:
 Omnibus GitLab takes care of these issues for you, but for source installations you should be extra
 careful.
 
-While restoring a backup, the current contents of `/home/git/repositories` are moved to 
+While restoring a backup, the current contents of `/home/git/repositories` are moved to
 `/home/git/repositories.old`. If `/home/git/repositories` is a mount point, then `mv` would be
 moving things between mount points, and problems can occur.
 

doc/administration/troubleshooting/elasticsearch.md

@@ -358,10 +358,10 @@ Elasticsearch administrator has more experience with.
 
 ### Troubleshooting background migrations
 
-Troubleshooting background migration failures can be difficult and may require contacting 
+Troubleshooting background migration failures can be difficult and may require contacting
 an Elasticsearch administrator or GitLab Support.
 
-The best place to start while debugging issues with a background migration is the 
+The best place to start while debugging issues with a background migration is the
 [`elasticsearch.log` file](../logs.md#elasticsearchlog). Migrations will
 print information while a migration is in progress and any errors encountered.
 Apply fixes for any errors found in the log and retry the migration.

doc/ci/cloud_deployment/ecs/quick_start_guide.md

@@ -145,7 +145,7 @@ Note the following:
 - Optionally, you can set a SSH key pair in the creation form. This allows you to SSH to the EC2
   instance for debugging.
 - If you don't choose an existing VPC, it creates a new VPC by default. This could cause an error if
-  it reaches the maximum allowed number of internet gateways on your account. 
+  it reaches the maximum allowed number of internet gateways on your account.
 - The cluster requires an EC2 instance, meaning it costs you [according to the instance-type](https://aws.amazon.com/ec2/pricing/on-demand/).
 
 ### Create an ECS Service

doc/development/code_review.md

@@ -283,7 +283,7 @@ first time.
   you forget to remove any debugging code?
 - Consider providing instructions on how to test the merge request. This can be
   helpful for reviewers not familiar with the product feature or area of the codebase.
-- If you know your change depends on another being merged first, note it in the 
+- If you know your change depends on another being merged first, note it in the
   description and set an [merge request dependency](../user/project/merge_requests/merge_request_dependencies.md).
 - Be grateful for the reviewer's suggestions. (`Good call. I'll make that change.`)
 - Don't take it personally. The review is of the code, not of you.
@@ -348,7 +348,7 @@ experience, refactors the existing code). Then:
     optionally resolve within the merge request or follow-up at a later stage.
   - There's a [Chrome/Firefox add-on](https://gitlab.com/conventionalcomments/conventional-comments-button) which you can use to apply [Conventional Comment](https://conventionalcomments.org/) prefixes.
 - Ensure there are no open dependencies. Check [related issues](../user/project/issues/related_issues.md) for blockers. Clarify with the author(s)
-if necessary. If blocked by one or more open MRs, set an [MR dependency](../user/project/merge_requests/merge_request_dependencies.md). 
+if necessary. If blocked by one or more open MRs, set an [MR dependency](../user/project/merge_requests/merge_request_dependencies.md).
 - After a round of line notes, it can be helpful to post a summary note such as
   "Looks good to me", or "Just a couple things to address."
 - Assign the merge request to the author if changes are required following your

doc/development/contributing/merge_request_workflow.md

@@ -69,7 +69,7 @@ request is as follows:
       request addresses. Referenced issues do not [close automatically](../../user/project/issues/managing_issues.md#closing-issues-automatically).
       You must close them manually once the merge request is merged.
    1. The MR must include *Before* and *After* screenshots if UI changes are made.
-   1. Include any steps or setup required to ensure reviewers can view the changes you've made (e.g. include any information about feature flags).     
+   1. Include any steps or setup required to ensure reviewers can view the changes you've made (e.g. include any information about feature flags).
 1. If you're allowed to, set a relevant milestone and [labels](issue_workflow.md).
 1. UI changes should use available components from the GitLab Design System,
    [Pajamas](https://design.gitlab.com/).

doc/development/directory_structure.md

@@ -65,7 +65,7 @@ end
 ```
 
 On the other hand, a feature category may sometimes be too granular. Features tend to be
-treated differently according to Product and Marketing, while they may share a lot of 
+treated differently according to Product and Marketing, while they may share a lot of
 domain models and behavior under the hood. In this case, having too many bounded contexts
 could make them shallow and more coupled with other contexts.
 

doc/development/documentation/styleguide/index.md

@@ -108,7 +108,7 @@ of GitLab more efficient.
 
 New information that would be useful toward the future usage or troubleshooting
 of GitLab should not be written directly in a forum or other messaging system,
-but added to a documentation MR and then referenced, as described above. 
+but added to a documentation MR and then referenced, as described above.
 
 The more we reflexively add information to the documentation, the more
 the documentation helps others efficiently accomplish tasks and solve problems.

doc/development/fe_guide/accessibility.md

@@ -93,7 +93,7 @@ Prefer **no** `tabindex` to using `tabindex`, since:
 ### Avoid using `tabindex="0"` to make an element interactive
 
 Use interactive elements instead of `div`s and `span`s.
-For example: 
+For example:
 
 - If the element should be clickable, use a `button`
 - If the element should be text editable, use an `input` or `textarea`
@@ -186,8 +186,8 @@ Use of ARIA would then only occur in [GitLab UI](https://gitlab.com/gitlab-org/g
 
 We have two options for Web accessibility testing:
 
-- [axe](https://www.deque.com/axe/) for [Firefox](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/) 
-- [axe](https://www.deque.com/axe/) for [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd) 
+- [axe](https://www.deque.com/axe/) for [Firefox](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/)
+- [axe](https://www.deque.com/axe/) for [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd)
 
 ### Other links
 

doc/development/fe_guide/dependencies.md

@@ -20,7 +20,7 @@ This distinction is used by omnibus to determine which dependencies it requires
 
 Exceptions are made for some tools that we require in the
 `compile-production-assets` CI job such as `webpack-bundle-analyzer` to analyze our
-production assets post-compile. 
+production assets post-compile.
 
 ## Updating dependencies
 

doc/development/fe_guide/security.md

@@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 ## Resources
 
-[Mozilla’s HTTP Observatory CLI](https://github.com/mozilla/http-observatory-cli) and 
+[Mozilla’s HTTP Observatory CLI](https://github.com/mozilla/http-observatory-cli) and
 [Qualys SSL Labs Server Test](https://www.ssllabs.com/ssltest/analyze.html) are good resources for finding
 potential problems and ensuring compliance with security best practices.
 

doc/development/feature_flags/development.md

@@ -410,16 +410,16 @@ Feature.enable(:feature_flag_name, Project.find_by_full_path("root/my-project"))
 
 ### Removing a feature flag locally (in development)
 
-Once you have manually enabled or disabled a feature flag to test in your local environment, 
+Once you have manually enabled or disabled a feature flag to test in your local environment,
 the flag's default value gets overwritten and it takes precedence over the `default_enabled` value.
 This can cause confusion when changing the flag's `default_enabled` attribute.
 
 For example, flags are commonly enabled and disabled several times during the development process.
 When we finally enable the flag by default, we set `default_enabled: true` in the YAML file.
 
-- If the flag was manually enabled before setting `default_enabled: true`, the feature will be enabled. 
+- If the flag was manually enabled before setting `default_enabled: true`, the feature will be enabled.
 Not because of the `default_enabled: true` value of the flag but because it was manually enabled.
-- If the flag was manually disabled before setting `default_enabled: true`, the feature will 
+- If the flag was manually disabled before setting `default_enabled: true`, the feature will
 remain disabled. The `default_enabled: true` value does not take precendence over the explicit `false`
 value set when disabling it manually.
 

doc/development/graphql_guide/graphql_pro.md

@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # GraphQL Pro
 
-GraphQL has become a key technology in GitLab and is implemented using the 
+GraphQL has become a key technology in GitLab and is implemented using the
 [GraphQL Ruby gem](https://graphql-ruby.org). As such, we've purchased a subscription to
 [GraphQL Pro](https://graphql.pro).
 
@@ -15,7 +15,7 @@ The main purpose is for support. Per the website:
 > As a GraphQL::Pro customer, you get direct access to the GraphQL Ruby gem
 > creator and maintainer. Get prioritized support for issues and requests.
 
-Note that we **cannot** use the Pro version directly in our product, since we are 
+Note that we **cannot** use the Pro version directly in our product, since we are
 an Open Core product - we can not require customers to purchase the Pro version, nor can we ship it.
 
 Details on the billing account and gem licensing can be found in the Engineering 1Password vault.

doc/development/migration_style_guide.md

@@ -1028,10 +1028,10 @@ D, [2020-07-06T00:37:12.653648 #130101] DEBUG -- :   ↳ config/initializers/con
 
 ## High traffic tables
 
-Here's a list of current [high-traffic tables](https://gitlab.com/gitlab-org/gitlab/-/blob/master/rubocop/rubocop-migrations.yml). 
+Here's a list of current [high-traffic tables](https://gitlab.com/gitlab-org/gitlab/-/blob/master/rubocop/rubocop-migrations.yml).
 
 Determining what tables are high-traffic can be difficult. Self-managed instances might use
-different features of GitLab with different usage patterns, thus making assumptions based 
+different features of GitLab with different usage patterns, thus making assumptions based
 on GitLab.com not enough.
 
 To identify a high-traffic table for GitLab.com the following measures are considered.

doc/development/transient/prevention-patterns.md

@@ -10,7 +10,7 @@ This page will cover architectural patterns and tips for developers to follow to
 
 ## Common root causes
 
-We've noticed a few root causes that come up frequently when addressing transient bugs. 
+We've noticed a few root causes that come up frequently when addressing transient bugs.
 
 - Needs better state management in the backend or frontend.
 - Frontend code needs improvements.

doc/security/two_factor_authentication.md

@@ -137,7 +137,7 @@ Once the OTP is verified, Git over SSH operations can be used for a session dura
 2FA does not protect users with compromised *private* SSH keys.
 
 Once an OTP is verified, anyone can run Git over SSH with that private SSH key for
-the configured [session duration](../user/admin_area/settings/account_and_limit_settings.md#customize-session-duration-for-git-operations-when-2fa-is-enabled). 
+the configured [session duration](../user/admin_area/settings/account_and_limit_settings.md#customize-session-duration-for-git-operations-when-2fa-is-enabled).
 
 ### Enable or disable Two-factor Authentication (2FA) for Git operations
 

doc/subscriptions/gitlab_com/index.md

@@ -37,8 +37,8 @@ Every occupied seat is counted in the subscription, with the following exception
 NOTE:
 To support the open source community and encourage the development of open
 source projects, GitLab grants access to **Ultimate** features for all GitLab SaaS
-**public** projects, regardless of the subscription. GitLab also provides qualifying 
-open source projects with 50,000 CI minutes and free access to the Ultimate tier for 
+**public** projects, regardless of the subscription. GitLab also provides qualifying
+open source projects with 50,000 CI minutes and free access to the Ultimate tier for
 groups through the [GitLab for Open Source program](https://about.gitlab.com/solutions/open-source/).
 
 ## Obtain a GitLab SaaS subscription

doc/topics/autodevops/stages.md

@@ -595,7 +595,7 @@ to restrict connections to and from selected pods, namespaces, and the internet.
 
 As the default network plugin for Kubernetes (`kubenet`)
 [does not implement](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#kubenet)
-support for it, you must have [Cilium](https://docs.cilium.io/en/v1.8/intro/) as your Kubernetes network plugin. 
+support for it, you must have [Cilium](https://docs.cilium.io/en/v1.8/intro/) as your Kubernetes network plugin.
 
 The [Cilium](https://cilium.io/) network plugin can be
 installed as a [cluster application](../../user/clusters/applications.md#install-cilium-using-gitlab-cicd)

doc/user/application_security/dast/index.md

@@ -130,22 +130,22 @@ Find the latest DAST versions on the [Releases](https://gitlab.com/gitlab-org/se
 ## Deployment options
 
 Depending on the complexity of the target application, there are a few options as to how to deploy and configure
-the DAST template. A set of example applications with their configurations have been made available in our 
+the DAST template. A set of example applications with their configurations have been made available in our
 [DAST demonstrations](https://gitlab.com/gitlab-org/security-products/demos/dast/) project.
 
 ### Review Apps
 
 Review Apps are the most involved method of deploying your DAST target application. To assist in the process,
-we created a Review App deployment using Google Kubernetes Engine (GKE). This example can be found in our 
-[Review Apps - GKE](https://gitlab.com/gitlab-org/security-products/demos/dast/review-app-gke) project along with detailed 
-instructions in the [README.md](https://gitlab.com/gitlab-org/security-products/demos/dast/review-app-gke/-/blob/master/README.md) 
+we created a Review App deployment using Google Kubernetes Engine (GKE). This example can be found in our
+[Review Apps - GKE](https://gitlab.com/gitlab-org/security-products/demos/dast/review-app-gke) project along with detailed
+instructions in the [README.md](https://gitlab.com/gitlab-org/security-products/demos/dast/review-app-gke/-/blob/master/README.md)
 on how to configure Review Apps for DAST.
 
 ### Docker Services
 
 If your application utilizes Docker containers you have another option for deploying and scanning with DAST.
-After your Docker build job completes and your image is added to your container registry, you can utilize the image as a 
-[service](../../../ci/docker/using_docker_images.md#what-is-a-service). 
+After your Docker build job completes and your image is added to your container registry, you can utilize the image as a
+[service](../../../ci/docker/using_docker_images.md#what-is-a-service).
 
 By using service definitions in your `gitlab-ci.yml`, you can scan services with the DAST analyzer.
 

doc/user/clusters/agent/index.md

@@ -231,7 +231,7 @@ the Agent in subsequent steps. You can create an Agent record either:
 
 ### Install the Agent into the cluster
 
-Next, install the in-cluster component of the Agent. 
+Next, install the in-cluster component of the Agent.
 
 #### One-liner installation
 

doc/user/group/saml_sso/index.md

@@ -365,7 +365,7 @@ the user gets the highest access level from the groups. For example, if one grou
 is linked as `Guest` and another `Maintainer`, a user in both groups gets `Maintainer`
 access.
 
-Users who are not members of any mapped SAML groups are removed from the GitLab group. 
+Users who are not members of any mapped SAML groups are removed from the GitLab group.
 
 You can prevent accidental member removal. For example, if you have a SAML group link for `Owner` level access
 in a top-level group, you should also set up a group link for all other members.

doc/user/packages/container_registry/index.md

@@ -577,7 +577,7 @@ Here are examples of regex patterns you may want to use:
   (?:v.+|master|release.*)
   ```
 
-### Set cleanup limits to conserve resources 
+### Set cleanup limits to conserve resources
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/288812) in GitLab 13.9.
 > - It's [deployed behind a feature flag](../../feature_flags.md), disabled by default.
@@ -595,7 +595,7 @@ To prevent server resource starvation, the following application settings are av
 - `container_registry_delete_tags_service_timeout`. The maximum time, in seconds, that the cleanup process can take to delete a batch of tags.
 - `container_registry_cleanup_tags_service_max_list_size`. The maximum number of tags that can be deleted in a single execution. Additional tags must be deleted in another execution.
    We recommend starting with a low number, like `100`, and increasing it after monitoring that container images are properly deleted.
-   
+
 For self-managed instances, those settings can be updated in the [Rails console](../../../administration/operations/rails_console.md#starting-a-rails-console-session):
 
   ```ruby

doc/user/profile/index.md

@@ -243,14 +243,14 @@ To set the busy status indicator, either:
 
   Issue and merge request sidebar:
 
-  | Sidebar| Collapsed sidebar | 
+  | Sidebar| Collapsed sidebar |
   | --- | --- |
-  | ![Busy status - sidebar](img/busy_indicator_sidebar_v13_9.png) | ![Busy status - sidebar collapsed](img/busy_indicator_sidebar_collapsed_v13_9.png) | 
+  | ![Busy status - sidebar](img/busy_indicator_sidebar_v13_9.png) | ![Busy status - sidebar collapsed](img/busy_indicator_sidebar_collapsed_v13_9.png) |
 
   Notes:
 
   | Notes | Note headers |
-  | --- | --- | 
+  | --- | --- |
   | ![Busy status - notes](img/busy_indicator_notes_v13_9.png) | ![Busy status - note header](img/busy_indicator_note_header_v13_9.png) |
 
 ### Disable busy status feature

doc/user/project/merge_requests/versions.md

@@ -64,7 +64,7 @@ In GitLab 12.10, we added a comparison mode, which
 shows a diff calculated by simulating how it would look like once merged - a more accurate
 representation of the changes rather than using the base of the two
 branches. The new mode is available from the comparison target drop down
-by selecting **master (HEAD)**. In GitLab 13.9, it 
+by selecting **master (HEAD)**. In GitLab 13.9, it
 [replaced](https://gitlab.com/gitlab-org/gitlab/-/issues/198458) the
 old default comparison. For technical details, additional information is available in the
 [developer documentation](../../../development/diffs.md#merge-request-diffs-against-the-head-of-the-target-branch).

doc/user/project/service_desk.md

@@ -73,7 +73,7 @@ To enable Service Desk in your project:
 1. Enable the **Activate Service Desk** toggle. This reveals a unique email address to email issues
    to the project.
 
-Service Desk is now enabled for this project! To access it in a project, in the left sidebar, select 
+Service Desk is now enabled for this project! To access it in a project, in the left sidebar, select
 **Issues > Service Desk**.
 
 WARNING: