diff --git a/data/reusables/actions/actions-group-concurrency.md b/data/reusables/actions/actions-group-concurrency.md
index 55ec220e27e0..e04d76c9468c 100644
--- a/data/reusables/actions/actions-group-concurrency.md
+++ b/data/reusables/actions/actions-group-concurrency.md
@@ -1,6 +1,6 @@
 This means that there can be at most one running and one pending job in a concurrency group at any time. When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any existing `pending` job or workflow in the same concurrency group, if it exists, will be canceled and the new queued job or workflow will take its place.
 
-To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`.  To conditionally cancel currently running jobs or workflows in the same concurrency group, you can specify `cancel-in-progress` as an expression with any of the allowed expression contexts.
+To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`. To conditionally cancel currently running jobs or workflows in the same concurrency group, you can specify `cancel-in-progress` as an expression with any of the allowed expression contexts.
 
 > [!NOTE]
 > * The concurrency group name is case insensitive. For example, `prod` and `Prod` will be treated as the same concurrency group.
diff --git a/data/reusables/actions/add-hosted-runner.md b/data/reusables/actions/add-hosted-runner.md
index 3b65799e8e31..678247bf8699 100644
--- a/data/reusables/actions/add-hosted-runner.md
+++ b/data/reusables/actions/add-hosted-runner.md
@@ -6,7 +6,7 @@
     * **Image**: Choose an image from the available options. Once you've selected an image, you will be able to choose a specific size.
       * **GitHub-owned**: For images managed by GitHub, select an image under this tab.
       * **Partner**: For images managed by a partner, select an image under this tab. Windows 11 desktop and GPU-optimized images are located under this tab.
-    * **Size**: Choose a hardware configuration from the list of available options. The available sizes depend on the image that you selected in a previous step.  For GPU runners, select a size under the **GPU-powered** tab.
+    * **Size**: Choose a hardware configuration from the list of available options. The available sizes depend on the image that you selected in a previous step. For GPU runners, select a size under the **GPU-powered** tab.
     * **Maximum concurrency**: Choose the maximum number of jobs that can be active at any time.
     * **Runner group**: Choose the group that your runner will be a member of. This group will host multiple instances of your runner, as they scale up and down to suit demand. {% ifversion ghec %}
     * **Networking**: Choose whether static IP address ranges will be assigned to instances of the {% data variables.actions.hosted_runner %}. You can use up to 10 {% data variables.actions.hosted_runner %}s with static IP addresses in total. {% endif %}
diff --git a/data/reusables/actions/azure-vnet-configure-azure-resources-script.md b/data/reusables/actions/azure-vnet-configure-azure-resources-script.md
index 78f71e05d245..2288318f9900 100644
--- a/data/reusables/actions/azure-vnet-configure-azure-resources-script.md
+++ b/data/reusables/actions/azure-vnet-configure-azure-resources-script.md
@@ -71,7 +71,7 @@ echo Delegate subnet to GitHub.Network/networkSettings and apply NSG rules
 
 echo
 echo Create network settings resource $NETWORK_SETTINGS_RESOURCE_NAME
-. az resource create --resource-group $RESOURCE_GROUP_NAME  --name $NETWORK_SETTINGS_RESOURCE_NAME --resource-type GitHub.Network/networkSettings --properties "{ \"location\": \"$AZURE_LOCATION\", \"properties\" : {  \"subnetId\": \"/subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP_NAME/providers/Microsoft.Network/virtualNetworks/$VNET_NAME/subnets/$SUBNET_NAME\", \"businessId\": \"$DATABASE_ID\" }}" --is-full-object --output table --query "{GitHubId:tags.GitHubId, name:name}" --api-version $API_VERSION
+. az resource create --resource-group $RESOURCE_GROUP_NAME --name $NETWORK_SETTINGS_RESOURCE_NAME --resource-type GitHub.Network/networkSettings --properties "{ \"location\": \"$AZURE_LOCATION\", \"properties\" : { \"subnetId\": \"/subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP_NAME/providers/Microsoft.Network/virtualNetworks/$VNET_NAME/subnets/$SUBNET_NAME\", \"businessId\": \"$DATABASE_ID\" }}" --is-full-object --output table --query "{GitHubId:tags.GitHubId, name:name}" --api-version $API_VERSION
 
 echo
 echo To clean up and delete resources run the following command:
diff --git a/data/reusables/actions/azure-vnet-procedures-prereqs.md b/data/reusables/actions/azure-vnet-procedures-prereqs.md
index 72a31810ddbf..3e3dfa526d1a 100644
--- a/data/reusables/actions/azure-vnet-procedures-prereqs.md
+++ b/data/reusables/actions/azure-vnet-procedures-prereqs.md
@@ -15,7 +15,7 @@ You will use a script to automate configuring your Azure resources.
   If you use {% data variables.enterprise.data_residency %}, in the `AllowOutBoundGitHub` section, you must also include the egress IP ranges for {% data variables.enterprise.data_residency_site %}. See "[AUTOTITLE](/admin/data-residency/network-details-for-ghecom#ranges-for-egress-traffic)."
 
   > [!NOTE]
