diff --git a/doc/install/aws/index.md b/doc/install/aws/index.md
index b7489b1b26377230ee73f487e0260f75ba2dc794..58d264e8f7cc0402a212d22ef0036d8cd4e6653b 100644
--- a/doc/install/aws/index.md
+++ b/doc/install/aws/index.md
@@ -307,15 +307,15 @@ On the Route 53 dashboard, select **Hosted zones** in the left navigation bar:
 
 1. Select an existing hosted zone or, if you do not already have one for your domain, select **Create Hosted Zone**, enter your domain name, and select **Create**.
 1. Select **Create record** and provide the following values:
-    1. **Name:** Use the domain name (the default value) or enter a subdomain.
-    1. **Type:** Select **A - IPv4 address**.
-    1. **Alias:** Defaults to **disabled**. Enable this option.
-    1. **Route traffic to:** Select **Alias to Network Load Balancer**.
-    1. **Region:** Select the region where the Network Load Balancer resides.
-    1. **Choose network load balancer:** Select the Network Load Balancer we created earlier.
-    1. **Routing Policy:** We use **Simple** but you can choose a different policy based on your use case.
-    1. **Evaluate Target Health:** We set this to **No** but you can choose to have the load balancer route traffic based on target health.
-    1. Select **Create**.
+   1. **Name:** Use the domain name (the default value) or enter a subdomain.
+   1. **Type:** Select **A - IPv4 address**.
+   1. **Alias:** Defaults to **disabled**. Enable this option.
+   1. **Route traffic to:** Select **Alias to Network Load Balancer**.
+   1. **Region:** Select the region where the Network Load Balancer resides.
+   1. **Choose network load balancer:** Select the Network Load Balancer we created earlier.
+   1. **Routing Policy:** We use **Simple** but you can choose a different policy based on your use case.
+   1. **Evaluate Target Health:** We set this to **No** but you can choose to have the load balancer route traffic based on target health.
+   1. Select **Create**.
 1. If you registered your domain through Route 53, you're done. If you used a different domain registrar, you must update your DNS records with your domain registrar. You must:
    1. Select **Hosted zones** and select the domain you added above.
    1. You see a list of `NS` records. From your domain registrar's administrator panel, add each of these as `NS` records to your domain's DNS records. These steps may vary between domain registrars. If you're stuck, Google **"name of your registrar" add DNS records** and you should find a help article specific to your domain registrar.
diff --git a/doc/install/relative_url.md b/doc/install/relative_url.md
index 2a32e977aea91759841679f5ef0a7072335a0525..3f56264314a91a096d832785deab5252e208562d 100644
--- a/doc/install/relative_url.md
+++ b/doc/install/relative_url.md
@@ -128,7 +128,7 @@ To disable the relative URL:
 1. Remove `/home/git/gitlab/config/initializers/relative_url.rb`
 
 1. Follow the same as above starting from 2. and set up the
-    GitLab URL to one that doesn't contain a relative path.
+   GitLab URL to one that doesn't contain a relative path.
 
 <!-- ## Troubleshooting
 
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index 988f75a33a629cafb18163be967210e6894a71c1..8453fcaea323da70e4d3d5234804fc7faf66920b 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -251,7 +251,7 @@ Redis stores all user sessions and the background task queue.
 The requirements for Redis are as follows:
 
 - Redis 6.x or 7.x is required in GitLab 16.0 and later. However, you should upgrade to
