Trim white space

doc/administration/dedicated/monitor.md

@@ -17,13 +17,13 @@ To gain read only access to the S3 bucket with your application logs:
 
 1. Open a [support ticket](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=4414917877650) with the title `Customer Log Access`.
 1. In the body of the ticket, include a list of IAM Principal Amazon Resource Names (ARNs) that require access to the logs from the S3 bucket. The ARNs can be for users or roles.
-   
+
    NOTE:
    Specify the full ARN path without wildcards (`*`). Wildcard characters are not supported. GitLab team members can read more about the proposed feature to add wildcard support in this confidential issue: [7010](https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/7010).
 
 GitLab provides the name of the S3 bucket. Your authorized users or roles can then access all objects in the bucket. To verify access, you can use the [AWS CLI](https://aws.amazon.com/cli/).
 
-## Find your S3 bucket name 
+## Find your S3 bucket name
 
 To find your S3 bucket name:
 

doc/administration/gitaly/configure_gitaly.md

@@ -960,7 +960,7 @@ should be:
   fetches, and probably the entire server, slows down.
 
 WARNING:
-All existing data in the specified directory will be removed. 
+All existing data in the specified directory will be removed.
 Take care not to use a directory with existing data.
 
 By default, the cache storage directory is set to a subdirectory of the first Gitaly storage

doc/administration/postgresql/replication_and_failover.md

@@ -586,15 +586,15 @@ associated internal load balancer), three PostgreSQL servers, and one
 application node.
 
 In this setup, all servers share the same `10.6.0.0/16` private network range.
-The servers communicate freely over these addresses. 
+The servers communicate freely over these addresses.
 
 While you can use a different networking setup, it's recommended to ensure that it allows
 for synchronous replication to occur across the cluster.
 As a general rule, a latency of less than 2 ms ensures replication operations to be performant.
 
-GitLab [reference architectures](../reference_architectures/index.md) are sized to 
-assume that application database queries are shared by all three nodes. 
-Communication latency higher than 2 ms can lead to database locks and 
+GitLab [reference architectures](../reference_architectures/index.md) are sized to
+assume that application database queries are shared by all three nodes.
+Communication latency higher than 2 ms can lead to database locks and
 impact the replica's ability to serve read-only queries in a timely fashion.
 
 - `10.6.0.22`: PgBouncer 2

doc/administration/self_hosted_models/supported_llm_serving_platforms.md