-  > As an alternative to using the following file, to allow {% data variables.product.prodname_actions %} to communicate with the runners, you can allow the same firewall domains that are required for communication between self-hosted runners and {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-cloud)." To determine the appropriate subnet IP address range,  we recommend adding a 30% buffer to the maximum job concurrency you anticipate. For instance, if your network configuration's runners are set to a maximum job concurrency of 300, it's recommended to utilize a subnet IP address range that can accommodate at least 390 runners. This buffer helps ensure that your network can handle unexpected increases in VM needs to meet job concurrency without running out of IP addresses.
+  > As an alternative to using the following file, to allow {% data variables.product.prodname_actions %} to communicate with the runners, you can allow the same firewall domains that are required for communication between self-hosted runners and {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-cloud)." To determine the appropriate subnet IP address range, we recommend adding a 30% buffer to the maximum job concurrency you anticipate. For instance, if your network configuration's runners are set to a maximum job concurrency of 300, it's recommended to utilize a subnet IP address range that can accommodate at least 390 runners. This buffer helps ensure that your network can handle unexpected increases in VM needs to meet job concurrency without running out of IP addresses.
 
   ```bicep copy
   @description('NSG for outbound rules')
diff --git a/data/reusables/actions/expression-syntax-if.md b/data/reusables/actions/expression-syntax-if.md
index db40c5764d41..fef2631fd775 100644
--- a/data/reusables/actions/expression-syntax-if.md
+++ b/data/reusables/actions/expression-syntax-if.md
@@ -1,6 +1,6 @@
 When you use expressions in an `if` conditional, you can, optionally, omit the {% raw %}`${{ }}`{% endraw %} expression syntax because {% data variables.product.prodname_actions %} automatically evaluates the `if` conditional as an expression. However, this exception does not apply everywhere.
 
-You must always use the {% raw %}`${{ }}`{% endraw %} expression syntax or escape with `''`, `""`,  or `()` when the expression starts with `!`, since `!` is reserved notation in YAML format. For example:
+You must always use the {% raw %}`${{ }}`{% endraw %} expression syntax or escape with `''`, `""`, or `()` when the expression starts with `!`, since `!` is reserved notation in YAML format. For example:
 
 {% raw %}
 
diff --git a/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md b/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
index ad34a787f0a0..d039bf637c7e 100644
--- a/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
+++ b/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
@@ -1,5 +1,5 @@
 You can use `permissions` to modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[AUTOTITLE](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token)."
 
-You can use `permissions` either as a top-level key, to apply to all jobs in the workflow, or within specific jobs. When you add the `permissions` key within a specific job, all actions and run commands within that job that use the `GITHUB_TOKEN` gain the access rights you specify.  For more information, see [`jobs.<job_id>.permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions).
+You can use `permissions` either as a top-level key, to apply to all jobs in the workflow, or within specific jobs. When you add the `permissions` key within a specific job, all actions and run commands within that job that use the `GITHUB_TOKEN` gain the access rights you specify. For more information, see [`jobs.<job_id>.permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions).
 
 {% data reusables.actions.github-token-scope-descriptions %}
diff --git a/data/reusables/actions/jobs/section-using-environments-for-jobs.md b/data/reusables/actions/jobs/section-using-environments-for-jobs.md
index 66015f307a7d..06492566e15a 100644
--- a/data/reusables/actions/jobs/section-using-environments-for-jobs.md
+++ b/data/reusables/actions/jobs/section-using-environments-for-jobs.md
@@ -37,7 +37,7 @@ environment:
 
 {% endraw %}
 
-The value of `name` can be an expression. Allowed expression contexts:  [`github`](/actions/learn-github-actions/contexts#github-context), [`inputs`](/actions/learn-github-actions/contexts#inputs-context), [`vars`](/actions/learn-github-actions/contexts#vars-context), [`needs`](/actions/learn-github-actions/contexts#needs-context), [`strategy`](/actions/learn-github-actions/contexts#strategy-context), and [`matrix`](/actions/learn-github-actions/contexts#matrix-context). For more information about expressions, see "[AUTOTITLE](/actions/learn-github-actions/expressions)."
+The value of `name` can be an expression. Allowed expression contexts: [`github`](/actions/learn-github-actions/contexts#github-context), [`inputs`](/actions/learn-github-actions/contexts#inputs-context), [`vars`](/actions/learn-github-actions/contexts#vars-context), [`needs`](/actions/learn-github-actions/contexts#needs-context), [`strategy`](/actions/learn-github-actions/contexts#strategy-context), and [`matrix`](/actions/learn-github-actions/contexts#matrix-context). For more information about expressions, see "[AUTOTITLE](/actions/learn-github-actions/expressions)."
 
 ### Example: Using an expression as environment name
 
diff --git a/data/reusables/actions/workflow-basic-example-and-explanation.md b/data/reusables/actions/workflow-basic-example-and-explanation.md
index 3062196a2e3a..bd18afd193fb 100644
--- a/data/reusables/actions/workflow-basic-example-and-explanation.md
+++ b/data/reusables/actions/workflow-basic-example-and-explanation.md
@@ -1,6 +1,6 @@
 ## Creating an example workflow
 
-{% data variables.product.prodname_actions %} uses YAML syntax to define the workflow.  Each workflow is stored as a separate YAML file in your code repository, in a directory named `.github/workflows`.
+{% data variables.product.prodname_actions %} uses YAML syntax to define the workflow. Each workflow is stored as a separate YAML file in your code repository, in a directory named `.github/workflows`.
 
 You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the [bats](https://www.npmjs.com/package/bats) testing framework, and runs a basic command to output the bats version: `bats -v`.
 
@@ -38,7 +38,7 @@ name: learn-github-actions
 # Optional - The name for workflow runs generated from the workflow, which will appear in the list of workflow runs on your repository's "Actions" tab. This example uses an expression with the `github` context to display the username of the actor that triggered the workflow run. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#run-name)."
 run-name: {% raw %}${{ github.actor }}{% endraw %} is learning GitHub Actions
 
-# Specifies the trigger for this workflow. This example uses the `push` event, so a workflow run is triggered every time someone pushes a change to the repository or merges a pull request.  This is triggered by a push to every branch; for examples of syntax that runs only on pushes to specific branches, paths, or tags, see "[AUTOTITLE](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+# Specifies the trigger for this workflow. This example uses the `push` event, so a workflow run is triggered every time someone pushes a change to the repository or merges a pull request. This is triggered by a push to every branch; for examples of syntax that runs only on pushes to specific branches, paths, or tags, see "[AUTOTITLE](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
 on: [push]
 
 # Groups together all the jobs that run in the `learn-github-actions` workflow.
diff --git a/data/reusables/actions/workflows/run-on-specific-branches-or-tags1.md b/data/reusables/actions/workflows/run-on-specific-branches-or-tags1.md
index 5a1fcf65ab26..f2b429913054 100644
--- a/data/reusables/actions/workflows/run-on-specific-branches-or-tags1.md
+++ b/data/reusables/actions/workflows/run-on-specific-branches-or-tags1.md
@@ -5,6 +5,6 @@ Use the `branches` filter when you want to include branch name patterns or when
 
 Use the `tags` filter when you want to include tag name patterns or when you want to both include and exclude tag names patterns. Use the `tags-ignore` filter when you only want to exclude tag name patterns. You cannot use both the `tags` and `tags-ignore` filters for the same event in a workflow.
 
-If you define only `tags`/`tags-ignore` or only `branches`/`branches-ignore`, the workflow won't run for events affecting the undefined Git ref. If you define neither  `tags`/`tags-ignore` or `branches`/`branches-ignore`, the workflow will run for events affecting either branches or tags. If you define both `branches`/`branches-ignore` and [`paths`/`paths-ignore`](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), the workflow will only run when both filters are satisfied.
+If you define only `tags`/`tags-ignore` or only `branches`/`branches-ignore`, the workflow won't run for events affecting the undefined Git ref. If you define neither `tags`/`tags-ignore` or `branches`/`branches-ignore`, the workflow will run for events affecting either branches or tags. If you define both `branches`/`branches-ignore` and [`paths`/`paths-ignore`](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), the workflow will only run when both filters are satisfied.
 
 The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to _escape_ each of these special characters with `\`. For more information about glob patterns, see the "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
diff --git a/data/reusables/actions/workflows/section-triggering-a-workflow-types.md b/data/reusables/actions/workflows/section-triggering-a-workflow-types.md
index c1210c529758..05b719abc969 100644
--- a/data/reusables/actions/workflows/section-triggering-a-workflow-types.md
+++ b/data/reusables/actions/workflows/section-triggering-a-workflow-types.md
@@ -1,4 +1,4 @@
-Use `on.<event_name>.types` to define the type of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity.  For example, the `label` is triggered when a label is `created`, `edited`, or `deleted`. The `types` keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the `types` keyword is unnecessary.
+Use `on.<event_name>.types` to define the type of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the `label` is triggered when a label is `created`, `edited`, or `deleted`. The `types` keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the `types` keyword is unnecessary.
 
 You can use an array of event `types`. For more information about each event and their activity types, see "[AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#available-events)."
 
diff --git a/data/reusables/apps/github_app_auth_saml.md b/data/reusables/apps/github_app_auth_saml.md
index 6fbef954d1fe..c8ad5734c866 100644
--- a/data/reusables/apps/github_app_auth_saml.md
+++ b/data/reusables/apps/github_app_auth_saml.md
@@ -1 +1 @@
-If a user reports that they cannot see resources owned by their organization after authorizing your {% data variables.product.prodname_github_app %} and the organization uses SAML SSO, instruct the user to start an active SAML session for their organization before reauthorizing. For more information, see {% ifversion ghec %}"[AUTOTITLE](/apps/using-github-apps/saml-and-github-apps)."{% else %}"[AUTOTITLE](/enterprise-cloud@latest/apps/using-github-apps/saml-and-github-apps)" in the  {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
+If a user reports that they cannot see resources owned by their organization after authorizing your {% data variables.product.prodname_github_app %} and the organization uses SAML SSO, instruct the user to start an active SAML session for their organization before reauthorizing. For more information, see {% ifversion ghec %}"[AUTOTITLE](/apps/using-github-apps/saml-and-github-apps)."{% else %}"[AUTOTITLE](/enterprise-cloud@latest/apps/using-github-apps/saml-and-github-apps)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
diff --git a/data/reusables/audit_log/audit-log-action-categories.md b/data/reusables/audit_log/audit-log-action-categories.md
index 45566fcad583..3ca3a35db895 100644
--- a/data/reusables/audit_log/audit-log-action-categories.md
+++ b/data/reusables/audit_log/audit-log-action-categories.md
@@ -40,7 +40,7 @@
 | `config_entry` |  Contains activities related to configuration settings. These events are only visible in the site admin audit log. |
 | {% endif %} |
 | `dependabot_alerts`  | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." |
-| `dependabot_alerts_new_repos`   | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. |
+| `dependabot_alerts_new_repos`   | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. |
 | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. |
 | `dependabot_security_updates`   | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." |
 | `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. |
@@ -126,7 +126,7 @@
 | `pull_request_review_comment` | Contains activities related to pull request review comments. |
 | `repo` | Contains activities related to the repositories owned by an organization. |
 | {% ifversion fpt or ghec %} |
-| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}.  For more information, see "[AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories)." |
+| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories)." |
 | `repository_content_analysis`   | Contains activities related to enabling or disabling data use for a private repository. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#enabling-or-disabling-security-and-analysis-features-for-private-repositories)." |
 | `repository_dependency_graph`   | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." |
 | {% endif %} |
