Fix article headings before running H3->H2 script (#19663)

* Fix 'How does upgrading or downgrading affect the billing process?'

* Fix 'About Git Large File StorageAbout Git Large File Storage'

* Fix 'What happens to forks when a repository is deleted or changes visibility?'

* Fix 'Audited actions'

* Fix 'About managing vulnerable dependencies'

* Fix 'GitHub Connect Addendum to the GitHub Enterprise License Agreement'

* Fix 'GitHub Government Takedown Policy'

* Fix 'GitHub Username Policy'

* Fix 'Using the Explorer'

* Fix 'Resource limitations'

content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md

@@ -16,7 +16,8 @@ topics:
   - Enterprise
   - Security
 ---
-#### Authentication
+
+### Authentication
 
 Action                               | Description
 ------------------------------------ | ----------------------------------------
@@ -39,13 +40,13 @@ Action                               | Description
   [2fa]: /articles/about-two-factor-authentication
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}
-#### {% data variables.product.prodname_actions %}
+### {% data variables.product.prodname_actions %}
 
 {% data reusables.actions.actions-audit-events-for-enterprise %}
 
 {% endif %}
 
-#### Hooks
+### Hooks
 
 Action                            | Description
 --------------------------------- | -------------------------------------------
@@ -54,7 +55,7 @@ Action                            | Description
 `hook.destroy`                    | A hook was deleted.
 `hook.events_changed`             | A hook's configured events were changed.
 
-#### Enterprise configuration settings
+### Enterprise configuration settings
 
 Action                                          | Description
 ----------------------------------------------- | -------------------------------------------{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
@@ -66,7 +67,7 @@ Action                                          | Description
 
 {% if currentVersion == "github-ae@latest" %}
 
-#### IP allow lists
+### IP allow lists
 
 Name                                 | Description
 ------------------------------------:| -----------------------------------------------------------
@@ -80,7 +81,7 @@ Name                                 | Description
 
 {% endif %}
 
-#### Issues and pull requests
+### Issues and pull requests
 
 Action                               | Description
 ------------------------------------ | -----------------------------------------------------------
@@ -89,7 +90,7 @@ Action                               | Description
 `pull_request_review_comment.delete` | A comment on a pull request was deleted.
 `issue.destroy`                      | An issue was deleted from the repository. For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)."
 
-#### Organizations
+### Organizations
 
 Action             | Description
 ------------------ | ----------------------------------------------------------
@@ -97,7 +98,7 @@ Action             | Description
 `org.delete`       | An organization was deleted by a user-initiated background job.{% if currentVersion != "github-ae@latest" %}
 `org.transform`    | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."{% endif %}
 
-#### Protected branches
+### Protected branches
 
 Action                     | Description
 -------------------------- | ----------------------------------------------------------
@@ -112,7 +113,7 @@ Action                     | Description
 `protected_branch.rejected_ref_update `     | A branch update attempt is rejected.
 `protected_branch.policy_override `         | A branch protection requirement is overridden by a repository administrator.
 
-#### Repositories
+### Repositories
 
 Action                | Description
 --------------------- | -------------------------------------------------------
@@ -132,7 +133,7 @@ Action                | Description
 `repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting is locked, preventing repository administrators from changing (enabling or disabling) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
 `repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting is unlocked, allowing repository administrators to change (enable or disable) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %}
 
-#### Site admin tools
+### Site admin tools
 
 Action                        | Description
 ----------------------------- | -----------------------------------------------
@@ -142,7 +143,7 @@ Action                        | Description
 `staff.repo_unlock`           | A site admin unlocked (temporarily gained full access to) one of a user's private repositories.
 `staff.unlock`                | A site admin unlocked (temporarily gained full access to) all of a user's private repositories.
 
-#### Teams
+### Teams
 
 Action                            | Description
 --------------------------------- | -------------------------------------------
@@ -153,7 +154,7 @@ Action                            | Description
 `team.promote_maintainer`         | A user was promoted from a team member to a team maintainer.{% endif %}
 
 
-#### Users
+### Users
 
 Action                            | Description
 --------------------------------- | -------------------------------------------

content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md

@@ -19,19 +19,19 @@ Changes to your paid user account or organization subscription does not affect s
 
 For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)" and "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
 
-#### Example of canceling a paid subscription for a personal account or organization
+### Example of canceling a paid subscription for a personal account or organization
 
 Kumiko pays for a monthly subscription on the 5th of every month. If Kumiko downgrades from the paid subscription to {% data variables.product.prodname_free_user %} on October 10th, her paid subscription will remain in effect until the end of her current billing cycle on November 4th. On November 5th, her account will move to {% data variables.product.prodname_free_user %}.
 
