Remove multiple spaces after hash (#37392)

content/actions/learn-github-actions/essential-features-of-github-actions.md

@@ -18,7 +18,7 @@ topics:
 
 {% data variables.product.prodname_actions %} allow you to customize your workflows to meet the unique needs of your application and team. In this guide, we'll discuss some of the essential customization techniques such as using variables, running scripts, and sharing data and artifacts between jobs.
 
-##  Using variables in your workflows
+## Using variables in your workflows
 
 {% data variables.product.prodname_actions %} include default environment variables for each workflow run. If you need to use custom environment variables, you can set these in your YAML workflow file. This example demonstrates how to create custom variables named `POSTGRES_HOST` and `POSTGRES_PORT`. These variables are then available to the `node client.js` script.
 

content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription-for-your-organization-or-enterprise.md

@@ -45,7 +45,7 @@ Before you can start using {% data variables.product.prodname_copilot %} in your
 
 {% endif %}
 
-##  Modifying your {% data variables.product.prodname_copilot_business_short %} subscription
+## Modifying your {% data variables.product.prodname_copilot_business_short %} subscription
 
 {% ifversion ghec %}
 

content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md

@@ -48,7 +48,7 @@ You set up {% data variables.product.prodname_dotcom %} to run {% data variables
 {% data reusables.code-scanning.edit-workflow %}
 For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/customizing-code-scanning)" and  "[AUTOTITLE](/actions/learn-github-actions)."
 
-##  About autobuild for {% data variables.product.prodname_codeql %}
+## About autobuild for {% data variables.product.prodname_codeql %}
 
 {% data variables.product.prodname_code_scanning_caps %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository.
 For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %}{% ifversion codeql-kotlin-beta %} Kotlin, {% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}

content/site-policy/github-terms/github-sponsors-additional-terms.md

@@ -105,7 +105,7 @@ While we understand that you may want to promote your Sponsors by posting their
 ### 4.1. Payment.
 GitHub will pay you the Sponsored Developer Payment in accordance with this Section 4, so long as you meet the Sponsored Developer Obligations in Section 3 and are not in violation of these Additional Terms. If you fail to meet these obligations for any given month, we may at our sole discretion withhold the Sponsored Developer Payment for that month. If you fail to meet or maintain the Sponsored Developer Obligations for two (2) or more months during the Term (consecutively or non-consecutively), then GitHub may terminate these Additional Terms as provided in Section 6.
 
-###  4.2. Sponsored Developer Payment Exclusions.
+### 4.2. Sponsored Developer Payment Exclusions.
 The following amounts are not included in Sponsored Developer Payments, or may be withheld by GitHub, as applicable.
 
 #### 4.2.1. Sponsored Developer Expenses.

content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md

@@ -34,7 +34,7 @@ These GitHub Supplemental Terms include the following Sections and Exhibits, eac
 
 
 
-##  SECTION 1: GITHUB ENTERPRISE SERVER LICENSE TERMS
+## SECTION 1: GITHUB ENTERPRISE SERVER LICENSE TERMS
 
 This Section 1 details terms applicable to Customer’s use of the Software.
 

data/reusables/enterprise-migration-tool/migration-destination-query.md

@@ -1,4 +1,4 @@
-####  `GetOrgInfo` query
+#### `GetOrgInfo` query
 
 ```graphql
 query(