@@ -77,14 +77,14 @@ You should at least a `a2-highgpu-4g` machine on GCP or equivalent (4x Nvidia A1
    ```
 
 1. Rename the token config:
-   
+
    ```shell
    cd <path-to-model>/Mixtral-8x7B-Instruct-v0.1
    cp tokenizer.model tokenizer.model.v3
    ```
 
 1. Run the model:
-   
+
    ```shell
    vllm serve <path-to-model>/Mixtral-8x7B-Instruct-v0.1 \
      --tensor_parallel_size 4 \

doc/administration/self_hosted_models/supported_models_and_hardware_requirements.md

@@ -36,7 +36,7 @@ Install one of the following GitLab-approved LLM models:
 | GPT | [GPT-4o](https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/models?tabs=python-secure#gpt-4o-and-gpt-4-turbo) | [Azure OpenAI](https://learn.microsoft.com/en-us/azure/ai-services/openai/overview) | Generally available | 🟢 Green | 🟢 Green | 🟢 Green |
 | GPT | [GPT-4o-mini](https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/models?tabs=python-secure#gpt-4o-and-gpt-4-turbo) | [Azure OpenAI](https://learn.microsoft.com/en-us/azure/ai-services/openai/overview) | Generally available | 🟢 Green | 🟢 Green | 🟡 Amber |
 
-Legend: 
+Legend:
 
 - 🟢 Green - Strongly recommended. The model can handle the feature without any loss of quality.
 - 🟡 Amber - Recommended. The model supports the feature, but there might be minor compromises or limitations.

doc/administration/terraform_state.md

@@ -251,7 +251,7 @@ The relative path is displayed.
 
 ## Restoring Terraform state files from backups
 
-To restore Terraform state files from backups, you must have access to the encrypted state files and the GitLab database. 
+To restore Terraform state files from backups, you must have access to the encrypted state files and the GitLab database.
 
 ### Database tables
 
@@ -263,7 +263,7 @@ The following database table helps trace the S3 path back to specific projects:
 
 The state files are stored in a specific directory structure, where:
 
-- The first three segments of the path are derived from the SHA-2 hash value of the project ID. 
+- The first three segments of the path are derived from the SHA-2 hash value of the project ID.
 - Each state has a UUID stored on the `terraform_states` database table that forms part of the path.  
 
 For example, for a project where the:
@@ -293,6 +293,6 @@ The state files are encrypted using Lockbox and require the following informatio
 
 The encryption key is derived from both the `db_key_base` and the project ID. If you can't access `db_key_base`, decryption is not possible.
 
-To learn how to manually decrypt files, see the documentation from [Lockbox](https://github.com/ankane/lockbox). 
+To learn how to manually decrypt files, see the documentation from [Lockbox](https://github.com/ankane/lockbox).
 
 To view the encryption key generation process, see the [state uploader code](https://gitlab.com/gitlab-org/gitlab/-/blob/e0137111fbbd28316f38da30075aba641e702b98/app/uploaders/terraform/state_uploader.rb#L43).

doc/api/usage_data.md

@@ -50,7 +50,7 @@ The Service Ping JSON payload includes `schema_inconsistencies_metric`. Database
 
 This metric is designed only for troubleshooting ongoing issues, and shouldn't be used as a regular health check. The metric should only be interpreted with
 the guidance of GitLab Support. The metric reports the same database schema inconsistencies as the
-[database schema checker Rake task](../administration/raketasks/maintenance.md#check-the-database-for-schema-inconsistencies). 
+[database schema checker Rake task](../administration/raketasks/maintenance.md#check-the-database-for-schema-inconsistencies).
 
 For more information, see [issue 467544](https://gitlab.com/gitlab-org/gitlab/-/issues/467544).
 

doc/ci/environments/protected_environments.md

@@ -171,9 +171,9 @@ Maintainers can:
 - Unprotect a protected environment by selecting the **Unprotect** button for that environment.
 
 After an environment is unprotected, all access entries are deleted and must
-be re-entered if the environment is re-protected. 
+be re-entered if the environment is re-protected.
 
-After an approval rule is deleted, previously approved deployments do not show who approved the deployment. 
+After an approval rule is deleted, previously approved deployments do not show who approved the deployment.
 Information on who approved a deployment is still available in the [project audit events](../../user/compliance/audit_events.md#project-audit-events).
 If a new rule is added, previous deployments show the new rules without the option to approve the deployment. [Issue 506687](https://gitlab.com/gitlab-org/gitlab/-/issues/506687) proposes to show the full approval history of deployments, even if an approval rule is deleted.
 

doc/ci/runners/hosted_runners/linux.md

@@ -43,7 +43,7 @@ GitLab offers the following machine type for hosted runners on Linux Arm64.
 NOTE:
 Users can experience network connectivity issues when they use Docker-in-Docker with hosted runners on Linux
 Arm. This issue occurs when the maximum transmission unit (MTU) value in Google Cloud and Docker don't match.
-To resolve this issue, set `--mtu=1400` in the client side Docker configuration. 
+To resolve this issue, set `--mtu=1400` in the client side Docker configuration.
 For more details, see [issue 473739](https://gitlab.com/gitlab-org/gitlab/-/issues/473739#workaround).
 
 ## Container images

doc/development/application_settings.md

@@ -88,5 +88,5 @@ This a required multi-milestone process that involves:
 1. Ignoring the column.
 1. Dropping the column.
 1. Removing the ignore rule.
- 
+
 Dropping the original column before ignoring it in the model can cause problems with zero-downtime migrations.

doc/development/deprecation_guidelines/index.md

@@ -22,7 +22,7 @@ If a deprecation or breaking change is unavoidable, then take the following step
 1. Review the [deprecation guidelines in our documentation](#minimize-the-impact-of-breaking-changes)
 1. Review the [breaking changes best practices](https://docs.google.com/document/d/1ByVZEhGJfjb6XTwiDeaSDRVwUiF6dsEQI01TW4BJA0k/edit?tab=t.0#heading=h.vxhro51h5zxn) (internal link)
 1. Review the [release post process for announcing breaking changes](https://handbook.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes)
-1. **(Required)** Create a [deprecation issue ticket](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Deprecations.md) and begin following the steps documented there 
+1. **(Required)** Create a [deprecation issue ticket](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Deprecations.md) and begin following the steps documented there
 
 The [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Deprecations.md) includes checklist that ensure each breaking change has sufficiently planned for:
 

doc/development/documentation/hugo_migration.md

@@ -264,7 +264,7 @@ You can review the new release process [here](https://gitlab.com/gitlab-org/tech
 
 The [Docs project maintenance tasks rotation](https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments) will pause when we launch on Hugo.
 
-For February 2025, run the checks for broken external links and `start_remove` content before Wednesday, February 12. Other tasks are fine to skip for now. From March onwards, the monthly maintenance task will be on hold until further notice. 
+For February 2025, run the checks for broken external links and `start_remove` content before Wednesday, February 12. Other tasks are fine to skip for now. From March onwards, the monthly maintenance task will be on hold until further notice.
 
 NOTE:
 This does not impact the release post [structural check](https://handbook.gitlab.com/handbook/marketing/blog/release-posts/#structural-check) or [monthly documentation release](https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/doc/releases.md) tasks. The assigned Technical Writer should continue to do these tasks as previously scheduled.

doc/development/python_guide/deployment.md

@@ -40,7 +40,7 @@ deploy:
 
 ### Runway deployment for .com
 
-Services for GitLab.com, GitLab Dedicated and self-hosted customers using CloudConnect are deployed using [Runway](https://docs.runway.gitlab.com/welcome/onboarding/). 
+Services for GitLab.com, GitLab Dedicated and self-hosted customers using CloudConnect are deployed using [Runway](https://docs.runway.gitlab.com/welcome/onboarding/).
 Please refer to the project documentation on how to add or manage Runway services.
 
 ### Deploying in self-hosted environments

doc/operations/incident_management/index.md

@@ -11,7 +11,7 @@ DETAILS:
 **Offering:** GitLab.com, GitLab Self-Managed, GitLab Dedicated
 
 NOTE:
-This feature is not under active development, but [community contributions](https://about.gitlab.com/community/contribute/) are welcome. 
+This feature is not under active development, but [community contributions](https://about.gitlab.com/community/contribute/) are welcome.
 For more information, see [issue 468607](https://gitlab.com/gitlab-org/gitlab/-/issues/468607#note_1967939452).
 To determine if the feature meets your needs, see the [open bug issues](https://gitlab.com/gitlab-org/gitlab/-/issues/?sort=updated_desc&state=opened&label_name%5B%5D=Category%3AIncident%20Management&label_name%5B%5D=type%3A%3Abug&first_page_size=20).
 

doc/subscriptions/gitlab_com/gitlab_subscription_troubleshooting.md

@@ -55,7 +55,7 @@ To resolve this issue, try the following:
   - [FineShift Software Private Limited](https://partners.gitlab.com/English/directory/partner/1737250/fineshift-software-private-limited)
 
 - For cards issued outside of the United States: Ensure your card is enabled for international use, and verify if there are country-specific restrictions.
-- Contact your financial institution: Ask for the reason why your transaction was declined, and request that your card is enabled for this type of transaction. 
+- Contact your financial institution: Ask for the reason why your transaction was declined, and request that your card is enabled for this type of transaction.
 
 ## Error: `Attempt_Exceed_Limitation`
 

doc/update/versions/gitlab_17_changes.md

@@ -89,9 +89,9 @@ For more information about upgrading GitLab Helm Chart, see [the release notes f
   Now you should be able to complete the migrations in GitLab 17.1 and finish
   the upgrade.
 
-- A [known issue](https://gitlab.com/gitlab-org/gitlab/-/issues/476542) in the Git versions shipped with 
-  GitLab 17.0.x and GitLab 17.1.x causes a noticeable increase in CPU usage when under load. The primary cause of 
-  this regression was resolved in the Git versions shipped with GitLab 17.2 so, for systems that see heavy peak loads, 
+- A [known issue](https://gitlab.com/gitlab-org/gitlab/-/issues/476542) in the Git versions shipped with
+  GitLab 17.0.x and GitLab 17.1.x causes a noticeable increase in CPU usage when under load. The primary cause of
+  this regression was resolved in the Git versions shipped with GitLab 17.2 so, for systems that see heavy peak loads,
   you should upgrade to GitLab 17.2.
 
 ### Linux package installations

doc/user/analytics/ai_impact_analytics.md

@@ -23,7 +23,7 @@ Use AI impact analytics for:
 - Snapshot of GitLab Duo usage: Track the use of seats and features in a project or group over the last 30 days.
 
 To learn how you can optimize your license utilization,
-see [GitLab Duo add-ons](../../subscriptions/subscription-add-ons.md). 
+see [GitLab Duo add-ons](../../subscriptions/subscription-add-ons.md).
 
 For a click-through demo, see the [AI impact analytics product tour](https://gitlab.navattic.com/ai-impact).
 

doc/user/application_security/vulnerability_report/index.md

@@ -100,7 +100,7 @@ You can filter by:
 ### Filter vulnerabilities
 
 > - Improved filtering [introduced](https://gitlab.com/groups/gitlab-org/-/epics/13339) in GitLab 16.9 [with a flag](../../../administration/feature_flags.md) named `vulnerability_report_advanced_filtering`. Disabled by default.
-> - [Enabled on GitLab.com, GitLab Self-Managed, and GitLab Dedicated](https://gitlab.com/gitlab-org/gitlab/-/issues/437128) in GitLab 17.1. 
+> - [Enabled on GitLab.com, GitLab Self-Managed, and GitLab Dedicated](https://gitlab.com/gitlab-org/gitlab/-/issues/437128) in GitLab 17.1.
 > - [Generally available in 17.2](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/157172). Feature flag `vulnerability_report_advanced_filtering` removed.
 
 Filter the vulnerability report to focus on a subset of vulnerabilities.

doc/user/gitlab_duo_chat/examples.md

@@ -245,7 +245,7 @@ For more information, see the history.
 GitLab.com customers must contact their Customer Success Manager to enable this feature.
 
 Add repository files to your Duo Chat conversations in VS Code or JetBrains IDEs by
-typing `/include` and choosing the files. 
+typing `/include` and choosing the files.
 
 Prerequisites:
 

doc/user/infrastructure/iac/terraform_state.md

@@ -36,7 +36,7 @@ or consider using a separate GitLab instance with no shared points of failure.
 For GitLab Self-Managed, before you can use GitLab for your OpenTofu state files:
 
 - An administrator must [set up Terraform/OpenTofu state storage](../../../administration/terraform_state.md).
-- You must turn on the **Infrastructure** menu for your project: 
+- You must turn on the **Infrastructure** menu for your project:
   1. Go to **Settings > General**.
   1. Expand **Visibility, project features, permissions**.
   1. Under **Infrastructure**, turn on the toggle.