-#### Example of changing from a yearly to a monthly subscription for a personal account or organization
+### Example of changing from a yearly to a monthly subscription for a personal account or organization
 
 Ravi pays for a yearly subscription on October 5th every year. If Ravi switches from a yearly to monthly billing on December 10th, his account remains on the yearly subscription until the end of its current billing cycle on October 4th the next year. On October 5th of the next year, Ravi will be charged for a month of service. His next billing date will be November 5th.
 
-#### Example of adding paid seats to your organization
+### Example of adding paid seats to your organization
 
 Mada's organization pays for 25 seats on the 15th of every month. If Mada adds ten paid seats on June 4th, her organization is immediately charged a prorated amount for ten additional seats for the time between June 4th and June 14th, and the seats are available to use immediately. On June 15th, Mada's organization will pay for 35 seats.
 
-#### Example of removing paid seats from your organization
+### Example of removing paid seats from your organization
 
 Stefan's organization pays for 50 seats every year on May 20th. If Stefan removes 20 seats and downgrades to a new total of 30 paid seats on September 30, his organization can still access its 50 paid seats until the end of its current billing cycle on May 19th. On May 20th, the downgrade will take effect - Stefan's organization will pay for 30 seats and will have access to 30 paid seats.
 

content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md

@@ -13,19 +13,18 @@ topics:
 
 {% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies.
 
-#### Dependency graph
+### Dependency graph
 The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}.
 For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 
-#### Dependency review
+### Dependency review
 By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
 
-#### {% data variables.product.prodname_dependabot_alerts %}
+### {% data variables.product.prodname_dependabot_alerts %}
 {% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
 
-#### {% data variables.product.prodname_dependabot_security_updates %}
+### {% data variables.product.prodname_dependabot_security_updates %}
 When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 
-
-#### {% data variables.product.prodname_dependabot_version_updates %}
+### {% data variables.product.prodname_dependabot_version_updates %}
 Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom  %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)."

content/github/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md

@@ -13,27 +13,27 @@ versions:
 topics:
   - Pull requests
 ---
