Remove unnecessary whitespace from end of lines of topics

doc/administration/database_load_balancing.md

@@ -208,7 +208,7 @@ response timings.
 ## Primary sticking
 
 After a write has been performed, GitLab sticks to using the primary for a
-certain period of time, scoped to the user that performed the write. GitLab 
+certain period of time, scoped to the user that performed the write. GitLab
 reverts back to using secondaries when they have either caught up, or after 30
 seconds.
 

doc/administration/gitaly/praefect.md

@@ -1453,7 +1453,7 @@ To determine the current primary Gitaly node for a specific Praefect node:
 - Use the `Shard Primary Election` [Grafana chart](#grafana) on the [`Gitlab Omnibus - Praefect` dashboard](https://gitlab.com/gitlab-org/grafana-dashboards/-/blob/master/omnibus/praefect.json).
   This is recommended.
 - If you do not have Grafana set up, use the following command on each host of each
-  Praefect node: 
+  Praefect node:
 
   ```shell
   curl localhost:9652/metrics | grep gitaly_praefect_primaries`

doc/administration/nfs.md

@@ -22,7 +22,7 @@ file system performance, see
 ## Gitaly and NFS deprecation
 
 WARNING:
-From GitLab 14.0, enhancements and bug fixes for NFS for Git repositories are no longer 
+From GitLab 14.0, enhancements and bug fixes for NFS for Git repositories are no longer
 considered and customer technical support is considered out of scope.
 [Read more about Gitaly and NFS](gitaly/index.md#nfs-deprecation-notice) and
 [the correct mount options to use](#upgrade-to-gitaly-cluster-or-disable-caching-if-experiencing-data-loss).

doc/administration/operations/rails_console.md

@@ -152,7 +152,7 @@ Traceback (most recent call last):
 In case you encounter a similar error to this:
 
 ```plaintext
-[root ~]# sudo gitlab-rails runner helloworld.rb 
+[root ~]# sudo gitlab-rails runner helloworld.rb
 Please specify a valid ruby command or the path of a script to run.
 Run 'rails runner -h' for help.
 

doc/administration/packages/container_registry.md

@@ -310,7 +310,7 @@ and GCS, this transfer is achieved with a copy followed by a delete. With object
 these deleted temporary upload artifacts are kept as non-current versions, therefore increasing the
 storage bucket size. To ensure that non-current versions are deleted after a given amount of time,
 you should configure an object lifecycle policy with your storage provider.
-   
+
 You can configure the Container Registry to use various storage backends by
 configuring a storage driver. By default the GitLab Container Registry
 is configured to use the [file system driver](#use-file-system)
@@ -1075,15 +1075,15 @@ If the registry fails to authenticate valid login attempts, you get the followin
 ```shell
 # docker login gitlab.company.com:4567
 Username: user
-Password: 
+Password:
 Error response from daemon: login attempt to https://gitlab.company.com:4567/v2/ failed with status: 401 Unauthorized
 ```
 
 And more specifically, this appears in the `/var/log/gitlab/registry/current` log file:
 
 ```plaintext
-level=info msg="token signed by untrusted key with ID: "TOKE:NL6Q:7PW6:EXAM:PLET:OKEN:BG27:RCIB:D2S3:EXAM:PLET:OKEN"" 
-level=warning msg="error authorizing context: invalid token" go.version=go1.12.7 http.request.host="gitlab.company.com:4567" http.request.id=74613829-2655-4f96-8991-1c9fe33869b8 http.request.method=GET http.request.remoteaddr=10.72.11.20 http.request.uri="/v2/" http.request.useragent="docker/19.03.2 go/go1.12.8 git-commit/6a30dfc kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64 UpstreamClient(Docker-Client/19.03.2 \(linux\))" 
+level=info msg="token signed by untrusted key with ID: "TOKE:NL6Q:7PW6:EXAM:PLET:OKEN:BG27:RCIB:D2S3:EXAM:PLET:OKEN""
+level=warning msg="error authorizing context: invalid token" go.version=go1.12.7 http.request.host="gitlab.company.com:4567" http.request.id=74613829-2655-4f96-8991-1c9fe33869b8 http.request.method=GET http.request.remoteaddr=10.72.11.20 http.request.uri="/v2/" http.request.useragent="docker/19.03.2 go/go1.12.8 git-commit/6a30dfc kernel/3.10.0-693.2.2.el7.x86_64 os/linux arch/amd64 UpstreamClient(Docker-Client/19.03.2 \(linux\))"
 ```
 
 GitLab uses the contents of the certificate key pair's two sides to encrypt the authentication token

doc/administration/reference_architectures/25k_users.md

@@ -34,7 +34,7 @@ full list of reference architectures, see
 | Monitoring node                          | 1           | 4 vCPU, 3.6 GB memory   | `n1-highcpu-4`   | `c5.xlarge`  | `F4s v2`  |
 | Object storage                           | n/a         | n/a                     | n/a              | n/a          | n/a       |
 | NFS server                               | 1           | 4 vCPU, 3.6 GB memory   | `n1-highcpu-4`   | `c5.xlarge`  | `F4s v2`  |
- 
+
 NOTE:
 Components marked with * can be optionally run on reputable
 third party external PaaS PostgreSQL solutions. Google Cloud SQL and AWS RDS are known to work.

doc/api/graphql/users_example.md

@@ -68,7 +68,7 @@ explorer. GraphiQL explorer is available for:
           }
         }
       }
-    } 
+    }
    ```
 
 1. Open the [GraphiQL explorer tool](https://gitlab.com/-/graphql-explorer).

doc/ci/environments/deployment_safety.md

@@ -154,7 +154,7 @@ If you have multiple jobs for the same environment (including non-deployment job
 build:service-a:
  environment:
    name: production
- 
+
 build:service-b:
  environment:
    name: production

doc/ci/troubleshooting.md

@@ -269,7 +269,7 @@ which pipelines can run.
 resource_group = Project.find_by_full_path('...').resource_groups.find_by(key: 'the-group-name')
 busy_resources = resource_group.resources.where('build_id IS NOT NULL')
 
-# identify which builds are occupying the resource 
+# identify which builds are occupying the resource
 # (I think it should be 1 as of today)
 busy_resources.pluck(:build_id)
 

doc/development/cascading_settings.md

@@ -26,7 +26,7 @@ Settings are not cascading by default. To define a cascading setting, take the f
     ```ruby
     class NamespaceSetting
       include CascadingNamespaceSettingAttribute
-   
+
       cascading_attr :delayed_project_removal
     end
     ```
@@ -40,11 +40,11 @@ Settings are not cascading by default. To define a cascading setting, take the f
     ```ruby
     class AddDelayedProjectRemovalCascadingSetting < ActiveRecord::Migration[6.0]
       include Gitlab::Database::MigrationHelpers::CascadingNamespaceSettings
-    
+
       def up
         add_cascading_namespace_setting :delayed_project_removal, :boolean, default: false, null: false
       end
-   
+
       def down
        remove_cascading_namespace_setting :delayed_project_removal
       end
@@ -100,7 +100,7 @@ cascaded value using the following criteria:
 ### `_locked?` method
 
 By default, the `_locked?` method (`delayed_project_removal_locked?`) returns
-`true` if an ancestor of the group or application setting locks the attribute. 
+`true` if an ancestor of the group or application setting locks the attribute.
 It returns `false` when called from the group that locked the attribute.
 
 When `include_self: true` is specified, it returns `true` when called from the group that locked the attribute.

doc/development/testing_guide/best_practices.md

@@ -451,7 +451,7 @@ expect(page).to have_current_path 'gitlab/gitlab-test/-/issues'
 
 expect(page).to have_title 'Not Found'
 
-# acceptable when a more specific matcher above is not possible 
+# acceptable when a more specific matcher above is not possible
 expect(page).to have_css 'h2', text: 'Issue title'
 expect(page).to have_css 'p', text: 'Issue description', exact: true
 expect(page).to have_css '[data-testid="weight"]', text: 2

doc/development/usage_ping/index.md

@@ -248,12 +248,12 @@ To deprecate a metric:
      end
    end
    ```
- 
+
 1. Update the Metrics Dictionary following [guidelines instructions](dictionary.md).
 
 ### 4. Remove a metric
 
-Only deprecated metrics can be removed from Usage Ping. 
+Only deprecated metrics can be removed from Usage Ping.
 
 For an example of the metric removal process take a look at this [example issue](https://gitlab.com/gitlab-org/gitlab/-/issues/297029)
 
@@ -262,9 +262,9 @@ To remove a deprecated metric:
 1. Verify that removing the metric from the Usage Ping payload does not cause
    errors in [Version App](https://gitlab.com/gitlab-services/version-gitlab-com)
    when the updated payload is collected and processed. Version App collects
-   and persists all Usage Ping reports. To do that you can modify 
+   and persists all Usage Ping reports. To do that you can modify
    [fixtures](https://gitlab.com/gitlab-services/version-gitlab-com/-/blob/master/spec/support/usage_data_helpers.rb#L540)
-   used to test 
+   used to test
    [`UsageDataController#create`](https://gitlab.com/gitlab-services/version-gitlab-com/-/blob/3760ef28/spec/controllers/usage_data_controller_spec.rb#L75)
    endpoint, and assure that test suite does not fail when metric that you wish to remove is not included into test payload.  
 
@@ -273,7 +273,7 @@ To remove a deprecated metric:
    Ask for confirmation that the metric is not referred to in any SiSense dashboards and
    can be safely removed from Usage Ping. Use this
    [example issue](https://gitlab.com/gitlab-data/analytics/-/issues/7539) for guidance.
-   This step can be skipped if verification done during [deprecation process](#3-deprecate-a-metric) 
+   This step can be skipped if verification done during [deprecation process](#3-deprecate-a-metric)
    reported that metric is not required by any data transformation in Snowflake data warehouse nor it is
    used by any of SiSense dashboards.
   
@@ -288,15 +288,15 @@ To remove a deprecated metric:
    instances might not immediately update to the latest version of GitLab, and
    therefore continue to report the removed metric. The Product Intelligence team
    requires a record of all removed metrics in order to identify and filter them.
-    
+
    For example please take a look at this [merge request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60149/diffs#b01f429a54843feb22265100c0e4fec1b7da1240_10_10).
-    
+
 1. After you verify the metric can be safely removed,
    remove the metric's instrumentation from
    [`lib/gitlab/usage_data.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data.rb)
    or
    [`ee/lib/ee/gitlab/usage_data.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/ee/gitlab/usage_data.rb).
-   
+
    For example please take a look at this [merge request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60149/diffs#6335dc533bd21df26db9de90a02dd66278c2390d_167_167).
 
 1. Remove any other records related to the metric:

doc/install/azure/index.md

@@ -190,7 +190,7 @@ To set up the GitLab external URL:
 1. Open `/etc/gitlab/gitlab.rb` with your editor.
 1. Find `external_url` and replace it with your own domain name. For the sake
    of this example, use the default domain name Azure sets up.
-   Using `https` in the URL 
+   Using `https` in the URL
    [automatically enables](https://docs.gitlab.com/omnibus/settings/ssl.html#lets-encrypt-integration),
    Let's Encrypt, and sets HTTPS by default:
 

doc/integration/saml.md

@@ -442,7 +442,7 @@ in the OmniAuth [`info` hash](https://github.com/omniauth/omniauth/wiki/Auth-Has
 
 For example, if your SAMLResponse contains an Attribute called `EmailAddress`,
 specify `{ email: ['EmailAddress'] }` to map the Attribute to the
-corresponding key in the `info` hash. URI-named Attributes are also supported, for example, 
+corresponding key in the `info` hash. URI-named Attributes are also supported, for example,
 `{ email: ['http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress'] }`.
 
 This setting allows you tell GitLab where to look for certain attributes required
@@ -859,7 +859,7 @@ For this you need take the following into account:
   the request to contain one. In this case the fingerprint or fingerprint
   validators are optional
 
-If none of the above described scenarios is valid, the request 
+If none of the above described scenarios is valid, the request
 fails with one of the mentioned errors.
 
 ### User is blocked when signing in through SAML

doc/ssh/README.md

@@ -325,7 +325,7 @@ If you are using [EGit](https://www.eclipse.org/egit/), you can [add your SSH ke
 
 If you're running Windows 10, you can either use the [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/install-win10)
 with [WSL 2](https://docs.microsoft.com/en-us/windows/wsl/install-win10#update-to-wsl-2) which
-has both `git` and `ssh` preinstalled, or install [Git for Windows](https://gitforwindows.org) to 
+has both `git` and `ssh` preinstalled, or install [Git for Windows](https://gitforwindows.org) to
 use SSH through Powershell.
 
 The SSH key generated in WSL is not directly available for Git for Windows, and vice versa,

doc/user/clusters/agent/index.md

@@ -100,7 +100,7 @@ To use the KAS:
 
 ### Define a configuration repository
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/259669) in GitLab 13.7, the Agent manifest configuration can be added to multiple directories (or subdirectories) of its repository. 
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/259669) in GitLab 13.7, the Agent manifest configuration can be added to multiple directories (or subdirectories) of its repository.
 
 To configure an Agent, you need:
 

doc/user/packages/npm_registry/index.md

@@ -318,7 +318,7 @@ npmScopes:
   foo:
     npmRegistryServer: "https://gitlab.example.com/api/v4/projects/<your_project_id>/packages/npm/"
     npmPublishRegistry: "https://gitlab.example.com/api/v4/projects/<your_project_id>/packages/npm/"
-      
+
 npmRegistries:
   //gitlab.example.com/api/v4/projects/<your_project_id>/packages/npm/:
     npmAlwaysAuth: true

doc/user/project/import/svn.md

@@ -44,9 +44,9 @@ directly in a file system level.
 
 The first step to mirror you SVN repository in GitLab is to create a new empty
 project that is used as a mirror. For Omnibus installations the path to
-the repository is 
+the repository is
 `/var/opt/gitlab/git-data/repositories/USER/REPO.git` by default. For
-installations from source, the default repository directory is 
+installations from source, the default repository directory is
 `/home/git/repositories/USER/REPO.git`. For convenience, assign this path to a
 variable: