Update no-trailing-spaces configuration to new standard

Author: eread

doc/.markdownlint/.markdownlint-cli2.yaml

@@ -1,7 +1,9 @@
 ---
 # Extended Markdown configuration to enforce no-trailing-spaces rule
-# To use this configuration, in the project directory run:
-#   markdownlint-cli2 --config doc/.markdownlint/.markdownlint-cli2.yaml 'doc/**/*.md'
+# To use this configuration, in the doc directory, run:
+#
+#   markdownlint-cli2 --config .markdownlint/.markdownlint-cli2.yaml '**/*.md'
 config:
-  extends: "../../.markdownlint-cli2.yaml"
+  default: false
   no-trailing-spaces: true
+fix: true

doc/maintenance/index.md

@@ -202,17 +202,17 @@ To rotate the secrets:
 1. If you have multiple nodes in your GitLab environment, you must copy the secrets to all of your other nodes:
 
    1. On all other nodes, move your current secrets file to a different location:
-   
+
       ```shell
       sudo mv /etc/gitlab/gitlab-secrets.json /etc/gitlab/gitlab-secrets.json.old
       ```
-   
+
    1. Copy the new `/etc/gitlab/gitlab-secrets.json` file from your Rails node onto all of your other GitLab nodes.
 
    1. On all other nodes, [reconfigure GitLab](https://docs.gitlab.com/ee/administration/restart_gitlab.html#reconfigure-a-linux-package-installation)
       on each node.
 
-   1. On all other nodes, [restart GitLab](https://docs.gitlab.com/ee/administration/restart_gitlab.html#restart-a-linux-package-installation) on each 
+   1. On all other nodes, [restart GitLab](https://docs.gitlab.com/ee/administration/restart_gitlab.html#restart-a-linux-package-installation) on each
       node to ensure all services are using the new secrets.
 
    1. On all nodes, run a checksum match on the `/etc/gitlab/gitlab-secrets.json` file to confirm that the secrets match:

doc/settings/database.md

@@ -605,7 +605,7 @@ update this setting in `/etc/gitlab/gitlab.rb`:
 gitlab_rails['databases']['ci']['enable'] = false
 ```
 
-In a multi-node environment, this setting should be updated on all Rails and Sidekiq nodes. 
+In a multi-node environment, this setting should be updated on all Rails and Sidekiq nodes.
 
 ## Using a non-packaged PostgreSQL database management server
 
@@ -866,7 +866,7 @@ when your installation is using PgBouncer.
 
 1. After upgrading PostgreSQL to a new major release, recreate the table statistics to ensure efficient query plans are picked and
    to reduce database server CPU load.
-   
+
    If the upgrade was "in-place" using `pg_upgrade`, run the following query on the PostgreSQL database console:
 
    ```SQL

doc/troubleshooting.md

@@ -1004,7 +1004,7 @@ make it available. See <https://docs.pulpproject.org/pulp_rpm/> for details.
 
 ## Error: `E: connection refused to d20rj4el6vkp4c.cloudfront.net 443`
 
-When you install a package hosted on our package repository at `packages.gitlab.com`, your client will receive and follow a redirect to the CloudFront address `d20rj4el6vkp4c.cloudfront.net`. Servers in an air-gapped environment can receive the following errors: 
+When you install a package hosted on our package repository at `packages.gitlab.com`, your client will receive and follow a redirect to the CloudFront address `d20rj4el6vkp4c.cloudfront.net`. Servers in an air-gapped environment can receive the following errors:
 
 ```shell
 E: connection refused to d20rj4el6vkp4c.cloudfront.net 443