-{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}                    
+{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
-#### Deleting a private repository
+### Deleting a private repository
 
 When you delete a private repository, all of its private forks are also deleted.
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-#### Deleting a public repository
+### Deleting a public repository
 
 When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent.
 
 {% endif %}
 
-#### Private forks and permissions
+### Private forks and permissions
 
 {% data reusables.repositories.private_forks_inherit_permissions %}
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-#### Changing a public repository to a private repository
+### Changing a public repository to a private repository
 
 If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent.
 
@@ -43,15 +43,15 @@ In other words, a public repository's forks will remain public in their own sepa
 If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
 {% endif %}
 
-##### Deleting the private repository
+#### Deleting the private repository
 
 If a public repository is made private and then deleted, its public forks will continue to exist in a separate network.
 
-#### Changing a private repository to a public repository
+### Changing a private repository to a public repository
 
 If a private repository is made public, each of its private forks is turned into a standalone private repository and becomes the parent of its own new repository network. Private forks are never automatically made public because they could contain sensitive commits that shouldn't be exposed publicly.
 
-##### Deleting the public repository
+#### Deleting the public repository
 
 If a private repository is made public and then deleted, its private forks will continue to exist as standalone private repositories in separate networks.
 
@@ -59,7 +59,7 @@ If a private repository is made public and then deleted, its private forks will
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 
-#### Changing the visibility of an internal repository
+### Changing the visibility of an internal repository
 
 {% note %}
 
@@ -69,7 +69,7 @@ If a private repository is made public and then deleted, its private forks will
 
 If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or user account will remain private.
 
-##### Deleting the internal repository
+#### Deleting the internal repository
 
 If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network.
 

content/github/managing-large-files/versioning-large-files/about-git-large-file-storage.md

@@ -28,7 +28,7 @@ You can also use {% data variables.large_files.product_name_short %} with {% dat
 
 {% data reusables.large_files.can-include-lfs-objects-archives %}
 
-#### Pointer file format
+### Pointer file format
 
 {% data variables.large_files.product_name_short %}'s pointer file looks like this:
 

content/github/site-policy-deprecated/github-connect-addendum-to-the-github-enterprise-license-agreement.md

@@ -15,7 +15,7 @@ PLEASE READ THIS ADDENDUM CAREFULLY AS IT AMENDS THE TERMS OF YOUR ENTERPRISE LI
 
 BY ACCESSING GITHUB CONNECT, YOU ACCEPT ALL THE TERMS AND CONDITIONS OF THIS ADDENDUM. IF YOU ARE ENTERING INTO THIS ADDENDUM ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY (“CUSTOMER”), YOU REPRESENT THAT YOU HAVE THE LEGAL AUTHORITY TO BIND CUSTOMER TO THIS AGREEMENT.
 
-#### 1. GitHub.com’s Terms of Service and the GitHub Enterprise Software License Agreement Will Apply; Pricing
+### 1. GitHub.com’s Terms of Service and the GitHub Enterprise Software License Agreement Will Apply; Pricing
 
 Customer can enable unified integrations, which allow Customer’s Enterprise users to connect with GitHub.com (“GitHub Connect”). In order to access GitHub Connect, Customer must have at least one (1) account on GitHub.com and one (1) licensed instance of GitHub Enterprise. Customer’s access to GitHub Connect will also be governed by its applicable GitHub.com Terms of Service and the Agreement which are hereby incorporated by reference, (the "Generally Applicable Terms"), such that the Generally Applicable Terms will apply concurrently. In the event of a direct conflict between this Addendum and the Generally Applicable Terms, the Generally Applicable Terms will control, except with respect to any use of GitHub Connect, in which case this Addendum will control.
 
@@ -23,41 +23,41 @@ Customer may not use GitHub Connect to violate its Generally Applicable Terms. A
 
 Participation in GitHub Connect is provided at no additional charge through the Addendum Term (as defined below).
 
-#### 2. Confidentiality
+### 2. Confidentiality
 
 To the extent they do not conflict with the confidentiality obligations provided in the GitHub Enterprise Software License Agreement, GitHub Connect including any Confidential Information will be governed by the confidentiality obligations stated herein.
 
 For the purposes of this Addendum, "Confidential Information" means any business or technical information shared with the other party (specifically excluding any Content or information created or shared on the Service or Website, which Content or information is governed by other provisions in this Addendum and the Generally Applicable Terms) that either one of us discloses to the other, in writing, orally, or by any other means, and including things like computer programs, code, algorithms, data, know-how, formulas, processes, ideas, inventions (whether patentable or not), schematics and other technical, business, financial, and product development plans, names and expertise of employees and consultants, and customer lists. Each party agrees to maintain the other party's Confidential Information in confidence using at least the same degree of care as it uses in safeguarding its own Confidential Information, subject to a minimum standard of reasonable diligence and protection.
 
-#### 3. Term and Termination
+### 3. Term and Termination
 
 This Addendum begins on the Addendum Effective Date and continues for the duration of the License Term as defined in the Generally Applicable Terms (“Addendum Term”). This Addendum may be terminated in accordance with the Generally Applicable Terms. This Addendum will terminate immediately, without the requirement of notice, if Customer breaches any term of this Addendum or the Generally Applicable Terms.
 
 The rights and obligations in Sections 1, 2, 4 through 12, or which should naturally survive the termination or expiration of an agreement will survive the termination or expiration of this Addendum or the Generally Applicable Terms. Upon termination or expiration of this Addendum all of the rights and licenses granted to Customer in this Addendum will immediately cease to exist, Customer must destroy (or, at GitHub’s request, return) all of GitHub’s Confidential Information and any copies (including electronic copies) which are in Customer’s possession or control, and certify in writing compliance with these requirements.
 
-#### 4. Warranties and Disclaimers
+### 4. Warranties and Disclaimers
 
 Customer warrants that it: (i) has the authority to execute this Addendum and to perform its obligations; (ii) will make no false or misleading statements or representations regarding GitHub or GitHub’s products and services; and (iii) will not take on any obligation or responsibility, or make any representation, warranty, guarantee or endorsement to anyone on GitHub’s behalf (including, without limitation, any of our products or services).
 
 CUSTOMER UNDERSTANDS AND AGREES THAT ANY MATERIALS OR INFORMATION IT IS PROVIDED OR THAT IT HAS ACCESS TO UNDER THIS ADDENDUM (INCLUDING, WITHOUT LIMITATION, ANY CONFIDENTIAL INFORMATION OR PRE-RELEASE MATERIALS) ARE PROVIDED “AS IS”, AND WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. GITHUB SPECIFICALLY DISCLAIMS ANY AND ALL IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
 
-#### 5. Indemnity
+### 5. Indemnity
 
 Customer agrees to indemnify, defend and hold GitHub harmless from and against any and all claims which may arise under or out of Customer’s participation in GitHub Connect; Customer’s negligence or intentional misconduct; any misrepresentations Customer makes with respect to GitHub or GitHub’s products or services; or Customer’s violation of any part of this Addendum.
 
-#### 6. Limitation of Liability
+### 6. Limitation of Liability
 
 IN NO EVENT WILL EITHER PARTY BE LIABLE TO THE OTHER OR TO ANY THIRD PARTY FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO DAMAGES FOR LOST DATA, LOST PROFITS OR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, TORT (INCLUDING WITHOUT LIMITATION PRODUCTS LIABILITY, STRICT LIABILITY AND NEGLIGENCE), OR ANY OTHER THEORY, AND WHETHER OR NOT THE PARTY KNEW OR SHOULD HAVE KNOWN ABOUT THE POSSIBILITY OF SUCH DAMAGE. IN NO EVENT WILL GITHUB’S AGGREGATE LIABILITY TO CUSTOMER ARISING OUT OF OR RELATED TO THIS ADDENDUM FOR ANY CAUSE WHATSOEVER, AND REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT OR IN TORT, EXCEED THE GREATER OF (I) AMOUNTS ACTUALLY PAID UNDER THIS ADDENDUM; OR (II) FIVE HUNDRED DOLLARS ($500). THE FOREGOING LIMITATIONS WILL APPLY NOTWITHSTANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY STATED IN THIS ADDENDUM.
 
-#### 7. Proprietary Rights
+### 7. Proprietary Rights
 
 Customer agrees that GitHub and its licensors own all right, title and interest in and to all GitHub products and services; all information and data relating to their configurations and combinations; and all modifications to and derivative works of any of the foregoing. Customer must not remove, alter, cover or obfuscate any copyright or other proprietary rights notices that GitHub places on or embeds in GitHub Connect, or any other GitHub products and services.
 
-#### 8. Independent Development
+### 8. Independent Development
 
 Nothing in this Addendum will impair GitHub’s right to develop, acquire, license, market, promote or distribute products, software or technologies that might compete with Customer’s.
 
-#### 9. Privacy
+### 9. Privacy
 
 GitHub may collect information about how Customer uses GitHub Connect and how GitHub can improve it. Customer may enable GitHub Connect to authorize GitHub to collect protected data, which includes private repository data and Customer Personal Information (as defined in the GitHub Privacy Statement), from Customer's Enterprise account. If Customer connects its Enterprise instance with its GitHub.com account, Customer sends identifying instance information to GitHub.com, which information is governed by [GitHub’s Privacy Statement](/articles/github-privacy-statement/). By enabling this configuration, Customer agrees that it is responsible for the actions that are performed on or through its account, subject to the terms of its Generally Applicable Terms.
 
@@ -65,14 +65,14 @@ GitHub may collect certain additional personal information from Customer in GitH
 
 GitHub's servers are located in the United States. GitHub processes and controls Customer’s data in the United States. However, Customer is solely responsible for determining what personal data it submits to GitHub. Please refer to our [Privacy Statement](/articles/github-privacy-statement/) for more information.
 
-#### 10. Feedback
+### 10. Feedback
 
 Customer may, at its option, provide ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for GitHub Connect or GitHub’s other products or services (collectively, “Feedback”). If Customer provides Feedback, it acknowledges and agrees that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit or incorporate the Feedback into its products, services, and documentation.
 
-#### 11. Entire Agreement
+### 11. Entire Agreement
 
 This Addendum and the Generally Applicable Terms contain the entire agreement of the parties with respect to its subject matter and supersede all prior communications, representations, understandings and agreements, whether written or oral. The terms or conditions of any of Customer’s purchase orders, acknowledgements, or other documents sent in connection with this Addendum will be null and void, and of no effect.
 
-#### 12. No Other Modifications; Order of Precedence
+### 12. No Other Modifications; Order of Precedence
 
 Except as expressly provided herein, nothing in this Addendum shall be deemed to waive or modify any of the provisions of the Agreement, which otherwise remains in full force and effect.  In the event of any conflict between the Agreement and this Addendum regarding the subject matter set forth herein, this Addendum shall prevail.

content/github/site-policy/github-government-takedown-policy.md

@@ -6,16 +6,17 @@ topics:
   - Policy
   - Legal
 ---
-#### What is this?
+
+### What is this?
 From time to time, GitHub receives requests from governments to remove content that has been declared unlawful in their local jurisdiction. Although we may not always agree with those laws, we may need to block content if we receive a complete request from a government official so that our users in that jurisdiction may continue to have access to GitHub to collaborate and build software.
 
-#### What is a complete government takedown request?
+### What is a complete government takedown request?
 To count as a complete request, a request or notice must
 - come from a relevant, official government agency
 - identify illegal content
 - specify the source of illegality in that jurisdiction (law or court order).
 
-#### What happens when we receive a complete takedown request from a government?
+### What happens when we receive a complete takedown request from a government?
 
 When we receive a notice from a relevant, official government agency that identifies illegal content and specifies the source of the illegality, we
 - notify the affected users of the specific content that allegedly violates the law, and that this is a legal takedown request
@@ -23,11 +24,11 @@ When we receive a notice from a relevant, official government agency that identi
 - limit the geographic scope of the takedown when possible and include that as part of the notification
 - post the official request that led to the takedown in our public [gov-takedowns repository](https://github.com/github/gov-takedowns).
 
-#### Why do we publicly post takedown notices?
+### Why do we publicly post takedown notices?
 We are concerned about Internet censorship, and believe that transparency on a specific and ongoing level is essential to good governance. By publicly posting the notices, we can better inform the public about what content is being withheld from GitHub, and why. We post takedown notices to document their potential to chill speech.
 
-#### What does it mean if we post a notice in our gov-takedowns repository?
+### What does it mean if we post a notice in our gov-takedowns repository?
 It means that we received the notice on the indicated date. It does *not* mean that the content was unlawful or wrong. It does *not* mean that the user identified in the notice has done anything wrong. We don't make or imply any judgment about the merit of the claims they make. We post these notices and requests only for informational purposes.
 
-#### Transparency reporting
+### Transparency reporting
 In addition to posting government takedown notices in our gov-takedowns repository, we report on them in our transparency report. We also track and report in our transparency report on government takedowns based on violations of GitHub's Terms of Service. We process those violations as we would process a Terms of Service violation reported by anyone else.

content/github/site-policy/github-username-policy.md

@@ -12,16 +12,16 @@ topics:
 
 GitHub account names are available on a first-come, first-served basis, and are intended for immediate and active use.
 
-#### What if the username I want is already taken?
+### What if the username I want is already taken?
 
 Keep in mind that not all activity on GitHub is publicly visible; accounts with no visible activity may be in active use.
 
 If the username you want has already been claimed, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you identify a desirable username still available.
 
-#### Trademark Policy
+### Trademark Policy
 
 If you believe someone's account is violating your trademark rights, you can find more information about making a trademark complaint on our [Trademark Policy](/articles/github-trademark-policy/) page.
 
-#### Name Squatting Policy
+### Name Squatting Policy
 
 GitHub prohibits account name squatting, and account names may not be reserved or inactively held for future use. Accounts violating this name squatting policy may be removed or renamed without notice. Attempts to sell, buy, or solicit other forms of payment in exchange for account names are prohibited and may result in permanent account suspension.

content/graphql/guides/using-the-explorer.md

@@ -11,7 +11,7 @@ topics:
   - API
 ---
 
-## About the GraphQL Explorer
+### About the GraphQL Explorer
 
 {% if currentVersion == "free-pro-team@latest" %}
 

content/graphql/overview/resource-limitations.md

@@ -19,7 +19,7 @@ To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all
 * Values of `first` and `last` must be within 1-100.
 * Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node).
 
-#### Calculating nodes in a call
+### Calculating nodes in a call
 
 These two examples show how to calculate the total nodes in a call.
 
@@ -148,7 +148,7 @@ Note that 5,000 points per hour is not the same as 5,000 calls per hour: the Gra
 
 {% endnote %}
 
-#### Returning a call's rate limit status
+### Returning a call's rate limit status
 
 With the REST API v3, you can check the rate limit status by [inspecting](/rest/overview/resources-in-the-rest-api#rate-limiting) the returned HTTP headers.
 
@@ -176,7 +176,7 @@ query {
 
 * The `resetAt` field returns the time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
 
-#### Calculating a rate limit score before running the call
+### Calculating a rate limit score before running the call
 
 Querying the `rateLimit` object returns a call's score, but running the call counts against the limit. To avoid this dilemma, you can calculate the score of a call before you run it. The following calculation works out to roughly the same cost that `rateLimit { cost }` returns.