diff --git a/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
index 5426b3187a3f..cd7f8f912b2e 100644
--- a/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
+++ b/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
@@ -1 +1 @@
-1. In the "Archive" section of the  sidebar, click **{% octicon "log" aria-hidden="true" %} Logs**, then click **Audit log**.
+1. In the "Archive" section of the sidebar, click **{% octicon "log" aria-hidden="true" %} Logs**, then click **Audit log**.
diff --git a/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
index 8f559aa32123..ab12e111c51d 100644
--- a/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
+++ b/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
@@ -1 +1 @@
-1. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-hidden="true" %} Security log**.
+1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-hidden="true" %} Security log**.
diff --git a/data/reusables/code-scanning/filter-non-default-branches.md b/data/reusables/code-scanning/filter-non-default-branches.md
index 6d8d85de0bac..6addef7e07ee 100644
--- a/data/reusables/code-scanning/filter-non-default-branches.md
+++ b/data/reusables/code-scanning/filter-non-default-branches.md
@@ -1 +1 @@
-Please note that if you have filtered for alerts on a non-default branch, but the same alerts exist on the default branch, the alert page for any given alert will still only reflect the alert's status on the default branch, even if that status conflicts with the status on a non-default branch. For example, an alert that appears in the "Open" list in the summary of alerts for `branch-x` could show a status of "Fixed" on the alert page, if the alert is already fixed on the default branch. You can view the status of the alert for the branch you filtered on in the  **Affected branches** section on the right side of the alert page.
+Please note that if you have filtered for alerts on a non-default branch, but the same alerts exist on the default branch, the alert page for any given alert will still only reflect the alert's status on the default branch, even if that status conflicts with the status on a non-default branch. For example, an alert that appears in the "Open" list in the summary of alerts for `branch-x` could show a status of "Fixed" on the alert page, if the alert is already fixed on the default branch. You can view the status of the alert for the branch you filtered on in the **Affected branches** section on the right side of the alert page.
diff --git a/data/reusables/codespaces/customize-vcpus-and-ram.md b/data/reusables/codespaces/customize-vcpus-and-ram.md
index 57f4593141d7..d2a9e8b129d6 100644
--- a/data/reusables/codespaces/customize-vcpus-and-ram.md
+++ b/data/reusables/codespaces/customize-vcpus-and-ram.md
@@ -1,5 +1,5 @@
 You can customize your codespace by adjusting the amount of vCPUs and RAM, adding dotfiles to personalize your environment, or by modifying the tools and scripts installed. For more information, see "[AUTOTITLE](/codespaces/customizing-your-codespace)."
 