-Redis 6.2.14 or later as [Redis 6.0 is no longer supported](https://endoflife.date/redis).
+  Redis 6.2.14 or later as [Redis 6.0 is no longer supported](https://endoflife.date/redis).
 - Redis Cluster mode is not supported. Redis Standalone must be used, with or without HA.
 - Storage requirements for Redis are minimal, about 25 kB per user on average.
 - [Redis eviction mode](../administration/redis/replication_and_failover_external.md#setting-the-eviction-policy) set appropriately.
diff --git a/doc/tutorials/configure_gitlab_runner_to_use_gke/index.md b/doc/tutorials/configure_gitlab_runner_to_use_gke/index.md
index d3576f198191ae58bbd076e4479593d31b8828fd..951a0efdd9253379174a6b4757a6a0409410ec40 100644
--- a/doc/tutorials/configure_gitlab_runner_to_use_gke/index.md
+++ b/doc/tutorials/configure_gitlab_runner_to_use_gke/index.md
@@ -128,7 +128,7 @@ Now that you have a cluster, you're ready to install and configure the Kubernete
    - To use the `cert-manager`:
 
      1. Use the `certificate-issuer-install.yaml` to install a `Certificate` and `Issuer` in the default namespace, in addition
-     to the operator installation:
+        to the operator installation:
 
         ```shell
         cat > certificate-issuer-install.yaml << EOF
diff --git a/doc/tutorials/set_up_gitlab_google_integration/index.md b/doc/tutorials/set_up_gitlab_google_integration/index.md
index 31e34436659dde3510095ebd6eead12bcd5e5ab8..b49b15090dcbb66e7aaea16462e83a7a30b545fa 100644
--- a/doc/tutorials/set_up_gitlab_google_integration/index.md
+++ b/doc/tutorials/set_up_gitlab_google_integration/index.md
@@ -29,11 +29,11 @@ To set up the integration, you must:
 
 - Have a GitLab project where you have at least the Maintainer role.
 - Have the [Owner](https://cloud.google.com/iam/docs/understanding-roles#owner) IAM role on the
-   Google Cloud projects that you want to use.
+  Google Cloud projects that you want to use.
 - Have [billing enabled for your Google Cloud project](https://cloud.google.com/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).
 - Have a Google Artifact Registry repository with Docker format and Standard mode.
 - Install the [Google Cloud CLI](https://cloud.google.com/sdk/docs/install)
-   and [Terraform](https://developer.hashicorp.com/terraform/install).
+  and [Terraform](https://developer.hashicorp.com/terraform/install).
 
 ## Secure your usage with Google Cloud Identity and Access Management (IAM)
 
@@ -56,7 +56,7 @@ After this step, you can view your Google Cloud artifacts in GitLab.
 1. Under **Enable integration**, select the **Active** checkbox.
 1. Complete the fields:
    - **[Google Cloud project ID](https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects)**:
-   The ID of the Google Cloud project where your Artifact Registry repository is located.
+     The ID of the Google Cloud project where your Artifact Registry repository is located.
    - **Repository name**: The name of your Artifact Registry repository.
    - **Repository location**: The location of your Artifact Registry repository.
 1. In **Configure Google Cloud IAM policies**, follow the onscreen instructions
@@ -80,9 +80,9 @@ a runner manager that creates temporary runners to execute multiple jobs simulta
 1. Complete the fields.
    - In the **Platform** section, select **Google Cloud**.
    - In the **Tags** section, in the **Tags** field, enter the job tags to specify jobs the runner can run.
-      If there are no job tags for this runner, select **Run untagged**.
+     If there are no job tags for this runner, select **Run untagged**.
    - Optional. In the **Runner description** field, add a description for the runner
-      that displays in GitLab.
+     that displays in GitLab.
    - Optional. In the **Configuration** section, add additional configurations.
 1. Select **Create runner**.
 1. Complete the fields in the **Step 1: Specify environment** section to specify the environment in
diff --git a/doc/tutorials/setup_steps/index.md b/doc/tutorials/setup_steps/index.md
index 4ddce9fd1d6c4a3c165b4abff5b740b741e2b556..b949294e6bfd59c23c8ead8fd70ef386d07e1398 100644
--- a/doc/tutorials/setup_steps/index.md
+++ b/doc/tutorials/setup_steps/index.md
@@ -291,7 +291,7 @@ Add an output to your `hello` step.
    ```
 
    - In this `spec`, you've defined a single output `greeting` without a default. Because
-   there is no default, the output `greeting` is required.
+     there is no default, the output `greeting` is required.
    - Outputs are written to a file `${{ output_file }}` (provided at run time) in the form `key=value`.
    - This step runs `echo greeting=hello ${{ inputs.name }}` and sends the output to the logs and the output file (`tee ${{ output_file }}`).
 
diff --git a/doc/user/analytics/analytics_dashboards.md b/doc/user/analytics/analytics_dashboards.md
index 36cdccb5ed74852dddcf44009f5121baa7fc2d5f..f5c64dcd29c4059090e044b768ed58c8b2389e8f 100644
--- a/doc/user/analytics/analytics_dashboards.md
+++ b/doc/user/analytics/analytics_dashboards.md
@@ -279,7 +279,7 @@ DETAILS:
 Prerequisites:
 
 - The top-level group of the project must have GitLab Duo
- [experiment and beta features enabled](../gitlab_duo/turn_on_off.md#turn-on-beta-and-experimental-features).
+  [experiment and beta features enabled](../gitlab_duo/turn_on_off.md#turn-on-beta-and-experimental-features).
 
 To generate a custom visualization with GitLab Duo using a natural language query:
 
@@ -321,7 +321,7 @@ defined in `ee/app/validators/json_schemas/analytics_visualization.json`.
 If a dashboard panel displays an error message:
 
 - Make sure your [Cube query](../product_analytics/index.md#product-analytics-dashboards) and
-[visualization](../analytics/analytics_dashboards.md#define-a-chart-visualization) configurations are set up correctly.
+  [visualization](../analytics/analytics_dashboards.md#define-a-chart-visualization) configurations are set up correctly.
 - For [product analytics](../product_analytics/index.md), also check that your visualization's Cube query is valid.
 
 ### Generate visualization with GitLab Duo returns unexpected results
@@ -330,4 +330,4 @@ If GitLab Duo doesn't return the expected or a useful result, try editing your q
 
 - Specify a date range. For example: _number of unique users in 2023 to 2024, grouped monthly_.
 - Use the same names for metrics and dimensions as shown in the visualization designer.
-For example: _returning users_ instead of _existing customers_.
+  For example: _returning users_ instead of _existing customers_.
diff --git a/doc/user/application_security/api_fuzzing/troubleshooting.md b/doc/user/application_security/api_fuzzing/troubleshooting.md
index 2cf42740d98455c86791bfdf113ab6ed438dfe90..95cb8f35dab6d38b193b8c4412c2b6455de0d2f0 100644
--- a/doc/user/application_security/api_fuzzing/troubleshooting.md
+++ b/doc/user/application_security/api_fuzzing/troubleshooting.md
@@ -93,8 +93,8 @@ For OpenAPI Specifications that are generated automatically validation errors ar
 **For generated OpenAPI Specifications**
 
 1. Identify the validation errors.
-    1. Use the [Swagger Editor](https://editor.swagger.io/) to identify validation problems in your specification. The visual nature of the Swagger Editor makes it easier to understand what needs to change.
-    1. Alternatively, you can check the log output and look for schema validation warnings. They are prefixed with messages such as `OpenAPI 2.0 schema validation error` or `OpenAPI 3.0.x schema validation error`. Each failed validation provides extra information about `location` and `description`. JSON Schema validation messages can be complex, and editors can help you validate schema documents.
+   1. Use the [Swagger Editor](https://editor.swagger.io/) to identify validation problems in your specification. The visual nature of the Swagger Editor makes it easier to understand what needs to change.
+   1. Alternatively, you can check the log output and look for schema validation warnings. They are prefixed with messages such as `OpenAPI 2.0 schema validation error` or `OpenAPI 3.0.x schema validation error`. Each failed validation provides extra information about `location` and `description`. JSON Schema validation messages can be complex, and editors can help you validate schema documents.
 1. Review the documentation for the OpenAPI generation your framework/tech stack is using. Identify the changes needed to produce a correct OpenAPI document.
 1. After the validation issues are resolved, re-run your pipeline.
 
diff --git a/doc/user/application_security/api_security_testing/checks/os_command_injection_check.md b/doc/user/application_security/api_security_testing/checks/os_command_injection_check.md
index 9e1abc6d5442d24855abfa65d5da1479dca38235..48f9c579bc773f49682e16f1e4f4eefaa5744bde 100644
--- a/doc/user/application_security/api_security_testing/checks/os_command_injection_check.md
+++ b/doc/user/application_security/api_security_testing/checks/os_command_injection_check.md
@@ -21,7 +21,7 @@ Ensure your application does not:
 
 - Use user supplied information in the process name to execute.
 - Use user supplied information in an OS command execution function which does
-not escape shell meta-characters.
+  not escape shell meta-characters.
 - Use user supplied information in arguments to OS commands.
 
 The application should have a hardcoded set of arguments that are to be passed to OS commands. If filenames are being passed to these functions, it is recommended that a hash of the filename be used instead, or some other unique identifier. It is strongly recommended that a native library that implements the same functionality be used instead of using OS system commands due to the risk of unknown attacks against third party commands.
diff --git a/doc/user/application_security/coverage_fuzzing/index.md b/doc/user/application_security/coverage_fuzzing/index.md
index 72b0feb3fcb5d49d76ac2f5f00ff62c0fea1315b..9a7f52b0533d7c807652addd64c93a264cbe9f10 100644
--- a/doc/user/application_security/coverage_fuzzing/index.md
+++ b/doc/user/application_security/coverage_fuzzing/index.md
@@ -83,8 +83,8 @@ To enable coverage-guided fuzz testing, edit `.gitlab-ci.yml`:
    ```
 
 1. [Include](../../../ci/yaml/index.md#includetemplate) the
-  [`Coverage-Fuzzing.gitlab-ci.yml` template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/Coverage-Fuzzing.gitlab-ci.yml)
-  provided as part of your GitLab installation.
+   [`Coverage-Fuzzing.gitlab-ci.yml` template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/Coverage-Fuzzing.gitlab-ci.yml)
+   provided as part of your GitLab installation.
 
 1. Customize the `my_fuzz_target` job to meet your requirements.
 
diff --git a/doc/user/application_security/sast/analyzers.md b/doc/user/application_security/sast/analyzers.md
index 7082d044adcae90746338cc5361afd27d53d7b88..96c000a86c705e9c4d7bd2e0a723a6b753257ad8 100644
--- a/doc/user/application_security/sast/analyzers.md
+++ b/doc/user/application_security/sast/analyzers.md
@@ -155,19 +155,19 @@ In GitLab 15.4, we [removed the deprecated analyzers](https://gitlab.com/gitlab-
 To preview the upcoming changes to the CI/CD configuration in GitLab 15.3 or earlier:
 
 1. Open an MR to switch from the Stable CI/CD template, `SAST.gitlab-ci.yml`, to [the Latest template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/SAST.latest.gitlab-ci.yml), `SAST.latest.gitlab-ci.yml`.
-    - On GitLab.com, use the latest template directly:
+   - On GitLab.com, use the latest template directly:
 
-      ```yaml
-      include:
-        template: 'Jobs/SAST.latest.gitlab-ci.yml'
-      ```
+     ```yaml
+     include:
+       template: 'Jobs/SAST.latest.gitlab-ci.yml'
+     ```
 
-    - On a self-managed instance, download the template from GitLab.com:
+   - On a self-managed instance, download the template from GitLab.com:
 
-      ```yaml
-      include:
-        remote: 'https://gitlab.com/gitlab-org/gitlab/-/raw/2851f4d5/lib/gitlab/ci/templates/Jobs/SAST.latest.gitlab-ci.yml'
-      ```
+     ```yaml
+     include:
+       remote: 'https://gitlab.com/gitlab-org/gitlab/-/raw/2851f4d5/lib/gitlab/ci/templates/Jobs/SAST.latest.gitlab-ci.yml'
+     ```
 
 1. Verify that scanning jobs succeed in the MR. You notice findings from the removed analyzers in _Fixed_ and findings from Semgrep in _New_. (Some findings may show different names, descriptions, and severities, since GitLab manages and edits the Semgrep rulesets.)
 1. Close the MR.
diff --git a/doc/user/group/value_stream_analytics/index.md b/doc/user/group/value_stream_analytics/index.md
index 4e1d66964885af535b44fc4d5b3195a90de76a92..e11581f2ee2f2f7dc61a34f57c6fc33ade56dccc 100644
--- a/doc/user/group/value_stream_analytics/index.md
+++ b/doc/user/group/value_stream_analytics/index.md
@@ -294,8 +294,10 @@ To view value stream analytics for your group or project:
    1. Select a parameter.
    1. Select a value or enter text to refine the results.
    1. To view metrics in a particular date range, from the dropdown list select a predefined date range or the **Custom** option. With the **Custom** option selected:
-        - In the **From** field, select a start date.
-        - In the **To** field, select an end date.
+
+      - In the **From** field, select a start date.
+      - In the **To** field, select an end date.
+
       The charts and list display workflow items created during the date range.
 1. Optional. Sort results by ascending or descending:
       - To sort by most recent or oldest workflow item, select the **Last event** header.
diff --git a/doc/user/packages/harbor_container_registry/index.md b/doc/user/packages/harbor_container_registry/index.md
index d5f32888a7d0819f9020b2b810fdb23618acb84e..671de564a961791cd13c27213f83c2ff711ce36d 100644
--- a/doc/user/packages/harbor_container_registry/index.md
+++ b/doc/user/packages/harbor_container_registry/index.md
@@ -35,9 +35,9 @@ Default settings for the Harbor integration at the project level are inherited f
 To download and run a Harbor image hosted in the GitLab Harbor registry:
 
 1. Copy the link to your container image:
-    1. On the left sidebar, select **Search or go to** and find your project or group.
-    1. Select **Deploy > Harbor Registry** and find the image you want.
-    1. Select the **Copy** icon next to the image name.
+   1. On the left sidebar, select **Search or go to** and find your project or group.
+   1. Select **Deploy > Harbor Registry** and find the image you want.
+   1. Select the **Copy** icon next to the image name.
 
 1. Use the command to run the container image you want.
 
diff --git a/doc/user/product_analytics/index.md b/doc/user/product_analytics/index.md
index fa95802eb897283b38b5fb4e29d16b385f67b3fe..f28d5597a9b1c906d7f780fd64f10e1211b20267 100644
--- a/doc/user/product_analytics/index.md
+++ b/doc/user/product_analytics/index.md
@@ -253,11 +253,11 @@ The autofill approach has both benefits and limitations.
   - Data exports have rows for the entire date range, making data analysis easier.
 - Limitations:
   - The `day` [granularity](https://cube.dev/docs/product/apis-integrations/rest-api/query-format) must be used.
-  All other granularities are not supported.
+    All other granularities are not supported.
   - Only date ranges defined by the [`inDateRange`](https://cube.dev/docs/product/apis-integrations/rest-api/query-format#indaterange) filter are filled.
     - The date selector in the UI already uses this filter.
   - The filling of data ignores the query-defined limit. If you set a limit of 10 data points over 20 days, it
-  returns 20 data points, with the missing data filled by `0`. [Issue 417231](https://gitlab.com/gitlab-org/gitlab/-/issues/417231) proposes a solution to this limitation.
+    returns 20 data points, with the missing data filled by `0`. [Issue 417231](https://gitlab.com/gitlab-org/gitlab/-/issues/417231) proposes a solution to this limitation.
 
 ## Funnel analysis
 
diff --git a/doc/user/profile/comment_templates.md b/doc/user/profile/comment_templates.md
index 245b49f0650f79702d00e9e60e895d37d0fead7c..4244c261e7bad370535971f78835d706cea317c4 100644
--- a/doc/user/profile/comment_templates.md
+++ b/doc/user/profile/comment_templates.md
@@ -133,7 +133,7 @@ DETAILS:
 **Tier:** Premium, Ultimate
 
 1. In the editor toolbar for a comment, select **Comment templates**
-(**{comment-lines}**), then select **Manage group comment templates**.
+   (**{comment-lines}**), then select **Manage group comment templates**.
 1. To edit, select **Edit** (**{pencil}**).
 1. To delete, select **Delete** (**{remove}**), then select **Delete** again on the dialog.
 
@@ -143,6 +143,6 @@ DETAILS:
 **Tier:** Premium, Ultimate
 
 1. In the editor toolbar for a comment, select **Comment templates**
-(**{comment-lines}**), then select **Manage project comment templates**.
+   (**{comment-lines}**), then select **Manage project comment templates**.
 1. To edit, select **Edit** (**{pencil}**).
 1. To delete, select **Delete** (**{remove}**), then select **Delete** again on the dialog.
diff --git a/doc/user/profile/index.md b/doc/user/profile/index.md
index 24fa472c9ae3ba9e9f0c20f541085129e4f3ef96..5d990493b72c7610d1a2d97feb97a9c337c24c5d 100644
--- a/doc/user/profile/index.md
+++ b/doc/user/profile/index.md
@@ -149,7 +149,7 @@ To create a new project and add its README to your profile:
    - In the **Project name** field, enter the name for your new project.
    - In the **Project URL** field, select your GitLab username.
    - In the **Project slug** field, enter your GitLab username.
-   All of these fields are case sensitive. If your username has capital letters, enter it into the project slug field with the capitals included.
+     All of these fields are case sensitive. If your username has capital letters, enter it into the project slug field with the capitals included.
 1. For **Visibility Level**, select **Public**.
    ![Proper project path for an individual on the hosted product](img/personal_readme_setup_v14_5.png)
 1. For **Project Configuration**, ensure **Initialize repository with a README** is selected.
diff --git a/doc/user/project/integrations/gitlab_slack_application.md b/doc/user/project/integrations/gitlab_slack_application.md
index 6e1631caeaea63cdd1c09e8cbc5d2394aaa54fe5..a9e28c55db1a2c7a075eac7cd2aea3fb06baa1ee 100644
--- a/doc/user/project/integrations/gitlab_slack_application.md
+++ b/doc/user/project/integrations/gitlab_slack_application.md
@@ -148,19 +148,19 @@ To configure Slack notifications:
 1. In the **Trigger** section:
    - Select the checkbox for each GitLab [event](#notification-events) you want to receive notifications for in Slack.
    - For each checkbox you select, enter the names of the Slack channels you want to receive notifications.
-   You can enter up to 10 channel names separated by commas (for example, `#channel-one, #channel-two`).
+     You can enter up to 10 channel names separated by commas (for example, `#channel-one, #channel-two`).
 
      NOTE:
      If the Slack channel is private, you must [add the GitLab for Slack app to the channel](#receive-notifications-to-a-private-channel).
 
 1. Optional. In the **Notification settings** section:
    - Select the **Notify only broken pipelines** checkbox
-   to receive notifications for failed pipelines only.
+     to receive notifications for failed pipelines only.
    - From the **Branches for which notifications are to be sent** dropdown list,
-   select the branches you want to receive notifications for.
+     select the branches you want to receive notifications for.
    - For **Labels to be notified**, enter any or all of the labels a GitLab
-   issue, merge request, or comment must have to receive notifications for.
-   Leave blank to receive notifications for all events.
+     issue, merge request, or comment must have to receive notifications for.
+     Leave blank to receive notifications for all events.
 1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
diff --git a/doc/user/project/integrations/squash_tm.md b/doc/user/project/integrations/squash_tm.md
index d3ca7b84991355c18241fe94d0afe9ed1c1cb7b8..0f46255c80fd4d85505706f1754f45c14de75ac8 100644
--- a/doc/user/project/integrations/squash_tm.md
+++ b/doc/user/project/integrations/squash_tm.md
@@ -25,13 +25,13 @@ see [Leverage Requirements and Test management in your SDLC](https://www.youtube
 
 1. Optional. Ask your system administrator to [configure a token in the properties file](https://tm-en.doc.squashtest.com/latest/redirect/gitlab-integration-token.html).
 1. Follow the [Squash TM documentation](https://tm-en.doc.squashtest.com/latest/redirect/gitlab-integration-configuration.html) to:
-    1. Create a GitLab server.
-    1. Enable the `Xsquash4GitLab` plugin
-    1. Configure a synchronization.
-    1. From the **Real-time synchronization** panel, copy the following fields to use later in GitLab:
+   1. Create a GitLab server.
+   1. Enable the `Xsquash4GitLab` plugin
+   1. Configure a synchronization.
+   1. From the **Real-time synchronization** panel, copy the following fields to use later in GitLab:
 
-       - **Webhook URL**.
-       - **Secret token** if your Squash TM system administrator configured one at step 1.
+      - **Webhook URL**.
+      - **Secret token** if your Squash TM system administrator configured one at step 1.
 
 ## Configure GitLab
 
diff --git a/doc/user/project/merge_requests/approvals/rules.md b/doc/user/project/merge_requests/approvals/rules.md
index 11c4026790f16abbf0b2aec92810dab2134d8578..164ea99a5c2d03596e3cd8144d01325a3b211229 100644
--- a/doc/user/project/merge_requests/approvals/rules.md
+++ b/doc/user/project/merge_requests/approvals/rules.md
@@ -85,9 +85,9 @@ To edit a merge request approval rule:
 1. In the **Merge request approvals** section, in the **Approval rules** section, next to the rule you want to edit, select **Edit**.
 1. On the right sidebar, edit the fields:
    - In **Approvals required**, a value of `0` makes
-    [the rule optional](#configure-optional-approval-rules), and any number greater than `0`
-    creates a required rule.
-    Maximum number of required approvals is `100`.
+     [the rule optional](#configure-optional-approval-rules), and any number greater than `0`
+     creates a required rule.
+     Maximum number of required approvals is `100`.
    - To remove users or groups, identify the group or user to remove, and select **Remove**
      (**{remove}**).
 1. Select **Save changes**.
diff --git a/doc/user/project/repository/mirror/troubleshooting.md b/doc/user/project/repository/mirror/troubleshooting.md
index 28d6a7a090589fa906f9e50240a6e55b06d5e091..f813992f13b390f3595472987f13fdef0a52efca 100644
--- a/doc/user/project/repository/mirror/troubleshooting.md
+++ b/doc/user/project/repository/mirror/troubleshooting.md
@@ -261,7 +261,7 @@ When mirroring fails due to Silent Mode the following are the debug steps:
 - [Triggering the mirror using the API](pull.md#trigger-pipelines-for-mirror-updates) shows: `The project is not mirrored`.
 
 - If pull or push mirror was already set up but there are no further updates on the mirrored repository,
-confirm the [project's pull and push mirror details ans status](../../../../api/projects.md#get-a-projects-pull-mirror-details) are not recent as shown below. This indicates mirroring was paused and disabling GitLab Silent Mode restarts it automatically.
+  confirm the [project's pull and push mirror details ans status](../../../../api/projects.md#get-a-projects-pull-mirror-details) are not recent as shown below. This indicates mirroring was paused and disabling GitLab Silent Mode restarts it automatically.
 
 For example, if Silent Mode is what is impeding your imports, the output is similar to the following:
 
diff --git a/doc/user/project/repository/signed_commits/x509.md b/doc/user/project/repository/signed_commits/x509.md
index ada3a3abfce25d718f541ab77b199f38bdfcb5e7..975a2a41997b9fe0bff41ac119775bc2588de0ec 100644
--- a/doc/user/project/repository/signed_commits/x509.md
+++ b/doc/user/project/repository/signed_commits/x509.md
@@ -520,7 +520,7 @@ This data can now be investigated on the Linux command line using OpenSSL:
        or the signature is missing the intermediate certificates and a chain to a trusted root can't be built.
        - Intermediate certificates can be put in the trust store if it's not possible to include them in the signature.
        - [The procedure for adding certificates](https://docs.gitlab.com/omnibus/settings/ssl/#install-custom-public-certificates)
-       to the trust store for packaged GitLab - using `/etc/gitlab/trusted-certs`.
+         to the trust store for packaged GitLab - using `/etc/gitlab/trusted-certs`.
      - Test additional trusted certificates using OpenSSL with: `-CAfile /path/to/rootcertificate.pem`
    - `unsupported certificate purpose`:
      - The certificate must specify `Digital Signature` in the `X509v3 Key Usage` section of the signer's certificate.
diff --git a/doc/user/project/service_desk/configure.md b/doc/user/project/service_desk/configure.md
index a2ba14c23694f33179dbb77069a8a7c947b9b2c1..91f79ba4a9637996b8652cb68b7f3fd86113855e 100644
--- a/doc/user/project/service_desk/configure.md
+++ b/doc/user/project/service_desk/configure.md
@@ -311,7 +311,8 @@ To troubleshoot this:
 1. Sometimes GitLab cannot automatically select an authentication method that the SMTP server supports. Either:
    - Try the available authentication methods (**Plain**, **Login** and **CRAM-MD5**).
    - Check which authentication methods your SMTP server supports, using the
-   [`swaks` command line tool](https://www.jetmore.org/john/code/swaks/):
+     [`swaks` command line tool](https://www.jetmore.org/john/code/swaks/):
+
      1. Run the following command with your credentials and look for a line that starts with `250-AUTH`:
 
         ```shell