Merge branch 'aqualls-trailing-spaces-fix2' into 'master'

Fix trailing spaces in documentation

See merge request gitlab-org/gitlab!70076

doc/administration/clusters/kas.md

@@ -138,14 +138,14 @@ If you are running a self-managed GitLab instance and:
 - The instance doesn't have HTTPS configured on the GitLab instance itself.
 - The instance's hostname resolves locally to its internal IP address.
 
-You may see the following error when the KAS tries to connect to the GitLab API: 
+You may see the following error when the KAS tries to connect to the GitLab API:
 
 ```json
 {"level":"error","time":"2021-08-16T14:56:47.289Z","msg":"GetAgentInfo()","correlation_id":"01FD7QE35RXXXX8R47WZFBAXTN","grpc_service":"gitlab.agent.reverse_tunnel.rpc.ReverseTunnel","grpc_method":"Connect","error":"Get \"https://gitlab.example.com/api/v4/internal/kubernetes/agent_info\": dial tcp 172.17.0.4:443: connect: connection refused"}
 ```
 
-To fix this for [Omnibus](https://docs.gitlab.com/omnibus/) package installations, 
-set the following parameter in `/etc/gitlab/gitlab.rb` 
+To fix this for [Omnibus](https://docs.gitlab.com/omnibus/) package installations,
+set the following parameter in `/etc/gitlab/gitlab.rb`
 (replacing `gitlab.example.com` with your GitLab instance's hostname):
 
 ```ruby

doc/administration/logs.md

@@ -670,8 +670,8 @@ access log of gRPC calls made by Gitaly to `gitaly-ruby`.
 ### `gitaly_hooks.log`
 
 This file is at `/var/log/gitlab/gitaly/gitaly_hooks.log` and is
-produced by `gitaly-hooks` command. It also contains records about 
-failures received during processing of the responses from GitLab API. 
+produced by `gitaly-hooks` command. It also contains records about
+failures received during processing of the responses from GitLab API.
 
 ## Puma Logs
 

doc/install/requirements.md

@@ -199,7 +199,7 @@ Take for example the following scenarios:
   ```plaintext
   The highest number from
   2
-  And 
+  And
   [
   the lowest number from
     - number of cores: 2
@@ -214,11 +214,11 @@ Take for example the following scenarios:
   ```plaintext
   The highest number from
   2
-  And 
+  And
   [
   the lowest number from
     - number of cores: 4
-    - memory limit: (4 - 1.5) = 2.5 
+    - memory limit: (4 - 1.5) = 2.5
   ]
   ```
 
@@ -229,7 +229,7 @@ Take for example the following scenarios:
   ```plaintext
   The highest number from
   2
-  And 
+  And
   [
   the lowest number from
     - number of cores: 4
@@ -258,7 +258,7 @@ works.
 
 ### Puma per worker maximum memory
 
-By default, each Puma worker will be limited to 1024 MB of memory. 
+By default, each Puma worker will be limited to 1024 MB of memory.
 This setting [can be adjusted](../administration/operations/puma.md#puma-worker-killer) and should be considered
 if you need to increase the number of Puma workers.
 

doc/user/application_security/policies/index.md

@@ -76,7 +76,7 @@ The policy editor has two modes:
   ![Policy Editor YAML Mode](img/container_policy_yaml_mode_v14_3.png)
 
 You can use both modes interchangeably and switch between them at any
-time. If a YAML resource is incorrect or contains data not supported 
+time. If a YAML resource is incorrect or contains data not supported
 by the Rule mode, Rule mode is automatically
 disabled. If the YAML is incorrect, you must use YAML
 mode to fix your policy before Rule mode is available again.

doc/user/application_security/threat_monitoring/index.md

@@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14707) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.9.
 
-The **Threat Monitoring** page provides alerts and metrics 
+The **Threat Monitoring** page provides alerts and metrics
 for the GitLab application runtime security features. You can access
 these by navigating to your project's **Security & Compliance > Threat
 Monitoring** page.