-{% data variables.product.prodname_github_codespaces %} uses a file called `devcontainer.json` to configure the development container that you use when you work in a codespace. Each repository can contain one or more  `devcontainer.json` files, to give you exactly the development environment you need to work on your code in a codespace.
+{% data variables.product.prodname_github_codespaces %} uses a file called `devcontainer.json` to configure the development container that you use when you work in a codespace. Each repository can contain one or more `devcontainer.json` files, to give you exactly the development environment you need to work on your code in a codespace.
 
 On launch, {% data variables.product.prodname_github_codespaces %} uses a `devcontainer.json` file, and any dependent files that make up the dev container configuration, to install tools and runtimes, and perform other setup tasks that the project requires. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
diff --git a/data/reusables/codespaces/publishing-template-codespaces.md b/data/reusables/codespaces/publishing-template-codespaces.md
index 0bc29f296404..89bfeb118272 100644
--- a/data/reusables/codespaces/publishing-template-codespaces.md
+++ b/data/reusables/codespaces/publishing-template-codespaces.md
@@ -1,7 +1,7 @@
 If you're working in a codespace, you can publish it from the {% data variables.product.prodname_vscode_shortname %} web client or desktop application.
 
 {% data reusables.codespaces.source-control-activity-bar %}
-1. To stage your changes, click  **+** next to the file you've added or changed, or next to **Changes** if you've changed multiple files and you want to stage them all.
+1. To stage your changes, click **+** next to the file you've added or changed, or next to **Changes** if you've changed multiple files and you want to stage them all.
 
    ![Screenshot of the "Source control" side bar with the staging button (a plus sign), to the right of "Changes," highlighted with a dark orange outline.](/assets/images/help/codespaces/codespaces-commit-stage.png)
 
diff --git a/data/reusables/codespaces/source-control.md b/data/reusables/codespaces/source-control.md
index f8071fbb5d9e..9dc5c6fc90d7 100644
--- a/data/reusables/codespaces/source-control.md
+++ b/data/reusables/codespaces/source-control.md
@@ -14,7 +14,7 @@ When you create a codespace from a template repository or a template on the "You
 ## Committing your changes
 
 {% data reusables.codespaces.source-control-activity-bar %}
-1. To stage your changes, click  {% octicon "plus" aria-label="Stage changes" %} next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all.
+1. To stage your changes, click {% octicon "plus" aria-label="Stage changes" %} next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all.
 
    ![Screenshot of the "Source control" side bar with the staging button (a plus sign), to the right of "Changes," highlighted with a dark orange outline.](/assets/images/help/codespaces/codespaces-commit-stage.png)
 
