fix commonmark issues (github#42054)

rachmari · web-flow · commit 2df2cdbb96d8 · 2023-09-06T16:29:28.000Z
diff --git a/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md b/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
@@ -39,11 +39,11 @@ product: '{% data reusables.gated-features.merge-queue %}'
 
    ![Screenshot of the merge queue options for a pull request.](/assets/images/help/pull_requests/merge-queue-options.png)
 
-  {% note %}
+   {% note %}
 
-  **Note:** You can click  **Merge when ready** whenever you're ready to merge your proposed changes. {% data variables.product.product_name %} will automatically add the pull request to the merge queue once required approval and status checks conditions are met.
+   **Note:** You can click  **Merge when ready** whenever you're ready to merge your proposed changes. {% data variables.product.product_name %} will automatically add the pull request to the merge queue once required approval and status checks conditions are met.
 
-  {% endnote %}
+   {% endnote %}
 
 1. Confirm you want to add the pull request to the merge queue by clicking  **Confirm merge when ready**.
 
diff --git a/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
@@ -49,7 +49,7 @@ If you decide you don't want the changes in a topic branch to be merged to the u
 
     - [Merge all of the commits into the base branch](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) by clicking **Merge pull request**. If the **Merge pull request** option is not shown, click the merge dropdown menu and select **Create a merge commit**.
 
-     ![Screenshot of the merge options for a pull request. The arrow to expand the dropdown is outlined in dark orange.](/assets/images/help/pull_requests/merge-pull-request-options.png)
+      ![Screenshot of the merge options for a pull request. The arrow to expand the dropdown is outlined in dark orange.](/assets/images/help/pull_requests/merge-pull-request-options.png)
 
     - [Squash the commits into one commit](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#squash-and-merge-your-pull-request-commits) by clicking the merge dropdown menu, selecting **Squash and merge** and then clicking **Squash and merge**.
 
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md
@@ -33,11 +33,11 @@ The summary list of methods and functions is created from these supported file t
 
 1. Select the changed function or method from the drop-down menu. You can also enter the name of the function or method to filter results.
 
- {% note %}
+   {% note %}
 
- **Note:** If you don't see the functions or methods you expected, confirm that your code compiles and doesn't contain errors. Only functions and methods changed in this pull request and found in _.go_, _.js_, _.ts_, _.py_, _.php_, and _.rb_ files appear in the drop-down menu.
+   **Note:** If you don't see the functions or methods you expected, confirm that your code compiles and doesn't contain errors. Only functions and methods changed in this pull request and found in _.go_, _.js_, _.ts_, _.py_, _.php_, and _.rb_ files appear in the drop-down menu.
 
- {% endnote %}
+   {% endnote %}
 
 1. You'll be redirected to the first line of the function or method you selected.
 
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -53,15 +53,15 @@ You can configure the {% data variables.dependency-review.action_name %} to bett
    ![Screenshot of the "Changed files" tab. A dropdown labeled "File filter" is expanded, displaying a list of file types with checkboxes.](/assets/images/help/pull_requests/file-filter-menu-json.png)
    The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default.
 
-  {% note %}
+   {% note %}
 
    **Note:** Dependency review rich diffs are not available for committed static JavaScript files like `jquery.js`.
 
    {% endnote %}
 
 1. On the right of the header for a manifest or lock file, display the dependency review by clicking **{% octicon "file" aria-label="Display the rich diff" %}**.
 
-    ![Screenshot of the "Files changed" tab of a pull request. The button to display the rich diff, labeled with a file icon, is outlined in dark orange.](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
+   ![Screenshot of the "Files changed" tab of a pull request. The button to display the rich diff, labeled with a file icon, is outlined in dark orange.](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
 
 1. Check the dependencies listed in the dependency review.
 
diff --git a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
@@ -37,11 +37,11 @@ Organizations can use the `name@organization.com` email as a public point of con
    >
    ```
 
-  {% tip %}
+   {% tip %}
 
-  **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer.
+   **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer.
 
-  {% endtip %}
+   {% endtip %}
 
 1. On the next line of the commit message, type `on-behalf-of: @org <name@organization.com>`, then a closing quotation mark.
 
diff --git a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
@@ -42,23 +42,23 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
 
 1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines.
 
-   ```
+   ```shell
    $ git commit -m "Refactor usability tests.
    >
    >
    ```
 
-  {% tip %}
+   {% tip %}
 
-  **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer.
+   **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer.
 
-  {% endtip %}
+   {% endtip %}
 
 1. On the next line of the commit message, type `Co-authored-by: name <name@example.com>` with specific information for each co-author. After the co-author information, add a closing quotation mark.
 
    If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. Do not add blank lines between each co-author line.
 
-   ```
+   ```shell
    $ git commit -m "Refactor usability tests.
    >
    >
diff --git a/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
@@ -16,10 +16,10 @@ shortTitle: Install Git LFS
 {% mac %}
 
 1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**. Alternatively, you can install {% data variables.large_files.product_name_short %} using a package manager:
-    - To use [Homebrew](https://brew.sh/), run `brew install git-lfs`.
-    - To use [MacPorts](https://www.macports.org/), run `port install git-lfs`.
+   - To use [Homebrew](https://brew.sh/), run `brew install git-lfs`.
+   - To use [MacPorts](https://www.macports.org/), run `port install git-lfs`.
 
- If you install {% data variables.large_files.product_name_short %} with Homebrew or MacPorts, skip to step six.
+   If you install {% data variables.large_files.product_name_short %} with Homebrew or MacPorts, skip to step six.
 
 1. On your computer, locate and unzip the downloaded file.
 {% data reusables.command_line.open_the_multi_os_terminal %}
@@ -61,11 +61,11 @@ shortTitle: Install Git LFS
 
 1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
 
-  {% tip %}
+   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Windows, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+   **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Windows, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
 
-  {% endtip %}
+   {% endtip %}
 1. On your computer, locate the downloaded file.
 1. Double click on the file called _git-lfs-windows-1.X.X.exe_, where 1.X.X is replaced with the Git LFS version you downloaded. When you open this file Windows will run a setup wizard to install {% data variables.large_files.product_name_short %}.
 {% data reusables.command_line.open_the_multi_os_terminal %}
@@ -84,11 +84,11 @@ shortTitle: Install Git LFS
 
 1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
 
-  {% tip %}
+   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Linux, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+   **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Linux, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
 
-  {% endtip %}
+   {% endtip %}
 1. On your computer, locate and unzip the downloaded file.
 {% data reusables.command_line.open_the_multi_os_terminal %}
 1. Change the current working directory into the folder you downloaded and unzipped.
diff --git a/content/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -17,11 +17,11 @@ shortTitle: Remove files
 1. Remove the file from the repository's Git history using either the `filter-repo` command or BFG Repo-Cleaner. For detailed information on using these, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)."
 1. Navigate to your _.gitattributes_ file.
 
-  {% note %}
+   {% note %}
 
-  **Note:** Your _.gitattributes_ file is generally saved within your local repository. In some cases, you may have created a global _.gitattributes_ file that contains all of your {% data variables.large_files.product_name_short %} associations.
+   **Note:** Your _.gitattributes_ file is generally saved within your local repository. In some cases, you may have created a global _.gitattributes_ file that contains all of your {% data variables.large_files.product_name_short %} associations.
 
-  {% endnote %}
+   {% endnote %}
 1. Find and remove the associated {% data variables.large_files.product_name_short %} tracking rule within the _.gitattributes_ file.
 1. Save and exit the _.gitattributes_ file.
 
diff --git a/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -62,7 +62,7 @@ Symbol search is a feature of code search. For more information, see "[AUTOTITLE
 1. Select a repository, then navigate to a file containing symbols.
 1. To bring up the symbols pane, above the file content, click {% octicon "code-square" aria-label="The code square icon" %}.
 
-  Alternatively, you can open the symbols pane by clicking an eligible symbol in your file. Clickable symbols are highlighted in yellow when you hover over them.
+   Alternatively, you can open the symbols pane by clicking an eligible symbol in your file. Clickable symbols are highlighted in yellow when you hover over them.
 
 1. Click the symbol you would like to find from the symbols pane or within the file itself.
 
diff --git a/content/rest/quickstart.md b/content/rest/quickstart.md
@@ -82,8 +82,7 @@ If you are authenticating with a {% data variables.product.prodname_github_app %
 1. Add a step to generate a token, and use that token instead of `GITHUB_TOKEN`. Note that this token will expire after 60 minutes. For example:
 
    ```yaml
-
-  {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=1 %}
+   {% data reusables.actions.actions-not-certified-by-github-comment %}
 
    on:
      workflow_dispatch:
@@ -97,13 +96,11 @@ If you are authenticating with a {% data variables.product.prodname_github_app %
            with:
              app_id: {% raw %}${{ secrets.APP_ID }}{% endraw %}
              private_key: {% raw %}${{ secrets.APP_PEM }}{% endraw %}
-
          - name: Use API
            env:
              GH_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
            run: |
              gh api repos/octocat/Spoon-Knife/issues
-
    ```
 
 {% endcli %}
@@ -230,7 +227,7 @@ If you are authenticating with a {% data variables.product.prodname_github_app %
 
    ```yaml
 
-  {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=1 %}
+   {% data reusables.actions.actions-not-certified-by-github-comment %}
 
    on:
      workflow_dispatch:
@@ -359,7 +356,7 @@ If you are authenticating with a {% data variables.product.prodname_github_app %
 
    ```yaml
 
-  {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=1 %}
+   {% data reusables.actions.actions-not-certified-by-github-comment %}
 
    on:
      workflow_dispatch:
diff --git a/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -26,7 +26,7 @@ topics:
 - To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "Search all of {% data variables.product.prodname_dotcom %}" in the search dropdown menu.
 - To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**.
 
-{% ifversion code-search-code-view %} You can also use suggestions and completions in the search bar to quickly find what you need.
+  {% 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.
diff --git a/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -250,7 +250,7 @@ You can filter issues and pull requests by the number of interactions with the `
 
 | Qualifier        | Example
 | ------------- | -------------
-| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions.
+| <code>interactions:<em>n</em></code> | [**interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions.
 | <code>interactions:<em>n..n</em></code> | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000.
 
 ## Search by number of reactions
@@ -259,7 +259,7 @@ You can filter issues and pull requests by the number of reactions using the `re
 
 | Qualifier        | Example
 | ------------- | -------------
-| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions.
+| <code>reactions:<em>n</em></code> | [**reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions.
 | <code>reactions:<em>n..n</em></code> | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000.
 
 ## Search for draft pull requests
diff --git a/content/site-policy/content-removal-policies/dmca-takedown-policy.md b/content/site-policy/content-removal-policies/dmca-takedown-policy.md
@@ -47,7 +47,7 @@ The DMCA framework is a bit like passing notes in class. The copyright owner han
 Here are the basic steps in the process.
 
 1. **Copyright Owner Investigates.** A copyright owner should always conduct an initial investigation to confirm both (a) that they own the copyright to an original work and (b) that the content on GitHub is unauthorized and infringing. This includes confirming that the use is not protected as [fair use](https://www.lumendatabase.org/topics/22). A particular use may be fair if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-> **Example:** An employee of Acme Web Company finds some of the company's code in a GitHub repository. Acme Web Company licenses its source code out to several trusted partners. Before sending in a take-down notice, Acme should review those licenses and its agreements to confirm that the code on GitHub is not authorized under any of them.
+   > **Example:** An employee of Acme Web Company finds some of the company's code in a GitHub repository. Acme Web Company licenses its source code out to several trusted partners. Before sending in a take-down notice, Acme should review those licenses and its agreements to confirm that the code on GitHub is not authorized under any of them.
 
 1. **Copyright Owner Sends A Notice.** After conducting an investigation, a copyright owner prepares and sends a [takedown notice](/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice) to GitHub. Assuming the takedown notice is sufficiently detailed according to the statutory requirements (as explained in the [how-to guide](/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice)), we will [post the notice](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the link along to the affected user.
 
diff --git a/content/site-policy/content-removal-policies/github-private-information-removal-policy.md b/content/site-policy/content-removal-policies/github-private-information-removal-policy.md
@@ -56,7 +56,7 @@ For the purposes of this document, “private information” refers to content t
 
 1. **User Notifies GitHub of Changes.** If the user chooses to make the specified changes, they must tell us so within the window of time they've been allowed. If they don't, we will disable the repository. If the user notifies us that they made changes, we will verify that the changes have been made and notify the complainant.
 
-  OR
+   OR
 
 1. **User May Dispute the Request.** If a user believes the content in question is not private information subject to this Policy, they may dispute it. If they do, we will generally leave it up to the complainant to contact the user and work things out with them directly, within reason.
 
diff --git a/content/site-policy/github-terms/github-registered-developer-agreement.md b/content/site-policy/github-terms/github-registered-developer-agreement.md
diff --git a/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md b/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md
diff --git a/data/reusables/repositories/rulesets-bypass-step.md b/data/reusables/repositories/rulesets-bypass-step.md

Original file line number	Diff line number	Diff line change
`@@ -42,23 +42,23 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit`
`42`	`42`
`43`	`43`	`1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines.`
`44`	`44`
`45`		- ```
	`45`	+ ```shell
`46`	`46`	`$ git commit -m "Refactor usability tests.`
`47`	`47`	`>`
`48`	`48`	`>`
`49`	`49`	```
`50`	`50`
`51`		`- {% tip %}`
	`51`	`+ {% tip %}`
`52`	`52`
`53`		- Tip: If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer.
	`53`	+ Tip: If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer.
`54`	`54`
`55`		`- {% endtip %}`
	`55`	`+ {% endtip %}`
`56`	`56`
`57`	`57`	1. On the next line of the commit message, type `Co-authored-by: name <name@example.com>` with specific information for each co-author. After the co-author information, add a closing quotation mark.
`58`	`58`
`59`	`59`	If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. Do not add blank lines between each co-author line.
`60`	`60`
`61`		- ```
	`61`	+ ```shell
`62`	`62`	`$ git commit -m "Refactor usability tests.`
`63`	`63`	`>`
`64`	`64`	`>`