Fix Markdown that is not Commonmark compliant (#41582)

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: rachmari

content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md

@@ -20,36 +20,28 @@ topics:
 
 {% data reusables.advanced-security.ghas-helps-developers %}
 
-{% ifversion ghes %}
 When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."
-{% else %}
-When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features.
-{% endif %}
 
 {% ifversion secret-scanning-enterprise-level-api %}{% data reusables.secret-scanning.secret-scanning-enterprise-level-api %}{% endif %}
 
-{% ifversion ghes %}
 For guidance on a phased deployment of GitHub Advanced Security, see "[AUTOTITLE](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)."
-{% endif %}
 
 ## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
 
-{% ifversion ghes %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
 1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage.
-{% endif %}
 
 ## Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
 
-1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes %} For information about licensing, see "[AUTOTITLE](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
+1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. For information about licensing, see "[AUTOTITLE](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."
 1. Download the new license file. For more information, see "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)."
-1. Upload the new license file to {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes %}
+1. Upload the new license file to {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."
 1. Review the prerequisites for the features you plan to enable.
 
     - {% data variables.product.prodname_code_scanning_caps %}, see "[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
-    - {% data variables.product.prodname_secret_scanning_caps %}, see "[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+    - {% data variables.product.prodname_secret_scanning_caps %}, see "[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."
     - {% data variables.product.prodname_dependabot %}, see "[AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 
 ## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
@@ -59,11 +51,7 @@ For guidance on a phased deployment of GitHub Advanced Security, see "[AUTOTITLE
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.advanced-security-tab %}
-{%- ifversion ghes %}
 1. Under "Security," select the features that you want to enable and deselect any features you want to disable.
-{%- else %}
-1. Under "{% data variables.product.prodname_advanced_security %}," select **{% data variables.product.prodname_code_scanning_caps %}**.
-{%- endif %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. For more information, see "[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance)."
@@ -90,15 +78,11 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s
     ghe-config app.secret-scanning.enabled true
     ```
 
-    - To enable the dependency graph, enter the following {% ifversion ghes %}command{% else %}commands{% endif %}.
-    {% ifversion ghes %}```shell
-    ghe-config app.dependency-graph.enabled true
+    - To enable the dependency graph, enter the following command.
 
+    ```shell
+    ghe-config app.dependency-graph.enabled true
     ```
-    {% else %}```shell
-    ghe-config app.github.dependency-graph-enabled true
-    ghe-config app.github.vulnerability-alerting-and-settings-enabled true
-    ```{% endif %}
 
 1. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}.
 
@@ -115,15 +99,11 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s
     ghe-config app.secret-scanning.enabled false
     ```
 
-    - To disable the dependency graph, enter the following {% ifversion ghes %}command{% else %}commands{% endif %}.
-    {% ifversion ghes %}```shell
-    ghe-config app.dependency-graph.enabled false
+    - To disable the dependency graph, enter the following command.
 
+    ```shell
+    ghe-config app.dependency-graph.enabled false
     ```
-    {% else %}```shell
-    ghe-config app.github.dependency-graph-enabled false
-    ghe-config app.github.vulnerability-alerting-and-settings-enabled false
-    ```{% endif %}
 
 1. Apply the configuration.
 

content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md

@@ -96,10 +96,9 @@ If you're setting up your AMI for the first time, you will need to create a secu
    aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID --protocol PROTOCOL --port PORT_NUMBER --cidr SOURCE IP RANGE
    ```
 
-  This table identifies what each port is used for.
-
-  {% data reusables.enterprise_installation.necessary_ports %}
+   This table identifies what each port is used for.
 
+   {% data reusables.enterprise_installation.necessary_ports %}
 ## Creating the {% data variables.product.prodname_ghe_server %} instance
 
 To create the instance, you'll need to launch an EC2 instance with your {% data variables.product.prodname_ghe_server %} AMI and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."

content/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md

@@ -55,7 +55,7 @@ If an organization enforces SAML SSO, you cannot use the enterprise settings to
    - If the organization uses SCIM, accept the organization invitation that will be generated by the SCIM integration.
    - If the organization does not use SCIM, visit the following URL, replacing ORGANIZATION with the name of the organization, then follow the prompts to authenticate.
 
-    `https://github.com/orgs/ORGANIZATION/sso`
+     `https://github.com/orgs/ORGANIZATION/sso`
 
 After you've joined the organization, you can use the enterprise settings to manage your role in the organization, such as becoming an organization owner. For more information, see "[Managing your role with the enterprise settings](#managing-your-role-with-the-enterprise-settings)."
 

content/code-security/code-scanning/managing-code-scanning-alerts/tracking-code-scanning-alerts-in-issues-using-task-lists.md

@@ -85,4 +85,4 @@ Instead of tracking a {% data variables.product.prodname_code_scanning %} alert
 1. Begin creating an issue through the API. For more information, see "[Create an issue](/rest/issues/issues#create-an-issue)."
 1. Provide the code scanning link within the body of the issue. You must use the following task list syntax to create the tracked relationship: `- [ ] <full-URL-to-the-code-scanning-alert>`.
 
-  For example, if you add `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` to an issue, the issue will track the code scanning alert that has an ID number of 17 in the **Security** tab of the `octocat-repo` repository in the `octocat-org` organization.
+   For example, if you add `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` to an issue, the issue will track the code scanning alert that has an ID number of 17 in the **Security** tab of the `octocat-repo` repository in the `octocat-org` organization.

content/code-security/secret-scanning/secret-scanning-patterns.md

@@ -91,7 +91,7 @@ This table lists the secrets supported by {% data variables.product.prodname_sec
 {% ifversion fpt %}
 
 | Provider | Token | Partner | User | Push protection | Validity check |
-|----|:----|:----:|:----:|:----:|
+|----|:----|:----:|:----:|:----:|:----:|
 {%- for entry in secretScanningData %}
 | {{ entry.provider }} | {{ entry.secretType }} | {% if entry.isPublic %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Unsupported" %}{% endif %} | {% if entry.isPrivateWithGhas %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Unsupported" %}{% endif %} | {% if entry.hasPushProtection %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Unsupported" %}{% endif %} | {% if entry.hasValidityCheck %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Unsupported" %}{% endif %} |
 {%- endfor %}

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md

@@ -40,7 +40,7 @@ body:
 You can set the following top-level keys for each issue form.
 
 | Key | Description | Required | Type |
-| :-- | :-- | :-- | :-- | :-- |
+| :-- | :-- | :-- | :-- |
 | `name` | A name for the issue form template. Must be unique from all other templates, including Markdown templates. | Required | String |
 | `description` | A description for the issue form template, which appears in the template chooser interface. | Required | String |
 | `body` | Definition of the input types in the form. | Required | Array |

content/discussions/managing-discussions-for-your-community/syntax-for-discussion-category-forms.md

@@ -39,7 +39,7 @@ body:
 You can set the following top-level keys for each issue form.
 
 | Key | Description | Required | Type |
-| :-- | :-- | :-- | :-- | :-- |
+| :-- | :-- | :-- | :-- |
 | `body` | Definition of the input types in the discussion form. | Required | Array |
 | `labels` | Labels that will automatically be added to discussions created with this template. | Optional | Array or comma-delimited string |
 | `title` | A default title that will be pre-populated in the discussion submission form. | Optional | String |

content/get-started/using-github/github-command-palette.md

@@ -138,7 +138,7 @@ These keystrokes are available when the command palette is in navigation and sea
 These commands are available from all scopes.
 
 | Command | Behavior|
-| :- | :- | :- |
+| :- | :- |
 |`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-github-importer/importing-a-repository-with-github-importer)."  |
 |`New gist`|Open a new gist. For more information, see "[AUTOTITLE](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." |
 |`New organization`|Create a new organization. For more information, see "[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." |

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

@@ -22,7 +22,7 @@ When you enable the auto-add workflow, existing items matching your criteria wil
 The auto-add workflow supports a subset of filters. You can use the following filters when configuring your workflow.
 
 | Qualifier | Possible values
-| --- | --- | --- |
+| --- | --- |
 | `is` | open, closed, merged, draft, issue, pr
 | `label` | "label name"
 | `reason` | completed, reopened, "not planned"

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

@@ -22,7 +22,7 @@ You can configure your project's built-in workflows to automatically archive ite
 The auto-archive workflow supports a subset of filters. You can use the following filters when configuring your workflow.
 
 | Qualifier | Possible values
-| --- | --- | --- |
+| --- | --- |
 | `is` | `open`, `closed`, `merged`, `draft`, `issue`, `pr`
 | `reason` | `completed`, `reopened`, `"not planned"`
 | `updated` | <code><@today-<em>14</em>d</code> (the last 14 days), <code><@today-<em>3</em>w</code> (the last 3 weeks), <code><@today-<em>1</em>m</code> (the last month)

data/reusables/enterprise_installation/download-package.md

@@ -1,5 +1,5 @@
 1. Download the upgrade package to {% data variables.location.product_location %} using `curl`:
 
-```shell
-admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL
-```
+   ```shell
+   admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL
+   ```

data/reusables/enterprise_installation/replica-ssh.md

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