diff --git a/data/reusables/copilot/differences-cfi-cfb-table.md b/data/reusables/copilot/differences-cfi-cfb-table.md
index c907338e0ebc..77619ec178be 100644
--- a/data/reusables/copilot/differences-cfi-cfb-table.md
+++ b/data/reusables/copilot/differences-cfi-cfb-table.md
@@ -7,7 +7,7 @@
 | {% data variables.product.prodname_copilot_chat_short %} in IDEs[^2] | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
 | {% data variables.product.prodname_copilot_mobile_short %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
 | {% data variables.product.prodname_copilot_chat_dotcom_short %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
-| {% data variables.product.prodname_copilot_chat_short %}  in {% data variables.product.prodname_windows_terminal %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
+| {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_windows_terminal %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
 | {% data variables.product.prodname_copilot_cli_short %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
 | Block suggestions matching public code     | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
 | {% data variables.product.prodname_copilot_for_prs %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} | {% octicon "check" aria-label="Included" %} |
diff --git a/data/reusables/dependabot/dependabot-security-updates-groups-supported.md b/data/reusables/dependabot/dependabot-security-updates-groups-supported.md
index 24fbb308eb74..9b07638794e7 100644
--- a/data/reusables/dependabot/dependabot-security-updates-groups-supported.md
+++ b/data/reusables/dependabot/dependabot-security-updates-groups-supported.md
@@ -1,4 +1,4 @@
-{% ifversion dependabot-grouped-security-updates-config %}You can use the  `dependabot.yml` file to create separate rules to group {% data variables.product.prodname_dependabot_version_updates %} and {% data variables.product.prodname_dependabot_security_updates %}.{% else %}
+{% ifversion dependabot-grouped-security-updates-config %}You can use the `dependabot.yml` file to create separate rules to group {% data variables.product.prodname_dependabot_version_updates %} and {% data variables.product.prodname_dependabot_security_updates %}.{% else %}
 You can only use the `dependabot.yml` file to create groups for {% data variables.product.prodname_dependabot_version_updates %}. Grouped {% data variables.product.prodname_dependabot_security_updates %} are enabled or disabled in your repository or organization settings and do not support customization. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates#about-grouped-security-updates)."{% endif %}
 
 > [!NOTE]
diff --git a/data/reusables/dependabot/supported-package-managers.md b/data/reusables/dependabot/supported-package-managers.md
index 65d8752eac0e..71f2ffd6373e 100644
--- a/data/reusables/dependabot/supported-package-managers.md
+++ b/data/reusables/dependabot/supported-package-managers.md
@@ -53,7 +53,7 @@ You can use `devcontainers` as a `package-ecosystem` in your `dependabot.yml` fi
 
 Dev containers are used in several tools and services, including {% data variables.product.prodname_codespaces %}. For more information about Features and the supported services, see [Features](https://containers.dev/implementors/features/) and [Supporting tools and services](https://containers.dev/supporting) in the Development Containers documentation, respectively.
 
-This updater ensures Features are pinned to the latest `major` version in the associated `devcontainer.json` file.  If a dev container has a lockfile, that file will also be updated. For more information about lockfile specifications, see [Lockfiles](https://github.com/devcontainers/spec/blob/main/docs/specs/devcontainer-lockfile.md) in the `devcontainers/spec` repository.
+This updater ensures Features are pinned to the latest `major` version in the associated `devcontainer.json` file. If a dev container has a lockfile, that file will also be updated. For more information about lockfile specifications, see [Lockfiles](https://github.com/devcontainers/spec/blob/main/docs/specs/devcontainer-lockfile.md) in the `devcontainers/spec` repository.
 
 Features in any valid dev container location will be updated in a single pull request. For more information about the dev container specification, see [Specification](https://containers.dev/implementors/spec/#devcontainerjson) in the Development Containers documentation.
 
@@ -69,7 +69,7 @@ Features in any valid dev container location will be updated in a single pull re
 In order for {% data variables.product.prodname_dependabot %} to fetch Docker metadata, maintainers of Docker images must add the `org.opencontainers.image.source` label to their Dockerfile, and include the URL of the source repository. Additionally, maintainers must tag the repository with the same tags as the published Docker images. For an example, see the [`dependabot-fixtures/docker-with-source`](https://github.com/dependabot-fixtures/docker-with-source) repository. For more information on Docker labels, see [Extension image labels](https://docs.docker.com/desktop/extensions-sdk/extensions/labels/) and [BUILDX_GIT_LABELS](https://docs.docker.com/build/building/env-vars/#buildx_git_labels) in the Docker documentation.
 {% endif %}
 
-{% data variables.product.prodname_dependabot %} can update Docker image tags in Kubernetes manifests. Add an entry to the Docker `package-ecosystem` element of your `dependabot.yml` file for each directory containing a Kubernetes manifest which references Docker image tags. Kubernetes manifests can be Kubernetes Deployment YAML files or Helm charts. For information about configuring your `dependabot.yml` file for `docker`, see  "`package-ecosystem`" in "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem)."
+{% data variables.product.prodname_dependabot %} can update Docker image tags in Kubernetes manifests. Add an entry to the Docker `package-ecosystem` element of your `dependabot.yml` file for each directory containing a Kubernetes manifest which references Docker image tags. Kubernetes manifests can be Kubernetes Deployment YAML files or Helm charts. For information about configuring your `dependabot.yml` file for `docker`, see "`package-ecosystem`" in "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem)."
 
 {% data variables.product.prodname_dependabot %} supports both public and private Docker registries. For a list of the supported registries, see "`docker-registry`" in "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#docker-registry)."
 {% endif %}
diff --git a/data/reusables/discussions/starting-a-discussion.md b/data/reusables/discussions/starting-a-discussion.md
index 7e33f133ea10..9952edcfbada 100644
--- a/data/reusables/discussions/starting-a-discussion.md
+++ b/data/reusables/discussions/starting-a-discussion.md
@@ -3,7 +3,7 @@
 1. On the right side of the page, click **New discussion**.
 1. Select a discussion category by clicking **Get started**.
 
-   ![Screenshot of the "Select a discussion category" page.  A button, labeled "Get started", is outlined in dark orange.](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png)
+   ![Screenshot of the "Select a discussion category" page. A button, labeled "Get started", is outlined in dark orange.](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png)
 
 1. Under "Discussion title", type a title for your discussion, and under "Write", type the body of your discussion.
 
diff --git a/data/reusables/enterprise-migration-tool/grant-migrator-role-graphql.md b/data/reusables/enterprise-migration-tool/grant-migrator-role-graphql.md
index d2b6a41bdcf0..a826086e4881 100644
--- a/data/reusables/enterprise-migration-tool/grant-migrator-role-graphql.md
+++ b/data/reusables/enterprise-migration-tool/grant-migrator-role-graphql.md
@@ -25,7 +25,7 @@ mutation grantMigratorRole (
 |----|----|
 | `organizationId` | The `ownerId` (or organization ID) for your organization, from the `GetOrgInfo` query.
 | `actor` | The team or username who you want to assign the migration role to.
-|  `actor_type` | Specify whether the migrator is a `USER` or `TEAM`.
+| `actor_type` | Specify whether the migrator is a `USER` or `TEAM`.
 
 #### `revokeMigratorRole` mutation
 
diff --git a/data/reusables/enterprise_installation/increase-resources-communicate-and-enable-maintenance-mode.md b/data/reusables/enterprise_installation/increase-resources-communicate-and-enable-maintenance-mode.md
index 05eae8d731ca..c1e90c69de10 100644
--- a/data/reusables/enterprise_installation/increase-resources-communicate-and-enable-maintenance-mode.md
+++ b/data/reusables/enterprise_installation/increase-resources-communicate-and-enable-maintenance-mode.md
@@ -1,4 +1,4 @@
-1. Communicate the upcoming downtime to your users and enable maintenance mode.  For more information, see the following articles.
+1. Communicate the upcoming downtime to your users and enable maintenance mode. For more information, see the following articles.
 
    * "[AUTOTITLE](/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-mandatory-message)"
    * "[AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode)"
diff --git a/data/reusables/enterprise_migrations/token-generation.md b/data/reusables/enterprise_migrations/token-generation.md
index 49a7c9f52f24..fcdf09b3203a 100644
--- a/data/reusables/enterprise_migrations/token-generation.md
+++ b/data/reusables/enterprise_migrations/token-generation.md
@@ -1 +1 @@
-[Generate an access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) with the `repo` and  `admin:org` scopes
+[Generate an access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) with the `repo` and `admin:org` scopes
diff --git a/data/reusables/files/choose-commit-email.md b/data/reusables/files/choose-commit-email.md
index 32cff80d725f..e8da0f234971 100644
--- a/data/reusables/files/choose-commit-email.md
+++ b/data/reusables/files/choose-commit-email.md
@@ -1,5 +1,5 @@
 {%- ifversion fpt or ghec %}
-1. If you have more than one email address associated with your account on {% data variables.product.prodname_dotcom %}, click the email address drop-down menu and select the email address to use as the Git author email address. Only verified email addresses appear in this drop-down menu. If you enabled email address privacy, then a no-reply will be the default commit author email address.  For more information about the exact form the no-reply email address can take, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)."
+1. If you have more than one email address associated with your account on {% data variables.product.prodname_dotcom %}, click the email address drop-down menu and select the email address to use as the Git author email address. Only verified email addresses appear in this drop-down menu. If you enabled email address privacy, then a no-reply will be the default commit author email address. For more information about the exact form the no-reply email address can take, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)."
 
     ![Screenshot of a {% data variables.product.prodname_dotcom %} pull request showing a dropdown menu with options to choose the commit author email address. octocat@github.com is selected.](/assets/images/help/repository/choose-commit-email-address.png)
 {%- endif %}
diff --git a/data/reusables/gated-features/historical-insights-for-projects.md b/data/reusables/gated-features/historical-insights-for-projects.md
index 88ea54d89f44..1531d3b247b7 100644
--- a/data/reusables/gated-features/historical-insights-for-projects.md
+++ b/data/reusables/gated-features/historical-insights-for-projects.md
@@ -1 +1 @@
-Insights is available for the new Projects experience, you cannot use Insights with {% data variables.product.prodname_projects_v1 %}. Historical charts are available with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations. You can save unlimited charts in private projects with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations and {% data variables.product.prodname_pro %} for users. Users and organizations using a public project can also save unlimited charts. Users and organizations using {% data variables.product.prodname_free_team %} or a legacy plan can save two charts in private projects.  {% data reusables.gated-features.more-info %}
+Insights is available for the new Projects experience, you cannot use Insights with {% data variables.product.prodname_projects_v1 %}. Historical charts are available with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations. You can save unlimited charts in private projects with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations and {% data variables.product.prodname_pro %} for users. Users and organizations using a public project can also save unlimited charts. Users and organizations using {% data variables.product.prodname_free_team %} or a legacy plan can save two charts in private projects. {% data reusables.gated-features.more-info %}
diff --git a/data/reusables/getting-started/github-pages-enterprise.md b/data/reusables/getting-started/github-pages-enterprise.md
index aed03e573bf3..b9675fbf505f 100644
--- a/data/reusables/getting-started/github-pages-enterprise.md
+++ b/data/reusables/getting-started/github-pages-enterprise.md
@@ -1 +1 @@
-{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can enable or disable {% data variables.product.prodname_pages %} for your enterprise members at the organization level. For more information, see  "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise)" and "[AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages)."
+{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can enable or disable {% data variables.product.prodname_pages %} for your enterprise members at the organization level. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise)" and "[AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages)."
diff --git a/data/reusables/identity-and-permissions/team-sync-usage-limits.md b/data/reusables/identity-and-permissions/team-sync-usage-limits.md
index 9a11b72ca4da..e08b2ea38815 100644
--- a/data/reusables/identity-and-permissions/team-sync-usage-limits.md
+++ b/data/reusables/identity-and-permissions/team-sync-usage-limits.md
@@ -1,6 +1,6 @@
 ### Usage limits
 
-There are usage limits for the team synchronization feature.  Exceeding these limits will lead to a degradation in performance and may cause synchronization failures.
+There are usage limits for the team synchronization feature. Exceeding these limits will lead to a degradation in performance and may cause synchronization failures.
 
 * Maximum number of members in a GitHub team: 5,000
 * Maximum number of members in a GitHub organization: 10,000
diff --git a/data/reusables/interactions/contributor-user-limit-definition.md b/data/reusables/interactions/contributor-user-limit-definition.md
index e750eb466295..1d4f85a074bd 100644
--- a/data/reusables/interactions/contributor-user-limit-definition.md
+++ b/data/reusables/interactions/contributor-user-limit-definition.md
@@ -1 +1 @@
-**Contributors only:** When you limit interactions to `contributors_only`,  users who have not previously contributed and are not collaborators will be temporarily restricted
+**Contributors only:** When you limit interactions to `contributors_only`, users who have not previously contributed and are not collaborators will be temporarily restricted
diff --git a/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md b/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md
index 4ecebf610fe4..ccd3525df755 100644
--- a/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md
+++ b/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md
@@ -1 +1 @@
-{% data variables.product.prodname_registry %} supports `SNAPSHOT` versions of Apache Maven. To use the {% data variables.product.prodname_registry %} repository for downloading `SNAPSHOT` artifacts, enable SNAPSHOTS in the POM of the consuming project or your  _~/.m2/settings.xml_ file.
+{% data variables.product.prodname_registry %} supports `SNAPSHOT` versions of Apache Maven. To use the {% data variables.product.prodname_registry %} repository for downloading `SNAPSHOT` artifacts, enable SNAPSHOTS in the POM of the consuming project or your _~/.m2/settings.xml_ file.
diff --git a/data/reusables/pages/twenty-minutes-to-publish.md b/data/reusables/pages/twenty-minutes-to-publish.md
index 69c96062b499..22cf2a175f14 100644
--- a/data/reusables/pages/twenty-minutes-to-publish.md
+++ b/data/reusables/pages/twenty-minutes-to-publish.md
@@ -1 +1 @@
-**Note:** It can take up to 10 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}.  If you don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see "[AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites)."
+**Note:** It can take up to 10 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}. If you don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see "[AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites)."
diff --git a/data/reusables/project-management/delete-label.md b/data/reusables/project-management/delete-label.md
index f3f93215ef9c..a051f353d8e6 100644
--- a/data/reusables/project-management/delete-label.md
+++ b/data/reusables/project-management/delete-label.md
@@ -1 +1 @@
-  1. In the labels list, to the right of the label you want to delete, click  **Delete**.
+  1. In the labels list, to the right of the label you want to delete, click **Delete**.
diff --git a/data/reusables/projects/about-table-layout.md b/data/reusables/projects/about-table-layout.md
index 80144b87c6e4..0df8fd62e1a8 100644
--- a/data/reusables/projects/about-table-layout.md
+++ b/data/reusables/projects/about-table-layout.md
@@ -1 +1 @@
-The table layout is a powerful and adaptable spreadsheet comprised of your issues, pull requests, and draft issues with metadata from {% data variables.product.company_short %} and the custom fields you've added to your project.  You can group, sort, and filter items, and show or hide fields in your table layouts to suit the needs of everyone on your team.
+The table layout is a powerful and adaptable spreadsheet comprised of your issues, pull requests, and draft issues with metadata from {% data variables.product.company_short %} and the custom fields you've added to your project. You can group, sort, and filter items, and show or hide fields in your table layouts to suit the needs of everyone on your team.
diff --git a/data/reusables/projects/project-description.md b/data/reusables/projects/project-description.md
index b5b8eb9f883b..9159c05dd29b 100644
--- a/data/reusables/projects/project-description.md
+++ b/data/reusables/projects/project-description.md
@@ -1,7 +1,7 @@
 You can set your project's description and README to share the purpose of your project, provide instructions on how to use the project, and include any relevant links.
 
 {% data reusables.projects.project-settings %}
-1. To add a short description to your project, under "Add a description", type your description in the text box  and click **Save**.
+1. To add a short description to your project, under "Add a description", type your description in the text box and click **Save**.
 1. To update your project's README, under "README", type your content in the text box.
    * You can format your README using Markdown. For more information, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
    * To toggle between the text box and a preview of your changes, click {% octicon "eye" aria-label="The preview icon" %} or {% octicon "pencil" aria-label="The edit icon" %}.
diff --git a/data/reusables/repositories/allow-maintainers-user-forks.md b/data/reusables/repositories/allow-maintainers-user-forks.md
index 56d803a1a4f6..0b0c2eafe9b4 100644
--- a/data/reusables/repositories/allow-maintainers-user-forks.md
+++ b/data/reusables/repositories/allow-maintainers-user-forks.md
@@ -1,4 +1,4 @@
 1. On user-owned forks, if you want to allow anyone with push access to the upstream repository to make changes to your pull request, select **Allow edits from maintainers**.
 
     > [!WARNING]
-    > If your fork contains {% data variables.product.prodname_actions %} workflows, the option is  **Allow edits and access to secrets by maintainers**. Allowing edits on a fork's branch that contains {% data variables.product.prodname_actions %} workflows also allows a maintainer to edit the forked repository's workflows, which can potentially reveal values of secrets and grant access to other branches.
+    > If your fork contains {% data variables.product.prodname_actions %} workflows, the option is **Allow edits and access to secrets by maintainers**. Allowing edits on a fork's branch that contains {% data variables.product.prodname_actions %} workflows also allows a maintainer to edit the forked repository's workflows, which can potentially reveal values of secrets and grant access to other branches.
diff --git a/data/reusables/repositories/relative-links.md b/data/reusables/repositories/relative-links.md
index 1d0010ee0da2..48dd8b6bd48c 100644
--- a/data/reusables/repositories/relative-links.md
+++ b/data/reusables/repositories/relative-links.md
@@ -1,6 +1,6 @@
 You can define relative links and image paths in your rendered files to help readers navigate to other files in your repository.
 
-A relative link is a link that is relative to the current file. For example, if you have a  README file in root of your repository, and you have another file in _docs/CONTRIBUTING.md_, the relative link to _CONTRIBUTING.md_ in your README might look like this:
+A relative link is a link that is relative to the current file. For example, if you have a README file in root of your repository, and you have another file in _docs/CONTRIBUTING.md_, the relative link to _CONTRIBUTING.md_ in your README might look like this:
 
 ```text
 [Contribution guidelines for this project](docs/CONTRIBUTING.md)
diff --git a/data/reusables/repositories/security-alerts-x-github-severity.md b/data/reusables/repositories/security-alerts-x-github-severity.md
index 2741a8f189a1..7fcc8de8a70d 100644
--- a/data/reusables/repositories/security-alerts-x-github-severity.md
+++ b/data/reusables/repositories/security-alerts-x-github-severity.md
@@ -1 +1 @@
-Email notifications for {% data variables.product.prodname_dependabot_alerts %} that affect one or more repositories include the `X-GitHub-Severity`  header field. You can use the value of the `X-GitHub-Severity` header field to filter email notifications for {% data variables.product.prodname_dependabot_alerts %}.
+Email notifications for {% data variables.product.prodname_dependabot_alerts %} that affect one or more repositories include the `X-GitHub-Severity` header field. You can use the value of the `X-GitHub-Severity` header field to filter email notifications for {% data variables.product.prodname_dependabot_alerts %}.
diff --git a/data/reusables/rest-api/secondary-rate-limit-rest-graphql.md b/data/reusables/rest-api/secondary-rate-limit-rest-graphql.md
index 406d89b65798..4f747331fc7f 100644
--- a/data/reusables/rest-api/secondary-rate-limit-rest-graphql.md
+++ b/data/reusables/rest-api/secondary-rate-limit-rest-graphql.md
@@ -19,6 +19,6 @@ Some secondary rate limits are determined by the point values of requests. For G
 | GraphQL requests without mutations | 1 |
 | GraphQL requests with mutations | 5 |
 | Most REST API `GET`, `HEAD`, and `OPTIONS` requests | 1 |
-| Most REST API `POST`, `PATCH`, `PUT`, or `DELETE`  requests | 5 |
+| Most REST API `POST`, `PATCH`, `PUT`, or `DELETE` requests | 5 |
 
 Some REST API endpoints have a different point cost that is not shared publicly.
diff --git a/data/reusables/saml/testing-saml-sso.md b/data/reusables/saml/testing-saml-sso.md
index 3129fa8d30ca..e34ba66a37b9 100644
--- a/data/reusables/saml/testing-saml-sso.md
+++ b/data/reusables/saml/testing-saml-sso.md
@@ -1 +1 @@
-When setting up SAML SSO in your organization, you can test your implementation without affecting your organization members by leaving  **Require SAML SSO authentication for all members of the _organization name_ organization** unchecked.
+When setting up SAML SSO in your organization, you can test your implementation without affecting your organization members by leaving **Require SAML SSO authentication for all members of the _organization name_ organization** unchecked.
diff --git a/data/reusables/secret-scanning/bypass-reasons-and-alerts.md b/data/reusables/secret-scanning/bypass-reasons-and-alerts.md
index 2013a23b7c33..82c68dc9bbec 100644
--- a/data/reusables/secret-scanning/bypass-reasons-and-alerts.md
+++ b/data/reusables/secret-scanning/bypass-reasons-and-alerts.md
@@ -1,6 +1,6 @@
 This table shows the behavior of alerts for each way a user can bypass a push protection block.
 
-| Bypass reason         | Alert  behavior                                              |
+| Bypass reason         | Alert behavior                                              |
 |-----------------------|------------------------------------------------------|
 | It's used in tests    | {% data variables.product.prodname_dotcom %} creates a closed alert, resolved as "used in tests"  |
 | It's a false positive | {% data variables.product.prodname_dotcom %} creates a closed alert, resolved as "false positive" |
diff --git a/data/reusables/support/help_resources.md b/data/reusables/support/help_resources.md
index c6dca457e416..d06da9d99df6 100644
--- a/data/reusables/support/help_resources.md
+++ b/data/reusables/support/help_resources.md
@@ -1,4 +1,4 @@
-For questions, bug reports, and discussions about {% data variables.product.prodname_github_apps %},  {% data variables.product.prodname_oauth_apps %}, and API development, explore the  {% data reusables.support.prodname_support_forum_with_url %}. The discussions are moderated and maintained by {% data variables.product.company_short %} staff, and answered by the {% data variables.product.company_short %} community.
+For questions, bug reports, and discussions about {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and API development, explore the {% data reusables.support.prodname_support_forum_with_url %}. The discussions are moderated and maintained by {% data variables.product.company_short %} staff, and answered by the {% data variables.product.company_short %} community.
 
 Consider reaching out to [GitHub Support](https://support.github.com/) directly using the contact form for:
 * guaranteed response from {% data variables.product.product_name %} staff
diff --git a/data/reusables/supported-languages/Cs.md b/data/reusables/supported-languages/Cs.md
index dc392b2ca2f5..7333586dad33 100644
--- a/data/reusables/supported-languages/Cs.md
+++ b/data/reusables/supported-languages/Cs.md
@@ -1 +1 @@
-| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI  | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI |{% endif %}
+| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>`dotnet` CLI |{% endif %}
diff --git a/data/reusables/supported-languages/swift.md b/data/reusables/supported-languages/swift.md
index 778e5a9e6c8f..1e36d67c51d3 100644
--- a/data/reusables/supported-languages/swift.md
+++ b/data/reusables/supported-languages/swift.md
@@ -1 +1 @@
-| Swift | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |  {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>Swift Package Manager  |
+| Swift | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>Swift Package Manager |
diff --git a/data/reusables/two_fa/manual-totp-app-setup.md b/data/reusables/two_fa/manual-totp-app-setup.md
index c0ef429d92e8..79b9cd97ce02 100644
--- a/data/reusables/two_fa/manual-totp-app-setup.md
+++ b/data/reusables/two_fa/manual-totp-app-setup.md
@@ -2,7 +2,7 @@ If you are unable to scan the setup QR code or wish to setup a TOTP app manually
 
 * Type: `TOTP`
 * Label: `GitHub:<username>` where `<username>` is your handle on {% data variables.product.prodname_dotcom %}, for example `monalisa`
-* Secret: This is the encoded setup key, shown if you click "Setup key"  during configuration
+* Secret: This is the encoded setup key, shown if you click "Setup key" during configuration
 * Issuer: `GitHub`
 * Algorithm: The default of SHA1 is used
 * Digits: The default of 6 is used
diff --git a/data/reusables/webhooks/public_short_desc.md b/data/reusables/webhooks/public_short_desc.md
index 3f7ac658afc0..f665fd28c0f0 100644
--- a/data/reusables/webhooks/public_short_desc.md
+++ b/data/reusables/webhooks/public_short_desc.md
@@ -1 +1 @@
-When a private repository is made public.  Without a doubt: the best {% data variables.product.product_name %} event.
+When a private repository is made public. Without a doubt: the best {% data variables.product.product_name %} event.