fix spacing content lint rules (#39332)

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md

@@ -33,8 +33,6 @@ If you have low vision, you may benefit from a high contrast theme, with greater
 1. Click the theme you'd like to use.
     - If you chose a single theme, click a theme.
 
-      
-
     - If you chose to follow your system settings, click a day theme and a night theme.{% ifversion fpt or ghec %}
     - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[AUTOTITLE](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
 

content/admin/code-security/managing-supply-chain-security-for-your-enterprise/configuring-dependabot-to-work-with-limited-internet-access.md

@@ -27,7 +27,7 @@ The instructions below assume that you need to set up {% data variables.product.
 
 Before configuring {% data variables.product.prodname_dependabot %}, install Docker on your self-hosted runner. For more information, see "[AUTOTITLE](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates#configuring-self-hosted-runners-for-dependabot-updates)."
 
-1.  On {% data variables.location.product_location %}, navigate to the `github/dependabot-action` repository and retrieve information about the `dependabot-updater` and `dependabot-proxy` container images from the `containers.json` file.
+1. On {% data variables.location.product_location %}, navigate to the `github/dependabot-action` repository and retrieve information about the `dependabot-updater` and `dependabot-proxy` container images from the `containers.json` file.
 
    Each release of {% data variables.product.product_name %} includes an updated `containers.json` file at: `https://HOSTNAME/github/dependabot-action/blob/ghes-VERSION/docker/containers.json`. You can see the {% data variables.product.prodname_dotcom_the_website %} version of the file at: [containers.json](https://github.com/github/dependabot-action/blob/main/docker/containers.json).
 

content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md

@@ -56,7 +56,6 @@ You can perform initial validation of your maintenance operation by configuring
 
 ## Validating changes in maintenance mode using the IP exception list
 
-
 The IP exception list provides controlled and restricted access to {% data variables.location.product_location %}, which is ideal for initial validation of server health following a maintenance operation. Once enabled, {% data variables.location.product_location %} will be taken out of maintenance mode and available only to the configured IP addresses. The maintenance mode checkbox will be updated to reflect the change in state.
 
 If you re-enable maintenance mode, the IP exception list will be disabled and {% data variables.location.product_location %} will return to maintenance mode. If you just disable the IP exception list, {% data variables.location.product_location %} will return to normal operation.

content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md

@@ -20,7 +20,6 @@ shortTitle: Manage GitHub Mobile
 
 You can allow or disallow people from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.location.product_location %} and access your instance's data. By default, {% data variables.product.prodname_mobile %} is enabled for people who use {% data variables.location.product_location %}.
 
-
 ## Enabling or disabling {% data variables.product.prodname_mobile %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}

content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md

@@ -221,7 +221,7 @@ To install the official bundled actions and starter workflows within a designate
     ghe-config app.actions.github-org ORGANIZATION
     ```
 
-1.  To add the bundled actions to your organization, unset the SHA.
+1. To add the bundled actions to your organization, unset the SHA.
 
     ```shell
     ghe-config --unset 'app.actions.actions-repos-sha1sum'

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md

@@ -31,7 +31,6 @@ This article explains how site administrators can configure {% data variables.pr
 
 ## Review hardware requirements
 
-
 The CPU and memory resources available to {% data variables.location.product_location %} determine the number of runners that can be configured without performance loss. {% data reusables.actions.minimum-hardware %}
 
 The peak quantity of connected runners without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated performance targets for GitHub Enterprise Server on a range of CPU and memory configurations.

content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md

@@ -62,7 +62,6 @@ After you configure the application for {% data variables.product.product_name %
 
 {% endif %}
 
-
 {% ifversion ghes %}
 
 {% data reusables.enterprise_user_management.external_auth_disables_2fa %}

content/apps/creating-github-apps/writing-code-for-a-github-app/building-ci-checks-with-a-github-app.md

@@ -920,7 +920,6 @@ After running RuboCop and saving the linting results, this code runs the command
 
 The `rm -rf` command cannot be undone. To keep your app secure, the code in this tutorial checks incoming webhooks for injected malicious commands that could be used to remove a different directory than intended by your app. For example, if a bad actor sent a webhook with the repository name `./`, your app would remove the root directory. The `verify_webhook_signature` method validates the sender of the webhook. The `verify_webhook_signature` event handler also checks that the repository name is valid. For more information, see "[Define a `before` filter](#define-a-before-filter)."
 
-
 ### Test the code
 
 The following steps will show you how to test that the code works and view the errors reported by RuboCop.

content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md

@@ -25,7 +25,6 @@ Rolling {% data variables.product.prodname_code_scanning %} out across hundreds
 {% ifversion ghec %}
 {% data variables.product.prodname_code_scanning_caps %} is also available for all public repositories on {% data variables.product.prodname_dotcom_the_website %} without a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
 
-
 ### Preparing teams for {% data variables.product.prodname_code_scanning %}
 
 First, prepare your teams to use {% data variables.product.prodname_code_scanning %}. The more teams that use {% data variables.product.prodname_code_scanning %}, the more data you'll have to drive remediation plans and monitor progress on your rollout. During this phase, focus on leveraging APIs and running internal enablement events.

content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md

@@ -54,7 +54,6 @@ To calculate the security severity of an alert, we use Common Vulnerability Scor
 
 By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/customizing-code-scanning#defining-the-severities-causing-pull-request-check-failure)."
 
-
 ### About {% ifversion remove-code-scanning-configurations %}alerts from multiple configurations{% else %}analysis origins{% endif %}
 
 {% ifversion remove-code-scanning-configurations %}

content/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli.md

@@ -74,7 +74,6 @@ From macOS version 10.15 ("Catalina") onwards you need to ensure that your web b
 1. Click the **General** Tab.
 1. Ensure the check-box labeled **Open "safe" files after downloading** is unchecked.
 
-
 ### 2. Extract the zip archive
 
 For Linux, Windows, and macOS users (version 10.14 "Mojave", and earlier) simply extract the zip archive.

content/code-security/getting-started/securing-your-repository.md

@@ -71,7 +71,6 @@ For more information, see "[AUTOTITLE](/code-security/supply-chain-security/unde
 
 For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts){% ifversion fpt or ghec %}" and "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}."
 
-
 ## Managing dependency review
 
 Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."

content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md

@@ -22,4 +22,3 @@ You can manually select the region that your codespaces will be created in, allo
 1. Under "Region", select the setting you want: **Set automatically** or **Set manually**.
 
 1. If you chose **Set manually**, select the dropdown menu and click your region.
-

content/codespaces/developing-in-codespaces/deleting-a-codespace.md

@@ -55,7 +55,6 @@ There are costs associated with storing codespaces. You should therefore delete
 
 {% endnote %}
 
-
 {% vscode %}
 
 {% data reusables.codespaces.deleting-a-codespace-in-vscode %}

content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md

@@ -81,7 +81,6 @@ Disabling the workflow runs for a prebuild configuration is useful if you need t
 
 {% endnote %}
 
-
 Deleting a prebuild configuration also deletes all previously created prebuilds for that configuration. As a result, shortly after you delete a configuration, prebuilds generated by that configuration will no longer be available when you create a new codespace.
 
 After you delete a prebuild configuration, workflow runs for that configuration that have been queued or started will still run. They will be listed in the workflow run history, along with previously completed workflow runs.

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md

@@ -56,7 +56,7 @@ assignees: octocat
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
 1. In the file name field:
-    -  To make your issue template visible in the repository's root directory, type the name of your _issue_template_. For example, `issue_template.md`.
+    - To make your issue template visible in the repository's root directory, type the name of your _issue_template_. For example, `issue_template.md`.
     - To make your issue template visible in the repository's `docs` directory, type _docs/_ followed by the name of your _issue_template_. For example, `docs/issue_template.md`,
     - To store your file in a hidden directory, type _.github/_ followed by the name of your _issue_template_. For example, `.github/issue_template.md`.
     - To create multiple issue templates and use the `template` query parameter to specify a template to fill the issue body, type _.github/ISSUE_TEMPLATE/_, then the name of your issue template. For example, `.github/ISSUE_TEMPLATE/issue_template.md`. You can also store multiple issue templates in an `ISSUE_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue)."

content/contributing/syntax-and-versioning-for-github-docs/changing-an-articles-title.md

@@ -11,7 +11,6 @@ versions:
 
 Sometimes, it's necessary to change the title of a help article. There are several considerations to keep in mind when you retitle an article.
 
-
 ## Background on changing the filename
 
 The title of the article corresponds directly to the name of the Markdown file that contains that article, for a couple of reasons:

content/contributing/writing-for-github-docs/content-model.md

@@ -380,7 +380,7 @@ Contents of tutorials:
   - Does not include the expected amount of time that it may take someone to complete the task - this depends on the experience level of the person completing the tutorial.
 - Procedural sections
   - Based on the tutorial's audience, the steps can be less explicit and formal than those used in procedural content. You do not have to use existing reusables to form these steps if the audience doesn’t require that level of detail.
-    - Use: "From your profile, click **Settings, and then click **Developer settings**.”
+    - Use: "From your profile, click **Settings**, and then click **Developer settings**.”
     - Avoid: In the upper-right corner of any page, click your profile photo, then click **Settings**. In the left sidebar, click **Developer settings**.
   - Link out to other articles or resources rather than replicating them, to avoid interrupting the flow of information in the tutorial.
   - Give visual cues. Use code blocks and screenshots heavily to help reassure people that they are performing the correct actions.

content/contributing/writing-for-github-docs/style-guide.md

@@ -995,7 +995,6 @@ Table content is left-aligned by default. Use Markdown table formatting, colons
 
 The following example shows part of a table from "[AUTOTITLE](/free-pro-team@latest/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)."
 
-
 <table>
 <thead>
 <tr>

content/contributing/writing-for-github-docs/templates.md

@@ -289,7 +289,6 @@ Include a bulleted list of tutorials or articles the user can reference to exten
 
 Use the content model for full instructions and examples on how to write for {% data variables.product.prodname_docs %}. For more information, see "[AUTOTITLE](/contributing/writing-for-github-docs/content-model)."
 
-
 ```yaml
 {% raw %}---
 title: Guide title

content/contributing/writing-for-github-docs/using-videos-in-github-docs.md

@@ -11,7 +11,6 @@ versions:
 
 Videos are used rarely in the {% data variables.product.prodname_docs %}. When videos are necessary to provide the best user experience for an article, they are used together with written text. Videos are not a replacement for written content. Videos should never be the only way information is communicated because they are more difficult to keep up to date and are not accessible to everyone.
 
-
 Use these guidelines to determine if a video is appropriate to include in an article or on a landing page in the docs.
 
 If you add a link to a video or embed a video in the {% data variables.product.prodname_docs %}, add the video's metadata to the "[Videos in {% data variables.product.prodname_docs %}](https://github.com/github/docs/blob/main/contributing/videos-in-github-docs.md)" file in the `github/docs` repository.

content/issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists.md

@@ -48,11 +48,11 @@ Draft tasks are text items that are added to your tasklist. Draft tasks appear i
   
 1. Add some draft tasks to sketch out this work. Type your draft task and then press <kbd>Enter</kbd> after each one.
 
-  For our example landing page scenario, you can add:
-    * "Design new landing page"
-    * "Create content for landing page"
-    * "Translate content into supported languages"
-    
+   For our example landing page scenario, you can add:
+   - "Design new landing page"
+   - "Create content for landing page"
+   - "Translate content into supported languages"
+
 ## Converting a draft task into an issue
 
 You can convert your draft tasks into issues. You can convert draft tasks when you're ready to start work on a particular task. The issues are created in the same repository you have used for your tracking issue.
@@ -126,7 +126,6 @@ You can also track existing issues by adding them to your tasklist. You can add
   
   ![Screenshot of an issue being edited. There are two tasklists present and the "Update comment" button is highlighted with an orange rectangle.](/assets/images/help/projects-v2/tasklist-markdown-draft-edit.png)
   
-
 You will see your new second tasklist displayed beneath your first tasklist.
 
 ## Tracking progress

content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md

@@ -15,7 +15,6 @@ topics:
 
 {% endif %}
 
-
 ## About automatically archiving items
 
 You can configure your project's built-in workflows to automatically archive items. Archiving items will help you stay below the limit of {% data variables.projects.item_limit %} items in each project.

content/migrations/using-ghe-migrator/exporting-migration-data-from-githubcom.md

@@ -56,7 +56,7 @@ The Migrations API is currently in a preview period, which means that the endpoi
       https://api.github.com/orgs/ORG_NAME/migrations
       ```
 
-    -  If you want to lock the repositories before migrating them, make sure `lock_repositories` is set to `true`. This is highly recommended.
+    - If you want to lock the repositories before migrating them, make sure `lock_repositories` is set to `true`. This is highly recommended.
     - You can exclude file attachments by passing `exclude_attachments: true` to the endpoint. {% data reusables.enterprise_migrations.exclude-file-attachments %} The final archive size must be less than 20 GB.
 
   This request returns a unique `id` which represents your migration. You'll need it for subsequent calls to the Migrations API.

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

@@ -66,7 +66,6 @@ If a private repository is made public and then deleted, its private forks will
 
 When you change a private repository to public, all the commits in that repository, including any commits made in the repositories it was forked into, will be visible to everyone. However, the private forks will not automatically become public. Instead, each private fork will become a separate private repository and create its own independent network of repositories. Any new changes made to these networks will not be accessible from the original 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/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md

@@ -110,7 +110,7 @@ The following scenario outlines what happens when a CI reports a failing status
 1. The merge queue creates a temporary branch with the prefix of `main/pr-1` that contains code changes from the target branch and pull request #1. A `merge_group` webhook event of type `checks_requested` is dispatched and the merge queue will await a response from your CI provider.
 1. User adds pull request #2 to the merge queue.
 1. The merge queue creates a temporary branch with the prefix of `main/pr-2` that contains code changes from the target branch, pull request #1, and pull request #2, and dispatches webhooks.
-1.  When the {% data variables.product.product_name %} API receives a failing status for `main/pr-1`, the merge queue automatically removes pull request #1 from the merge queue.
+1. When the {% data variables.product.product_name %} API receives a failing status for `main/pr-1`, the merge queue automatically removes pull request #1 from the merge queue.
 1. The merge queue recreates the temporary branch with the prefix of `main/pr-2` to only contain changes from the target branch and pull request #2.
 1. When the {% data variables.product.product_name %} API receives successful CI responses for `merge_group` branch `main/pr-2`, the temporary branch `main/pr-2` will be merged in to the target branch without pull request #1 included.
 

content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md

@@ -28,9 +28,9 @@ topics:
 
 {% ifversion code-search-code-view %} You can also use suggestions and completions in the search bar to quickly find what you need.
 
--  If you click on the search bar in the top navigation of GitHub.com, you will see a list of suggestions organized by category, including recent searches and suggested repositories, teams, and projects that you have access to.
--  Clicking on any of the specific suggestions will take you directly to the page for that suggestion (for example, the repository or project page). If you click on a recent search, depending on the type of search, the search term will appear in the search bar or you will be taken to the search results page for the search term.
--  Once you start typing, you will see a list of completions and suggestions that match your query. You can click on a suggestion to jump to a specific location. As you continue to type, you will see more specific suggestions, such as code files you can jump to directly.
+- If you click on the search bar in the top navigation of GitHub.com, you will see a list of suggestions organized by category, including recent searches and suggested repositories, teams, and projects that you have access to.
+- Clicking on any of the specific suggestions will take you directly to the page for that suggestion (for example, the repository or project page). If you click on a recent search, depending on the type of search, the search term will appear in the search bar or you will be taken to the search results page for the search term.
+- Once you start typing, you will see a list of completions and suggestions that match your query. You can click on a suggestion to jump to a specific location. As you continue to type, you will see more specific suggestions, such as code files you can jump to directly.
 
 After typing a search query, you can press **Enter** to go to the full search results view, where you can see each match and a visual interface for applying filters. For more information, see "[Searching using a visual interface](#searching-using-a-visual-interface)."
 {% endif %}

content/search-github/searching-on-github/searching-discussions.md

@@ -145,7 +145,6 @@ You can filter discussions by specific labels that are applied to discussions.
 | :- | :- |
 | <code>label: <em>"LABEL NAME"</em></code> | [**label:"Product Feedback"**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22product+feedback%22&type=discussions) matches discussions that match the label "Product Feedback".
 
-
 ## Further reading
 
 - "[AUTOTITLE](/search-github/getting-started-with-searching-on-github/sorting-search-results)"

data/reusables/dependabot/beta-security-and-version-updates.md

@@ -1,5 +1,4 @@
 
-
 {% ifversion ghae = 3.4 %}
 
 {% note %}

data/reusables/enterprise_installation/replica-ssh.md

@@ -1,4 +1,4 @@
-1.  Connect to the replica node over SSH as the `admin` user on port 122:
+1. Connect to the replica node over SSH as the `admin` user on port 122:
 
 ```shell
 ssh -p 122 admin@REPLICA_HOST

data/reusables/supported-languages/swift.md

@@ -1,2 +1 @@
 | Swift | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |  {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Unsupported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %}<br>Swift Package Manager  |
-