From b1a68cb155e4e66753d0d1728a44a7cd2f1297d3 Mon Sep 17 00:00:00 2001
From: Artur Kordowski <9746197+akordowski@users.noreply.github.com>
Date: Fri, 8 Nov 2024 18:20:31 +0100
Subject: [PATCH] Fix inconsistent alerts by using the markdown notation - part
 2 (#35221)

Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com>
---
 .../upgrading-git-large-file-storage.md       |   7 +-
 ...ewing-your-git-large-file-storage-usage.md |  10 +-
 ...-your-spending-limit-for-github-actions.md |   6 +-
 .../viewing-your-github-actions-usage.md      |  17 +--
 ...ut-billing-for-github-advanced-security.md |   7 +-
 ...he-spending-limit-for-github-codespaces.md |   7 +-
 .../viewing-your-github-codespaces-usage.md   |  10 +-
 .../about-billing-for-github-marketplace.md   |   7 +-
 ...your-spending-limit-for-github-packages.md |   7 +-
 .../viewing-your-github-packages-usage.md     |   7 +-
 ...io-subscriptions-with-github-enterprise.md |  13 +-
 .../about-billing-for-plans.md                |   7 +-
 .../about-per-user-pricing.md                 |  24 ++--
 .../connecting-an-azure-subscription.md       |   7 +-
 .../discounted-plans-for-github-accounts.md   |   6 +-
 .../downgrading-your-accounts-plan.md         |  14 +-
 ...ne-time-payments-for-customers-in-india.md |   7 +-
 ...ing-license-usage-for-github-enterprise.md |  14 +-
 ...new-license-to-github-enterprise-server.md |   5 +-
 ...renewing-your-clients-paid-organization.md |   7 +-
 ...ngrading-your-clients-paid-organization.md |  10 +-
 .../adding-information-to-your-receipts.md    |  14 +-
 .../adding-or-editing-a-payment-method.md     |   7 +-
 ...ging-the-duration-of-your-billing-cycle.md |  14 +-
 ...ewing-your-payment-history-and-receipts.md |   7 +-
 ...ing-your-subscriptions-and-billing-date.md |   7 +-
 .../phase-2-preparing-to-enable-at-scale.md   |  18 +--
 ...phase-5-rollout-and-scale-code-scanning.md |   7 +-
 ...ase-6-rollout-and-scale-secret-scanning.md |  27 ++--
 ...ql-code-scanning-for-compiled-languages.md |  14 +-
 ...guring-advanced-setup-for-code-scanning.md |  12 +-
 ...g-your-advanced-setup-for-code-scanning.md | 107 +++++---------
 ...ing-codeql-code-scanning-in-a-container.md |   7 +-
 ...efault-setup-for-code-scanning-at-scale.md |  33 ++---
 ...iguring-default-setup-for-code-scanning.md |  42 ++----
 .../sarif-support-for-code-scanning.md        |   7 +-
 .../uploading-a-sarif-file-to-github.md       |   5 +-
 .../about-code-scanning-alerts.md             |   7 +-
 ...ode-scanning-alerts-for-your-repository.md |  17 +--
 .../resolving-code-scanning-alerts.md         |  19 +--
 ...nning-alerts-in-issues-using-task-lists.md |   5 +-
 ...g-code-scanning-alerts-in-pull-requests.md |  19 +--
 .../about-the-tool-status-page.md             |  21 +--
 ...guring-larger-runners-for-default-setup.md |  11 +-
 .../set-code-scanning-merge-protection.md     |  13 +-
 .../viewing-code-scanning-logs.md             |   7 +-
 ...analyzing-your-code-with-codeql-queries.md |  32 ++---
 .../customizing-analysis-with-codeql-packs.md |  34 ++---
 ...preparing-your-code-for-codeql-analysis.md |  39 ++---
 .../setting-up-the-codeql-cli.md              |  15 +-
 ...ading-codeql-analysis-results-to-github.md |   7 +-
 .../advanced-setup-of-the-codeql-cli.md       |  13 +-
 .../creating-and-working-with-codeql-packs.md |  19 +--
 .../creating-codeql-query-suites.md           |  22 +--
 .../publishing-and-using-codeql-packs.md      |  14 +-
 ...-options-in-a-codeql-configuration-file.md |  12 +-
 .../testing-custom-queries.md                 |  17 +--
 ...sing-custom-queries-with-the-codeql-cli.md |   7 +-
 .../managing-codeql-databases.md              |   7 +-
 ...-with-multi-repository-variant-analysis.md |  14 +-
 .../running-codeql-queries.md                 |  15 +-
 .../accessing-logs.md                         |   7 +-
 .../configuring-access-to-the-codeql-cli.md   |  12 +-
 .../creating-a-custom-query.md                |   7 +-
 ...oring-the-structure-of-your-source-code.md |   7 +-
 .../setting-up-a-codeql-workspace.md          |  14 +-
 ...emetry-in-codeql-for-visual-studio-code.md |   7 +-
 .../using-the-codeql-model-editor.md          |  14 +-
 .../about-dependabot-alerts.md                |  27 ++--
 .../configuring-dependabot-alerts.md          |   5 +-
 ...ing-notifications-for-dependabot-alerts.md |   7 +-
 .../viewing-and-updating-dependabot-alerts.md |  13 +-
 ...e-rules-to-prioritize-dependabot-alerts.md |  21 +--
 ...managing-automatically-dismissed-alerts.md |   7 +-
 ...t-rules-to-prioritize-dependabot-alerts.md |   7 +-
 .../about-dependabot-security-updates.md      |   7 +-
 ...configuring-dependabot-security-updates.md |  14 +-
 ...ion-options-for-the-dependabot.yml-file.md | 134 ++++++------------
 .../customizing-dependency-updates.md         |  19 ++-
 ...tomating-dependabot-with-github-actions.md |   7 +-
 ...your-actions-up-to-date-with-dependabot.md |   5 +-
 ...ng-pull-requests-for-dependency-updates.md |  27 ++--
 ...-dependabot-access-to-public-registries.md |  84 ++++-------
 .../troubleshooting-dependabot-errors.md      |   7 +-
 ...ng-a-security-policy-to-your-repository.md |   7 +-
 ...venting-data-leaks-in-your-organization.md |   7 +-
 .../dependabot-quickstart-guide.md            |   7 +-
 .../secret-scanning-partner-program.md        |  21 +--
 ...ing-custom-patterns-for-secret-scanning.md |  19 +--
 ...-folders-and-files-from-secret-scanning.md |  10 +-
 ...eleting-a-custom-security-configuration.md |   7 +-
 ...editing-a-custom-security-configuration.md |   7 +-
 .../interpreting-security-findings.md         |   7 +-
 ...-github-advanced-security-license-usage.md |  10 +-
 ...reating-a-custom-security-configuration.md |  14 +-
 ...-using-advanced-setup-for-code-scanning.md |  13 +-
 ...-disclosure-of-security-vulnerabilities.md |  15 +-
 ...-writing-repository-security-advisories.md |  18 +--
 ...tely-reporting-a-security-vulnerability.md |  14 +-
 .../about-global-security-advisories.md       |   7 +-
 ...isories-in-the-github-advisory-database.md |  12 +-
 ...lve-a-repository-security-vulnerability.md |   9 +-
 ...creating-a-repository-security-advisory.md |   7 +-
 ...blishing-a-repository-security-advisory.md |  33 ++---
 .../exporting-data-from-security-overview.md  |  14 +-
 .../filtering-alerts-in-security-overview.md  |   7 +-
 .../securing-accounts.md                      |  10 +-
 .../end-to-end-supply-chain/securing-code.md  |  14 +-
 .../configuring-dependency-review.md          |   6 +-
 ...loring-the-dependencies-of-a-repository.md |   5 +-
 ...ing-the-machine-type-for-your-codespace.md |   7 +-
 .../changing-the-shell-in-a-codespace.md      |  14 +-
 .../connecting-to-a-private-network.md        |   7 +-
 .../creating-a-codespace-for-a-repository.md  |  29 ++--
 .../creating-a-codespace-from-a-template.md   |  19 +--
 ...nvironment-variables-for-your-codespace.md |   7 +-
 .../deleting-a-codespace.md                   |  14 +-
 .../forwarding-ports-in-your-codespace.md     |   7 +-
 ...-github-codespaces-for-machine-learning.md |   7 +-
 .../opening-an-existing-codespace.md          |  28 ++--
 ...github-codespaces-in-visual-studio-code.md |   7 +-
 ...github-codespaces-in-your-jetbrains-ide.md |  14 +-
 ...using-github-codespaces-with-github-cli.md |  25 ++--
 .../using-source-control-in-your-codespace.md |  25 +---
 .../working-collaboratively-in-a-codespace.md |   7 +-
 .../codespaces/getting-started/deep-dive.md   |  25 ++--
 ...ays-for-codespaces-in-your-organization.md |  12 +-
 ...github-codespaces-for-your-organization.md |  12 +-
 ...ing-the-codespaces-in-your-organization.md |   7 +-
 ...-github-codespaces-in-your-organization.md |  14 +-
 .../restricting-access-to-machine-types.md    |   7 +-
 ...stricting-the-base-image-for-codespaces.md |  12 +-
 .../restricting-the-idle-timeout-period.md    |   7 +-
 ...ion-billed-codespaces-a-user-can-create.md |   7 +-
 ...ing-the-retention-period-for-codespaces.md |  19 +--
 ...cting-the-visibility-of-forwarded-ports.md |   7 +-
 ...-gpg-verification-for-github-codespaces.md |   7 +-
 ...g-repository-access-for-your-codespaces.md |  17 +--
 .../about-github-codespaces-prebuilds.md      |   7 +-
 ...a-prebuild-to-access-other-repositories.md |  17 +--
 .../configuring-prebuilds.md                  |  38 ++---
 .../managing-prebuilds.md                     |   7 +-
 .../testing-dev-container-changes.md          |   7 +-
 ...disaster-recovery-for-github-codespaces.md |  14 +-
 .../security-in-github-codespaces.md          |  11 +-
 .../introduction-to-dev-containers.md         |  38 ++---
 ...iles-in-the-codespaces-for-a-repository.md |   7 +-
 ...um-specification-for-codespace-machines.md |   7 +-
 ...ng-recommended-secrets-for-a-repository.md |   7 +-
 ...k-creation-and-resumption-of-codespaces.md |  18 +--
 ...mplate-repository-for-github-codespaces.md |   7 +-
 .../choosing-the-stable-or-beta-host-image.md |  11 +-
 ...g-automatic-deletion-of-your-codespaces.md |  28 ++--
 ...zing-github-codespaces-for-your-account.md |  28 ++--
 ...ur-timeout-period-for-github-codespaces.md |   7 +-
 .../exporting-changes-to-a-branch.md          |   7 +-
 ...shooting-authentication-to-a-repository.md |   7 +-
 ...ing-creation-and-deletion-of-codespaces.md |  31 ++--
 ...-gpg-verification-for-github-codespaces.md |   7 +-
 .../troubleshooting-included-usage.md         |  29 ++--
 .../about-wikis.md                            |  16 +--
 .../blocking-a-user-from-your-organization.md |   7 +-
 ...cking-a-user-from-your-personal-account.md |   7 +-
 .../reporting-abuse-or-spam.md                |  11 +-
 ...nblocking-a-user-from-your-organization.md |   7 +-
 ...cking-a-user-from-your-personal-account.md |   7 +-
 .../managing-disruptive-comments.md           |   7 +-
 ...dding-support-resources-to-your-project.md |   7 +-
 ...-guidelines-for-repository-contributors.md |   7 +-
 ...ing-issue-templates-for-your-repository.md |   7 +-
 ...ngle-issue-template-for-your-repository.md |   7 +-
 .../syntax-for-githubs-form-schema.md         |  18 +--
 .../syntax-for-issue-forms.md                 |   7 +-
 .../about-contributing-to-github-docs.md      |   7 +-
 .../using-git-on-github-docs.md               |  34 ++---
 ...g-the-todocs-placeholder-to-leave-notes.md |   7 +-
 .../creating-a-local-environment.md           |  17 +--
 .../creating-screenshots.md                   |  13 +-
 ...sing-markdown-and-liquid-in-github-docs.md |  21 +--
 .../using-yaml-frontmatter.md                 |  21 +--
 .../versioning-documentation.md               |  20 +--
 ...m-your-local-computer-to-github-desktop.md |   6 +-
 ...epository-from-github-to-github-desktop.md |  13 +-
 ...ring-a-default-editor-in-github-desktop.md |  10 +-
 .../configuring-git-for-github-desktop.md     |   7 +-
 .../installing-github-desktop.md              |   7 +-
 ...anges-to-your-project-in-github-desktop.md |  14 +-
 .../managing-branches-in-github-desktop.md    |  13 +-
 ...g-changes-to-github-from-github-desktop.md |  17 +--
 ...checking-out-a-commit-in-github-desktop.md |   7 +-
 .../managing-tags-in-github-desktop.md        |  13 +-
 ...-for-managing-commits-in-github-desktop.md |   7 +-
 .../reverting-a-commit-in-github-desktop.md   |   7 +-
 ...sue-or-pull-request-from-github-desktop.md |   7 +-
 .../syncing-your-branch-in-github-desktop.md  |  12 +-
 .../moderating-discussions.md                 |   5 +-
 .../viewing-insights-for-your-discussions.md  |   7 +-
 .../about-github-education-for-students.md    |   7 +-
 .../apply-to-github-education-as-a-student.md |   7 +-
 ...-github-education-for-students-approved.md |  13 +-
 ...-github-education-for-teachers-approved.md |   6 +-
 .../applying-to-be-a-github-campus-expert.md  |  22 ++-
 ...isual-studio-code-with-github-classroom.md |  14 +-
 ...github-codespaces-with-github-classroom.md |  14 +-
 .../about-assignments.md                      |   7 +-
 ...management-system-course-to-a-classroom.md |   7 +-
 .../create-a-group-assignment.md              |  12 +-
 .../editing-an-assignment.md                  |  56 +++-----
 ...nts-deadline-for-an-individual-or-group.md |  10 +-
 .../manage-classrooms.md                      |  12 +-
 ...management-system-with-github-classroom.md |  15 +-
 content/education/quickstart.md               |  21 +--
 .../accessibility/github-command-palette.md   |  10 +-
 .../managing-your-theme-settings.md           |   7 +-
 .../featured-github-integrations.md           |   5 +-
 .../contributing-to-a-project.md              |   7 +-
 .../saving-repositories-with-stars.md         |   7 +-
 .../about-remote-repositories.md              |  17 +--
 .../caching-your-github-credentials-in-git.md |  21 +--
 .../managing-remote-repositories.md           |  15 +-
 .../getting-started-with-git/set-up-git.md    |  24 ++--
 ...ing-credentials-from-the-macos-keychain.md |  13 +-
 .../about-github-advanced-security.md         |   7 +-
 .../github-language-support.md                |  13 +-
 .../learning-about-github/githubs-plans.md    |  14 +-
 .../about-github-certifications.md            |   7 +-
 ...tering-for-a-github-certifications-exam.md |   7 +-
 .../setting-up-your-profile.md                |   6 +-
 .../uploading-a-project-to-github.md          |   9 +-
 .../get-started/using-git/about-git-rebase.md |   7 +-
 .../using-git/about-git-subtree-merges.md     |   7 +-
 ...g-a-subfolder-out-into-a-new-repository.md |  21 +--
 .../about-versions-of-github-docs.md          |   7 +-
 ...hubs-services-from-a-restricted-network.md |   7 +-
 ...ly-access-releases-with-feature-preview.md |   2 +-
 .../get-started/using-github/github-flow.md   |  14 +-
 .../about-task-lists.md                       |   7 +-
 .../attaching-files.md                        |  41 ++----
 .../autolinked-references-and-urls.md         |  14 +-
 ...ting-a-permanent-link-to-a-code-snippet.md |   7 +-
 .../creating-and-highlighting-code-blocks.md  |   7 +-
 .../creating-diagrams.md                      |   7 +-
 .../using-saved-replies.md                    |  10 +-
 .../creating-github-cli-extensions.md         |  35 ++---
 content/github-cli/github-cli/quickstart.md   |   7 +-
 .../github-cli/using-github-cli-extensions.md |   7 +-
 .../guides/forming-calls-with-graphql.md      |  21 +--
 .../graphql/guides/introduction-to-graphql.md |  15 +-
 .../graphql/guides/using-global-node-ids.md   |   7 +-
 content/graphql/guides/using-the-explorer.md  |  19 +--
 content/graphql/overview/explorer.md          |   5 +-
 ...its-and-node-limits-for-the-graphql-api.md |   7 +-
 content/graphql/overview/schema-previews.md   |   9 +-
 content/graphql/reference/queries.md          |   7 +-
 ...nfiguring-automation-for-project-boards.md |   7 +-
 .../creating-a-project-board.md               |   5 +-
 .../deleting-a-project-board.md               |   7 +-
 .../editing-a-project-board.md                |   7 +-
 ...linking-a-repository-to-a-project-board.md |   7 +-
 ...es-and-pull-requests-to-a-project-board.md |  23 +--
 .../adding-notes-to-a-project-board.md        |  26 ++--
 .../filtering-cards-on-a-project-board.md     |   7 +-
 .../automating-projects-using-actions.md      |  27 ++--
 .../using-the-api-to-manage-projects.md       |  30 ++--
 .../migrating-from-projects-classic.md        |  26 ++--
 .../customizing-the-board-layout.md           |   7 +-
 .../customizing-the-table-layout.md           |   7 +-
 .../adding-items-to-your-project.md           |  21 +--
 .../archiving-items-from-your-project.md      |   7 +-
 .../adding-your-project-to-a-team.md          |   7 +-
 .../administering-issues/closing-an-issue.md  |   7 +-
 ...sferring-an-issue-to-another-repository.md |   7 +-
 .../using-issues/about-slash-commands.md      |   7 +-
 .../creating-a-branch-for-an-issue.md         |   7 +-
 .../using-issues/creating-an-issue.md         |   7 +-
 ...-and-searching-issues-and-pull-requests.md |  25 ++--
 .../linking-a-pull-request-to-an-issue.md     |   6 +-
 .../about-milestones.md                       |   7 +-
 ...g-issues-and-pull-requests-by-milestone.md |  12 +-
 ...m-foundation-version-control-repository.md |   7 +-
 .../overview/about-locked-repositories.md     |   7 +-
 .../using-ghe-migrator/about-ghe-migrator.md  |   7 +-
 ...rating-data-to-github-enterprise-server.md |   7 +-
 ...ion-logs-for-github-enterprise-importer.md |  14 +-
 ...nnequins-for-github-enterprise-importer.md |  16 +--
 ...gration-with-github-enterprise-importer.md |  20 +--
 ...bout-migrations-between-github-products.md |   7 +-
 ...for-a-migration-between-github-products.md |  20 +--
 ...prise-server-to-github-enterprise-cloud.md |  29 ++--
 ...-of-a-migration-between-github-products.md |  27 ++--
 ...azure-devops-to-github-enterprise-cloud.md |   7 +-
 ...ucket-server-to-github-enterprise-cloud.md |   7 +-
 292 files changed, 1230 insertions(+), 2749 deletions(-)

diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md b/content/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
index 92efbf4ea4..af3ae01ec4 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
@@ -49,11 +49,8 @@ shortTitle: Upgrade Git LFS storage
 
 {% data reusables.enterprise-accounts.billing-perms %}
 
-{% note %}
-
-**Note:** If your enterprise account is invoiced, you may not be able to purchase Git LFS data packs on {% data variables.product.prodname_dotcom %}. Instead, contact {% data variables.contact.contact_enterprise_sales %}.
-
-{% endnote %}
+> [!NOTE]
+> If your enterprise account is invoiced, you may not be able to purchase Git LFS data packs on {% data variables.product.prodname_dotcom %}. Instead, contact {% data variables.contact.contact_enterprise_sales %}.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md b/content/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
index 92ce0a5eef..3094dd30b5 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
@@ -36,11 +36,10 @@ shortTitle: View Git LFS usage
 ## Viewing storage and bandwidth usage for an organization
 
 {% ifversion billing-beta-enterprise %}
-{% note %}
 
-**Note:** If your organization belongs to an enterprise enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.large_files.product_name_short %}, you will not see {% data variables.large_files.product_name_short %} usage on the existing billing pages.
+> [!NOTE]
+> If your organization belongs to an enterprise enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.large_files.product_name_short %}, you will not see {% data variables.large_files.product_name_short %} usage on the existing billing pages.
 
-{% endnote %}
 {% endif %}
 
 {% data reusables.dotcom_billing.org-billing-perms %}
@@ -53,11 +52,10 @@ shortTitle: View Git LFS usage
 ## Viewing storage and bandwidth for an enterprise account
 
 {% ifversion billing-beta-enterprise %}
-{% note %}
 
-**Note:** If your enterprise is enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.large_files.product_name_short %}, you will not see {% data variables.large_files.product_name_short %} usage on the existing billing pages.
+> [!NOTE]
+> If your enterprise is enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.large_files.product_name_short %}, you will not see {% data variables.large_files.product_name_short %} usage on the existing billing pages.
 
-{% endnote %}
 {% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
index 6424d1f989..a450a8cfd4 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
@@ -56,11 +56,9 @@ Organizations owners and billing managers can manage the spending limit for {% d
 {% data reusables.dotcom_billing.manage-spending-limit %}
 1. Under "Monthly spending limit", choose to limit spending or allow unlimited spending.
 
-   {% note %}
+   > [!NOTE]
+   > If {% data variables.product.prodname_github_codespaces %} is enabled for your organization, scroll to "Actions & Packages", then choose to limit spending or allow unlimited spending.
 
-   **Note:** If {% data variables.product.prodname_github_codespaces %} is enabled for your organization, scroll to "Actions & Packages", then choose to limit spending or allow unlimited spending.
-
-   {% endnote %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
 {% ifversion ghec %}
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-actions/viewing-your-github-actions-usage.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
index a77e848566..c87b3fb399 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
@@ -38,11 +38,10 @@ Anyone can view {% data variables.product.prodname_actions %} usage for their ow
 ## Viewing {% data variables.product.prodname_actions %} usage for your organization
 
 {% ifversion billing-beta-enterprise %}
-{% note %}
 
-**Note:** If your organization belongs to an enterprise enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.product.prodname_actions %}, you will not see {% data variables.product.prodname_actions %} usage on the existing billing pages.
+> [!NOTE]
+> If your organization belongs to an enterprise enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.product.prodname_actions %}, you will not see {% data variables.product.prodname_actions %} usage on the existing billing pages.
 
-{% endnote %}
 {% endif %}
 
 Organization owners and billing managers can view {% data variables.product.prodname_actions %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_actions %} usage in the organization billing page.
@@ -57,20 +56,16 @@ Organization owners and billing managers can view {% data variables.product.prod
 ## Viewing {% data variables.product.prodname_actions %} usage for your enterprise account
 
 {% ifversion billing-beta-enterprise %}
-{% note %}
 
-**Note:** If your enterprise is enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.product.prodname_actions %}, you will not see {% data variables.product.prodname_actions %} usage on the existing billing pages.
+> [!NOTE]
+> If your enterprise is enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.product.prodname_actions %}, you will not see {% data variables.product.prodname_actions %} usage on the existing billing pages.
 
-{% endnote %}
 {% endif %}
 
 Enterprise owners and billing managers can view {% data variables.product.prodname_actions %} usage for an enterprise account.
 
-{% note %}
-
-**Note:** Billing details for enterprise accounts don't summarize the usage minutes for each operating system. {% data reusables.actions.enterprise-billing-details %}
-
-{% endnote %}
+> [!NOTE]
+> Billing details for enterprise accounts don't summarize the usage minutes for each operating system. {% data reusables.actions.enterprise-billing-details %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
index 239e0ba159..e3fa5a8ad7 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
@@ -63,11 +63,8 @@ If you have further questions about using {% data variables.product.prodname_GH_
 
 {% data reusables.advanced-security.ghas-license-info-for-fpt %}
 
-{% note %}
-
-**Note:** If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.
-
-{% endnote %}
+> [!NOTE]
+> If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.
 
 For pricing details for {% data variables.product.prodname_GH_advanced_security %}, see our [pricing information](https://github.com/enterprise/advanced-security#pricing).
 
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces.md
index 3187094fe7..b76632c17f 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces.md
@@ -51,11 +51,8 @@ You can set a spending limit for {% data variables.product.prodname_github_codes
 
 Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization.
 
-{% note %}
-
-**Note**: Organizations that are owned by an enterprise account cannot specify their own spending limit as this is specified in the enterprise settings.
-
-{% endnote %}
+> [!NOTE]
+> Organizations that are owned by an enterprise account cannot specify their own spending limit as this is specified in the enterprise settings.
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.manage-spending-limit %}
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
index 2b12016b84..cb9cee9110 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
@@ -51,13 +51,9 @@ Organization owners and billing managers can view {% data variables.product.prod
 {% data reusables.organizations.billing-settings %}
 1. Under "Usage this month", under "{% data variables.product.prodname_codespaces %}", view the details of the compute hours and storage used so far this month.
 
-   {% note %}
-
-   **Notes**:
-   * The costs shown here are the cumulative costs within the current billing month. The usage-based costs for {% data variables.product.prodname_github_codespaces %} shown on this page are reset to zero at the start of each billing month. Outstanding costs from previous months are not shown.
-   * The figures on this page are updated every hour.
-
-   {% endnote %}
+   > [!NOTE]
+   > * The costs shown here are the cumulative costs within the current billing month. The usage-based costs for {% data variables.product.prodname_github_codespaces %} shown on this page are reset to zero at the start of each billing month. Outstanding costs from previous months are not shown.
+   > * The figures on this page are updated every hour.
 
    You can also see and update your current spending limit. See "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)."
 
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
index 94fbc9f31f..c28e517758 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
@@ -43,11 +43,8 @@ When you choose a paid plan with a free trial:
 
 {% data reusables.user-settings.context_switcher %}
 
-{% note %}
-
-**Note:** When you transfer an organization with paid {% data variables.product.prodname_marketplace %} apps into an enterprise account, you may receive a second receipt but you will not be charged twice.
-
-{% endnote %}
+> [!NOTE]
+> When you transfer an organization with paid {% data variables.product.prodname_marketplace %} apps into an enterprise account, you may receive a second receipt but you will not be charged twice.
 
 ## Unit plan limits
 
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
index 791e4dd1af..d610d05a6a 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
@@ -57,11 +57,8 @@ Organizations owners and billing managers can manage the spending limit for {% d
 {% data reusables.dotcom_billing.manage-spending-limit %}
 1. Under "Monthly spending limit", choose to limit spending or allow unlimited spending.
 
-   {% note %}
-
-   **Note:** If {% data variables.product.prodname_github_codespaces %} is enabled for your organization, scroll to "Actions & Packages", then choose to limit spending or allow unlimited spending.
-
-   {% endnote %}
+   > [!NOTE]
+   > If {% data variables.product.prodname_github_codespaces %} is enabled for your organization, scroll to "Actions & Packages", then choose to limit spending or allow unlimited spending.
 
 {% data reusables.dotcom_billing.update-spending-limit %}
 
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-packages/viewing-your-github-packages-usage.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
index 7e48cabd92..714f063f6b 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
@@ -49,11 +49,8 @@ Organization owners and billing managers can view {% data variables.product.prod
 
 Enterprise owners and billing managers can view {% data variables.product.prodname_registry %} usage for an enterprise account.
 
-{% note %}
-
-**Note:** Billing details for enterprise accounts only summarize the storage data usage per organization. {% data reusables.actions.enterprise-billing-details %}
-
-{% endnote %}
+> [!NOTE]
+> Billing details for enterprise accounts only summarize the storage data usage per organization. {% data reusables.actions.enterprise-billing-details %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/content/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/content/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
index 2654a2b9d3..6b05bf5f4b 100644
--- a/content/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
+++ b/content/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
@@ -52,15 +52,10 @@ One person may be able to complete the tasks because the person has all of the r
 
 1. An organization owner must invite the subscriber to the organization on {% data variables.location.product_location %} from step 1. The subscriber can accept the invitation with an existing personal account or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see "[AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
 
-   {% tip %}
-
-   **Tips**:
-
-   * While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.location.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license.
-   * If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.location.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)."
-   * If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository.
-
-    {% endtip %}
+   > [!TIP]
+   > * While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.location.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license.
+   > * If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.location.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)."
+   > * If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository.
 
 After {% data variables.visual_studio.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
 
diff --git a/content/billing/managing-the-plan-for-your-github-account/about-billing-for-plans.md b/content/billing/managing-the-plan-for-your-github-account/about-billing-for-plans.md
index de890ef642..363009befe 100644
--- a/content/billing/managing-the-plan-for-your-github-account/about-billing-for-plans.md
+++ b/content/billing/managing-the-plan-for-your-github-account/about-billing-for-plans.md
@@ -39,8 +39,5 @@ You can purchase other subscriptions and usage-based billing with your existing
 
 {% data reusables.user-settings.context_switcher %}
 
-{% tip %}
-
-**Tip:** {% data variables.product.prodname_dotcom %} has programs for verified students and academic faculty, which include academic discounts. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/).
-
-{% endtip %}
+> [!TIP]
+> {% data variables.product.prodname_dotcom %} has programs for verified students and academic faculty, which include academic discounts. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/).
diff --git a/content/billing/managing-the-plan-for-your-github-account/about-per-user-pricing.md b/content/billing/managing-the-plan-for-your-github-account/about-per-user-pricing.md
index 89e23af760..65e3fdd588 100644
--- a/content/billing/managing-the-plan-for-your-github-account/about-per-user-pricing.md
+++ b/content/billing/managing-the-plan-for-your-github-account/about-per-user-pricing.md
@@ -62,14 +62,10 @@ If you currently pay for your {% data variables.product.prodname_enterprise %} l
 * Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
 * Dormant users
 
-{% note %}
-
-**Notes:**
-* {% data variables.product.company_short %} counts each outside collaborator once for billing purposes, even if the user account has access to multiple repositories owned by your organization.
-* {% data reusables.organizations.org-invite-scim %}
-* Inviting an outside collaborator to a repository using their email address temporarily uses an available seat, even if they already have access to other repositories. After they accept the invite, the seat will be freed up again. However, inviting them using their username does not temporarily use a seat.
-
-{% endnote %}
+> [!NOTE]
+> * {% data variables.product.company_short %} counts each outside collaborator once for billing purposes, even if the user account has access to multiple repositories owned by your organization.
+> * {% data reusables.organizations.org-invite-scim %}
+> * Inviting an outside collaborator to a repository using their email address temporarily uses an available seat, even if they already have access to other repositories. After they accept the invite, the seat will be freed up again. However, inviting them using their username does not temporarily use a seat.
 
 {% data variables.product.company_short %} does not bill for the following people:
 
@@ -95,14 +91,10 @@ If your enterprise does not use {% data variables.product.prodname_emus %}, you
 * Anyone with a pending invitation to become an organization owner or member
 * Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
 
-{% note %}
-
-**Notes:**
-* {% data variables.product.company_short %} counts each member or outside collaborator once for billing purposes, even if the user account has membership in multiple organizations in an enterprise or access to multiple repositories owned by your organization.
-* {% data reusables.organizations.org-invite-scim %}
-* Inviting an outside collaborator to a repository using their email address temporarily uses an available seat, even if they already have access to other repositories. After they accept the invite, the seat will be freed up again. However, inviting them using their username does not temporarily use a seat.
-
-{% endnote %}
+> [!NOTE]
+> * {% data variables.product.company_short %} counts each member or outside collaborator once for billing purposes, even if the user account has membership in multiple organizations in an enterprise or access to multiple repositories owned by your organization.
+> * {% data reusables.organizations.org-invite-scim %}
+> * Inviting an outside collaborator to a repository using their email address temporarily uses an available seat, even if they already have access to other repositories. After they accept the invite, the seat will be freed up again. However, inviting them using their username does not temporarily use a seat.
 
 {% data variables.product.company_short %} does not bill for any of the following accounts:
 
diff --git a/content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md b/content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md
index c6cb9b53c0..534f93a4df 100644
--- a/content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md
+++ b/content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md
@@ -92,11 +92,8 @@ To see a demo of the process from beginning to end, see [Billing GitHub consumpt
 
 To connect your Azure subscription, you must have owner permissions to the Azure subscription and be an organization owner on {% data variables.product.prodname_dotcom %}.
 
-{% note %}
-
-**Note**: If your organization account on {% data variables.location.product_location %} belongs an enterprise account, you must connect your Azure subscription to the enterprise account instead of the organization account. See "[Connecting your Azure subscription to your enterprise account](/enterprise-cloud@latest/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription#connecting-your-azure-subscription-to-your-enterprise-account)" in the {% data variables.product.prodname_ghe_cloud %} version of this article.
-
-{% endnote %}
+> [!NOTE]
+> If your organization account on {% data variables.location.product_location %} belongs an enterprise account, you must connect your Azure subscription to the enterprise account instead of the organization account. See "[Connecting your Azure subscription to your enterprise account](/enterprise-cloud@latest/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription#connecting-your-azure-subscription-to-your-enterprise-account)" in the {% data variables.product.prodname_ghe_cloud %} version of this article.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/content/billing/managing-the-plan-for-your-github-account/discounted-plans-for-github-accounts.md b/content/billing/managing-the-plan-for-your-github-account/discounted-plans-for-github-accounts.md
index f502e8906b..3de7fc16cb 100644
--- a/content/billing/managing-the-plan-for-your-github-account/discounted-plans-for-github-accounts.md
+++ b/content/billing/managing-the-plan-for-your-github-account/discounted-plans-for-github-accounts.md
@@ -21,11 +21,9 @@ topics:
   - User account
 shortTitle: Discounted plans
 ---
-{% tip %}
 
-**Tip**: Discounts for an account's plan do not apply to other subscriptions or usage-based billing.
-
-{% endtip %}
+> [!TIP]
+> Discounts for an account's plan do not apply to other subscriptions or usage-based billing.
 
 ## Discounts for personal accounts
 
diff --git a/content/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan.md b/content/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan.md
index 1e834eb4c2..40582308f6 100644
--- a/content/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan.md
+++ b/content/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan.md
@@ -54,11 +54,8 @@ After an organization's plan is downgraded, the organization will lose access to
 
 Downgrading from {% data variables.product.prodname_ghe_cloud %} disables any SAML settings. If you later purchase {% data variables.product.prodname_enterprise %}, you will need to reconfigure SAML.
 
-{% note %}
-
-**Note:** If your organization is owned by an enterprise account, billing cannot be managed at the organization level. To downgrade, you must remove the organization from the enterprise account first. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
-
-{% endnote %}
+> [!NOTE]
+> If your organization is owned by an enterprise account, billing cannot be managed at the organization level. To downgrade, you must remove the organization from the enterprise account first. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
 
 {% data reusables.organizations.billing-settings %}
 1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want.
@@ -102,11 +99,8 @@ To downgrade the plan of an individual organization within the enterprise accoun
 
 {% data reusables.enterprise-accounts.billing-perms %}
 
-{% note %}
-
-**Note:** If your enterprise account is invoiced, you cannot remove seats on {% data variables.product.prodname_dotcom %}. Instead, contact {% data variables.contact.contact_enterprise_sales %}.
-
-{% endnote %}
+> [!NOTE]
+> If your enterprise account is invoiced, you cannot remove seats on {% data variables.product.prodname_dotcom %}. Instead, contact {% data variables.contact.contact_enterprise_sales %}.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/content/billing/managing-the-plan-for-your-github-account/one-time-payments-for-customers-in-india.md b/content/billing/managing-the-plan-for-your-github-account/one-time-payments-for-customers-in-india.md
index e18f741b4d..4cc1687359 100644
--- a/content/billing/managing-the-plan-for-your-github-account/one-time-payments-for-customers-in-india.md
+++ b/content/billing/managing-the-plan-for-your-github-account/one-time-payments-for-customers-in-india.md
@@ -52,11 +52,8 @@ Existing sponsorships will remain in place during this period and maintainers wi
 
 ## Making a one-time payment for a GitHub subscription
 
-{% note %}
-
-**Note**: Affected customers will receive an email notification with a link to their billing settings when payment is due. Two further reminder emails will be sent 7 and 14 days later if payment has not been made. After 14 days, paid features and services will be locked until payment is made.
-
-{% endnote %}
+> [!NOTE]
+> Affected customers will receive an email notification with a link to their billing settings when payment is due. Two further reminder emails will be sent 7 and 14 days later if payment has not been made. After 14 days, paid features and services will be locked until payment is made.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.billing_plans_payment %}
diff --git a/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md b/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md
index 0c938f750a..89ca5344f8 100644
--- a/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md
+++ b/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md
@@ -22,11 +22,8 @@ For privacy reasons, enterprise owners cannot directly access the details of use
 
 ## About the calculation of consumed licenses
 
-{% note %}
-
-**Note:** For {% data variables.visual_studio.prodname_vs_subscriber %}s, see "[AUTOTITLE](/enterprise-cloud@latest/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."
-
-{% endnote %}
+> [!NOTE]
+> For {% data variables.visual_studio.prodname_vs_subscriber %}s, see "[AUTOTITLE](/enterprise-cloud@latest/billing/managing-billing-for-your-products/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."
 
 A person consumes a license for {% data variables.product.prodname_enterprise %} depending on specific criteria. If a user has not yet accepted an invitation to join your enterprise, the user still consumes a license. For more information about the people in your enterprise who consume a license, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/about-per-user-pricing)."
 
@@ -98,11 +95,8 @@ To ensure that the each user is only consuming a single seat for different deplo
 
 1. To help identify users that are consuming multiple seats, if your enterprise uses verified domains for {% data variables.product.prodname_ghe_cloud %}, review the list of enterprise members who do not have an email address from a verified domain associated with their account on {% data variables.product.prodname_ghe_cloud %}. Often, these are the users who erroneously consume more than one licensed seat. For more information, see "[AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)."
 
-   {% note %}
-
-   **Note:** To make troubleshooting easier, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
-
-   {% endnote %}
+   > [!NOTE]
+   > To make troubleshooting easier, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
 
 1. After you identify users who are consuming multiple seats, make sure that the same email address is associated with all of the user's accounts. For more information about which email addresses must match, see "[About the calculation of consumed licenses](#about-the-calculation-of-consumed-licenses)."
 1. If an email address was recently updated or verified to correct a mismatch, view the timestamp of the last license sync job. If a job hasn't run since the correction was made, manually trigger a new job. For more information, see "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
diff --git a/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md b/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
index eff5807336..3241377bbe 100644
--- a/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
+++ b/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
@@ -19,11 +19,10 @@ After you purchase or upgrade a license for {% data variables.product.prodname_e
 ## Uploading your license from the {% data variables.enterprise.management_console %}
 
 {% ifversion ghes < 3.13 %}
-{% warning %}
 
-**Warning:** Updating your license causes a small amount of downtime for {% data variables.location.product_location %}.
+> [!WARNING]
+> Updating your license causes a small amount of downtime for {% data variables.location.product_location %}.
 
-{% endwarning %}
 {% endif %}
 
 1. Sign into {% data variables.location.product_location_enterprise %} as a site administrator.
diff --git a/content/billing/setting-up-paid-accounts-for-procurement-companies/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md b/content/billing/setting-up-paid-accounts-for-procurement-companies/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
index d950bf5429..decfe0319e 100644
--- a/content/billing/setting-up-paid-accounts-for-procurement-companies/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
+++ b/content/billing/setting-up-paid-accounts-for-procurement-companies/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
@@ -17,11 +17,8 @@ shortTitle: Renewing paid organization
 ---
 {% data reusables.organizations.reseller-ask-to-become-billing-manager %}
 
-{% tip %}
-
-**Tip**: Billing managers can also [change the organization's number of paid seats](/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization) anytime.
-
-{% endtip %}
+> [!TIP]
+> Billing managers can also [change the organization's number of paid seats](/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization) anytime.
 
 ## Updating your organization's credit card
 
diff --git a/content/billing/setting-up-paid-accounts-for-procurement-companies/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md b/content/billing/setting-up-paid-accounts-for-procurement-companies/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
index 0141042f56..bf3f4a0414 100644
--- a/content/billing/setting-up-paid-accounts-for-procurement-companies/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/content/billing/setting-up-paid-accounts-for-procurement-companies/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -18,13 +18,9 @@ shortTitle: Upgrade or downgrade
 ---
 {% data reusables.organizations.reseller-ask-to-become-billing-manager %}
 
-{% tip %}
-
-**Tips**:
-* Before you upgrade your client's organization, you can [view or update the payment method on file for the organization](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method).
-* These instructions are for upgrading and downgrading organizations on the _per-seat subscription_. If your client pays for {% data variables.product.product_name %} using a _legacy per-repository_ plan, you can upgrade or [downgrade](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan) their legacy plan, or [switch their organization to per-seat pricing](/billing/managing-the-plan-for-your-github-account/upgrading-your-accounts-plan).
-
-{% endtip %}
+> [!TIP]
+> * Before you upgrade your client's organization, you can [view or update the payment method on file for the organization](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method).
+> * These instructions are for upgrading and downgrading organizations on the _per-seat subscription_. If your client pays for {% data variables.product.product_name %} using a _legacy per-repository_ plan, you can upgrade or [downgrade](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan) their legacy plan, or [switch their organization to per-seat pricing](/billing/managing-the-plan-for-your-github-account/upgrading-your-accounts-plan).
 
 ## Upgrading an organization's number of paid seats
 
diff --git a/content/billing/using-the-billing-platform/adding-information-to-your-receipts.md b/content/billing/using-the-billing-platform/adding-information-to-your-receipts.md
index e9275edbcf..5235bb8c63 100644
--- a/content/billing/using-the-billing-platform/adding-information-to-your-receipts.md
+++ b/content/billing/using-the-billing-platform/adding-information-to-your-receipts.md
@@ -27,11 +27,8 @@ shortTitle: Add to your receipts
 
 Your receipts include your {% data variables.product.prodname_dotcom %} subscription as well as any subscriptions for other paid features and products. For more information, see "[AUTOTITLE](/billing/managing-your-github-billing-settings/about-billing-on-github)."
 
-{% warning %}
-
-**Warning**: For security reasons, we strongly recommend against including any confidential or financial information (such as credit card numbers) on your receipts.
-
-{% endwarning %}
+> [!WARNING]
+> For security reasons, we strongly recommend against including any confidential or financial information (such as credit card numbers) on your receipts.
 
 ## Adding information to your personal account's receipts
 
@@ -46,11 +43,8 @@ You can add information to your personal account's receipts, such as a VAT or GS
 
 You can add information to your organization's receipts, such as a VAT or GST identification number, or your full business name or address of record.
 
-{% note %}
-
-**Note**: {% data reusables.dotcom_billing.org-billing-perms %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.organizations.billing-settings %}
 1. At the top of the page, click **Payment information**.
diff --git a/content/billing/using-the-billing-platform/adding-or-editing-a-payment-method.md b/content/billing/using-the-billing-platform/adding-or-editing-a-payment-method.md
index bbb512be81..aa8dc8474d 100644
--- a/content/billing/using-the-billing-platform/adding-or-editing-a-payment-method.md
+++ b/content/billing/using-the-billing-platform/adding-or-editing-a-payment-method.md
@@ -72,11 +72,8 @@ You can update your enterprise account's credit card or PayPal details, or you c
 
 ### Updating your enterprise account's credit card or PayPal details
 
-{% note %}
-
-**Note:** If your enterprise account is invoiced, you cannot change your payment method on {% data variables.product.prodname_dotcom %}. Instead, contact {% data variables.contact.contact_enterprise_sales %}.
-
-{% endnote %}
+> [!NOTE]
+> If your enterprise account is invoiced, you cannot change your payment method on {% data variables.product.prodname_dotcom %}. Instead, contact {% data variables.contact.contact_enterprise_sales %}.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/content/billing/using-the-billing-platform/changing-the-duration-of-your-billing-cycle.md b/content/billing/using-the-billing-platform/changing-the-duration-of-your-billing-cycle.md
index 32249e4607..1ef86a1d5e 100644
--- a/content/billing/using-the-billing-platform/changing-the-duration-of-your-billing-cycle.md
+++ b/content/billing/using-the-billing-platform/changing-the-duration-of-your-billing-cycle.md
@@ -21,11 +21,8 @@ shortTitle: Billing cycle
 ---
 When you change your billing cycle's duration, your {% data variables.product.prodname_dotcom %} subscription, along with any other paid features and products, will be moved to your new billing cycle on your next billing date.
 
-{% note %}
-
-**Note:** Certain products, such as {% data variables.product.prodname_copilot_for_business %} and {% data variables.product.prodname_copilot_enterprise %}, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_registry %}, only offer monthly billing.
-
-{% endnote %}
+> [!NOTE]
+> Certain products, such as {% data variables.product.prodname_copilot_for_business %} and {% data variables.product.prodname_copilot_enterprise %}, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_registry %}, only offer monthly billing.
 
 ## Changing the duration of your personal account's billing cycle
 
@@ -58,11 +55,8 @@ When you change your billing cycle's duration, your {% data variables.product.pr
 
 {% data reusables.enterprise-accounts.billing-perms %}
 
-{% note %}
-
-**Note:** You cannot change the duration of your billing cycle if your enterprise account is invoiced.
-
-{% endnote %}
+> [!NOTE]
+> You cannot change the duration of your billing cycle if your enterprise account is invoiced.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/content/billing/using-the-billing-platform/viewing-your-payment-history-and-receipts.md b/content/billing/using-the-billing-platform/viewing-your-payment-history-and-receipts.md
index 3215ef5051..62bee26762 100644
--- a/content/billing/using-the-billing-platform/viewing-your-payment-history-and-receipts.md
+++ b/content/billing/using-the-billing-platform/viewing-your-payment-history-and-receipts.md
@@ -42,11 +42,8 @@ shortTitle: View history & receipts
 
 {% data reusables.enterprise-accounts.billing-perms %}
 
-{% note %}
-
-**Note:** You cannot view receipts if your enterprise account is invoiced.
-
-{% endnote %}
+> [!NOTE]
+> You cannot view receipts if your enterprise account is invoiced.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/content/billing/using-the-billing-platform/viewing-your-subscriptions-and-billing-date.md b/content/billing/using-the-billing-platform/viewing-your-subscriptions-and-billing-date.md
index ca5e536fc4..5a9b246ac8 100644
--- a/content/billing/using-the-billing-platform/viewing-your-subscriptions-and-billing-date.md
+++ b/content/billing/using-the-billing-platform/viewing-your-subscriptions-and-billing-date.md
@@ -39,11 +39,8 @@ shortTitle: Subscriptions & billing date
 
 {% data reusables.enterprise-accounts.billing-perms %}
 
-{% note %}
-
-**Note:** You cannot view your next billing date if your enterprise account is invoiced.
-
-{% endnote %}
+> [!NOTE]
+> You cannot view your next billing date if your enterprise account is invoiced.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md b/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
index be84168568..0589406dce 100644
--- a/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
+++ b/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
@@ -42,11 +42,8 @@ Your core focus should be preparing as many teams to use {% data variables.produ
 
 You can programmatically gather information about the different programming languages used in your repositories and use that data to enable {% data variables.product.prodname_code_scanning %} on all repositories that use the same language, using {% data variables.product.product_name %}'s GraphQL API.
 
-{% note %}
-
-**Note:** To gather this data without manually running the GraphQL queries described in this article, you can use our publicly available tool. For more information, see the "[ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement)" repository.
-
-{% endnote %}
+> [!NOTE]
+> To gather this data without manually running the GraphQL queries described in this article, you can use our publicly available tool. For more information, see the "[ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement)" repository.
 
 If you want to gather information from repositories belonging to multiple organizations in your enterprise, you can use the query below to obtain the names of your organizations and then feed those into repository query. Replace OCTO-ENTERPRISE with your enterprise name.
 
@@ -128,13 +125,10 @@ Before you can proceed with pilot programs and rolling out {% data variables.pro
 
 ## Preparing to enable {% data variables.product.prodname_secret_scanning %}
 
-{% note %}
-
-**Note:** When a secret is detected in a repository that has enabled {% data variables.product.prodname_secret_scanning %}, {% data variables.product.prodname_dotcom %} alerts all users with access to security alerts for the repository. {% ifversion ghec %}
-
-Secrets found in public repositories using {% data variables.secret-scanning.partner_alerts %} are reported directly to the partner, without creating an alert on {% data variables.product.product_name %}. For details about the supported partner patterns, see "[AUTOTITLE](/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)."{% endif %}
-
-{% endnote %}
+> [!NOTE]
+> When a secret is detected in a repository that has enabled {% data variables.product.prodname_secret_scanning %}, {% data variables.product.prodname_dotcom %} alerts all users with access to security alerts for the repository. {% ifversion ghec %}
+>
+> Secrets found in public repositories using {% data variables.secret-scanning.partner_alerts %} are reported directly to the partner, without creating an alert on {% data variables.product.product_name %}. For details about the supported partner patterns, see "[AUTOTITLE](/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)."{% endif %}
 
 If a project communicates with an external service, it might use a token or private key for authentication. If you check a secret into a repository, anyone who has read access to the repository can use the secret to access the external service with your privileges. {% data variables.product.prodname_secret_scanning_caps %} will scan your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repositories for secrets and alert you or block the push containing the secret. For more information, see "[AUTOTITLE](/code-security/secret-scanning/introduction/about-secret-scanning)."
 
diff --git a/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md b/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
index 1d32a3dca8..f6972bf4c7 100644
--- a/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
+++ b/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
@@ -36,11 +36,8 @@ Using the data you collated in [Phase 2](/code-security/adopting-github-advanced
 
 There is a publicly available tool that completes the first two steps called the [ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement). You can re-run the ghas-enablement tool in batches of languages where it makes sense. For example, JavaScript, TypeScript, Python, and Go likely have a similar build process and could therefore use a similar {% data variables.product.prodname_codeql %} analysis file. The ghas-enablement tool can also be used for languages such as Java, C, and C++, but due to the varied nature of how these languages build and compile you may need to create more targeted {% data variables.product.prodname_codeql %} analysis files.
 
-{% note %}
-
-**Note:** If you are intending to use {% data variables.product.prodname_actions %} to control {% data variables.product.prodname_code_scanning %} and you do not use the [ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement), keep in mind that there is no API access to the `.github/workflow` directory. This means that you cannot create a script without a git client underlying the automation. The workaround is to leverage bash scripting on a machine or container which has a git client. The git client can push and pull files into the `.github/workflows` directory where the `codeql-analysis.yml` file is located.
-
-{% endnote %}
+> [!NOTE]
+> If you are intending to use {% data variables.product.prodname_actions %} to control {% data variables.product.prodname_code_scanning %} and you do not use the [ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement), keep in mind that there is no API access to the `.github/workflow` directory. This means that you cannot create a script without a git client underlying the automation. The workaround is to leverage bash scripting on a machine or container which has a git client. The git client can push and pull files into the `.github/workflows` directory where the `codeql-analysis.yml` file is located.
 
 It is important to not just push the `codeql-analysis.yml` file the repository's default branch. Using a pull request puts ownership on the development team to review and merge, allowing the development team to learn about {% data variables.product.prodname_code_scanning %} and involving the team in the process.
 
diff --git a/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md b/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
index 8e140ec4a4..f562b61105 100644
--- a/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
+++ b/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
@@ -40,20 +40,15 @@ There are a few approaches for tackling newly committed credentials, but one exa
 1. **Notify**: Use webhooks to ensure that any new secret alerts are seen by the right teams as quickly as possible. A webhook fires when a secret alert is either created, resolved, or reopened. You can then parse the webhook payload, and integrate it into any tools you and your team use such Slack, Teams, Splunk, or email. For more information, see "[AUTOTITLE](/webhooks-and-events/webhooks/about-webhooks)" and "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert)."
 1. **Follow Up**: Create a high-level remediation process that works for all secret types. For example, you could contact the developer who committed the secret and their technical lead on that project, highlighting the dangers of committing secrets to {% data variables.product.prodname_dotcom %}, and asking the them to revoke, and update the detected secret.
 
-   {% note %}
+   > [!NOTE]
+   > You can automate this step. For large enterprises and organizations with hundreds of repositories, manually following up is unsustainable. You could incorporate automation into the webhook process defined in the first step. The webhook payload contains repository and organization information about the leaked secret. Using this information, you can contact the current maintainers on the repository and create an email/message to the responsible people or open an issue.
 
-   **Note:** You can automate this step. For large enterprises and organizations with hundreds of repositories, manually following up is unsustainable. You could incorporate automation into the webhook process defined in the first step. The webhook payload contains repository and organization information about the leaked secret. Using this information, you can contact the current maintainers on the repository and create an email/message to the responsible people or open an issue.
-
-   {% endnote %}
 1. **Educate**: Create an internal training document assigned to the developer who committed the secret. Within this training document, you can explain the risks created by committing secrets and direct them to your best practice information about using secrets securely in development. If a developer doesn't learn from the experience and continues to commit secrets, you could create an escalation process, but education usually works well.
 
 Repeat the last two steps for any new secrets leaked. This process encourages developers to take responsibility for managing the secrets used in their code securely, and allows you to measure the reduction in newly committed secrets.
 
-{% note %}
-
-**Note:** More advanced organizations may want to perform auto-remediation of certain types of secrets. There is an open-source initiative called [GitHub Secret Scanner Auto Remediator](https://github.com/NickLiffen/GSSAR) which you can deploy into your AWS, Azure, or GCP environment and tailor to automatically revoke certain types of secrets based on what you define as the most critical. This is also an excellent way to react to new secrets being committed with a more automated approach.
-
-{% endnote %}
+> [!NOTE]
+> More advanced organizations may want to perform auto-remediation of certain types of secrets. There is an open-source initiative called [GitHub Secret Scanner Auto Remediator](https://github.com/NickLiffen/GSSAR) which you can deploy into your AWS, Azure, or GCP environment and tailor to automatically revoke certain types of secrets based on what you define as the most critical. This is also an excellent way to react to new secrets being committed with a more automated approach.
 
 ## 2. Enable push protection
 
@@ -81,11 +76,8 @@ Once you have decided on the secret types, you can do the following:
 
 1. Define a process for remediating each type of secret. The actual procedure for each secret type is often drastically different. Write down the process for each type of secret in a document or internal knowledge base.
 
-   {% note %}
-
-   **Note:** When you create the process for revoking secrets, try and give the responsibility for revoking secrets to the team maintaining the repository instead of a central team. One of the principles of GHAS is developers taking ownership of security and having the responsibility of fixing security issues, especially if they have created them.
-
-   {% endnote %}
+   > [!NOTE]
+   > When you create the process for revoking secrets, try and give the responsibility for revoking secrets to the team maintaining the repository instead of a central team. One of the principles of GHAS is developers taking ownership of security and having the responsibility of fixing security issues, especially if they have created them.
 
 1. When you have created the process that teams will follow for revoking credentials, you can collate information about the types of secrets and other metadata associated with the leaked secrets so you can discern who to communicate the new process to.
 
@@ -99,11 +91,8 @@ Once you have decided on the secret types, you can do the following:
    * Secret value
    * Maintainers on repository to contact
 
-   {% note %}
-
-   **Note:** Use the UI if you have few secrets leaked of that type. If you have hundreds of leaked secrets, use the API to collect information. For more information, see "[AUTOTITLE](/rest/secret-scanning)."
-
-   {% endnote %}
+   > [!NOTE]
+   > Use the UI if you have few secrets leaked of that type. If you have hundreds of leaked secrets, use the API to collect information. For more information, see "[AUTOTITLE](/rest/secret-scanning)."
 
 1. After you collect information about leaked secrets, create a targeted communication plan for the users who maintain the repositories affected by each secret type. You could use email, messaging, or even create GitHub issues in the affected repositories. If you can use APIs provided by these tools to send out the communications in an automated manner, this will make it easier for you to scale across multiple secret types.
 
diff --git a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages.md b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages.md
index ab441c209e..f60dce08d4 100644
--- a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages.md
+++ b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages.md
@@ -262,11 +262,8 @@ If you added manual build steps for compiled languages and {% data variables.pro
 * [Building Java and Kotlin](#building-java-and-kotlin)
 * [Building Swift](#building-swift)
 
-{% note %}
-
-**Note**: If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands.
-
-{% endnote %}
+> [!NOTE]
+> If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands.
 
 ## Building C/C++
 
@@ -431,11 +428,8 @@ The `autobuild` process attempts to autodetect a suitable way to install the dep
 1. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes.
 1. Extract all Go code in the repository, similar to running `go build ./...`.
 
-{% note %}
-
-**Note:** If you use default setup, it will look for a `go.mod` file to automatically install a compatible version of the Go language.{% ifversion code-scanning-default-setup-self-hosted-310 %} If you're using a self-hosted runner with default setup that doesn't have internet access, you can manually install a compatible version of Go.{% endif %}
-
-{% endnote %}
+> [!NOTE]
+> If you use default setup, it will look for a `go.mod` file to automatically install a compatible version of the Go language.{% ifversion code-scanning-default-setup-self-hosted-310 %} If you're using a self-hosted runner with default setup that doesn't have internet access, you can manually install a compatible version of Go.{% endif %}
 
 ### Extractor options for Go
 
diff --git a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning.md b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning.md
index f35e38c7f4..d1fbc481a4 100644
--- a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning.md
+++ b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning.md
@@ -57,11 +57,10 @@ You can customize your {% data variables.product.prodname_codeql %} analysis by
 {% data reusables.code-scanning.billing %}
 
 {% ifversion fpt %}
-  {% note %}
 
-  **Note:** You can configure {% data variables.product.prodname_code_scanning %} for any public repository where you have write access.
+  > [!NOTE]
+  > You can configure {% data variables.product.prodname_code_scanning %} for any public repository where you have write access.
 
-  {% endnote %}
 {% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -69,11 +68,8 @@ You can customize your {% data variables.product.prodname_codeql %} analysis by
 {% data reusables.user-settings.security-analysis %}
 1. Scroll down to the "{% data variables.product.prodname_code_scanning_caps %}" section, select **Set up** {% octicon "triangle-down" aria-hidden="true" %}, then click **Advanced**.
 
-   {% note %}
-
-   **Note:** If you are switching from default setup to advanced setup, in the "{% data variables.product.prodname_code_scanning_caps %}" section, select {% octicon "kebab-horizontal" aria-label="Menu" %}, then click {% octicon "workflow" aria-hidden="true" %} **Switch to advanced**. In the pop-up window that appears, click **Disable {% data variables.product.prodname_codeql %}**.
-
-   {% endnote %}
+   > [!NOTE]
+   > If you are switching from default setup to advanced setup, in the "{% data variables.product.prodname_code_scanning_caps %}" section, select {% octicon "kebab-horizontal" aria-label="Menu" %}, then click {% octicon "workflow" aria-hidden="true" %} **Switch to advanced**. In the pop-up window that appears, click **Disable {% data variables.product.prodname_codeql %}**.
 
    ![Screenshot of the "{% data variables.product.prodname_code_scanning_caps %}" section of "Code security and analysis" settings. The "Advanced setup" button is highlighted with an orange outline.](/assets/images/help/security/advanced-code-scanning-setup.png)
 
diff --git a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.md b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.md
index cf22324d3b..4d3ca26dee 100644
--- a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.md
+++ b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.md
@@ -76,11 +76,8 @@ Using the `pull_request` trigger, configured to scan the pull request's merge co
 
 {% ifversion fpt or ghec %}
 
-{% note %}
-
-**Note:** If your repository is configured with a merge queue, you need to include the `merge_group` event as an additional trigger for {% data variables.product.prodname_code_scanning %}. This will ensure that pull requests are also scanned when they are added to a merge queue. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)."
-
-{% endnote %}
+> [!NOTE]
+> If your repository is configured with a merge queue, you need to include the `merge_group` event as an additional trigger for {% data variables.product.prodname_code_scanning %}. This will ensure that pull requests are also scanned when they are added to a merge queue. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)."
 
 {% endif %}
 
@@ -99,11 +96,8 @@ on:
       - '**/*.txt'
 ```
 
-{% note %}
-
-**Note:** `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
-
-{% endnote %}
+> [!NOTE]
+> `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
 
 For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
 
@@ -111,11 +105,8 @@ For more information about using `on:pull_request:paths-ignore` and `on:pull_req
 
 If you use the default {% data variables.code-scanning.codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onschedule)."
 
-{% note %}
-
-**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
 
 ### Example
 
@@ -138,15 +129,10 @@ This workflow scans:
 
 ## Specifying an operating system
 
-{% note %}
-
-**Notes**:
-
-* Code scanning of Swift code uses macOS runners by default. {% ifversion fpt or ghec %}{% data variables.product.company_short %}-hosted macOS runners are more expensive than Linux and Windows runners, so you should consider only scanning the build step. For more information about configuring code scanning for Swift, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#considerations-for-building-swift)." For more information about pricing for {% data variables.product.company_short %}-hosted runners, see "[AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %}
-
-* {% data reusables.code-scanning.default-setup-swift-self-hosted-runners %}
-
-{% endnote %}
+> [!NOTE]
+> * Code scanning of Swift code uses macOS runners by default. {% ifversion fpt or ghec %}{% data variables.product.company_short %}-hosted macOS runners are more expensive than Linux and Windows runners, so you should consider only scanning the build step. For more information about configuring code scanning for Swift, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#considerations-for-building-swift)." For more information about pricing for {% data variables.product.company_short %}-hosted runners, see "[AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %}
+>
+> * {% data reusables.code-scanning.default-setup-swift-self-hosted-runners %}
 
 If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.code-scanning.codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
 
@@ -299,11 +285,8 @@ In this example, the default queries will be run for Java, as well as the querie
 
 To add one or more {% data variables.product.prodname_codeql %} query packs, add a `with: packs:` entry within the `uses: {% data reusables.actions.action-codeql-action-init %}` section of the workflow. Within `packs` you specify one or more packages to use and, optionally, which version to download. Where you don't specify a version, the latest version is downloaded. If you want to use packages that are not publicly available, you need to set the `GITHUB_TOKEN` environment variable to a secret that has access to the packages. For more information, see "[AUTOTITLE](/actions/security-guides/automatic-token-authentication)" and "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
 
-{% note %}
-
-**Note:** For workflows that generate {% data variables.product.prodname_codeql %} databases for multiple languages, you must instead specify the {% data variables.product.prodname_codeql %} query packs in a configuration file. For more information, see "[Specifying {% data variables.product.prodname_codeql %} query packs](#specifying-codeql-query-packs)" below.
-
-{% endnote %}
+> [!NOTE]
+> For workflows that generate {% data variables.product.prodname_codeql %} databases for multiple languages, you must instead specify the {% data variables.product.prodname_codeql %} query packs in a configuration file. For more information, see "[Specifying {% data variables.product.prodname_codeql %} query packs](#specifying-codeql-query-packs)" below.
 
 In the example below, `scope` is the organization or personal account that published the package. When the workflow runs, the four {% data variables.product.prodname_codeql %} query packs are downloaded from {% data variables.product.product_name %} and the default queries or query suite for each pack run:
 * The latest version of `pack1` is downloaded and all default queries are run.
@@ -318,18 +301,10 @@ In the example below, `scope` is the organization or personal account that publi
     packs: scope/pack1,scope/pack2@1.2.3,scope/pack3@~3.2.1,scope/pack4@4.5.6:path/to/queries
 ```
 
-{% note %}
-
-**Note:** If you specify a particular version of a query pack to use,
-beware that the version you specify may eventually become too old to
-be used efficiently by the default
-{% data variables.product.prodname_codeql %} engine used by the
-{% data variables.product.prodname_codeql %} action.
-To ensure optimal performance, if you need to specify exact query pack versions, you should consider reviewing periodically whether the pinned version of the query pack needs to be moved forward.
-
-For more information about pack compatibility, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs#about-codeql-pack-compatibility)."
-
-{% endnote %}
+> [!NOTE]
+> If you specify a particular version of a query pack to use, beware that the version you specify may eventually become too old to be used efficiently by the default {% data variables.product.prodname_codeql %} engine used by the {% data variables.product.prodname_codeql %} action. To ensure optimal performance, if you need to specify exact query pack versions, you should consider reviewing periodically whether the pinned version of the query pack needs to be moved forward.
+>
+> For more information about pack compatibility, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs#about-codeql-pack-compatibility)."
 
 ### Downloading {% data variables.product.prodname_codeql %} packs from {% data variables.product.prodname_ghe_server %}
 
@@ -517,13 +492,9 @@ query-filters:
 
 To find the id of a query, you can click the alert in the list of alerts in the **Security** tab. This opens the alert details page. The `Rule ID` field contains the query id. For more information about the alert details page, see "[AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts#about-alert-details)."
 
-{% tip %}
-
-**Tips:**
-* The order of the filters is important. The first filter instruction that appears after the instructions about the queries and query packs determines whether the queries are included or excluded by default.
-* Subsequent instructions are executed in order and the instructions that appear later in the file take precedence over the earlier instructions.
-
-{% endtip %}
+> [!TIP]
+> * The order of the filters is important. The first filter instruction that appears after the instructions about the queries and query packs determines whether the queries are included or excluded by default.
+> * Subsequent instructions are executed in order and the instructions that appear later in the file take precedence over the earlier instructions.
 
 You can find another example illustrating the use of these filters in the "[Example configuration files](#example-configuration-files)" section.
 
@@ -541,15 +512,10 @@ paths-ignore:
   - '**/*.test.js'
 ```
 
-{% note %}
-
-**Note**:
-
-* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
-* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
-* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
-
-{% endnote %}
+> [!NOTE]
+> * The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+> * The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+> * `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
 
 For analysis where code is built, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
 
@@ -582,22 +548,17 @@ This step in a {% data variables.product.prodname_actions %} workflow file uses
 
 You can use the same approach to specify any valid configuration options in the workflow file.
 
-{% tip %}
-
-**Tip:**
-
-You can share one configuration across multiple repositories using  {% data variables.product.prodname_actions %} variables. One benefit of this approach is that you can update the configuration in a single place without editing the workflow file.
-
-In the following example, `vars.CODEQL_CONF` is a {% data variables.product.prodname_actions %} variable. Its value can be the contents of any valid configuration file. For more information, see "[AUTOTITLE](/actions/learn-github-actions/variables#defining-configuration-variables-for-multiple-workflows)."
-
-```yaml
-- uses: {% data reusables.actions.action-codeql-action-init %}
-  with:
-    languages: {% raw %}${{ matrix.language }}{% endraw %}
-    config: {% raw %}${{ vars.CODEQL_CONF }}{% endraw %}
-```
-
-{% endtip %}
+> [!TIP]
+> You can share one configuration across multiple repositories using  {% data variables.product.prodname_actions %} variables. One benefit of this approach is that you can update the configuration in a single place without editing the workflow file.
+>
+> In the following example, `vars.CODEQL_CONF` is a {% data variables.product.prodname_actions %} variable. Its value can be the contents of any valid configuration file. For more information, see "[AUTOTITLE](/actions/learn-github-actions/variables#defining-configuration-variables-for-multiple-workflows)."
+>
+> ```yaml
+> - uses: {% data reusables.actions.action-codeql-action-init %}
+>   with:
+>     languages: {% raw %}${{ matrix.language }}{% endraw %}
+>     config: {% raw %}${{ vars.CODEQL_CONF }}{% endraw %}
+> ```
 
 ## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
 
diff --git a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/running-codeql-code-scanning-in-a-container.md b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/running-codeql-code-scanning-in-a-container.md
index 6d1befecc1..a9f72a4760 100644
--- a/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/running-codeql-code-scanning-in-a-container.md
+++ b/content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/running-codeql-code-scanning-in-a-container.md
@@ -30,11 +30,8 @@ If you're configuring {% data variables.product.prodname_code_scanning %} for a
 
 You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %}, see "[AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/using-code-scanning-with-your-existing-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
 
-{% note %}
-
-**Note:** {% data reusables.code-scanning.non-glibc-linux-support %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.code-scanning.non-glibc-linux-support %}
 
 ## Dependencies for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}
 
diff --git a/content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale.md b/content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale.md
index 1dbac96f79..27c30b89e6 100644
--- a/content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale.md
+++ b/content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale.md
@@ -59,11 +59,10 @@ A repository must meet all the following criteria to be eligible for default set
 {% data reusables.code-scanning.default-setup-pre-enablement-explanation %}
 {% endif %}
 {% ifversion code-security-multi-repo-enablement %}
-{% note %}
 
-**Note:** Configuring default setup for all repositories in an organization through your organization's settings page _will not_ override existing configurations of default setup. However, configuring default setup on a subset of repositories in an organization through security overview _will_ override existing configurations of default setup on those repositories.
+> [!NOTE]
+> Configuring default setup for all repositories in an organization through your organization's settings page _will not_ override existing configurations of default setup. However, configuring default setup on a subset of repositories in an organization through security overview _will_ override existing configurations of default setup on those repositories.
 
-{% endnote %}
 {% endif %}
 {% ifversion code-scanning-default-setup-automatic-311 %}
 
@@ -90,14 +89,10 @@ Through the "Code security and analysis" page of your organization's settings, y
 1. Optionally, to recommend the "Extended" query suite throughout your organization when enabling default setup, select "Recommend the extended query suite for repositories enabling default setup."{% else %}
 1. In the "Enable {% data variables.product.prodname_code_scanning %} for eligible repositories" dialog box displayed, click **Enable for eligible repositories** to enable your configuration of default setup.{% endif %}
 
-{% note %}
-
-**Notes:**
-  * {% data reusables.code-scanning.limitation-org-enable-all %}
-  * Enabling {% data variables.product.prodname_code_scanning %} for all eligible repositories in an organization will not override existing {% data variables.product.prodname_code_scanning %} configurations. For information on configuring default setup with different settings for specific repositories, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning){% ifversion code-security-multi-repo-enablement %}" and "[Configuring default setup for a subset of repositories in an organization](#configuring-default-setup-for-a-subset-of-repositories-in-an-organization){% endif %}."{% ifversion default-setup-pre-enablement %}
-  * Enabling default setup for all eligible repositories in an organization includes eligible repositories without {% data variables.product.prodname_codeql %}-supported languages. If a {% data variables.product.prodname_codeql %}-supported language is later added to one of these repositories, default setup will begin scanning that repository and consuming {% data variables.product.prodname_actions %} minutes.{% endif %}
-
-{% endnote %}
+> [!NOTE]
+> * {% data reusables.code-scanning.limitation-org-enable-all %}
+> * Enabling {% data variables.product.prodname_code_scanning %} for all eligible repositories in an organization will not override existing {% data variables.product.prodname_code_scanning %} configurations. For information on configuring default setup with different settings for specific repositories, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning){% ifversion code-security-multi-repo-enablement %}" and "[Configuring default setup for a subset of repositories in an organization](#configuring-default-setup-for-a-subset-of-repositories-in-an-organization){% endif %}."{% ifversion default-setup-pre-enablement %}
+> * Enabling default setup for all eligible repositories in an organization includes eligible repositories without {% data variables.product.prodname_codeql %}-supported languages. If a {% data variables.product.prodname_codeql %}-supported language is later added to one of these repositories, default setup will begin scanning that repository and consuming {% data variables.product.prodname_actions %} minutes.{% endif %}
 
 {% endif %}
 
@@ -165,20 +160,12 @@ You can select all of the displayed repositories, or a subset of them, and enabl
 1. Optionally, to choose a different query suite than your organization's default query suite, select **Query suite: SUITE NAME**, then click the query suite your configuration of default setup should use. For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites)."{% endif %}
 1. To confirm the enablement of {% data variables.product.prodname_code_scanning %} for the selected repositories, click **Apply changes NUMBER**. Alternatively, to select or deselect more repositories for {% data variables.product.prodname_code_scanning %} enablement, click {% octicon "x" aria-label="Close" %} to close the panel without applying your changes.
 
+> [!NOTE]
 {% ifversion default-setup-pre-enablement %}
-  {% note %}
-
-  **Notes:**
-  * Enabling {% data variables.product.prodname_code_scanning %} for multiple repositories in an organization using security overview will override any existing {% data variables.product.prodname_code_scanning %} configurations for the selected repositories, including any previous query suite selections and workflows for advanced setups.
-  * You can enable default setup for eligible repositories that do not contain {% data variables.product.prodname_codeql %}-supported languages. If a {% data variables.product.prodname_codeql %}-supported language is later added to one of these repositories, default setup will begin scanning that repository and consuming {% data variables.product.prodname_actions %} minutes.
-
-  {% endnote %}
+> * Enabling {% data variables.product.prodname_code_scanning %} for multiple repositories in an organization using security overview will override any existing {% data variables.product.prodname_code_scanning %} configurations for the selected repositories, including any previous query suite selections and workflows for advanced setups.
+> * You can enable default setup for eligible repositories that do not contain {% data variables.product.prodname_codeql %}-supported languages. If a {% data variables.product.prodname_codeql %}-supported language is later added to one of these repositories, default setup will begin scanning that repository and consuming {% data variables.product.prodname_actions %} minutes.
 {% else %}
-  {% note %}
-
-  **Note:** Enabling {% data variables.product.prodname_code_scanning %} for multiple repositories in an organization using security overview will override any existing {% data variables.product.prodname_code_scanning %} configurations for the selected repositories, including any previous query suite selections and workflows for advanced setups.
-
-  {% endnote %}
+> Enabling {% data variables.product.prodname_code_scanning %} for multiple repositories in an organization using security overview will override any existing {% data variables.product.prodname_code_scanning %} configurations for the selected repositories, including any previous query suite selections and workflows for advanced setups.
 {% endif %}
 
   ![Screenshot of the "Security coverage" view with the side panel open. The "Apply changes" button is highlighted in a dark orange outline.](/assets/images/help/security-overview/security-coverage-view-multi-repo-side-panel.png)
diff --git a/content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning.md b/content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning.md
index 62464949c6..b6d6d2d129 100644
--- a/content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning.md
+++ b/content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning.md
@@ -34,11 +34,10 @@ Default setup for {% data variables.product.prodname_code_scanning %} is the qui
 * On a weekly schedule.
 
 {% ifversion code-scanning-default-setup-exclude-dormant-repos %}
-{% note %}
 
-**Note:** If no pushes and pull requests have occurred in a repository with default setup enabled for 6 months, the weekly schedule will be disabled to save your {% data variables.product.prodname_actions %} minutes.
+> [!NOTE]
+> If no pushes and pull requests have occurred in a repository with default setup enabled for 6 months, the weekly schedule will be disabled to save your {% data variables.product.prodname_actions %} minutes.
 
-{% endnote %}
 {% endif %}
 {% endif %}
 
@@ -89,22 +88,17 @@ Compiled languages are not automatically included in default setup configuration
 When you initially configure default setup for {% data variables.product.prodname_code_scanning %} for a repository, all {% data variables.product.prodname_codeql %}-supported languages in the repository will be analyzed automatically. The languages that are analyzed successfully will be retained in the new default setup configuration. Languages that are not analyzed successfully will be automatically deselected from the default setup configuration.
 {% endif %}
 
-{% note %}
-
-**Note:** {% ifversion default-setup-pre-enablement %}If the analyses fail for all {% data variables.product.prodname_codeql %}-supported languages in a repository, default setup will still be enabled, but it will not run any scans or use any {% data variables.product.prodname_actions %} minutes until another {% data variables.product.prodname_codeql %}-supported language is added to the repository or default setup is manually reconfigured, and the analysis of a {% data variables.product.prodname_codeql %}-supported language succeeds.
+> [!NOTE]
+{% ifversion default-setup-pre-enablement %}
+> If the analyses fail for all {% data variables.product.prodname_codeql %}-supported languages in a repository, default setup will still be enabled, but it will not run any scans or use any {% data variables.product.prodname_actions %} minutes until another {% data variables.product.prodname_codeql %}-supported language is added to the repository or default setup is manually reconfigured, and the analysis of a {% data variables.product.prodname_codeql %}-supported language succeeds.
 {% else %}
-At least one {% data variables.product.prodname_codeql %}-supported language's analysis in a repository must succeed, or else default setup will not be successfully enabled in that repository.
+> At least one {% data variables.product.prodname_codeql %}-supported language's analysis in a repository must succeed, or else default setup will not be successfully enabled in that repository.
 {% endif %}
 
-{% endnote %}
-
 {% data reusables.repositories.navigate-to-repo %}
 
-   {% note %}
-
-   **Note:** If you are configuring default setup on a fork, you must first enable {% data variables.product.prodname_actions %}. To enable {% data variables.product.prodname_actions %}, under your repository name, click {% octicon "play" aria-hidden="true" %} **Actions**, then click **I understand my workflows, go ahead and enable them**. Be aware that this will enable all existing workflows on your fork.
-
-   {% endnote %}
+   > [!NOTE]
+   > If you are configuring default setup on a fork, you must first enable {% data variables.product.prodname_actions %}. To enable {% data variables.product.prodname_actions %}, under your repository name, click {% octicon "play" aria-hidden="true" %} **Actions**, then click **I understand my workflows, go ahead and enable them**. Be aware that this will enable all existing workflows on your fork.
 
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.user-settings.security-analysis %}
@@ -116,11 +110,8 @@ At least one {% data variables.product.prodname_codeql %}-supported language's a
 
    {% ifversion code-scanning-default-setup-recommended-languages %}
 
-   {% note %}
-
-   **Note:** If your repository contains _only_ compiled {% data variables.product.prodname_codeql %}-supported languages (for example, Java), you will be taken to the settings page to select the languages you want to add to your default setup configuration.
-
-   {% endnote %}
+   > [!NOTE]
+   > If your repository contains _only_ compiled {% data variables.product.prodname_codeql %}-supported languages (for example, Java), you will be taken to the settings page to select the languages you want to add to your default setup configuration.
 
 1. Optionally, to customize your {% data variables.product.prodname_code_scanning %} setup, click {% octicon "pencil" aria-hidden="true" %} **Edit**.
    * To add or remove a language from the analysis performed by default setup, select or deselect that language in the "Languages" section. {% ifversion code-scanning-default-setup-recommended-languages %}If you would like to analyze a {% data variables.product.prodname_codeql %}-supported compiled language with default setup, select that language here.{% endif %}
@@ -134,20 +125,15 @@ At least one {% data variables.product.prodname_codeql %}-supported language's a
 
    If you choose the **Extended** query suite, your {% data variables.product.prodname_code_scanning %} configuration will run lower severity and precision queries in addition to the queries included in the **Default** query suite. For more information on the available query suites, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites)."
 
-   {% note %}
+   > [!NOTE]
+   > If you configure {% data variables.product.prodname_code_scanning %} to use the **Extended** query suite, you may experience a higher rate of false positive alerts.
 
-   **Note:** If you configure {% data variables.product.prodname_code_scanning %} to use the **Extended** query suite, you may experience a higher rate of false positive alerts.
-
-   {% endnote %}
 {%- endif %}
 
 1. Review the settings for default setup on your repository, then click **Enable {% data variables.product.prodname_codeql %}**. This will trigger a workflow that tests the new, automatically generated configuration.
 
-   {% note %}
-
-   **Note:** If you are switching to default setup from advanced setup, you will see a warning informing you that default setup will override existing {% data variables.product.prodname_code_scanning %} configurations. This warning means default setup will disable the existing workflow file and block any {% data variables.product.prodname_codeql %} analysis API uploads.
-
-   {% endnote %}
+   > [!NOTE]
+   > If you are switching to default setup from advanced setup, you will see a warning informing you that default setup will override existing {% data variables.product.prodname_code_scanning %} configurations. This warning means default setup will disable the existing workflow file and block any {% data variables.product.prodname_codeql %} analysis API uploads.
 
 1. Optionally, to view your default setup configuration after enablement, select {% octicon "kebab-horizontal" aria-label="Menu" %}, then click {% octicon "gear" aria-hidden="true" %} **View {% data variables.product.prodname_codeql %} configuration**.
 
diff --git a/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
index 36a443f6a7..5fffafa31b 100644
--- a/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
+++ b/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
@@ -129,11 +129,8 @@ If you upload a second SARIF file for a commit with the same category and from t
 
 If you use a code analysis engine other than {% data variables.product.prodname_codeql %}, you can review the supported SARIF properties to optimize how your analysis results will appear on {% data variables.product.prodname_dotcom %}.
 
-{% note %}
-
-**Note:** You must supply an explicit value for any property marked as "required". The empty string is not supported for required properties.
-
-{% endnote %}
+> [!NOTE]
+> You must supply an explicit value for any property marked as "required". The empty string is not supported for required properties.
 
 Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.product.prodname_code_scanning %} will only use the following supported properties.
 
diff --git a/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index 8b079f70b2..d20ef199cb 100644
--- a/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -41,11 +41,10 @@ You can upload the results using {% data variables.product.prodname_actions %},
 * A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[AUTOTITLE](/rest/code-scanning/code-scanning#upload-an-analysis-as-sarif-data)").
 
 {% ifversion fpt or ghec %}
-{% note %}
 
-**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)."
+> [!NOTE]
+> For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)."
 
-{% endnote %}
 {% endif %}
 
 ## Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md b/content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md
index ca48edcd62..e058970cba 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md
@@ -85,11 +85,8 @@ When you click through to see details for the alert, you can see that the file p
 
 {% ifversion codeql-ml-queries %}
 
-{% note %}
-
-**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} were available a {% data variables.release-phases.public_preview %} release for JavaScript using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature was {% data variables.release-phases.retired %}. For more information, see [{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} deprecates ML-powered alerts](https://github.blog/changelog/2023-09-29-codeql-code-scanning-deprecates-ml-powered-alerts/).
-
-{% endnote %}
+> [!NOTE]
+> Experimental alerts for {% data variables.product.prodname_code_scanning %} were available a {% data variables.release-phases.public_preview %} release for JavaScript using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature was {% data variables.release-phases.retired %}. For more information, see [{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} deprecates ML-powered alerts](https://github.blog/changelog/2023-09-29-codeql-code-scanning-deprecates-ml-powered-alerts/).
 
 {% endif %}
 
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository.md b/content/code-security/code-scanning/managing-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository.md
index 9bf1fd8458..6210adb174 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository.md
@@ -40,11 +40,8 @@ By default, the {% data variables.product.prodname_code_scanning %} alerts page
 
 For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts)."
 
-{% note %}
-
-**Note:** You can see information about when {% data variables.product.prodname_code_scanning %} analysis last ran on the tool status page. For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page)."
-
-{% endnote %}
+> [!NOTE]
+> You can see information about when {% data variables.product.prodname_code_scanning %} analysis last ran on the tool status page. For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page)."
 
 {% ifversion copilot-chat-ghas-alerts %}
 
@@ -94,13 +91,9 @@ You can search the list of alerts. This is useful if there is a large number of
 | OR search | `sql OR injection` | Returns all the alerts containing `sql` or `injection` |
 | AND search | `sql AND injection` | Returns all the alerts containing both words `sql` and `injection` |
 
-{% tip %}
-
-**Tips:**
-* The multiple word search is equivalent to an OR search.
-* The AND search will return results where the search terms are found _anywhere_, in any order in the alert name or details.
-
-{% endtip %}
+> [!TIP]
+> * The multiple word search is equivalent to an OR search.
+> * The AND search will return results where the search terms are found _anywhere_, in any order in the alert name or details.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md b/content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md
index 8b873e9b11..4a65a61410 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md
@@ -64,13 +64,8 @@ Alerts may be fixed in one branch but not in another. You can use the "Branch" f
 
 {% data reusables.code-scanning.filter-non-default-branches %}
 
-{% note %}
-
-**Note:**
-
-If you run {% data variables.product.prodname_code_scanning %} using multiple configurations, the same alert will sometimes be generated by more than one configuration. Unless you run all configurations regularly, you may see alerts that are fixed in one configuration but not in another. These stale configurations and alerts can be removed from a branch. For more information, see "[Removing stale configurations and alerts from a branch](#removing-stale-configurations-and-alerts-from-a-branch)."
-
-{% endnote %}
+> [!NOTE]
+> If you run {% data variables.product.prodname_code_scanning %} using multiple configurations, the same alert will sometimes be generated by more than one configuration. Unless you run all configurations regularly, you may see alerts that are fixed in one configuration but not in another. These stale configurations and alerts can be removed from a branch. For more information, see "[Removing stale configurations and alerts from a branch](#removing-stale-configurations-and-alerts-from-a-branch)."
 
 ## Dismissing alerts
 
@@ -126,13 +121,9 @@ You may have multiple code scanning configurations on a single repository. When
 
    If you save your changes after accidentally deleting a configuration, re-run the configuration to update the alert. For more information on re-running configurations that use {% data variables.product.prodname_actions %}, see "[AUTOTITLE](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-all-the-jobs-in-a-workflow)."
 
-{% note %}
-
-**Notes:**
-* If you remove all {% data variables.product.prodname_code_scanning %} configurations for the default branch of your repository, the default branch will remain in the "Affected branches" sidebar, but it will not be analyzed by any configurations.
-* If you remove all {% data variables.product.prodname_code_scanning %} configurations for any branch other than the default branch of your repository, that branch will be removed from the "Affected branches" sidebar.
-
-{% endnote %}
+> [!NOTE]
+> * If you remove all {% data variables.product.prodname_code_scanning %} configurations for the default branch of your repository, the default branch will remain in the "Affected branches" sidebar, but it will not be analyzed by any configurations.
+> * If you remove all {% data variables.product.prodname_code_scanning %} configurations for any branch other than the default branch of your repository, that branch will be removed from the "Affected branches" sidebar.
 
 ## Further reading
 
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/content/code-security/code-scanning/managing-code-scanning-alerts/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index 705fd5f942..b2f246b8d1 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -72,10 +72,9 @@ Instead of tracking a {% data variables.product.prodname_code_scanning %} alert
    * The title contains the name of the {% data variables.product.prodname_code_scanning %} alert.
    * The body contains the task list item with the full URL to the {% data variables.product.prodname_code_scanning %} alert.
 1. Optionally, edit the title and the body of the issue.
-   {% warning %}
 
-    **Warning:** You may want to edit the title of the issue as it may expose security information. You can also edit the body of the issue. Make sure that you keep the task list item with a link to the alert otherwise the issue will no longer track the alert.
-   {% endwarning %}
+    > [!WARNING]
+    > You may want to edit the title of the issue as it may expose security information. You can also edit the body of the issue. Make sure that you keep the task list item with a link to the alert otherwise the issue will no longer track the alert.
 
 1. Click **Submit new issue**.
 
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests.md b/content/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests.md
index 8815de960d..2d61645b76 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests.md
@@ -33,11 +33,8 @@ If the lines of code changed in the pull request generate {% data variables.prod
 * The **Conversation** tab of the pull request, as part of a pull request review
 * The **Files changed** tab of the pull request
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_code_scanning_caps %} displays alerts in pull requests only when all the lines of code identified by the alert exist in the pull request diff. For more information, see "[AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#specifying-the-location-for-source-files)."
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_code_scanning_caps %} displays alerts in pull requests only when all the lines of code identified by the alert exist in the pull request diff. For more information, see "[AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#specifying-the-location-for-source-files)."
 
 {% ifversion code-scanning-autofix %}
 
@@ -129,14 +126,10 @@ Anyone with push access to a pull request can fix a {% data variables.product.pr
 
 When {% data variables.product.prodname_copilot_autofix_short %} is enabled for a repository, alerts are displayed in pull requests as normal and information from any alerts found by {% data variables.product.prodname_code_scanning %} is automatically sent to the LLM for processing. When LLM analysis is complete, any results are published as comments on relevant alerts. For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/responsible-use-autofix-code-scanning)."
 
-{% note %}
-
-**Notes:**
-* {% data variables.product.prodname_copilot_autofix_short %} supports a subset of {% data variables.product.prodname_codeql %} queries. For information about the availability of {% data variables.product.prodname_copilot_autofix_short %}, see the query tables linked from "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites#query-lists-for-the-default-query-suites)."
-* When analysis is complete, all relevant results are published to the pull request at once. If at least one alert in your pull request has an {% data variables.product.prodname_copilot_autofix_short %} suggestion, you should assume that the LLM has finished identifying potential fixes for your code.
-* On alerts generated from queries that are not supported by {% data variables.product.prodname_copilot_autofix_short %}, you will see a note telling you that the query is not supported. If a suggestion for a supported query fails to generate, you will see a note on the alert prompting you to try pushing another commit or to contact support.
-
-{% endnote %}
+> [!NOTE]
+> * {% data variables.product.prodname_copilot_autofix_short %} supports a subset of {% data variables.product.prodname_codeql %} queries. For information about the availability of {% data variables.product.prodname_copilot_autofix_short %}, see the query tables linked from "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites#query-lists-for-the-default-query-suites)."
+> * When analysis is complete, all relevant results are published to the pull request at once. If at least one alert in your pull request has an {% data variables.product.prodname_copilot_autofix_short %} suggestion, you should assume that the LLM has finished identifying potential fixes for your code.
+> * On alerts generated from queries that are not supported by {% data variables.product.prodname_copilot_autofix_short %}, you will see a note telling you that the query is not supported. If a suggestion for a supported query fails to generate, you will see a note on the alert prompting you to try pushing another commit or to contact support.
 
 Usually, when you suggest changes to a pull request, your comment contains changes for a single file that is changed in the pull request. The following screenshot shows an {% data variables.product.prodname_copilot_autofix_short %} comment that suggests changes to the `index.js` file where the alert is displayed. Since the potential fix requires a new dependency on `escape-html`, the comment also suggests adding this dependency to the `package.json` file, even though the original pull request makes no changes to this file.
 
diff --git a/content/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page.md b/content/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page.md
index d9df3930f5..a0e2052b18 100644
--- a/content/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page.md
+++ b/content/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page.md
@@ -28,11 +28,8 @@ Using the {% data variables.code-scanning.tool_status_page %}, you can see how w
 
 You can also see the rules your code was checked against by each configuration of a {% data variables.product.prodname_code_scanning %} tool and download a summary of the results.
 
-{% note %}
-
-**Note:** The {% data variables.code-scanning.tool_status_page %} shows how tools are working at the repository level, not the organization level. The tool status is only shown for the default branch of the repository for which that tool is configured.
-
-{% endnote %}
+> [!NOTE]
+> The {% data variables.code-scanning.tool_status_page %} shows how tools are working at the repository level, not the organization level. The tool status is only shown for the default branch of the repository for which that tool is configured.
 
 ## Viewing the {% data variables.code-scanning.tool_status_page %} for a repository
 
@@ -100,11 +97,8 @@ You can remove stale, duplicate, or unwanted configurations for the default bran
 
 To remove a configuration, select the configuration you want to delete. Then click **{% octicon "kebab-horizontal" aria-label="Configuration menu" %}** on the top right of the page, and select **{% octicon "trash" aria-hidden="true" %} Delete configuration**. Once you have read the warning about alerts, to confirm the deletion, click the **Delete** button.
 
-{% note %}
-
-**Note:** You can only use the {% data variables.code-scanning.tool_status_page %} to remove configurations for the default branch of a repository. For information about removing configurations from non-default branches, see "[AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts#removing-stale-configurations-and-alerts-from-a-branch)."
-
-{% endnote %}
+> [!NOTE]
+> You can only use the {% data variables.code-scanning.tool_status_page %} to remove configurations for the default branch of a repository. For information about removing configurations from non-default branches, see "[AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts#removing-stale-configurations-and-alerts-from-a-branch)."
 
 ## Debugging using the {% data variables.code-scanning.tool_status_page %}
 
@@ -116,10 +110,7 @@ For integrated tools such as {% data variables.product.prodname_codeql %}, you c
 * If the language has a low scanned percentage, you may wish to investigate diagnostic output produced by {% data variables.product.prodname_codeql %} for that language: for more information see "[AUTOTITLE](/code-security/code-scanning/troubleshooting-code-scanning/codeql-scanned-fewer-lines-than-expected)."
 * If the language has a scanned percentage of zero, you may have source code in your repository written in languages supported by {% data variables.product.prodname_codeql %} but not currently being analyzed with {% data variables.product.prodname_codeql %}. In this case, you may wish to update your setup to start analyzing these additional languages. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning#changing-the-languages-that-are-analyzed)."
 
-{% note %}
-
-**Note:** If you have set up {% data variables.product.prodname_codeql %} using advanced setup and then set up default setup on the same repository, the {% data variables.code-scanning.tool_status_page %} will only show default setup.
-
-{% endnote %}
+> [!NOTE]
+> If you have set up {% data variables.product.prodname_codeql %} using advanced setup and then set up default setup on the same repository, the {% data variables.code-scanning.tool_status_page %} will only show default setup.
 
 For more information, see "[AUTOTITLE](/code-security/code-scanning/troubleshooting-code-scanning)" and "[AUTOTITLE](/code-security/code-scanning/troubleshooting-sarif-uploads)."
diff --git a/content/code-security/code-scanning/managing-your-code-scanning-configuration/configuring-larger-runners-for-default-setup.md b/content/code-security/code-scanning/managing-your-code-scanning-configuration/configuring-larger-runners-for-default-setup.md
index e2aff3c30c..24e2122989 100644
--- a/content/code-security/code-scanning/managing-your-code-scanning-configuration/configuring-larger-runners-for-default-setup.md
+++ b/content/code-security/code-scanning/managing-your-code-scanning-configuration/configuring-larger-runners-for-default-setup.md
@@ -22,13 +22,10 @@ Consider configuring {% data variables.actions.hosted_runners %} for default set
 * Your scans with standard {% data variables.product.prodname_dotcom %}-hosted runners are returning memory or disk errors.
 * You want to customize aspects of your {% data variables.product.prodname_code_scanning %} runner like the runner size, runner image, and job concurrency without using self-hosted runners.
 
-{% warning %}
-
-**Warning:** Currently, Swift analysis is not available on {% data variables.actions.hosted_runners %} for default setup. Additionally, if your repository has access to a runner with the `code-scanning` label, such as a {% data variables.actions.hosted_runner %} provisioned for default setup, default setup workflows will _only_ use runners labeled `code-scanning`. If you would like to configure default setup on {% data variables.actions.hosted_runners %} _and_ analyze Swift, you have two options:
-  * Provision a self-hosted macOS runner with the `code-scanning` label in addition to your {% data variables.actions.hosted_runner %}. For more information, see {% ifversion ghec %}"[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance)."{% else %}"[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."{% endif %}
-  * Ensure any repositories containing Swift _do not_ have access to runners with the label `code-scanning`. Default setup workflows for that repository will only use standard runners.
-
-{% endwarning %}
+> [!WARNING]
+> Currently, Swift analysis is not available on {% data variables.actions.hosted_runners %} for default setup. Additionally, if your repository has access to a runner with the `code-scanning` label, such as a {% data variables.actions.hosted_runner %} provisioned for default setup, default setup workflows will _only_ use runners labeled `code-scanning`. If you would like to configure default setup on {% data variables.actions.hosted_runners %} _and_ analyze Swift, you have two options:
+> * Provision a self-hosted macOS runner with the `code-scanning` label in addition to your {% data variables.actions.hosted_runner %}. For more information, see {% ifversion ghec %}"[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance)."{% else %}"[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."{% endif %}
+> * Ensure any repositories containing Swift _do not_ have access to runners with the label `code-scanning`. Default setup workflows for that repository will only use standard runners.
 
 {% ifversion ghec %}
 
diff --git a/content/code-security/code-scanning/managing-your-code-scanning-configuration/set-code-scanning-merge-protection.md b/content/code-security/code-scanning/managing-your-code-scanning-configuration/set-code-scanning-merge-protection.md
index 9a329863c5..bc9a11df53 100644
--- a/content/code-security/code-scanning/managing-your-code-scanning-configuration/set-code-scanning-merge-protection.md
+++ b/content/code-security/code-scanning/managing-your-code-scanning-configuration/set-code-scanning-merge-protection.md
@@ -14,15 +14,10 @@ topics:
 
 ## About using rulesets for {% data variables.product.prodname_code_scanning %} merge protection
 
-{% note %}
-
-**Notes:**
-
-* This feature is currently in {% data variables.release-phases.public_preview %} and subject to change.
-* Merge protection with rulesets is not related to status checks. For more information about status checks, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
-* Merge protection with rulesets will not apply to merge queue groups or {% data variables.product.prodname_dependabot %} pull requests analyzed by default setup.
-
-{% endnote %}
+> [!NOTE]
+> * This feature is currently in {% data variables.release-phases.public_preview %} and subject to change.
+> * Merge protection with rulesets is not related to status checks. For more information about status checks, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
+> * Merge protection with rulesets will not apply to merge queue groups or {% data variables.product.prodname_dependabot %} pull requests analyzed by default setup.
 
 You can use rulesets to prevent pull requests from being merged when one of the following conditions is met:
 
diff --git a/content/code-security/code-scanning/managing-your-code-scanning-configuration/viewing-code-scanning-logs.md b/content/code-security/code-scanning/managing-your-code-scanning-configuration/viewing-code-scanning-logs.md
index 687fab820a..58d431f731 100644
--- a/content/code-security/code-scanning/managing-your-code-scanning-configuration/viewing-code-scanning-logs.md
+++ b/content/code-security/code-scanning/managing-your-code-scanning-configuration/viewing-code-scanning-logs.md
@@ -58,11 +58,8 @@ After configuring {% data variables.product.prodname_code_scanning %} for your r
 
 1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow.
 
-   {% note %}
-
-   **Note:** If you are looking for the {% data variables.product.prodname_codeql %} workflow run triggered by enabling default setup, the text of the entry is "{% data variables.product.prodname_codeql %}."
-
-   {% endnote %}
+   > [!NOTE]
+   > If you are looking for the {% data variables.product.prodname_codeql %} workflow run triggered by enabling default setup, the text of the entry is "{% data variables.product.prodname_codeql %}."
 
 1. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
 
diff --git a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md
index 2a59ef1fa5..26085d6c3a 100644
--- a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md
+++ b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md
@@ -47,17 +47,14 @@ You can analyze a database by running the following command:
 codeql database analyze <database> --format=<format> --output=<output> <query-specifiers>...
 ```
 
-{% note %}
-
-**Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results.
-
-```shell
-codeql database analyze <database> --format=<format> \
-    --sarif-category=<language-specifier> --output=<output> \
-    <packs,queries>
-```
-
-{% endnote %}
+> [!NOTE]
+> If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results.
+>
+> ```shell
+> codeql database analyze <database> --format=<format> \
+>     --sarif-category=<language-specifier> --output=<output> \
+>     <packs,queries>
+> ```
 
 You must specify `<database>`, `--format`, and `--output`. You can specify additional options depending on what analysis you want to do.
 
@@ -168,17 +165,8 @@ You can run all the queries located in a directory by providing the directory
 path, rather than listing all the individual query files. Paths are searched
 recursively, so any queries contained in subfolders will also be executed.
 
-{% note %}
-
-**Important**
-
-You should avoid specifying the root of a core {% data variables.product.prodname_codeql %} query pack when executing `database analyze`
-as it might contain some special queries that aren’t designed to be used with
-the command. Rather, run the query pack to include the
-pack’s default queries in the analysis, or run one of the
-code scanning query suites.
-
-{% endnote %}
+> [!IMPORTANT]
+> You should avoid specifying the root of a core {% data variables.product.prodname_codeql %} query pack when executing `database analyze` as it might contain some special queries that aren’t designed to be used with the command. Rather, run the query pack to include the pack’s default queries in the analysis, or run one of the code scanning query suites.
 
 For example, to execute all Python queries contained in the `Functions` directory in the
 `codeql/python-queries` query pack you would run:
diff --git a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md
index e04a64042e..94e8d1d809 100644
--- a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md
+++ b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md
@@ -58,13 +58,10 @@ Before you can use a {% data variables.product.prodname_codeql %} query pack to
 | <code><span style="white-space: nowrap;"><scope/name@version:path></span></code> | {% octicon "check" aria-label="Required" %} | Specify the scope and name of one or more {% data variables.product.prodname_codeql %} query packs to download using a comma-separated list. Optionally, include the version to download and unzip. By default the latest version of this pack is downloaded. Optionally, include a path to a query, directory, or query suite to run. If no path is included, then run the default queries of this pack. |
 | <code><span style="white-space: nowrap;">--github-auth-stdin</span></code> | {% octicon "x" aria-label="Optional" %}  | Pass the CLI the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} created for authentication with {% data variables.product.company_short %}'s REST API from your secret store via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token.
 
-{% note %}
-
-**Note:** If you specify a particular version of a query pack to use, be aware that the version you specify may eventually become too old for the latest version of {% data variables.product.prodname_codeql %} to make efficient use of. To ensure optimal performance, if you need to specify exact query pack versions, you should reevaluate which versions you pin to whenever you upgrade the {% data variables.product.prodname_codeql_cli %} you're using.
-
-For more information about pack compatibility, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs#about-codeql-pack-compatibility)."
-
-{% endnote %}
+> [!NOTE]
+> If you specify a particular version of a query pack to use, be aware that the version you specify may eventually become too old for the latest version of {% data variables.product.prodname_codeql %} to make efficient use of. To ensure optimal performance, if you need to specify exact query pack versions, you should reevaluate which versions you pin to whenever you upgrade the {% data variables.product.prodname_codeql_cli %} you're using.
+>
+> For more information about pack compatibility, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs#about-codeql-pack-compatibility)."
 
 ### Basic example of downloading and using query packs
 
@@ -148,21 +145,14 @@ pack.
 
 * `suites/my-suite.qls` - All queries in the `suites/my-suite.qls` file relative to the current working directory.
 
-{% note %}
-
-**Tip**
-
-The default query suite of the standard {% data variables.product.prodname_codeql %} query packs are `codeql-suites/<lang>-code-scanning.qls`. Several other useful query suites can also be found in the `codeql-suites` directory of each pack. For example, the `codeql/cpp-queries` pack contains the following query suites:
-
-* `cpp-code-scanning.qls` - Standard Code Scanning queries for C++. The default query suite for this pack.
-
-* `cpp-security-extended.qls` - Queries from the default  `cpp-code-scanning.qls` suite for C++, plus lower severity and precision queries.
-
-* `cpp-security-and-quality.qls` - Queries from `cpp-security-extended.qls`, plus maintainability and reliability queries.
-
-You can see the sources for these query suites in the [{% data variables.product.prodname_codeql %} repository](https://github.com/github/codeql/tree/main/cpp/ql/src/codeql-suites). Query suites for other languages are similar.
-
-{% endnote %}
+> [!TIP]
+> The default query suite of the standard {% data variables.product.prodname_codeql %} query packs are `codeql-suites/<lang>-code-scanning.qls`. Several other useful query suites can also be found in the `codeql-suites` directory of each pack. For example, the `codeql/cpp-queries` pack contains the following query suites:
+>
+> * `cpp-code-scanning.qls` - Standard Code Scanning queries for C++. The default query suite for this pack.
+> * `cpp-security-extended.qls` - Queries from the default  `cpp-code-scanning.qls` suite for C++, plus lower severity and precision queries.
+> * `cpp-security-and-quality.qls` - Queries from `cpp-security-extended.qls`, plus maintainability and reliability queries.
+>
+> You can see the sources for these query suites in the [{% data variables.product.prodname_codeql %} repository](https://github.com/github/codeql/tree/main/cpp/ql/src/codeql-suites). Query suites for other languages are similar.
 
 {% ifversion codeql-model-packs %}
 
diff --git a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis.md b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis.md
index 210a964aeb..9bc43e0f01 100644
--- a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis.md
+++ b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis.md
@@ -149,11 +149,8 @@ When the database is successfully created, you’ll find a new directory at the
 
 The {% data variables.product.prodname_codeql_cli %} includes extractors to create databases for non-compiled languages—specifically, JavaScript (and TypeScript), Python, and Ruby. These extractors are automatically invoked when you specify JavaScript, Python, or Ruby as the `--language` option when executing `database create`. When creating databases for these languages you must ensure that all additional dependencies are available.
 
-{% note %}
-
-**Note:** When you run `database create` for JavaScript, TypeScript, Python, and Ruby, you should not specify a `--command` option. Otherwise this overrides the normal extractor invocation, which will create an empty database. If you create databases for multiple languages and one of them is a compiled language, use the `--no-run-unnecessary-builds` option to skip the command for the languages that don’t need to be compiled.
-
-{% endnote %}
+> [!NOTE]
+> When you run `database create` for JavaScript, TypeScript, Python, and Ruby, you should not specify a `--command` option. Otherwise this overrides the normal extractor invocation, which will create an empty database. If you create databases for multiple languages and one of them is a compiled language, use the `--no-run-unnecessary-builds` option to skip the command for the languages that don’t need to be compiled.
 
 ### JavaScript and TypeScript
 
@@ -216,24 +213,16 @@ codeql database create --language=cpp <output-folder>/cpp-database
 
 If a codebase uses a standard build system, relying on an autobuilder is often the simplest way to create a database. For sources that require non-standard build steps, you may need to explicitly define each step in the command line.
 
-{% note %}
-
-**Notes:**
-
-* If you are building a Go database, install the Go toolchain (version 1.11 or later) and, if there are dependencies, the appropriate dependency manager (such as [dep](https://golang.github.io/dep/)).
-* The Go autobuilder attempts to automatically detect code written in Go in a repository, and only runs build scripts in an attempt to fetch dependencies. To force {% data variables.product.prodname_codeql %} to limit extraction to the files compiled by your build script, set the environment variable `CODEQL_EXTRACTOR_GO_BUILD_TRACING=on` or use the `--command` option to specify a build command.
-
-{% endnote %}
+> [!NOTE]
+> * If you are building a Go database, install the Go toolchain (version 1.11 or later) and, if there are dependencies, the appropriate dependency manager (such as [dep](https://golang.github.io/dep/)).
+> * The Go autobuilder attempts to automatically detect code written in Go in a repository, and only runs build scripts in an attempt to fetch dependencies. To force {% data variables.product.prodname_codeql %} to limit extraction to the files compiled by your build script, set the environment variable `CODEQL_EXTRACTOR_GO_BUILD_TRACING=on` or use the `--command` option to specify a build command.
 
 ### Specifying build commands
 
 The following examples are designed to give you an idea of some of the build commands that you can specify for compiled languages.
 
-{% note %}
-
-**Note:** The `--command` option accepts a single argument—if you need to use more than one command, specify `--command` multiple times. If you need to pass subcommands and options, the whole argument needs to be quoted to be interpreted correctly.
-
-{% endnote %}
+> [!NOTE]
+> The `--command` option accepts a single argument—if you need to use more than one command, specify `--command` multiple times. If you need to pass subcommands and options, the whole argument needs to be quoted to be interpreted correctly.
 
 * C/C++ project built using `make`:
 
@@ -362,11 +351,8 @@ You must specify:
 
 You may specify other options for the `codeql database init` command as normal.
 
-{% note %}
-
-**Note:** If the build runs on Windows, you must set either `--trace-process-level <number>` or `--trace-process-name <parent process name>` so that the option points to a parent CI process that will observe all build steps for the code being analyzed.
-
-{% endnote %}
+> [!NOTE]
+> If the build runs on Windows, you must set either `--trace-process-level <number>` or `--trace-process-name <parent process name>` so that the option points to a parent CI process that will observe all build steps for the code being analyzed.
 
 The `codeql database init` command will output a message:
 
@@ -387,11 +373,8 @@ Once you have created a {% data variables.product.prodname_codeql %} database us
 
 ### Example of creating a {% data variables.product.prodname_codeql %} database using indirect build tracing
 
-{% note %}
-
-**Note:** If you use Azure DevOps pipelines, the simplest way to create a {% data variables.product.prodname_codeql %} database is to use {% data variables.product.prodname_ghas_azdo %}. For documentation, see [Configure {% data variables.product.prodname_ghas_azdo %}](https://learn.microsoft.com/en-us/azure/devops/repos/security/configure-github-advanced-security-features) in Microsoft Learn.
-
-{% endnote %}
+> [!NOTE]
+> If you use Azure DevOps pipelines, the simplest way to create a {% data variables.product.prodname_codeql %} database is to use {% data variables.product.prodname_ghas_azdo %}. For documentation, see [Configure {% data variables.product.prodname_ghas_azdo %}](https://learn.microsoft.com/en-us/azure/devops/repos/security/configure-github-advanced-security-features) in Microsoft Learn.
 
 The following example shows how you could use indirect build tracing in an Azure DevOps pipeline to create a {% data variables.product.prodname_codeql %} database:
 
diff --git a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli.md b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli.md
index 2d3bb67f51..82585e7fee 100644
--- a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli.md
+++ b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli.md
@@ -35,11 +35,8 @@ If you are setting up the {% data variables.product.prodname_codeql_cli %} in yo
 If you are using macOS on Apple Silicon (for example, Apple M1), ensure that the [Xcode command-line developer
 tools](https://developer.apple.com/downloads/index.action) and [Rosetta 2](https://support.apple.com/en-us/HT211861) are installed.
 
-{% note %}
-
-**Note:** The {% data variables.product.prodname_codeql_cli %} is currently not compatible with non-glibc Linux distributions such as (muslc-based) Alpine Linux.
-
-{% endnote %}
+> [!NOTE]
+> The {% data variables.product.prodname_codeql_cli %} is currently not compatible with non-glibc Linux distributions such as (muslc-based) Alpine Linux.
 
 ### 1. Download the {% data variables.product.prodname_codeql_cli %} tar archive
 
@@ -53,12 +50,8 @@ Extract the {% data variables.product.prodname_codeql_cli %} tar archive to a di
 
 {% data reusables.codeql-cli.launch-codeql %}
 
-{% note %}
-
-**Note:** If you add `codeql` to your `PATH`, it can be accessed by {% data variables.product.prodname_codeql %} for {% data variables.product.prodname_vscode %} to compile and run queries.
- For more information about configuring {% data variables.product.prodname_vscode_shortname %} to access the {% data variables.product.prodname_codeql_cli %}, see "[AUTOTITLE](/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/configuring-access-to-the-codeql-cli)."
-
- {% endnote %}
+> [!NOTE]
+> If you add `codeql` to your `PATH`, it can be accessed by {% data variables.product.prodname_codeql %} for {% data variables.product.prodname_vscode %} to compile and run queries. For more information about configuring {% data variables.product.prodname_vscode_shortname %} to access the {% data variables.product.prodname_codeql_cli %}, see "[AUTOTITLE](/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/configuring-access-to-the-codeql-cli)."
 
 ## Testing the {% data variables.product.prodname_codeql_cli %} configuration
 
diff --git a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/uploading-codeql-analysis-results-to-github.md b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/uploading-codeql-analysis-results-to-github.md
index e469b5636f..2fc0ad7400 100644
--- a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/uploading-codeql-analysis-results-to-github.md
+++ b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/uploading-codeql-analysis-results-to-github.md
@@ -76,11 +76,8 @@ codeql github upload-results \
 
 For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/github-upload-results)."
 
-{% note %}
-
-**Note:** If you analyzed more than one {% data variables.product.prodname_codeql %} database for a single commit, you must have specified a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results. For more information, see "[AUTOTITLE](/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries#running-codeql-database-analyze)."
-
-{% endnote %}
+> [!NOTE]
+> If you analyzed more than one {% data variables.product.prodname_codeql %} database for a single commit, you must have specified a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results. For more information, see "[AUTOTITLE](/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries#running-codeql-database-analyze)."
 
 ### Basic example of uploading results to {% data variables.product.product_name %}
 
diff --git a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/advanced-setup-of-the-codeql-cli.md b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/advanced-setup-of-the-codeql-cli.md
index 8f7815dd9e..0a5341b0ec 100644
--- a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/advanced-setup-of-the-codeql-cli.md
+++ b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/advanced-setup-of-the-codeql-cli.md
@@ -57,14 +57,11 @@ packs. Along with the queries themselves, {% data variables.product.prodname_cod
 that tells the {% data variables.product.prodname_codeql_cli %} how to process the query files. For more information,
 see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs)."
 
-{% note %}
-
-**Note:** There are different versions of the {% data variables.product.prodname_codeql %} queries available for different users. Check out the correct version for your use case:
-
-* For the queries that are intended to be used with the latest {% data variables.product.prodname_codeql_cli %} release, check out the branch tagged `codeql-cli/latest`. You should use this branch for databases you’ve built using the {% data variables.product.prodname_codeql_cli %} or recently downloaded from {% data variables.product.github %}.
-* For the most up to date {% data variables.product.prodname_codeql %} queries, check out the `main` branch. This branch represents the very latest version of {% data variables.product.prodname_codeql %}’s analysis.
-
-{% endnote %}
+> [!NOTE]
+> There are different versions of the {% data variables.product.prodname_codeql %} queries available for different users. Check out the correct version for your use case:
+>
+> * For the queries that are intended to be used with the latest {% data variables.product.prodname_codeql_cli %} release, check out the branch tagged `codeql-cli/latest`. You should use this branch for databases you’ve built using the {% data variables.product.prodname_codeql_cli %} or recently downloaded from {% data variables.product.github %}.
+> * For the most up to date {% data variables.product.prodname_codeql %} queries, check out the `main` branch. This branch represents the very latest version of {% data variables.product.prodname_codeql %}’s analysis.
 
 ### 4. Extract the {% data variables.product.prodname_codeql_cli %} tar archive
 
diff --git a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs.md b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs.md
index 15efaa35d4..6e0c4512ad 100644
--- a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs.md
+++ b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs.md
@@ -105,11 +105,8 @@ Once you've created a model pack, you can publish it in the same way as other {%
 
 ## Adding and installing dependencies on a {% data variables.product.prodname_codeql %} pack
 
-{% note %}
-
-**Note:** This is only supported for {% data variables.product.prodname_codeql %} query and library packs.
-
-{% endnote %}
+> [!NOTE]
+> This is only supported for {% data variables.product.prodname_codeql %} query and library packs.
 
 You can add dependencies on {% data variables.product.prodname_codeql %} packs using the command `codeql pack add`. You must specify the scope, name, and (optionally) a compatible version range.
 
@@ -129,15 +126,9 @@ codeql pack install
 
 This command downloads all dependencies to the shared cache on the local disk.
 
-{% note %}
-
-**Notes:**
-
-* Running the `codeql pack add` and `codeql pack install` commands will generate or update the `codeql-pack.lock.yml` file. This file should be checked-in to version control. The `codeql-pack.lock.yml` file contains the precise version numbers used by the pack. For more information, see "[About codeql-pack.lock.yml files](/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs##about-codeql-packlockyml-files)."
-
-* By default `codeql pack install` will install dependencies from the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_dotcom_the_website %}. You can install dependencies from a {% data variables.product.prodname_ghe_server %} {% data variables.product.prodname_container_registry %} by creating a `qlconfig.yml` file. For more information, see "[AUTOTITLE](/enterprise-server@latest/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs)" in the {% data variables.product.prodname_ghe_server %} documentation.
-
-{% endnote %}
+> [!NOTE]
+> * Running the `codeql pack add` and `codeql pack install` commands will generate or update the `codeql-pack.lock.yml` file. This file should be checked-in to version control. The `codeql-pack.lock.yml` file contains the precise version numbers used by the pack. For more information, see "[About codeql-pack.lock.yml files](/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs##about-codeql-packlockyml-files)."
+> * By default `codeql pack install` will install dependencies from the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_dotcom_the_website %}. You can install dependencies from a {% data variables.product.prodname_ghe_server %} {% data variables.product.prodname_container_registry %} by creating a `qlconfig.yml` file. For more information, see "[AUTOTITLE](/enterprise-server@latest/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs)" in the {% data variables.product.prodname_ghe_server %} documentation.
 
 ## Customizing a downloaded {% data variables.product.prodname_codeql %} pack
 
diff --git a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-codeql-query-suites.md b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-codeql-query-suites.md
index bd08c63abd..ce014c9c4f 100644
--- a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-codeql-query-suites.md
+++ b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-codeql-query-suites.md
@@ -29,11 +29,8 @@ mapping with (usually) a single key. The instructions are executed in the order
 they appear in the query suite definition. After all the instructions in the
 suite definition have been executed, the result is a set of selected queries.
 
-{% note %}
-
-**Note:** Any custom queries that you want to add to a query suite must be in a "[{% data variables.product.prodname_codeql %} pack](/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs)" and contain the correct query metadata. For more information, see "[Using custom queries with the {% data variables.product.prodname_codeql_cli %}](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/using-custom-queries-with-the-codeql-cli)."
-
-{% endnote %}
+> [!NOTE]
+> Any custom queries that you want to add to a query suite must be in a "[{% data variables.product.prodname_codeql %} pack](/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs)" and contain the correct query metadata. For more information, see "[Using custom queries with the {% data variables.product.prodname_codeql_cli %}](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/using-custom-queries-with-the-codeql-cli)."
 
 ## Locating queries to add to a query suite
 
@@ -85,11 +82,8 @@ named {% data variables.product.prodname_codeql %} pack:
   The `version` field is optional and specifies a range of compatible versions of this {% data variables.product.prodname_codeql %} pack.
   If you don’t specify a version, then the most recent version of the pack is used.
 
-{% note %}
-
-**Note:** When pathnames appear in query suite definitions, they must always be given with a forward slash, `/`, as a directory separator. This ensures that query suite definitions work on all operating systems.
-
-{% endnote %}
+> [!NOTE]
+> When pathnames appear in query suite definitions, they must always be given with a forward slash, `/`, as a directory separator. This ensures that query suite definitions work on all operating systems.
 
 You must add at least one `query`, `queries`, or `qlpack` instruction to
 your suite definition, otherwise no queries will be selected. If the suite
@@ -244,12 +238,8 @@ use:
     - very-high
 ```
 
-<!--Changed this to a note to fit with style guide -->
-{% note %}
-
-**Note:** You can use the `codeql resolve queries /path/to/suite.qls` command to see which queries are selected by a query suite definition. For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/resolve-queries)."
-
-{% endnote %}
+> [!NOTE]
+> You can use the `codeql resolve queries /path/to/suite.qls` command to see which queries are selected by a query suite definition. For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/resolve-queries)."
 
 ## Reusing existing query suite definitions
 
diff --git a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md
index 603f6c307b..f6af538ec9 100644
--- a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md
+++ b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md
@@ -115,11 +115,8 @@ codeql pack publish
 
 The published package will be displayed in the packages section of {% data variables.product.prodname_dotcom %} organization specified by the scope in the `qlpack.yml` file.
 
-{% note %}
-
-**Note:** If you're publishing model packs to the {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_container_registry %} in order to extend coverage to all repositories in an organization as part of a default setup configuration, then you need to ensure that repositories running code scanning can access those model packs. For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup)" and "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
-
-{% endnote %}
+> [!NOTE]
+> If you're publishing model packs to the {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_container_registry %} in order to extend coverage to all repositories in an organization as part of a default setup configuration, then you need to ensure that repositories running code scanning can access those model packs. For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup)" and "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
 
 ## Running `codeql pack download <scope>/<pack>`
 
@@ -164,11 +161,8 @@ The `analyze` command will run the default suite of any specified {% data variab
 codeql <database> analyze <scope>/<pack> <scope>/<other-pack>
 ```
 
-{% note %}
-
-**Note:** The `codeql pack download` command stores the pack it downloads in an internal location that is not intended for local modification.  Unexpected (and hard to troubleshoot) behavior may result if the pack is modified after downloading. For more information about customizing packs, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs)."
-
-{% endnote %}
+> [!NOTE]
+> The `codeql pack download` command stores the pack it downloads in an internal location that is not intended for local modification.  Unexpected (and hard to troubleshoot) behavior may result if the pack is modified after downloading. For more information about customizing packs, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs)."
 
 ## About {% data variables.product.prodname_codeql %} pack compatibility
 
diff --git a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/specifying-command-options-in-a-codeql-configuration-file.md b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/specifying-command-options-in-a-codeql-configuration-file.md
index 31242212db..4621e36deb 100644
--- a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/specifying-command-options-in-a-codeql-configuration-file.md
+++ b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/specifying-command-options-in-a-codeql-configuration-file.md
@@ -41,14 +41,10 @@ To apply the same options to more than one command you can:
 * Omit the `<subcommand>`, which will specify the option for every `<subcommand>` to which it’s relevant.
 * Omit both `<command>` and `<subcommand>`, which will globally specify the option for every `<command>` and `<subcommand>` to which it’s relevant.
 
-{% note %}
-
-**Notes:**
-* `config` files only accept spaces between option flags and values—{% data variables.product.prodname_codeql %} will throw an error if you use `=` to specify an option value.
-* If you specify an option in the command line, this overrides the `config` value defined for that option.
-* If you want to specify more than one option for a `<command>`, `<subcommand>` or globally, use one line per option.
-
-{% endnote %}
+> [!NOTE]
+> * `config` files only accept spaces between option flags and values—{% data variables.product.prodname_codeql %} will throw an error if you use `=` to specify an option value.
+> * If you specify an option in the command line, this overrides the `config` value defined for that option.
+> * If you want to specify more than one option for a `<command>`, `<subcommand>` or globally, use one line per option.
 
 ### Examples
 
diff --git a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/testing-custom-queries.md b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/testing-custom-queries.md
index 7fdf7e4052..df278e4784 100644
--- a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/testing-custom-queries.md
+++ b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/testing-custom-queries.md
@@ -75,17 +75,12 @@ the example code, by creating a file with the extension `.expected`. Alternative
 
 For an example showing how to create and test a query, see the [example](#example) below.
 
-{% note %}
-
-**Note:** Your `.ql`, `.qlref`, and `.expected` files must have consistent names:
-
-* If you want to directly specify the `.ql` file itself in the test command, it must have the same base name as the corresponding `.expected` file. For example, if the query is `MyJavaQuery.ql`, the expected results file must be `MyJavaQuery.expected`.
-
-* If you want to specify a `.qlref` file in the command, it must have the same base name as the corresponding `.expected` file, but the query itself may have a different name.
-
-* The names of the example code files don’t have to be consistent with the other test files. All example code files found next to the `.qlref` (or `.ql`) file and in any subdirectories will be used to create a test database. Therefore, for simplicity, we recommend you don’t save test files in directories that are ancestors of each other.
-
-{% endnote %}
+> [!NOTE]
+> Your `.ql`, `.qlref`, and `.expected` files must have consistent names:
+>
+> * If you want to directly specify the `.ql` file itself in the test command, it must have the same base name as the corresponding `.expected` file. For example, if the query is `MyJavaQuery.ql`, the expected results file must be `MyJavaQuery.expected`.
+> * If you want to specify a `.qlref` file in the command, it must have the same base name as the corresponding `.expected` file, but the query itself may have a different name.
+> * The names of the example code files don’t have to be consistent with the other test files. All example code files found next to the `.qlref` (or `.ql`) file and in any subdirectories will be used to create a test database. Therefore, for simplicity, we recommend you don’t save test files in directories that are ancestors of each other.
 
 ## Running `codeql test run`
 
diff --git a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/using-custom-queries-with-the-codeql-cli.md b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/using-custom-queries-with-the-codeql-cli.md
index 19eb92c9be..8f47129b6a 100644
--- a/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/using-custom-queries-with-the-codeql-cli.md
+++ b/content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/using-custom-queries-with-the-codeql-cli.md
@@ -43,11 +43,8 @@ When running queries with the `database analyze` command, you must include the f
 
 For more information about these metadata properties, see "[Metadata for {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/metadata-for-codeql-queries/#metadata-for-codeql-queries)" and the [Query metadata style guide](https://github.com/github/codeql/blob/main/docs/query-metadata-style-guide.md).
 
-{% note %}
-
-**Note:** Metadata requirements may differ if you want to use your query with other applications. For more information, see "[Metadata for {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/metadata-for-codeql-queries/#metadata-for-codeql-queries)."
-
-{% endnote %}
+> [!NOTE]
+> Metadata requirements may differ if you want to use your query with other applications. For more information, see "[Metadata for {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/metadata-for-codeql-queries/#metadata-for-codeql-queries)."
 
 ## Packaging custom QL queries
 
diff --git a/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/managing-codeql-databases.md b/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/managing-codeql-databases.md
index 6ce09671d7..95edce9d63 100644
--- a/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/managing-codeql-databases.md
+++ b/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/managing-codeql-databases.md
@@ -31,11 +31,8 @@ You can check if a repository has any {% data variables.product.prodname_codeql
 
 1. Once you've chosen a database, it will be displayed in the "Databases" view. To see the menu options for interacting with a database, right-click an entry in the list. You can select multiple databases at once.
 
-{% note %}
-
-**Note:** You can also analyze test databases. Test databases (folders with a `.testproj` extension) are generated when you run regression tests on custom queries using the {% data variables.product.prodname_codeql_cli %}. If a query fails a regression test, you may want to import the test database into {% data variables.product.prodname_vscode %} to debug the failure. For more information about running query tests, see "[AUTOTITLE](/code-security/codeql-cli/using-the-codeql-cli/testing-custom-queries)."
-
-{% endnote %}
+> [!NOTE]
+> You can also analyze test databases. Test databases (folders with a `.testproj` extension) are generated when you run regression tests on custom queries using the {% data variables.product.prodname_codeql_cli %}. If a query fails a regression test, you may want to import the test database into {% data variables.product.prodname_vscode %} to debug the failure. For more information about running query tests, see "[AUTOTITLE](/code-security/codeql-cli/using-the-codeql-cli/testing-custom-queries)."
 
 ## Filtering databases and queries by language
 
diff --git a/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/running-codeql-queries-at-scale-with-multi-repository-variant-analysis.md b/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/running-codeql-queries-at-scale-with-multi-repository-variant-analysis.md
index 3ec497c46f..5a79a1ae05 100644
--- a/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/running-codeql-queries-at-scale-with-multi-repository-variant-analysis.md
+++ b/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/running-codeql-queries-at-scale-with-multi-repository-variant-analysis.md
@@ -124,11 +124,8 @@ You can export your results for further analysis or to discuss them with collabo
 
 ## Creating a custom list of repositories
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_codeql %} analysis always requires a {% data variables.product.prodname_codeql %} database to run queries against. When you run variant analysis against a list of repositories, your query will only be executed against the repositories that currently have a {% data variables.product.prodname_codeql %} database available to download.  The best way to make a repository available for variant analysis is to enable {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}. For information about enabling {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#configuring-code-scanning-automatically)."
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_codeql %} analysis always requires a {% data variables.product.prodname_codeql %} database to run queries against. When you run variant analysis against a list of repositories, your query will only be executed against the repositories that currently have a {% data variables.product.prodname_codeql %} database available to download.  The best way to make a repository available for variant analysis is to enable {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}. For information about enabling {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#configuring-code-scanning-automatically)."
 
 1. In the "Variant Analysis Repositories" view, click the "Add list" icon.
 
@@ -161,11 +158,8 @@ You can then insert the `new-repo-list` of repositories into `databases.json`for
 
 ### Using {% data variables.product.github %} code search to add repositories to a custom list
 
-{% note %}
-
-**Note:** This feature uses the legacy code search via the {% data variables.product.github %} code search API. For more information on the syntax to use, see "[AUTOTITLE](/search-github/searching-on-github/searching-code)."
-
-{% endnote %}
+> [!NOTE]
+> This feature uses the legacy code search via the {% data variables.product.github %} code search API. For more information on the syntax to use, see "[AUTOTITLE](/search-github/searching-on-github/searching-code)."
 
 You can use code search directly in the {% data variables.product.prodname_codeql %} extension to add a subset of repositories from {% data variables.product.github %} to a custom list.
 
diff --git a/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/running-codeql-queries.md b/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/running-codeql-queries.md
index f2641ced68..cd4a13e99b 100644
--- a/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/running-codeql-queries.md
+++ b/content/code-security/codeql-for-vs-code/getting-started-with-codeql-for-vs-code/running-codeql-queries.md
@@ -112,11 +112,8 @@ The "Query History" view contains information including the date and time when t
 
 1. Click a query in the "Query History" view to display its results in the "Results" view.
 
-    {% note %}
-
-    **Note:** Depending on the query, you can also choose different views such as CSV, [AUTOTITLE](/code-security/codeql-cli/codeql-cli-reference/sarif-output), or [DIL format](https://codeql.github.com/docs/codeql-overview/codeql-glossary/#dil). For example, to view the DIL format, right-click a result and select **View DIL**. The available output views are determined by the format and the metadata of the query. For more information, see "[{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/#codeql-queries)."
-
-    {% endnote %}
+    > [!NOTE]
+    > Depending on the query, you can also choose different views such as CSV, [AUTOTITLE](/code-security/codeql-cli/codeql-cli-reference/sarif-output), or [DIL format](https://codeql.github.com/docs/codeql-overview/codeql-glossary/#dil). For example, to view the DIL format, right-click a result and select **View DIL**. The available output views are determined by the format and the metadata of the query. For more information, see "[{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/#codeql-queries)."
 
 1. Use the dropdown menu in the "Results" view to choose which results to display, and in what form to display them, such as a formatted alert message or a table of raw results.
 
@@ -126,12 +123,8 @@ If a result links to a source code element, you can click it to display it in th
 
 To use standard code navigation features in the source code, you can right-click an element and use the commands **Go to Definition** or **Go to References**. This runs a {% data variables.product.prodname_codeql %}  query over the active file, which may take a few seconds. This query needs to run once for every file, so any additional references from the same file will be fast.
 
-{% note %}
-
-**Note:** If you're using an older database, code navigation commands such as **Go to Definition** and **Go to References** may not work.
-To use code navigation, try unzipping the database and running `codeql database cleanup <database>` on the unzipped database using the {% data variables.product.prodname_codeql_cli %}. Then, re-add the database to {% data variables.product.prodname_vscode %}. For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/database-cleanup)."
-
-{% endnote %}
+> [!NOTE]
+> If you're using an older database, code navigation commands such as **Go to Definition** and **Go to References** may not work. To use code navigation, try unzipping the database and running `codeql database cleanup <database>` on the unzipped database using the {% data variables.product.prodname_codeql_cli %}. Then, re-add the database to {% data variables.product.prodname_vscode %}. For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/database-cleanup)."
 
 ### Comparing query results
 
diff --git a/content/code-security/codeql-for-vs-code/troubleshooting-codeql-for-vs-code/accessing-logs.md b/content/code-security/codeql-for-vs-code/troubleshooting-codeql-for-vs-code/accessing-logs.md
index 650398b075..a7e3b23778 100644
--- a/content/code-security/codeql-for-vs-code/troubleshooting-codeql-for-vs-code/accessing-logs.md
+++ b/content/code-security/codeql-for-vs-code/troubleshooting-codeql-for-vs-code/accessing-logs.md
@@ -28,11 +28,8 @@ You can access the following logs:
 
 * {% data variables.product.prodname_codeql %} Tests
 
-{% note %}
-
-**Note:** The {% data variables.product.prodname_codeql %} Language Server log contains more advanced debug logs for  {% data variables.product.prodname_codeql %} language maintainers. You should only need these to provide details in a bug report.
-
-{% endnote %}
+> [!NOTE]
+> The {% data variables.product.prodname_codeql %} Language Server log contains more advanced debug logs for  {% data variables.product.prodname_codeql %} language maintainers. You should only need these to provide details in a bug report.
 
 ## Accessing logs
 
diff --git a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/configuring-access-to-the-codeql-cli.md b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/configuring-access-to-the-codeql-cli.md
index ca43157d46..2e98e89aba 100644
--- a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/configuring-access-to-the-codeql-cli.md
+++ b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/configuring-access-to-the-codeql-cli.md
@@ -20,15 +20,9 @@ If you already have the {% data variables.product.prodname_codeql_cli %} install
 
 Otherwise, the extension automatically manages access to the executable of the {% data variables.product.prodname_codeql_cli %} for you. This ensures that the {% data variables.product.prodname_codeql_cli %} is compatible with the {% data variables.product.prodname_codeql %} extension. You can also check for updates with the **{% data variables.product.prodname_codeql %}: Check for CLI Updates** command from the {% data variables.product.prodname_vscode_command_palette_shortname %}.
 
-{% note %}
-
-**Notes:**
-
-* The extension-managed {% data variables.product.prodname_codeql_cli %} is not accessible from the terminal. If you intend to use the CLI outside of the extension (for example to create databases), we recommend that you install your own copy of the {% data variables.product.prodname_codeql_cli %}."
-
-* To override the default behavior and use a specific version of the {% data variables.product.prodname_codeql_cli %}, you can specify the {% data variables.product.prodname_codeql_cli %} **Executable Path** in the extension settings. For more information, see "[AUTOTITLE](/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/customizing-settings)."
-
-{% endnote %}
+> [!NOTE]
+> * The extension-managed {% data variables.product.prodname_codeql_cli %} is not accessible from the terminal. If you intend to use the CLI outside of the extension (for example to create databases), we recommend that you install your own copy of the {% data variables.product.prodname_codeql_cli %}."
+> * To override the default behavior and use a specific version of the {% data variables.product.prodname_codeql_cli %}, you can specify the {% data variables.product.prodname_codeql_cli %} **Executable Path** in the extension settings. For more information, see "[AUTOTITLE](/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/customizing-settings)."
 
 ## Troubleshooting
 
diff --git a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/creating-a-custom-query.md b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/creating-a-custom-query.md
index 1823882d69..ce16f8b483 100644
--- a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/creating-a-custom-query.md
+++ b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/creating-a-custom-query.md
@@ -15,11 +15,8 @@ intro: 'You can work from a template to write your own code to create a custom q
 
 ## About custom queries
 
-{% note %}
-
-**Note:** Creating a custom query is optional, and the [`github/codeql`](https://github.com/github/codeql) repository contains a large number of example queries you can use instead.
-
-{% endnote %}
+> [!NOTE]
+> Creating a custom query is optional, and the [`github/codeql`](https://github.com/github/codeql) repository contains a large number of example queries you can use instead.
 
 You create a new query file from a template for a given language, which imports the standard libraries for analyzing that language. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
 
diff --git a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/exploring-the-structure-of-your-source-code.md b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/exploring-the-structure-of-your-source-code.md
index 464796a078..dd25c8a94f 100644
--- a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/exploring-the-structure-of-your-source-code.md
+++ b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/exploring-the-structure-of-your-source-code.md
@@ -23,11 +23,8 @@ The abstract syntax tree (AST) of a program represents the program's syntactic s
 
 ## Viewing the abstract syntax tree of a source file
 
-{% note %}
-
-**Note:** If you don't have an appropriate query (usually `printAST.ql`) in your workspace, the **{% data variables.product.prodname_codeql %}: View AST** command in the following steps won't work. To fix this, you can update your copy of the [`github/codeql`](https://github.com/github/codeql) repository from the `main` branch. If you do this, query caches may be discarded, so your next query runs may be slower.
-
-{% endnote %}
+> [!NOTE]
+> If you don't have an appropriate query (usually `printAST.ql`) in your workspace, the **{% data variables.product.prodname_codeql %}: View AST** command in the following steps won't work. To fix this, you can update your copy of the [`github/codeql`](https://github.com/github/codeql) repository from the `main` branch. If you do this, query caches may be discarded, so your next query runs may be slower.
 
 1. Open the "Databases" view in the extension, and right-click the database that you want to explore. Click **Add Database Source to Workspace**.
 
diff --git a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/setting-up-a-codeql-workspace.md b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/setting-up-a-codeql-workspace.md
index f7b856a9a5..4698cf181e 100644
--- a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/setting-up-a-codeql-workspace.md
+++ b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/setting-up-a-codeql-workspace.md
@@ -26,11 +26,8 @@ There are several different ways to give the extension access to the standard li
 
 ### Option 1: Using the starter workspace (recommended)
 
-{% note %}
-
-**Note:** The {% data variables.product.prodname_codeql %} repository is included as a submodule in the starter workspace. You should use `git submodule update --remote` regularly to keep the submodules up to date, and ensure that they remain compatible with newer versions of the {% data variables.product.prodname_vscode_shortname %} extension and the {% data variables.product.prodname_codeql_cli %}.
-
-{% endnote %}
+> [!NOTE]
+> The {% data variables.product.prodname_codeql %} repository is included as a submodule in the starter workspace. You should use `git submodule update --remote` regularly to keep the submodules up to date, and ensure that they remain compatible with newer versions of the {% data variables.product.prodname_vscode_shortname %} extension and the {% data variables.product.prodname_codeql_cli %}.
 
 1. Clone the [vscode-codeql-starter repository](https://github.com/github/vscode-codeql-starter/) to your computer. Make sure you include the submodules, either by using `git clone --recursive`, or by using `git submodule update --init --remote` after cloning.
 
@@ -56,10 +53,7 @@ There are several different ways to give the extension access to the standard li
 
 ### Option 3: Open the directory containing the extracted {% data variables.product.prodname_codeql_cli %} archive
 
-{% note %}
-
-**Note:** For this option, you need to set up the  {% data variables.product.prodname_codeql_cli %}. For more information, see "[AUTOTITLE](/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli)."
-
-{% endnote %}
+> [!NOTE]
+> For this option, you need to set up the  {% data variables.product.prodname_codeql_cli %}. For more information, see "[AUTOTITLE](/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli)."
 
 In {% data variables.product.prodname_vscode_shortname %}, open the directory where you extracted the {% data variables.product.prodname_codeql_cli %} .zip archive to create a {% data variables.product.prodname_codeql %} directory (for example `codeql-home`).
diff --git a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/telemetry-in-codeql-for-visual-studio-code.md b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/telemetry-in-codeql-for-visual-studio-code.md
index de9c49ab41..ab718a75ee 100644
--- a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/telemetry-in-codeql-for-visual-studio-code.md
+++ b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/telemetry-in-codeql-for-visual-studio-code.md
@@ -18,11 +18,8 @@ redirect_from:
 
 This data will not be shared with any parties outside of {% data variables.product.company_short %}. IP addresses and installation IDs will be retained for a maximum of 30 days. Anonymous data will be retained for a maximum of 180 days.
 
-{% note %}
-
-**Note:** Telemetry collection is disabled by default in {% data variables.product.prodname_codeql %} for {% data variables.product.prodname_vscode %}. When telemetry collection is disabled, no data will be sent to {% data variables.product.company_short %} servers.
-
-{% endnote %}
+> [!NOTE]
+> Telemetry collection is disabled by default in {% data variables.product.prodname_codeql %} for {% data variables.product.prodname_vscode %}. When telemetry collection is disabled, no data will be sent to {% data variables.product.company_short %} servers.
 
 ## Why we collect data
 
diff --git a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md
index b995564e48..f58b14c6d0 100644
--- a/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md
+++ b/content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md
@@ -33,11 +33,8 @@ The rest of this article covers the practical aspects of modelling dependencies
 
 ## Displaying the {% data variables.product.prodname_codeql %} model editor
 
-{% note %}
-
-**Note:** To use this {% data variables.release-phases.public_preview %} functionality, install the latest version of the {% data variables.product.prodname_codeql %} extension for {% data variables.product.prodname_vscode %}.
-
-{% endnote %}
+> [!NOTE]
+> To use this {% data variables.release-phases.public_preview %} functionality, install the latest version of the {% data variables.product.prodname_codeql %} extension for {% data variables.product.prodname_vscode %}.
 
 1. Open your {% data variables.product.prodname_codeql %} workspace in {% data variables.product.prodname_vscode_shortname %}. For example, the [`vscode-codeql-starter` workspace](https://github.com/github/vscode-codeql-starter). If you are using the starter workspace, update the `ql` submodule from `main` to ensure that you have the queries used to gather data for the model editor.
 
@@ -51,11 +48,8 @@ The rest of this article covers the practical aspects of modelling dependencies
 
 1. When the telemetry queries are complete, the APIs that have been identified are shown in the editor.
 
-{% tip %}
-
-**Tip:** You can move the {% data variables.product.prodname_codeql %} "Method Modeling" view from the primary sidebar to the secondary sidebar, if you want more space while you are modeling calls or methods. If you close the view, you can reopen it from the "View" menu in {% data variables.product.prodname_vscode_shortname %} and clicking **Open View...**.
-
-{% endtip %}
+> [!TIP]
+> You can move the {% data variables.product.prodname_codeql %} "Method Modeling" view from the primary sidebar to the secondary sidebar, if you want more space while you are modeling calls or methods. If you close the view, you can reopen it from the "View" menu in {% data variables.product.prodname_vscode_shortname %} and clicking **Open View...**.
 
 ## Modeling the calls your codebase makes to external APIs
 
diff --git a/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
index 562dcf7418..44f9595ad8 100644
--- a/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
+++ b/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
@@ -40,28 +40,20 @@ If your code depends on a package with a security vulnerability, this can cause
 
 * New advisory data is synchronized to {% data variables.product.prodname_dotcom %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
 
-  {% note %}
+  > [!NOTE]
+  > Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}.
 
-  **Note:** Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}.
-
-  {% endnote %}
 * The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_dependabot %} doesn't scan archived repositories.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_dependabot %} doesn't scan archived repositories.
 
 {% data reusables.repositories.dependency-review %}
 
 As {% data variables.product.prodname_dependabot_alerts %} rely on the dependency graph, the ecosystems that are supported by {% data variables.product.prodname_dependabot_alerts %} are the same as those supported by the dependency graph. For a list of these ecosystems, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/dependency-graph-supported-package-ecosystems#supported-package-ecosystems)."
 
-{% note %}
-
-**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for insecure dependencies that you use. You may also get alerts for dependencies that you no longer use.
-
-{% endnote %}
+> [!NOTE]
+> It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for insecure dependencies that you use. You may also get alerts for dependencies that you no longer use.
 
 {% data reusables.dependabot.dependabot-alert-actions-semver %}
 
@@ -90,11 +82,8 @@ When {% data variables.product.product_name %} identifies a vulnerable dependenc
 
 {% endif %}
 
-{% warning %}
-
-**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. We actively maintain {% data variables.product.prodname_advisory_database %} and generate alerts with the most up-to-date information. However, we cannot catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough dependency review when necessary.
-
-{% endwarning %}
+> [!WARNING]
+> {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. We actively maintain {% data variables.product.prodname_advisory_database %} and generate alerts with the most up-to-date information. However, we cannot catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough dependency review when necessary.
 
 ## Access to  {% data variables.product.prodname_dependabot_alerts %}
 
diff --git a/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md
index 235d2cb5e9..900d00e233 100644
--- a/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md
+++ b/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md
@@ -120,11 +120,10 @@ You can enable or disable {% data variables.product.prodname_dependabot_alerts %
 {% endif %}
 
 {% ifversion dependabot-alerts-enterprise-enablement %}
-{% note %}
 
-**Note:** When {% data variables.product.prodname_dependabot_alerts %} are enabled or disabled at the enterprise level, it overrides the organization and repository level settings for {% data variables.product.prodname_dependabot_alerts %}.
+> [!NOTE]
+> When {% data variables.product.prodname_dependabot_alerts %} are enabled or disabled at the enterprise level, it overrides the organization and repository level settings for {% data variables.product.prodname_dependabot_alerts %}.
 
-{% endnote %}
 {% endif %}
 
 {% ifversion dependabot-alerts-enterprise-enablement or ghes %}
diff --git a/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
index 7241dc58d4..12b8f7f4c8 100644
--- a/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
+++ b/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
@@ -51,11 +51,8 @@ You can configure notification settings for yourself or your organization from t
 ![Screenshot of the notification options for {% data variables.product.prodname_dependabot_alerts %}. A dropdown menu, showing notification frequency options, is highlighted with an orange outline.](/assets/images/help/dependabot/dependabot-notification-frequency.png){% endif %}{% ifversion ghes %}
 ![Screenshot of the notification options for {% data variables.product.prodname_dependabot_alerts %}.](/assets/images/help/enterprises/dependabot-alerts-options-no-ui.png){% endif %}
 
-{% note %}
-
-**Note:** You can filter your notifications on {% data variables.product.company_short %} to show  {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox#dependabot-custom-filters)."
-
-{% endnote %}
+> [!NOTE]
+> You can filter your notifications on {% data variables.product.company_short %} to show  {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox#dependabot-custom-filters)."
 
 {% data reusables.repositories.security-alerts-x-github-severity %} For more information, see "[AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#filtering-email-notifications)."
 
diff --git a/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
index e864dedf92..7484545004 100644
--- a/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
+++ b/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
@@ -77,11 +77,8 @@ When {% data variables.product.prodname_dependabot %} tells you that your reposi
 
 For supported languages, {% data variables.product.prodname_dependabot %} automatically detects whether you use a vulnerable function and adds the label "Vulnerable call" to affected alerts. You can use this information in the {% data variables.product.prodname_dependabot_alerts %} view to triage and prioritize remediation work more effectively.
 
-{% note %}
-
-**Note:** During the {% data variables.release-phases.public_preview %} release, this feature is available only for new Python advisories created _after_ April 14, 2022, and for a subset of historical Python advisories. {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages.
-
-{% endnote %}
+> [!NOTE]
+> During the {% data variables.release-phases.public_preview %} release, this feature is available only for new Python advisories created _after_ April 14, 2022, and for a subset of historical Python advisories. {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages.
 
 ![Screenshot showing an alert with the "Vulnerable call" label. The label is outlined in orange.](/assets/images/help/repository/dependabot-alerts-vulnerable-call-label.png)
 
@@ -149,10 +146,8 @@ With a {% data variables.product.prodname_copilot_enterprise %} license, you can
 
 ## Dismissing {% data variables.product.prodname_dependabot_alerts %}
 
-{% tip %}
-
-**Tip:** You can only dismiss open alerts.
-{% endtip %}
+> [!TIP]
+> You can only dismiss open alerts.
 
 If you schedule extensive work to upgrade a dependency, or decide that an alert does not need to be fixed, you can dismiss the alert. Dismissing alerts that you have already assessed makes it easier to triage new alerts as they appear.
 
diff --git a/content/code-security/dependabot/dependabot-auto-triage-rules/customizing-auto-triage-rules-to-prioritize-dependabot-alerts.md b/content/code-security/dependabot/dependabot-auto-triage-rules/customizing-auto-triage-rules-to-prioritize-dependabot-alerts.md
index f55973a75c..21757959c2 100644
--- a/content/code-security/dependabot/dependabot-auto-triage-rules/customizing-auto-triage-rules-to-prioritize-dependabot-alerts.md
+++ b/content/code-security/dependabot/dependabot-auto-triage-rules/customizing-auto-triage-rules-to-prioritize-dependabot-alerts.md
@@ -30,11 +30,8 @@ Organization owners and security managers can set {% data variables.dependabot.c
    * **Enforced**: If an organization-level rule is "enforced", repository administrators cannot edit, disable, or delete the rule.
    * **Enabled**: If an organization-level rule is "enabled", repository administrators can still disable the rule for their repository.
 
-{% note %}
-
-**Note:** In the event that an organization-level rule and a repository-level rule specify conflicting behaviors, the action set out by the organization-level rule takes precedence. Dismissal rules always act before rules which trigger {% data variables.product.prodname_dependabot %} pull requests.
-
-{% endnote %}
+> [!NOTE]
+> In the event that an organization-level rule and a repository-level rule specify conflicting behaviors, the action set out by the organization-level rule takes precedence. Dismissal rules always act before rules which trigger {% data variables.product.prodname_dependabot %} pull requests.
 
 You can create rules to target alerts using the following metadata:
 
@@ -58,11 +55,8 @@ For more information about enabling or disabling {% data variables.product.prodn
 
 ## Adding {% data variables.dependabot.custom_rules %} to your repository
 
-{% note %}
-
-**Note:** During the {% data variables.release-phases.public_preview %}, you can create up to 10 {% data variables.dependabot.custom_rules %} for a repository.
-
-{% endnote %}
+> [!NOTE]
+> During the {% data variables.release-phases.public_preview %}, you can create up to 10 {% data variables.dependabot.custom_rules %} for a repository.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -83,11 +77,8 @@ For more information about enabling or disabling {% data variables.product.prodn
 
 {% else %}
 
-{% note %}
-
-**Note:** During the {% data variables.release-phases.public_preview %}, you can create up to 25 {% data variables.dependabot.custom_rules %} for your organization.
-
-{% endnote %}
+> [!NOTE]
+> During the {% data variables.release-phases.public_preview %}, you can create up to 25 {% data variables.dependabot.custom_rules %} for your organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/content/code-security/dependabot/dependabot-auto-triage-rules/managing-automatically-dismissed-alerts.md b/content/code-security/dependabot/dependabot-auto-triage-rules/managing-automatically-dismissed-alerts.md
index 3222869455..eaf44bc12e 100644
--- a/content/code-security/dependabot/dependabot-auto-triage-rules/managing-automatically-dismissed-alerts.md
+++ b/content/code-security/dependabot/dependabot-auto-triage-rules/managing-automatically-dismissed-alerts.md
@@ -18,11 +18,8 @@ redirect_from:
 
 ## Managing automatically dismissed alerts
 
-{% note %}
-
-**Note:** The {% data variables.product.prodname_dependabot_alerts %} page defaults to showing open alerts. To filter and view auto-dismissed alerts, you must first clear the `is:open` default filter from the view.
-
-{% endnote %}
+> [!NOTE]
+> The {% data variables.product.prodname_dependabot_alerts %} page defaults to showing open alerts. To filter and view auto-dismissed alerts, you must first clear the `is:open` default filter from the view.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
diff --git a/content/code-security/dependabot/dependabot-auto-triage-rules/using-github-preset-rules-to-prioritize-dependabot-alerts.md b/content/code-security/dependabot/dependabot-auto-triage-rules/using-github-preset-rules-to-prioritize-dependabot-alerts.md
index 07ea451ee6..8e46bc16d8 100644
--- a/content/code-security/dependabot/dependabot-auto-triage-rules/using-github-preset-rules-to-prioritize-dependabot-alerts.md
+++ b/content/code-security/dependabot/dependabot-auto-triage-rules/using-github-preset-rules-to-prioritize-dependabot-alerts.md
@@ -26,11 +26,8 @@ The `Dismiss low impact issues for development-scoped dependencies` rule is a {%
 * At worst, have limited effects like slow builds or long-running tests.
 * Are not indicative of issues in production.
 
-{% note %}
-
-**Note:** Automatic dismissal of low impact development alerts is currently only supported for npm.
-
-{% endnote %}
+> [!NOTE]
+> Automatic dismissal of low impact development alerts is currently only supported for npm.
 
 The `Dismiss low impact issues for development-scoped dependencies` rule includes vulnerabilities relating to resource management, programming and logic, and information disclosure issues. For more information, see "[Publicly disclosed CWEs used by the `Dismiss low impact issues for development-scoped dependencies` rule](#publicly-disclosed-cwes-used-by-the-dismiss-low-impact-issues-for-development-scoped-dependencies-rule)."
 
diff --git a/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md b/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md
index a5a95d9934..2d941a81ed 100644
--- a/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md
+++ b/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md
@@ -47,11 +47,8 @@ If you enable {% data variables.product.prodname_dependabot_security_updates %},
 
 The {% data variables.product.prodname_dependabot_security_updates %} feature is available for repositories where you have enabled the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. You will see a {% data variables.product.prodname_dependabot %} alert for every vulnerable dependency identified in your full dependency graph. However, security updates are triggered only for dependencies that are specified in a manifest or lock file. For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#dependencies-included)."
 
-{% note %}
-
-**Note**: For npm, {% data variables.product.prodname_dependabot %} will raise a pull request to update an explicitly defined dependency to a secure version, even if it means updating the parent dependency or dependencies, or even removing a sub-dependency that is no longer needed by the parent. For other ecosystems, {% data variables.product.prodname_dependabot %} is unable to update an indirect or transitive dependency if it would also require an update to the parent dependency. For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors#dependabot-tries-to-update-dependencies-without-an-alert)."
-
-{% endnote %}
+> [!NOTE]
+> For npm, {% data variables.product.prodname_dependabot %} will raise a pull request to update an explicitly defined dependency to a secure version, even if it means updating the parent dependency or dependencies, or even removing a sub-dependency that is no longer needed by the parent. For other ecosystems, {% data variables.product.prodname_dependabot %} is unable to update an indirect or transitive dependency if it would also require an update to the parent dependency. For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors#dependabot-tries-to-update-dependencies-without-an-alert)."
 
 You can enable a related feature, {% data variables.product.prodname_dependabot_version_updates %}, so that {% data variables.product.prodname_dependabot %} raises pull requests to update the manifest to the latest version of the dependency, whenever it detects an outdated dependency. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)."
 
diff --git a/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
index e0c7e0d71d..c0a59dd176 100644
--- a/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
+++ b/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
@@ -68,11 +68,8 @@ To reduce the number of pull requests you may be seeing, you can enable grouped
 * **{% data variables.product.prodname_dependabot_alerts %}**. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)."
 * **{% data variables.product.prodname_dependabot_security_updates %}**. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
 
-{% note %}
-
-**Note:** When grouped security updates are first enabled, {% data variables.product.prodname_dependabot %} will immediately try to create grouped pull requests. You may notice {% data variables.product.prodname_dependabot %} closing old pull requests and opening new ones.
-
-{% endnote %}
+> [!NOTE]
+> When grouped security updates are first enabled, {% data variables.product.prodname_dependabot %} will immediately try to create grouped pull requests. You may notice {% data variables.product.prodname_dependabot %} closing old pull requests and opening new ones.
 
 {% data reusables.dependabot.dependabot-grouped-security-updates-how-enable %}
 {% data reusables.dependabot.dependabot-grouped-security-updates-order %}
@@ -150,11 +147,8 @@ updates:
           - "golang.org*"{% endif %}
 ```
 
-{% note %}
-
-**Note:** In order for {% data variables.product.prodname_dependabot %} to use this configuration for security updates,  the `directory` must be the path to the manifest files, and you should not specify a `target-branch`.
-
-{% endnote %}
+> [!NOTE]
+> In order for {% data variables.product.prodname_dependabot %} to use this configuration for security updates,  the `directory` must be the path to the manifest files, and you should not specify a `target-branch`.
 
 ## Further reading
 
diff --git a/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
index dd08f7eb28..13f096982a 100644
--- a/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+++ b/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@@ -31,11 +31,8 @@ You must store this file in the `.github` directory of your repository in the de
 
 Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update.  For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
 
-{% note %}
-
-**Note:** You cannot configure {% data variables.product.prodname_dependabot_alerts %} using the `dependabot.yml` file.
-
-{% endnote %}
+> [!NOTE]
+> You cannot configure {% data variables.product.prodname_dependabot_alerts %} using the `dependabot.yml` file.
 
 The `dependabot.yml` file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key. The file must start with `version: 2`.
 
@@ -61,15 +58,12 @@ These options fit broadly into the following categories.
 
 In addition, the [`open-pull-requests-limit`](#open-pull-requests-limit) option changes the maximum number of pull requests for version updates that {% data variables.product.prodname_dependabot %} can open.
 
-{% note %}
-
-**Note:** Some of these configuration options may also affect pull requests raised for security updates of vulnerable package manifests.
-
-Security updates are raised for vulnerable package manifests only on the default branch. When configuration options are set for the same branch (true unless you use `target-branch`), and specify a `package-ecosystem` and `directory` for the vulnerable manifest, then pull requests for security updates use relevant options.
-
-In general, security updates use any configuration options that affect pull requests, for example, adding metadata or changing their behavior. For more information about security updates, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
-
-{% endnote %}
+> [!NOTE]
+> Some of these configuration options may also affect pull requests raised for security updates of vulnerable package manifests.
+>
+> Security updates are raised for vulnerable package manifests only on the default branch. When configuration options are set for the same branch (true unless you use `target-branch`), and specify a `package-ecosystem` and `directory` for the vulnerable manifest, then pull requests for security updates use relevant options.
+>
+> In general, security updates use any configuration options that affect pull requests, for example, adding metadata or changing their behavior. For more information about security updates, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
 
 ### `package-ecosystem`
 
@@ -79,11 +73,8 @@ If you want to enable vendoring for a package manager that supports it, the vend
 
 If you want to allow {% data variables.product.prodname_dependabot %} to access a private package registry when performing a version update, you can include a `registries` setting in the configuration file. For more information, see [`registries`](#registries) below.{% ifversion ghes %}
 
-{% note %}
-
-**Note:** Enterprise owners can download the most recent version of the [{% data variables.product.prodname_dependabot %} action](https://github.com/github/dependabot-action) to get the best ecosystem coverage. {% data reusables.actions.action-bundled-actions %}
-
-{% endnote %}
+> [!NOTE]
+> Enterprise owners can download the most recent version of the [{% data variables.product.prodname_dependabot %} action](https://github.com/github/dependabot-action) to get the best ecosystem coverage. {% data reusables.actions.action-bundled-actions %}
 
 {% endif %}
 
@@ -247,11 +238,8 @@ updates:
 
 **Required**. You must define how often to check for new versions for each package manager. By default, {% data variables.product.prodname_dependabot %} randomly assigns a time to apply all the updates in the configuration file. To set a specific time, you can use [`schedule.time`](#scheduletime) and [`schedule.timezone`](#scheduletimezone).
 
-{% note %}
-
-**Note:** The `schedule.time` option is a best effort, and it may take some time before {% data variables.product.prodname_dependabot %} opens pull requests to update to newer dependency versions.
-
-{% endnote %}
+> [!NOTE]
+> The `schedule.time` option is a best effort, and it may take some time before {% data variables.product.prodname_dependabot %} opens pull requests to update to newer dependency versions.
 
 | Interval types | Frequency |
 |----------------|-----------|
@@ -279,13 +267,10 @@ updates:
       interval: "weekly"
 ```
 
-{% note %}
-
-**Note**: `schedule` defines when {% data variables.product.prodname_dependabot %} attempts a new update. However, it's not the only time you may receive pull requests. Updates can be triggered based on changes to your `dependabot.yml` file, {% ifversion dependabot-updates-deprecate-rerun-failed-jobs %}{% else %}changes to your manifest file(s) after a failed update, {% endif %}or {% data variables.product.prodname_dependabot_security_updates %}. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)."
-
-{% data reusables.dependabot.version-updates-skip-scheduled-runs %}
-
-{% endnote %}
+> [!NOTE]
+> `schedule` defines when {% data variables.product.prodname_dependabot %} attempts a new update. However, it's not the only time you may receive pull requests. Updates can be triggered based on changes to your `dependabot.yml` file, {% ifversion dependabot-updates-deprecate-rerun-failed-jobs %}{% else %}changes to your manifest file(s) after a failed update, {% endif %}or {% data variables.product.prodname_dependabot_security_updates %}. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)."
+>
+> {% data reusables.dependabot.version-updates-skip-scheduled-runs %}
 
 ### `allow`
 
@@ -372,11 +357,8 @@ We populate the titles of pull requests based on the commit messages, whether ex
 
 Supported options
 
-{% note %}
-
-**Note:** The `prefix` and the `prefix-development` options have a 50-character limit.
-
-{% endnote %}
+> [!NOTE]
+> The `prefix` and the `prefix-development` options have a 50-character limit.
 
 * `prefix` specifies a prefix for all commit messages and it will also be added to the start of the PR title.
    When you specify a prefix for commit messages, {% data variables.product.prodname_dotcom %} will automatically add a colon between the defined prefix and the commit message provided the defined prefix ends with a letter, number, closing parenthesis, or closing bracket. This means that, for example, if you end the prefix with a whitespace, there will be no colon added between the prefix and the commit message.
@@ -476,14 +458,9 @@ You can also manage pull requests for grouped version updates and security updat
 
 Dependencies can be ignored either by adding them to `ignore` or by using the `@dependabot ignore` command on a pull request opened by {% data variables.product.prodname_dependabot %}.
 
-{% warning %}
-
-**Warning**:
-* We recommend you do _not_ use `ignore` to prevent {% data variables.product.prodname_dependabot %} from accessing private registries. This may work for some ecosystems but we have no means of knowing whether package managers require access to all dependencies to be able to successfully perform updates, which makes this method unreliable. The supported way to handle private dependencies is to give {% data variables.product.prodname_dependabot %} access to private registries or private repositories. For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot)."
-
-* For {% data variables.product.prodname_actions %} and Docker, you may use `ignore` to prevent {% data variables.product.prodname_dependabot %} from accessing private registries.
-
-{% endwarning %}
+> [!WARNING]
+> * We recommend you do _not_ use `ignore` to prevent {% data variables.product.prodname_dependabot %} from accessing private registries. This may work for some ecosystems but we have no means of knowing whether package managers require access to all dependencies to be able to successfully perform updates, which makes this method unreliable. The supported way to handle private dependencies is to give {% data variables.product.prodname_dependabot %} access to private registries or private repositories. For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot)."
+> * For {% data variables.product.prodname_actions %} and Docker, you may use `ignore` to prevent {% data variables.product.prodname_dependabot %} from accessing private registries.
 
 #### Creating `ignore` conditions from `@dependabot ignore`
 
@@ -535,17 +512,11 @@ updates:
         versions: '>= 3'
 ```
 
-{% note %}
+> [!NOTE]
+> {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private{% ifversion ghec or ghes %}-or-internal{% endif %}-dependencies)" and "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)."
 
-**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private{% ifversion ghec or ghes %}-or-internal{% endif %}-dependencies)" and "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)."
-
-{% endnote %}
-
-{% note %}
-
-**Note**: For the `pub` ecosystem, {% data variables.product.prodname_dependabot %} won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
-
-{% endnote %}
+> [!NOTE]
+> For the `pub` ecosystem, {% data variables.product.prodname_dependabot %} won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
 
 The following examples show how `ignore` can be used to customize which dependencies are updated.
 
@@ -738,11 +709,8 @@ updates:
 
 By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects any changes to the pull request. Use `rebase-strategy` to disable this behavior.
 
-{% note %}
-
-**Note:** {% data reusables.dependabot.pull-requests-30-days-cutoff %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.dependabot.pull-requests-30-days-cutoff %}
 
 Available rebase strategies
 
@@ -757,11 +725,8 @@ When `rebase-strategy` is set to `auto`, {% data variables.product.prodname_depe
 
 When `rebase-strategy` is set to `disabled`, {% data variables.product.prodname_dependabot %} stops rebasing pull requests.
 
-{% note %}
-
-**Note:** This behavior only applies to pull requests that go into conflict with the target branch. {% data variables.product.prodname_dependabot %} will keep rebasing (until 30 days after opening) pull requests opened prior to the `rebase-strategy` setting being changed, and pull requests that are part of a scheduled run.
-
-{% endnote %}
+> [!NOTE]
+> This behavior only applies to pull requests that go into conflict with the target branch. {% data variables.product.prodname_dependabot %} will keep rebasing (until 30 days after opening) pull requests opened prior to the `rebase-strategy` setting being changed, and pull requests that are part of a scheduled run.
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -1003,11 +968,8 @@ Available update strategies:
 | `pub` | `auto`, `increase`, `increase-if-necessary`, `widen` | `auto` |
 | `terraform` | N/A | N/A |
 
-{% note %}
-
-**Note:** `N/A` indicates that the package manager does not yet support configuring the `versioning-strategy` parameter. The strategy code is open source, so if you'd like a particular ecosystem to support a new strategy, you are always welcome to submit a pull request in https://github.com/dependabot/dependabot-core/.
-
-{% endnote %}
+> [!NOTE]
+> `N/A` indicates that the package manager does not yet support configuring the `versioning-strategy` parameter. The strategy code is open source, so if you'd like a particular ecosystem to support a new strategy, you are always welcome to submit a pull request in https://github.com/dependabot/dependabot-core/.
 
 ```yaml
 # Example configuration for customizing the manifest version strategy
@@ -1055,22 +1017,21 @@ The top-level `registries` key is optional. It allows you to specify authenticat
 
 You can give {% data variables.product.prodname_dependabot %} access to private package registries hosted by GitLab or Bitbucket by specifying a `type` of `git`. For more information, see [`git`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#git).
 {% ifversion ghes %}
-{% note %}
 
-**Note:** Private registries behind firewalls on private networks are supported for the following ecosystems:
+> [!NOTE]
+> Private registries behind firewalls on private networks are supported for the following ecosystems:
+>
+> * Bundler{% ifversion dependabot-updates-cargo-private-registry-support %}
+> * Cargo{% endif %}
+> * Docker
+> * Gradle
+> * Maven
+> * Npm
+> * Nuget{% ifversion dependabot-updates-pub-private-registry %}
+> * Pub{% endif %}
+> * Python
+> * Yarn
 
-* Bundler{% ifversion dependabot-updates-cargo-private-registry-support %}
-* Cargo{% endif %}
-* Docker
-* Gradle
-* Maven
-* Npm
-* Nuget{% ifversion dependabot-updates-pub-private-registry %}
-* Pub{% endif %}
-* Python
-* Yarn
-
-{% endnote %}
 {% endif %}
 
 The value of the `registries` key is an associative array, each element of which consists of a key that identifies a particular registry and a value which is an associative array that specifies the settings required to access that registry. The following `dependabot.yml` file configures a registry identified as `dockerhub` in the `registries` section of the file and then references this in the `updates` section of the file.
@@ -1255,11 +1216,8 @@ The `npm-registry` type supports username and password, or token. {% data reusab
 
 When using username and password, your `.npmrc`'s auth token may contain a `base64` encoded `_password`; however, the password referenced in your {% data variables.product.prodname_dependabot %} configuration file must be the original (unencoded) password.
 
-{% note %}
-
-**Note**: When using `npm.pkg.github.com`, don't include a path. Instead use the `https://npm.pkg.github.com` URL without a path.
-
-{% endnote %}
+> [!NOTE]
+> When using `npm.pkg.github.com`, don't include a path. Instead use the `https://npm.pkg.github.com` URL without a path.
 
 {% raw %}
 
diff --git a/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md b/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
index b786abbc9a..d97b80acef 100644
--- a/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
+++ b/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
@@ -45,11 +45,12 @@ If you customize the `dependabot.yml` file, you may notice some changes to the p
 
 For an example, see "[Setting custom labels](#setting-custom-labels)" below.
 
-{% ifversion dependabot-grouped-security-updates-config %}{% note %}
+{% ifversion dependabot-grouped-security-updates-config %}
 
-**Note:** If you use grouped security updates, the grouped pull requests will also inherit non-group configuration settings from the `dependabot.yml` file, and any group rules specified with `applies-to: security-updates` will apply. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates#about-grouped-security-updates)."
+> [!NOTE]
+> If you use grouped security updates, the grouped pull requests will also inherit non-group configuration settings from the `dependabot.yml` file, and any group rules specified with `applies-to: security-updates` will apply. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates#about-grouped-security-updates)."
 
-{% endnote %}{% endif %}
+{% endif %}
 
 ## Modifying scheduling
 
@@ -108,11 +109,8 @@ You can use `labels` to override the default labels and specify alternative labe
 
 The example `dependabot.yml` file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have custom labels. It also changes the Docker configuration to check for version updates against a custom branch and to raise pull requests with custom labels against that custom branch. The changes to Docker will not affect security update pull requests because security updates are always made against the default branch.
 
-{% note %}
-
-**Note:** The new `target-branch` must contain a Dockerfile to update, otherwise this change will have the effect of disabling version updates for Docker.
-
-{% endnote %}
+> [!NOTE]
+> The new `target-branch` must contain a Dockerfile to update, otherwise this change will have the effect of disabling version updates for Docker.
 
 ```yaml
 # `dependabot.yml` file with
@@ -183,11 +181,10 @@ If you would like to un-ignore a dependency or ignore condition, you can delete
 * Un-ignore all ignore conditions for all dependencies in a {% data variables.product.prodname_dependabot %} pull request
 
 {% ifversion dependabot-grouped-security-updates-config %}{% else %}
-{% note %}
 
-**Note:** The `@dependabot unignore` comment commands only work on pull requests for grouped version updates.
+> [!NOTE]
+> The `@dependabot unignore` comment commands only work on pull requests for grouped version updates.
 
-{% endnote %}
 {% endif %}
 
 For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-for-grouped-{% ifversion dependabot-grouped-security-updates-config %}{% else %}version-{% endif %}updates-with-comment-commands)."{% endif %}
diff --git a/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
index 7a8f3f2fd6..c9e022e894 100644
--- a/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
+++ b/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
@@ -223,11 +223,8 @@ If you want to allow maintainers to mark certain pull requests for auto-merge, y
 
 {% ifversion repo-rules %}As an alternative to branch protection rules, you can create rulesets. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."{% endif %}
 
-{% note %}
-
-**Note:** If you use status checks to test pull requests, you should enable **Require status checks to pass before merging** for the target branch for {% data variables.product.prodname_dependabot %} pull requests. This branch protection rule ensures that pull requests are not merged unless all the required status checks pass. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)."
-
-{% endnote %}
+> [!NOTE]
+> If you use status checks to test pull requests, you should enable **Require status checks to pass before merging** for the target branch for {% data variables.product.prodname_dependabot %} pull requests. This branch protection rule ensures that pull requests are not merged unless all the required status checks pass. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule)."
 
 You can instead use {% data variables.product.prodname_actions %} and the {% data variables.product.prodname_cli %}. Here is an example that auto merges all patch updates to `my-dependency`:
 
diff --git a/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md b/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
index aa60fee6d9..acbe481c42 100644
--- a/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
+++ b/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
@@ -32,11 +32,10 @@ If a more recent version of the action is available, {% data variables.product.p
 {% data variables.product.prodname_dependabot %} also checks workflow files for uses of reusable workflows, and updates the git reference for these called reusable workflows. For more information about reusable workflows, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows)."
 
 {% ifversion fpt or ghec %}
-{% note %}
 
-**Note:**  {% data reusables.actions.workflow-runs-dependabot-note %}
+> [!NOTE]
+> {% data reusables.actions.workflow-runs-dependabot-note %}
 
-{% endnote %}
 {% endif %}
 
 ## Enabling {% data variables.product.prodname_dependabot_version_updates %} for actions
diff --git a/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md b/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md
index cea9c0047a..a157cf78c0 100644
--- a/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md
+++ b/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md
@@ -31,11 +31,8 @@ When {% data variables.product.prodname_dependabot %} raises a pull request, you
 
 If you have many dependencies to manage, you may want to customize the configuration for each package manager so that pull requests have specific reviewers, assignees, and labels. {% ifversion dependabot-version-updates-groups %} You may also want to group sets of dependencies together, so that multiple dependencies are updated in a single pull request.{% endif %} For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates){% ifversion dependabot-grouped-security-updates-config %}" and "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#grouping-dependabot-updates-into-a-single-pull-request)."{% else %}" and "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#grouping-dependabot-security-updates-into-a-single-pull-request)."{% endif %}
 
-{% note %}
-
-**Note**: If you don't interact with {% data variables.product.prodname_dependabot %} pull requests for a repository during a 90-day time period, {% data variables.product.prodname_dependabot %} considers your repository as inactive, and will automatically pause {% data variables.product.prodname_dependabot_updates %}. For more information about inactivity criteria, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#about-automatic-deactivation-of-dependabot-updates)" and "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates#about-automatic-deactivation-of-dependabot-updates)."
-
-{% endnote %}
+> [!NOTE]
+> If you don't interact with {% data variables.product.prodname_dependabot %} pull requests for a repository during a 90-day time period, {% data variables.product.prodname_dependabot %} considers your repository as inactive, and will automatically pause {% data variables.product.prodname_dependabot_updates %}. For more information about inactivity criteria, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#about-automatic-deactivation-of-dependabot-updates)" and "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates#about-automatic-deactivation-of-dependabot-updates)."
 
 ## Viewing {% data variables.product.prodname_dependabot %} pull requests
 
@@ -92,11 +89,8 @@ In {% data variables.product.prodname_dependabot %} pull requests for grouped ve
 * `@dependabot unignore DEPENDENCY_NAME` closes the current pull request, clears all `ignore` conditions stored for the dependency, then opens a new pull request that includes available updates for the specified dependency. For example, `@dependabot unignore lodash` would open a new pull request that includes updates for the Lodash dependency.
 * `@dependabot unignore DEPENDENCY_NAME IGNORE_CONDITION` closes the current pull request, clears the stored `ignore` condition, then opens a new pull request that includes available updates for the specified ignore condition. For example, `@dependabot unignore express [< 1.9, > 1.8.0]` would open a new pull request that includes updates for Express between versions 1.8.0 and 1.9.0.
 
-{% note %}
-
-**Tip:** When you want to un-ignore a specific ignore condition, use the `@dependabot show DEPENDENCY_NAME ignore conditions` command to quickly check what ignore conditions a dependency currently has.
-
-{% endnote %}
+> [!TIP]
+> When you want to un-ignore a specific ignore condition, use the `@dependabot show DEPENDENCY_NAME ignore conditions` command to quickly check what ignore conditions a dependency currently has.
 
 {% elsif dependabot-version-updates-groups %}
 
@@ -104,11 +98,8 @@ In {% data variables.product.prodname_dependabot %} pull requests for grouped ve
 
 In {% data variables.product.prodname_dependabot %} pull requests for grouped version updates, you can use comment commands to ignore and un-ignore updates for specific dependencies and versions. You can use any of the following commands to manage ignore conditions for grouped version updates.
 
-{% note %}
-
-**Note:** The following comment commands do not work for grouped {% data variables.product.prodname_dependabot_security_updates %}.
-
-{% endnote %}
+> [!NOTE]
+> The following comment commands do not work for grouped {% data variables.product.prodname_dependabot_security_updates %}.
 
 * `@dependabot ignore DEPENDENCY_NAME` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from updating this dependency.
 * `@dependabot ignore DEPENDENCY_NAME major version` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from updating this dependency's major version.
@@ -118,9 +109,7 @@ In {% data variables.product.prodname_dependabot %} pull requests for grouped ve
 * `@dependabot unignore DEPENDENCY_NAME` closes the current pull request, clears all `ignore` conditions stored for the dependency, then opens a new pull request that includes available version updates for the specified dependency. For example, `@dependabot unignore lodash` would open a new pull request that includes version updates for the Lodash dependency.
 * `@dependabot unignore DEPENDENCY_NAME IGNORE_CONDITION` closes the current pull request, clears the stored `ignore` condition, then opens a new pull request that includes available version updates for the specified ignore condition. For example, `@dependabot unignore express [< 1.9, > 1.8.0]` would open a new pull request that includes version updates for Express between versions 1.8.0 and 1.9.0.
 
-{% note %}
+> [!TIP]
+> When you want to un-ignore a specific ignore condition, use the `@dependabot show DEPENDENCY_NAME ignore conditions` command to quickly check what ignore conditions a dependency currently has.
 
-**Tip:** When you want to un-ignore a specific ignore condition, use the `@dependabot show DEPENDENCY_NAME ignore conditions` command to quickly check what ignore conditions a dependency currently has.
-
-{% endnote %}
 {% endif %}
diff --git a/content/code-security/dependabot/working-with-dependabot/removing-dependabot-access-to-public-registries.md b/content/code-security/dependabot/working-with-dependabot/removing-dependabot-access-to-public-registries.md
index 7d63ccb912..60c648fc61 100644
--- a/content/code-security/dependabot/working-with-dependabot/removing-dependabot-access-to-public-registries.md
+++ b/content/code-security/dependabot/working-with-dependabot/removing-dependabot-access-to-public-registries.md
@@ -25,11 +25,8 @@ You can configure {% data variables.product.prodname_dependabot %} to access _on
 
 {% ifversion dependabot-ghes-no-public-internet %}
 
-{% note %}
-
-**Note:** Before you remove access to public registries from your configuration for {% data variables.product.prodname_dependabot_updates %}, check that your site administrator has set up the {% data variables.product.prodname_dependabot %} runners with access to the private registries you need. For more information, see "[AUTOTITLE](/admin/code-security/managing-supply-chain-security-for-your-enterprise/configuring-dependabot-to-work-with-limited-internet-access)."
-
-{% endnote %}
+> [!NOTE]
+> Before you remove access to public registries from your configuration for {% data variables.product.prodname_dependabot_updates %}, check that your site administrator has set up the {% data variables.product.prodname_dependabot %} runners with access to the private registries you need. For more information, see "[AUTOTITLE](/admin/code-security/managing-supply-chain-security-for-your-enterprise/configuring-dependabot-to-work-with-limited-internet-access)."
 
 {% endif %}
 
@@ -53,11 +50,8 @@ To configure the Docker ecosystem to only access private registries, you can use
 
 Define the private registry configuration in a `dependabot.yml` file without `replaces-base`. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#docker-registry)."
 
-{% note %}
-
-**Note:** Remove `replaces-base: true` from the configuration file.
-
-{% endnote %}
+> [!NOTE]
+> Remove `replaces-base: true` from the configuration file.
 
 ```yaml
 version: 2
@@ -85,11 +79,8 @@ To configure the Gradle ecosystem to only access private registries, you can use
 
 Define the private registry configuration in a `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#maven-repository)."
 
-{% note %}
-
-**Note**: Remove replaces-base: true from the configuration file.
-
-{% endnote %}
+> [!NOTE]
+> Remove replaces-base: true from the configuration file.
 
 Additionally, you also need to specify the private registry URL in the `repositories` section of the `build.gradle` file.
 
@@ -138,11 +129,8 @@ To configure the npm ecosystem to only access private registries, you can use th
 
 Define the private registry configuration in a `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#npm-registry)."
 
-{% note %}
-
-**Note:** Remove `replaces-base: true` from the configuration file.
-
-{% endnote %}
+> [!NOTE]
+> Remove `replaces-base: true` from the configuration file.
 
 The npm ecosystem additionally requires a `.npmrc` file with the private registry URL to be checked into the repository.
 
@@ -154,11 +142,8 @@ The npm ecosystem additionally requires a `.npmrc` file with the private registr
 
 If there is no global registry defined in an `.npmrc` file, you can set `replaces-base` as `true` in the `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#npm-registry)."
 
-{% note %}
-
-**Note:** For scoped dependencies (`@my-org/my-dep`), {% data variables.product.prodname_dependabot %} requires that the private registry is defined in the project's `.npmrc` file. To define private registries for individual scopes, use `@myscope:registry=https://private_registry_url`.
-
-{% endnote %}
+> [!NOTE]
+> For scoped dependencies (`@my-org/my-dep`), {% data variables.product.prodname_dependabot %} requires that the private registry is defined in the project's `.npmrc` file. To define private registries for individual scopes, use `@myscope:registry=https://private_registry_url`.
 
 ### Yarn
 
@@ -172,11 +157,8 @@ To configure the Yarn Classic ecosystem to only access private registries, you c
 
 Define the private registry configuration in a `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#npm-registry)."
 
-{% note %}
-
-**Note:** Delete `replaces-base: true` from the configuration file.
-
-{% endnote %}
+> [!NOTE]
+> Delete `replaces-base: true` from the configuration file.
 
 To ensure the private registry is listed as the dependency source in the project's `yarn.lock` file, run `yarn install` on a machine with private registry access. Yarn should update the `resolved` field to include the private registry URL.
 
@@ -203,11 +185,8 @@ If the `yarn.lock` file doesn't list the private registry as the dependency sour
 
 If there is no global registry defined in a `.yarnrc` file, you can set `replaces-base` as `true` in the `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#npm-registry)."
 
-{% note %}
-
-**Note:** For scoped dependencies (`@my-org/my-dep`), {% data variables.product.prodname_dependabot %} requires that the private registry is defined in the project's `.npmrc` file. To define private registries for individual scopes, use `@myscope:registry=https://private_registry_url`.
-
-{% endnote %}
+> [!NOTE]
+> For scoped dependencies (`@my-org/my-dep`), {% data variables.product.prodname_dependabot %} requires that the private registry is defined in the project's `.npmrc` file. To define private registries for individual scopes, use `@myscope:registry=https://private_registry_url`.
 
 #### Yarn Berry
 
@@ -217,11 +196,8 @@ To configure the Yarn Berry ecosystem to only access private registries, you can
 
 Define the private registry configuration in a `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#npm-registry)."
 
-{% note %}
-
-**Note:** Delete `replaces-base: true` from the configuration file.
-
-{% endnote %}
+> [!NOTE]
+> Delete `replaces-base: true` from the configuration file.
 
 To ensure the private registry is listed as the dependency source in the project's `yarn.lock` file, run `yarn install` on a machine with private registry access. Yarn should update the `resolved` field to include the private registry URL.
 
@@ -247,11 +223,8 @@ If the `yarn.lock` file doesn't list the private registry as the dependency sour
     npmRegistryServer: "https://private_registry_url"
     ```
 
-{% note %}
-
-**Note:** For scoped dependencies (`@my-org/my-dep`), {% data variables.product.prodname_dependabot %} requires that the private registry is defined in the project's `.yarnrc` file. To define private registries for individual scopes, use `"@myscope:registry" "https://private_registry_url"`.
-
-{% endnote %}
+> [!NOTE]
+> For scoped dependencies (`@my-org/my-dep`), {% data variables.product.prodname_dependabot %} requires that the private registry is defined in the project's `.yarnrc` file. To define private registries for individual scopes, use `"@myscope:registry" "https://private_registry_url"`.
 
 ## Nuget
 
@@ -318,11 +291,8 @@ To configure the Pip ecosystem to only access private registries, you can use th
 
 Define the private registry configuration in a `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#npm-registry)."
 
-{% note %}
-
-**Note:** Delete `replaces-base: true` from the configuration file.
-
-{% endnote %}
+> [!NOTE]
+> Delete `replaces-base: true` from the configuration file.
 
 Add the private registry URL to the `[global]` section of the `pip.conf` file and check the file into the repository.
 
@@ -348,11 +318,8 @@ Set `replaces-base` as `true` in the `dependabot.yml` file. For more information
 
 Define the private registry configuration in a `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#npm-registry)."
 
-{% note %}
-
-**Note:** Delete `replaces-base: true` from the configuration file.
-
-{% endnote %}
+> [!NOTE]
+> Delete `replaces-base: true` from the configuration file.
 
 Add the private registry URL to the `requirements.txt` file and check the file into the repository.
 
@@ -364,11 +331,8 @@ Add the private registry URL to the `requirements.txt` file and check the file i
 
 To configure Pipenv to only access private registries, remove `replaces-base` from the `dependabot.yml` file. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#python-index)."
 
-{% note %}
-
-**Note:** Delete `replaces-base: true` from the configuration file.
-
-{% endnote %}
+> [!NOTE]
+> Delete `replaces-base: true` from the configuration file.
 
 Add the private registry URL to the `[[source]]` section of the `Pipfile` file and check the file into the repository.
 
diff --git a/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md b/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
index d8ec843274..99a9603005 100644
--- a/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
+++ b/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
@@ -31,11 +31,8 @@ topics:
 
 If anything prevents {% data variables.product.prodname_dependabot %} from raising a pull request, this is reported as an error.
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_dependabot %} doesn't create pull requests for inactive repositories. For information about inactivity criteria, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates#about-automatic-deactivation-of-dependabot-updates)" and "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#about-automatic-deactivation-of-dependabot-updates)," for security and version updates, respectively.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_dependabot %} doesn't create pull requests for inactive repositories. For information about inactivity criteria, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates#about-automatic-deactivation-of-dependabot-updates)" and "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#about-automatic-deactivation-of-dependabot-updates)," for security and version updates, respectively.
 
 {% ifversion dependabot-on-actions-opt-in %}
 For more information about troubleshooting when running {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_actions %} runners, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners)."
diff --git a/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
index 3716e45fe6..a88201555b 100644
--- a/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
+++ b/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -24,11 +24,8 @@ To give people instructions for reporting security vulnerabilities in your proje
 
 You can create a default security policy for your organization or personal account. For more information, see "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
 
-{% tip %}
-
-**Tip:** To help people find your security policy, you can link to your `SECURITY.md` file from other places in your repository, such as your `README` file. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)."
-
-{% endtip %}
+> [!TIP]
+> To help people find your security policy, you can link to your `SECURITY.md` file from other places in your repository, such as your `README` file. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)."
 
 {% ifversion fpt or ghec %}
 After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[AUTOTITLE](/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories)."
diff --git a/content/code-security/getting-started/best-practices-for-preventing-data-leaks-in-your-organization.md b/content/code-security/getting-started/best-practices-for-preventing-data-leaks-in-your-organization.md
index abde5f9184..67410ddce1 100644
--- a/content/code-security/getting-started/best-practices-for-preventing-data-leaks-in-your-organization.md
+++ b/content/code-security/getting-started/best-practices-for-preventing-data-leaks-in-your-organization.md
@@ -111,13 +111,10 @@ At the organization level, if you're unable to coordinate with the user who push
 
 If you're unable to coordinate directly with the repository owner to remove data that you're confident you own, you can fill out a DMCA takedown notice form and tell GitHub Support. For more information, see [DMCA takedown notice](https://support.github.com/contact/dmca-takedown).
 
-{% note %}
-
-**Note:** If one of your repositories has been taken down due to a false claim, you should fill out a DMCA
+> [!NOTE]
+> If one of your repositories has been taken down due to a false claim, you should fill out a DMCA
 counter notice form and alert GitHub Support. For more information, see [DMCA counter notice](https://support.github.com/contact/dmca-counter-notice).
 
-{% endnote %}
-
 ## Next steps
 
 * "[AUTOTITLE](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)"
diff --git a/content/code-security/getting-started/dependabot-quickstart-guide.md b/content/code-security/getting-started/dependabot-quickstart-guide.md
index dd82f829e4..5d458e0cdf 100644
--- a/content/code-security/getting-started/dependabot-quickstart-guide.md
+++ b/content/code-security/getting-started/dependabot-quickstart-guide.md
@@ -47,11 +47,8 @@ You need to follow the steps below on the repository you forked in "[Prerequisit
 1. Under "Code security and analysis", to the right of {% data variables.product.prodname_dependabot_alerts %}, click **Enable** for {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}, and {% data variables.product.prodname_dependabot_version_updates %}.
 1. Optionally, if you are interested in experimenting with {% data variables.product.prodname_dependabot_version_updates %}, click **.github/dependabot.yml**. This will create a default `dependabot.yml` configuration file in the `/.github` directory of your repository. To enable {% data variables.product.prodname_dependabot_version_updates %} for your repository, you typically configure this file to suit your needs by editing the default file, and committing your changes. You can refer to the snippet provided in "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#example-dependabotyml-file)" for an example.
 
-{% note %}
-
-**Note:** If the dependency graph is not already enabled for the repository, {% data variables.product.prodname_dotcom %} will enable it automatically when you enable {% data variables.product.prodname_dependabot %}.
-
-{% endnote %}
+> [!NOTE]
+> If the dependency graph is not already enabled for the repository, {% data variables.product.prodname_dotcom %} will enable it automatically when you enable {% data variables.product.prodname_dependabot %}.
 
 For more information about configuring each of these {% data variables.product.prodname_dependabot %} features, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)," "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)," and "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
 
diff --git a/content/code-security/secret-scanning/secret-scanning-partnership-program/secret-scanning-partner-program.md b/content/code-security/secret-scanning/secret-scanning-partnership-program/secret-scanning-partner-program.md
index 5559f593a7..006ac2a266 100644
--- a/content/code-security/secret-scanning/secret-scanning-partnership-program/secret-scanning-partner-program.md
+++ b/content/code-security/secret-scanning/secret-scanning-partnership-program/secret-scanning-partner-program.md
@@ -120,17 +120,11 @@ You can retrieve the {% data variables.product.prodname_dotcom %} secret scannin
 will provide several `key_identifier` and public keys. You can determine which public
 key to use based on the value of `Github-Public-Key-Identifier`.
 
-{% note %}
+> [!NOTE]
+> When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required) or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required) as suggested in the samples below, or use a conditional request. For more information, see "[AUTOTITLE](/rest/guides/getting-started-with-the-rest-api#conditional-requests)."
 
-**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required) or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required) as suggested in the samples below, or use a conditional request. For more information, see "[AUTOTITLE](/rest/guides/getting-started-with-the-rest-api#conditional-requests)."
-
-{% endnote %}
-
-{% note %}
-
-**Note**: The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
-
-{% endnote %}
+> [!NOTE]
+> The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
 
 **Sample HTTP POST sent to verify endpoint**
 
@@ -403,8 +397,5 @@ A few important points:
 * For the hashed form of the raw token, you can only use SHA-256 to hash the token, not any other hashing algorithm.
 * The label indicates whether the token is a true ("true_positive") or a false positive ("false_positive"). Only these two lowercased literal strings are allowed.
 
-{% note %}
-
-**Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
-
-{% endnote %}
+> [!NOTE]
+> Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
diff --git a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning.md b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning.md
index 885f816a1d..bd693c2e19 100644
--- a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning.md
+++ b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning.md
@@ -66,11 +66,9 @@ Before defining a custom pattern, you must ensure that {% data variables.product
 {% endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}{% ifversion secret-scanning-push-protection-custom-patterns %}
 1. Optionally, to enable push protection for your custom pattern, click **Enable**.
-   {% note %}
 
-   **Note**: The "Enable" button isn't available until after the dry run succeeds and you publish the pattern.
-
-   {% endnote %}
+   > [!NOTE]
+   > The "Enable" button isn't available until after the dry run succeeds and you publish the pattern.
 
    For more information about push protection, see "[AUTOTITLE](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
 
@@ -139,19 +137,14 @@ After your pattern is created, {% data variables.product.prodname_secret_scannin
 
 Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
 
-{% note %}
-
+> [!NOTE]
 {% ifversion custom-pattern-dry-run-ga %}
-**Notes:**
-* At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run.
-* {% data reusables.secret-scanning.dry-runs-enterprise-permissions %}
+> * At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run.
+> * {% data reusables.secret-scanning.dry-runs-enterprise-permissions %}
 {% else %}
-**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.secret-scanning.alerts %}.
-
+> As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.secret-scanning.alerts %}.
 {% endif %}
 
-{% endnote %}
-
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}{% ifversion security-feature-enablement-policies %}
 {% data reusables.enterprise-accounts.code-security-and-analysis-policies %}
diff --git a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/excluding-folders-and-files-from-secret-scanning.md b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/excluding-folders-and-files-from-secret-scanning.md
index b69c704bec..55b183598a 100644
--- a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/excluding-folders-and-files-from-secret-scanning.md
+++ b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/excluding-folders-and-files-from-secret-scanning.md
@@ -45,13 +45,9 @@ You can configure a `secret_scanning.yml` file to exclude directories from {% da
       - "foo/bar/*.js"
     ```
 
-    {% note %}
-
-    **Notes:**
-    * If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans.
-    * If `secret_scanning.yml` is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file.
-
-    {% endnote %}
+    > [!NOTE]
+    > * If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans.
+    > * If `secret_scanning.yml` is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file.
 
 ## Verifying that the folder is excluded from {% data variables.product.prodname_secret_scanning %}
 
diff --git a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/deleting-a-custom-security-configuration.md b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/deleting-a-custom-security-configuration.md
index 8a468f586c..cec56aee37 100644
--- a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/deleting-a-custom-security-configuration.md
+++ b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/deleting-a-custom-security-configuration.md
@@ -15,11 +15,8 @@ topics:
 
 If you no longer need a {% data variables.product.prodname_custom_security_configuration %}, you can delete that configuration to ensure it will not be applied to any repositories in the future. If you are deleting a {% data variables.product.prodname_custom_security_configuration %} because you want to change the security enablement settings in that configuration, you can instead edit the configuration. For more information, see "[AUTOTITLE](/code-security/securing-your-organization/managing-the-security-of-your-organization/editing-a-custom-security-configuration)."
 
-{% warning %}
-
-**Warning:** Deleting a {% data variables.product.prodname_custom_security_configuration %} will detach all repositories that are linked to that configuration. The existing security settings for those repositories will be unchanged, but you must apply a different {% data variables.product.prodname_security_configuration %} or manage their security settings at the repository level to keep their settings up to date.
-
-{% endwarning %}
+> [!WARNING]
+> Deleting a {% data variables.product.prodname_custom_security_configuration %} will detach all repositories that are linked to that configuration. The existing security settings for those repositories will be unchanged, but you must apply a different {% data variables.product.prodname_security_configuration %} or manage their security settings at the repository level to keep their settings up to date.
 
 ## Deleting a {% data variables.product.prodname_custom_security_configuration %} from your organization
 
diff --git a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/editing-a-custom-security-configuration.md b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/editing-a-custom-security-configuration.md
index a8f4df27f2..7896a7e464 100644
--- a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/editing-a-custom-security-configuration.md
+++ b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/editing-a-custom-security-configuration.md
@@ -17,11 +17,8 @@ After creating and applying a {% data variables.product.prodname_custom_security
 
 To determine if your {% data variables.product.prodname_custom_security_configuration %} is meeting your security needs, see "[AUTOTITLE](/code-security/securing-your-organization/managing-the-security-of-your-organization/interpreting-security-findings)."
 
-{% note %}
-
-**Note:** The {% data variables.product.prodname_github_security_configuration %} is managed by {% data variables.product.company_short %} and cannot be edited. If you would like to customize your security enablement settings, you need to create a {% data variables.product.prodname_custom_security_configuration %}. For more information, see "[AUTOTITLE](/code-security/securing-your-organization/meeting-your-specific-security-needs-with-custom-security-configurations/creating-a-custom-security-configuration)."
-
-{% endnote %}
+> [!NOTE]
+> The {% data variables.product.prodname_github_security_configuration %} is managed by {% data variables.product.company_short %} and cannot be edited. If you would like to customize your security enablement settings, you need to create a {% data variables.product.prodname_custom_security_configuration %}. For more information, see "[AUTOTITLE](/code-security/securing-your-organization/meeting-your-specific-security-needs-with-custom-security-configurations/creating-a-custom-security-configuration)."
 
 ## Modifying your {% data variables.product.prodname_custom_security_configuration %}
 
diff --git a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/interpreting-security-findings.md b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/interpreting-security-findings.md
index 7be3af0d87..7ba4f7fe7c 100644
--- a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/interpreting-security-findings.md
+++ b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/interpreting-security-findings.md
@@ -70,11 +70,8 @@ For an introduction to {% data variables.product.prodname_dependabot_alerts %},
 
 To learn how to interpret and resolve {% data variables.product.prodname_dependabot_alerts %}, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
 
-{% note %}
-
-**Note:** If you enabled {% data variables.product.prodname_dependabot_security_updates %}, {% data variables.product.prodname_dependabot %} can also automatically raise pull requests to update the dependencies used in the repositories of the organization. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)."
-
-{% endnote %}
+> [!NOTE]
+> If you enabled {% data variables.product.prodname_dependabot_security_updates %}, {% data variables.product.prodname_dependabot %} can also automatically raise pull requests to update the dependencies used in the repositories of the organization. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)."
 
 ## Next steps
 
diff --git a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/managing-your-github-advanced-security-license-usage.md b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/managing-your-github-advanced-security-license-usage.md
index 69a65bfb43..9988cbdc84 100644
--- a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/managing-your-github-advanced-security-license-usage.md
+++ b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/managing-your-github-advanced-security-license-usage.md
@@ -55,12 +55,8 @@ To learn about GHAS licenses, as well as unique and active committers, see "[AUT
 1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Disable {% data variables.product.prodname_GH_advanced_security %}**.
 1. To finish disabling GHAS features on the selected private or internal repositories, in the "Disable {% data variables.product.prodname_GH_advanced_security %}?" window, click **Disable {% data variables.product.prodname_GH_advanced_security %}**.
 
-    {% note %}
-
-    **Notes:**
-    * Disabling GHAS features for a private or internal repository will also detach that repository from any linked {% data variables.product.prodname_security_configuration %}.
-    * Disabling GHAS features through the repository table _will not_ disable those features on public repositories since they do not require {% data variables.product.prodname_GH_advanced_security %} licenses.
-
-    {% endnote %}
+    > [!NOTE]
+    > * Disabling GHAS features for a private or internal repository will also detach that repository from any linked {% data variables.product.prodname_security_configuration %}.
+    > * Disabling GHAS features through the repository table _will not_ disable those features on public repositories since they do not require {% data variables.product.prodname_GH_advanced_security %} licenses.
 
 {% endif %}
diff --git a/content/code-security/securing-your-organization/meeting-your-specific-security-needs-with-custom-security-configurations/creating-a-custom-security-configuration.md b/content/code-security/securing-your-organization/meeting-your-specific-security-needs-with-custom-security-configurations/creating-a-custom-security-configuration.md
index 2268adb79a..b2401b83b7 100644
--- a/content/code-security/securing-your-organization/meeting-your-specific-security-needs-with-custom-security-configurations/creating-a-custom-security-configuration.md
+++ b/content/code-security/securing-your-organization/meeting-your-specific-security-needs-with-custom-security-configurations/creating-a-custom-security-configuration.md
@@ -19,11 +19,8 @@ With {% data variables.product.prodname_custom_security_configurations %}, you c
 
 ## Creating a {% data variables.product.prodname_custom_security_configuration %}
 
-{% note %}
-
-**Note:** The enablement status of some security features is dependent on other, higher-level security features. For example, disabling dependency graph will also disable {% data variables.product.prodname_dependabot %}, vulnerability exposure analysis, and security updates. For {% data variables.product.prodname_security_configurations %}, dependent security features are indicated with indentation and {% octicon "reply" aria-hidden="true" %}.
-
-{% endnote %}
+> [!NOTE]
+> The enablement status of some security features is dependent on other, higher-level security features. For example, disabling dependency graph will also disable {% data variables.product.prodname_dependabot %}, vulnerability exposure analysis, and security updates. For {% data variables.product.prodname_security_configurations %}, dependent security features are indicated with indentation and {% octicon "reply" aria-hidden="true" %}.
 
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.org_settings %}
@@ -37,11 +34,8 @@ With {% data variables.product.prodname_custom_security_configurations %}, you c
     * {% data variables.product.prodname_dependabot %}. To learn about {% data variables.product.prodname_dependabot %}, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
     * Security updates. To learn about security updates, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates)."
 
-    {% note %}
-
-    **Note:** You cannot manually change the enablement settings for vulnerable function calls. If {% data variables.product.prodname_GH_advanced_security %} features and {% data variables.product.prodname_dependabot_alerts %} are enabled, vulnerable function calls is also enabled. Otherwise, it is disabled.
-
-    {% endnote %}
+    > [!NOTE]
+    > You cannot manually change the enablement settings for vulnerable function calls. If {% data variables.product.prodname_GH_advanced_security %} features and {% data variables.product.prodname_dependabot_alerts %} are enabled, vulnerable function calls is also enabled. Otherwise, it is disabled.
 
 1. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the security settings table, choose whether you want to enable, disable, or keep the existing settings for {% data variables.product.prodname_code_scanning %} default setup. To learn about default setup, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning#about-default-setup)."
 1. In the "{% data variables.product.prodname_secret_scanning_caps %}" section of the security settings table, choose whether you want to enable, disable, or keep the existing settings for the following security features:
diff --git a/content/code-security/securing-your-organization/troubleshooting-security-configurations/a-repository-is-using-advanced-setup-for-code-scanning.md b/content/code-security/securing-your-organization/troubleshooting-security-configurations/a-repository-is-using-advanced-setup-for-code-scanning.md
index 7778017a96..d82ab32616 100644
--- a/content/code-security/securing-your-organization/troubleshooting-security-configurations/a-repository-is-using-advanced-setup-for-code-scanning.md
+++ b/content/code-security/securing-your-organization/troubleshooting-security-configurations/a-repository-is-using-advanced-setup-for-code-scanning.md
@@ -25,14 +25,11 @@ If you try to attach a {% data variables.product.prodname_security_configuration
 
 For all repositories without an active advanced setup, the {% data variables.product.prodname_security_configuration %} will be applied as expected, and {% data variables.product.prodname_code_scanning %} default setup will be enabled.
 
-{% note %}
-
-**Note:** If advanced setup is considered inactive for a repository, default setup _will_ still be enabled for that repository. Advanced setup is considered inactive for a repository if the repository meets any of the following criteria:
-* The latest {% data variables.product.prodname_codeql %} analysis is more than 90 days old
-* All {% data variables.product.prodname_codeql %} configurations have been deleted
-* The workflow file has been deleted or disabled (exclusively for YAML-based advanced setup)
-
-{% endnote %}
+> [!NOTE]
+> If advanced setup is considered inactive for a repository, default setup _will_ still be enabled for that repository. Advanced setup is considered inactive for a repository if the repository meets any of the following criteria:
+> * The latest {% data variables.product.prodname_codeql %} analysis is more than 90 days old
+> * All {% data variables.product.prodname_codeql %} configurations have been deleted
+> * The workflow file has been deleted or disabled (exclusively for YAML-based advanced setup)
 
 ## Solving the problem
 
diff --git a/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/about-coordinated-disclosure-of-security-vulnerabilities.md b/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/about-coordinated-disclosure-of-security-vulnerabilities.md
index 755cc4a681..33f21124ca 100644
--- a/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -64,11 +64,8 @@ The process for reporting and disclosing vulnerabilities for projects on {% data
 
  If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use.
 
-{% note %}
-
-**Note**: _For npm only_ - If we receive a report of malware in an npm package, we try to contact you privately. If you don't address the issue in a timely manner, we will disclose it. For more information, see "[Reporting malware in an npm package](https://docs.npmjs.com/reporting-malware-in-an-npm-package)" on the npm Docs website.
-
-{% endnote %}
+> [!NOTE]
+> _For npm only_ - If we receive a report of malware in an npm package, we try to contact you privately. If you don't address the issue in a timely manner, we will disclose it. For more information, see "[Reporting malware in an npm package](https://docs.npmjs.com/reporting-malware-in-an-npm-package)" on the npm Docs website.
 
  If you've found a security vulnerability in {% data variables.product.prodname_dotcom %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website.
 
@@ -84,9 +81,5 @@ The process for reporting and disclosing vulnerabilities for projects on {% data
 
  Private vulnerability reporting provides an easy way for vulnerability reporters to privately disclose security risks to repository maintainers, within {% data variables.product.prodname_dotcom %}, and in a way that immediately notifies the repository maintainers of the issue. For more information for security researchers and repository maintainers, see "[AUTOTITLE](/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)" and "[AUTOTITLE](/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/managing-privately-reported-security-vulnerabilities)", respectively.
 
-{% note %}
-
-**Note**:
-If the repository containing the vulnerability doesn't have private vulnerability reporting enabled, both security researchers and repository maintainers need to follow the instructions described in the "[Standard process](#standard-process)" section above.
-
-{% endnote %}
+> [!NOTE]
+> If the repository containing the vulnerability doesn't have private vulnerability reporting enabled, both security researchers and repository maintainers need to follow the instructions described in the "[Standard process](#standard-process)" section above.
diff --git a/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories.md b/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories.md
index b6bded7fe0..cd14cd02b0 100644
--- a/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories.md
+++ b/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories.md
@@ -87,11 +87,8 @@ For examples showing how affected versions are defined in some existing advisori
   * Each operator sequence must be specified as the operator, a single space, and then the version. For more information about valid operators, see [Supported operators](#supported-operators) above.
   * The version must begin with a number followed by any number of numbers, letters, dots, dashes, or underscores (anything other than a space or comma). For more information about version formatting, see [Version syntax](#version-syntax) above.
 
-   {% note %}
-
-   **Note:** Affected version strings cannot contain leading or trailing spaces.
-
-   {% endnote %}
+   > [!NOTE]
+   > Affected version strings cannot contain leading or trailing spaces.
 
 * Upper-bound operators can be inclusive or exclusive, i.e. `<=` or `<`, respectively.
 * Lower-bound operators can be inclusive or exclusive, i.e. `>=` or `>`, respectively. However, if you publish your repository advisory, and we graduate your repository advisory into a global advisory, a different rule applies: lower-bound strings can only be inclusive, i.e. `>=`. The exclusive lower bound operator (`>`) is only allowed when the version is `0`, for example `> 0`.
@@ -101,13 +98,10 @@ For examples showing how affected versions are defined in some existing advisori
    * Do not use a space between a number and a comma in `>= lower bound, <= upper bound`.
    * Use a space between a comma and the upper bound operator.
 
-  {% note %}
-
-  **Notes:** The lower-bound limitation:
-  * Is due to incompatibilities with the OSV schema.
-  * Only applies when you make a suggestion on an existing advisory in the {% data variables.product.prodname_advisory_database %}.
-
-  {% endnote %}
+  > [!NOTE]
+  > The lower-bound limitation:
+  > * Is due to incompatibilities with the OSV schema.
+  > * Only applies when you make a suggestion on an existing advisory in the {% data variables.product.prodname_advisory_database %}.
 
 * You cannot specify multiple affected version ranges in the same field, such as `> 2.0, < 2.3, > 3.0, < 3.2`.To specify more than one range, you must create a new **Affected products** section for each range, by clicking the **+ Add another affected product** button.
 
diff --git a/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability.md b/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability.md
index 5456097440..b9e710abcc 100644
--- a/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability.md
+++ b/content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability.md
@@ -15,15 +15,11 @@ redirect_from:
 
 {% data reusables.security-advisory.private-vulnerability-reporting-enable %}
 
-{% note %}
-
-**Notes:**
-* If you have admin or security permissions for a public repository, you don't need to submit a vulnerability report. Instead, you can create a draft security advisory directly. For more information, see "[AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/creating-a-repository-security-advisory)."
-* The ability to privately report a vulnerability in a repository is not related to the presence of a `SECURITY.md` file in that repository's root or `docs` directory.
-    * The `SECURITY.md` file contains the security policy for the repository. Repository administrators can add and use this file to provide _public_ instructions for how to report a security vulnerability in their repository. For more information, see "[AUTOTITLE](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
-    * You can only report a vulnerability privately for repositories where private vulnerability reporting is enabled, and you don't have to follow the instructions in the `SECURITY.md` file. This reporting process is fully private, and {% data variables.product.prodname_dotcom %} notifies the repository administrators directly about your submission.
-
-{% endnote %}
+> [!NOTE]
+> * If you have admin or security permissions for a public repository, you don't need to submit a vulnerability report. Instead, you can create a draft security advisory directly. For more information, see "[AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/creating-a-repository-security-advisory)."
+> * The ability to privately report a vulnerability in a repository is not related to the presence of a `SECURITY.md` file in that repository's root or `docs` directory.
+>     * The `SECURITY.md` file contains the security policy for the repository. Repository administrators can add and use this file to provide _public_ instructions for how to report a security vulnerability in their repository. For more information, see "[AUTOTITLE](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+>     * You can only report a vulnerability privately for repositories where private vulnerability reporting is enabled, and you don't have to follow the instructions in the `SECURITY.md` file. This reporting process is fully private, and {% data variables.product.prodname_dotcom %} notifies the repository administrators directly about your submission.
 
 ## About privately reporting a security vulnerability
 
diff --git a/content/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories.md b/content/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories.md
index 746d6e1364..b009c25350 100644
--- a/content/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories.md
+++ b/content/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories.md
@@ -24,11 +24,8 @@ Global security advisories are grouped into these categories: {% data variables.
 * {% data reusables.advisory-database.unreviewed-overview %}
 * {% data reusables.advisory-database.malware-overview %}
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_dependabot %} doesn't generate {% data variables.product.prodname_dependabot_alerts %} for unreviewed and malware advisories.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_dependabot %} doesn't generate {% data variables.product.prodname_dependabot_alerts %} for unreviewed and malware advisories.
 
 For more information about the {% data variables.product.prodname_advisory_database %}, see "[AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-the-github-advisory-database)."
 
diff --git a/content/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/browsing-security-advisories-in-the-github-advisory-database.md b/content/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/browsing-security-advisories-in-the-github-advisory-database.md
index 2975b7c3c2..93bc5c6ef8 100644
--- a/content/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/browsing-security-advisories-in-the-github-advisory-database.md
+++ b/content/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/browsing-security-advisories-in-the-github-advisory-database.md
@@ -30,11 +30,8 @@ You can access any advisory in the {% data variables.product.prodname_advisory_d
 1. Navigate to https://github.com/advisories.
 1. Optionally, to filter the list of advisories, use the search field or the drop-down menus at the top of the list.
 
-   {% note %}
-
-   **Note:** You can use the sidebar on the left to explore {% data variables.product.company_short %}-reviewed and unreviewed advisories separately, or to filter by ecosystem.
-
-   {% endnote %}
+   > [!NOTE]
+   > You can use the sidebar on the left to explore {% data variables.product.company_short %}-reviewed and unreviewed advisories separately, or to filter by ecosystem.
 
 1. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.
 
@@ -98,11 +95,10 @@ You can use your local advisory database to check whether a specific security vu
 
 1. Navigate to `https://HOSTNAME/advisories`.
 1. Optionally, to filter the list, use any of the drop-down menus.
-   {% note %}
 
-   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
+   > [!NOTE]
+   > Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
 
-   {% endnote %}
 1. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.
 
 You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
diff --git a/content/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/content/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
index edad72ae55..a53f716244 100644
--- a/content/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
+++ b/content/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
@@ -102,13 +102,10 @@ Additionally, there can be no merge conflicts, and {% data variables.product.pro
 1. In the "Security Advisories" list, click the name of the security advisory with changes that you'd like to merge.
 1. Scroll to the bottom of the advisory form. Then, under "This advisory is ready to be merged", click **Merge pull request(s)** to merge all open pull requests in the temporary private fork.
 
-   ![Screenshot of the "Collaborate on a patch" area of a draft security advisory. The "Merge pull requests" button is outlined in dark orange.](/assets/images/help/security/merge-pull-requests-button.png)
+  ![Screenshot of the "Collaborate on a patch" area of a draft security advisory. The "Merge pull requests" button is outlined in dark orange.](/assets/images/help/security/merge-pull-requests-button.png)
 
-  {% note %}
-
-  **Note:** You can only merge one pull request into the `main` branch of a temporary private fork. If more than one pull request targets the `main` branch, merging is blocked.
-
-  {% endnote %}
+  > [!NOTE]
+  > You can only merge one pull request into the `main` branch of a temporary private fork. If more than one pull request targets the `main` branch, merging is blocked.
 
 After you merge changes in a security advisory, you can publish the security advisory to alert your community about the security vulnerability in previous versions of your project. For more information, see "[AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/publishing-a-repository-security-advisory)."
 
diff --git a/content/code-security/security-advisories/working-with-repository-security-advisories/creating-a-repository-security-advisory.md b/content/code-security/security-advisories/working-with-repository-security-advisories/creating-a-repository-security-advisory.md
index dfa0a2f5b7..a9eb28455a 100644
--- a/content/code-security/security-advisories/working-with-repository-security-advisories/creating-a-repository-security-advisory.md
+++ b/content/code-security/security-advisories/working-with-repository-security-advisories/creating-a-repository-security-advisory.md
@@ -72,11 +72,8 @@ You can assign different types of credit to people.
 
 If someone accepts credit, the person's username appears in the "Credits" section of the security advisory. Anyone with read access to the repository can see the advisory and the people who accepted credit for it.
 
-{% note %}
-
-**Note:** If you believe you should be credited for a security advisory, please contact the creator of the advisory and to ask for the advisory to be edited to include your credit. Only the creator of the advisory can credit you, so please don't contact {% data variables.product.company_short %} Support about credits for security advisories.
-
-{% endnote %}
+> [!NOTE]
+> If you believe you should be credited for a security advisory, please contact the creator of the advisory and to ask for the advisory to be edited to include your credit. Only the creator of the advisory can credit you, so please don't contact {% data variables.product.company_short %} Support about credits for security advisories.
 
 ## Next steps
 
diff --git a/content/code-security/security-advisories/working-with-repository-security-advisories/publishing-a-repository-security-advisory.md b/content/code-security/security-advisories/working-with-repository-security-advisories/publishing-a-repository-security-advisory.md
index 0809bbcd9a..2b53d84797 100644
--- a/content/code-security/security-advisories/working-with-repository-security-advisories/publishing-a-repository-security-advisory.md
+++ b/content/code-security/security-advisories/working-with-repository-security-advisories/publishing-a-repository-security-advisory.md
@@ -39,28 +39,22 @@ When you publish a security advisory, you notify your community about the securi
 
 Before you publish a security advisory, you can privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)."
 
-{% warning %}
-
-**Warning**: Whenever possible, you should always add a fix version to a security advisory prior to publishing the advisory. If you don't, the advisory will be published without a fixed version, and {% data variables.product.prodname_dependabot %} will alert your users about the issue, without offering any safe version to update to.
-
-We recommend you take the following steps in these different situations:
-
-* If a fix version is imminently available, and you are able to, wait to disclose the issue when the fix is ready.
-* If a fix version is in development but not yet available, mention this in the advisory, and edit the advisory later, after publication.
-* If you are not planning to fix the issue, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue.
-
-{% endwarning %}
+> [!WARNING]
+> Whenever possible, you should always add a fix version to a security advisory prior to publishing the advisory. If you don't, the advisory will be published without a fixed version, and {% data variables.product.prodname_dependabot %} will alert your users about the issue, without offering any safe version to update to.
+>
+> We recommend you take the following steps in these different situations:
+>
+> * If a fix version is imminently available, and you are able to, wait to disclose the issue when the fix is ready.
+> * If a fix version is in development but not yet available, mention this in the advisory, and edit the advisory later, after publication.
+> * If you are not planning to fix the issue, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue.
 
 When you publish a draft advisory from a public repository, everyone is able to see:
 
 * The current version of the advisory data.
 * Any advisory credits that the credited users have accepted.
 
-{% note %}
-
-**Note**: The general public will never have access to the edit history of the advisory, and will only see the published version.
-
-{% endnote %}
+> [!NOTE]
+> The general public will never have access to the edit history of the advisory, and will only see the published version.
 
 After you publish a security advisory, the URL for the security advisory will remain the same as before you published the security advisory. Anyone with read access to the repository can see the security advisory. Collaborators on the security advisory can continue to view past conversations, including the full comment stream, in the security advisory unless someone with admin permissions removes the collaborator from the security advisory.
 
@@ -78,11 +72,8 @@ Publishing a security advisory deletes the temporary private fork for the securi
 
    ![Screenshot of the "Required advisory information has been provided" area of a draft security advisory. The "Publish advisory" button is outlined in dark orange.](/assets/images/help/security/publish-advisory-button.png)
 
-  {% note %}
-
-  **Note:** If you selected "Request CVE ID later", you will see a **Request CVE** button in place of the **Publish advisory** button. For more information, see "[Requesting a CVE identification number (Optional)](#requesting-a-cve-identification-number-optional)" below.
-
-  {% endnote %}
+  > [!NOTE]
+  > If you selected "Request CVE ID later", you will see a **Request CVE** button in place of the **Publish advisory** button. For more information, see "[Requesting a CVE identification number (Optional)](#requesting-a-cve-identification-number-optional)" below.
 
 ## {% data variables.product.prodname_dependabot_alerts %} for published security advisories
 
diff --git a/content/code-security/security-overview/exporting-data-from-security-overview.md b/content/code-security/security-overview/exporting-data-from-security-overview.md
index fc3a7cd790..34ef515779 100644
--- a/content/code-security/security-overview/exporting-data-from-security-overview.md
+++ b/content/code-security/security-overview/exporting-data-from-security-overview.md
@@ -24,11 +24,8 @@ The overview page contains data about security alerts across your organization,
 
 The CSV file you download will contain data corresponding to the filters you have applied to security overview. For example, if you add the filter `dependabot-alerts:enabled`, your file will only contain data for repositories that have enabled {% data variables.product.prodname_dependabot_alerts %}.
 
-{% note %}
-
-**Note:** In the "Teams" column of the CSV file, each repository will list a maximum of 20 teams with write access to that repository. If more than 20 teams have write access to a repository, the data will be truncated.
-
-{% endnote %}
+> [!NOTE]
+> In the "Teams" column of the CSV file, each repository will list a maximum of 20 teams with write access to that repository. If more than 20 teams have write access to a repository, the data will be truncated.
 
 ## Exporting data from your organization's security overview
 
@@ -42,10 +39,7 @@ The CSV file you download will contain data corresponding to the filters you hav
 
 {% ifversion secret-scanning-non-provider-patterns %}
 
-{% note %}
-
-**Note:** The summary views ({% ifversion security-overview-dashboard %}"Overview", {% endif %}"Coverage" and "Risk") show data only for {% ifversion secret-scanning-alert-experimental-list %}default{% else %}high confidence{% endif %} alerts. {% data variables.product.prodname_code_scanning_caps %} alerts from third-party tools, and {% data variables.product.prodname_secret_scanning %} alerts for non-provider patterns or for ignored directories are all omitted from these views. Consequently, files exported from the summary views do not contain data for these types of alert.
-
-{% endnote %}
+> [!NOTE]
+> The summary views ({% ifversion security-overview-dashboard %}"Overview", {% endif %}"Coverage" and "Risk") show data only for {% ifversion secret-scanning-alert-experimental-list %}default{% else %}high confidence{% endif %} alerts. {% data variables.product.prodname_code_scanning_caps %} alerts from third-party tools, and {% data variables.product.prodname_secret_scanning %} alerts for non-provider patterns or for ignored directories are all omitted from these views. Consequently, files exported from the summary views do not contain data for these types of alert.
 
 {% endif %}
diff --git a/content/code-security/security-overview/filtering-alerts-in-security-overview.md b/content/code-security/security-overview/filtering-alerts-in-security-overview.md
index 4c57fd103e..850df50113 100644
--- a/content/code-security/security-overview/filtering-alerts-in-security-overview.md
+++ b/content/code-security/security-overview/filtering-alerts-in-security-overview.md
@@ -75,11 +75,8 @@ These qualifiers are available in all views.
 
 ## Custom repository property filters
 
-{% note %}
-
-**Note:** Repository properties are in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> Repository properties are in {% data variables.release-phases.public_preview %} and subject to change.
 
 Custom repository properties are metadata that organization owners can add to repositories in an organization, providing a way to group repositories by the information you are interested in. For example, you can add custom repository properties for compliance frameworks or data sensitivity. For more information on adding custom repository properties, see "[AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)."
 
diff --git a/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md b/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
index e422506f6e..23b5c98f36 100644
--- a/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
+++ b/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
@@ -100,11 +100,10 @@ For more information, see {% ifversion ghec %}"[AUTOTITLE](/admin/identity-and-a
 ### Configure your personal account
 
 {% ifversion ghec or ghes %}
-{% note %}
 
-**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured, you may not be able to enable 2FA for your personal account.
+> [!NOTE]
+> Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured, you may not be able to enable 2FA for your personal account.
 
-{% endnote %}
 {% endif %}
 
 {% data variables.product.product_name %} supports several options for 2FA, and while any of them is better than nothing, the most secure option is a WebAuthn credential. WebAuthn requires an authenticator such as a FIDO2 hardware security key, a platform authenticator like Windows Hello, an Apple or Google phone, or a password manager. It's possible, although difficult, to phish other forms of 2FA (for example, someone asking you to read them your 6 digit one-time password). However WebAuthn is much more resistant to phishing, because domain scoping is built into the protocol, which prevents credentials from a website impersonating the login page from being used on {% data variables.product.product_name %}.
@@ -114,11 +113,10 @@ When you set up 2FA, you should always download the recovery codes and set up mo
 ### Configure your organization account
 
 {% ifversion ghec or ghes %}
-{% note %}
 
-**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured, you may not be able to require 2FA for your organization.
+> [!NOTE]
+> Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured, you may not be able to require 2FA for your organization.
 
-{% endnote %}
 {% endif %}
 
 If you're an organization owner, you can see which users don't have 2FA enabled, help them get set up, and then require 2FA for your organization. To guide you through that process, see:
diff --git a/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
index d6ff8da471..bf4199b74c 100644
--- a/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
+++ b/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
@@ -65,11 +65,8 @@ Code often needs to communicate with other systems over a network, and requires
 
 ### Automatic detection of secrets committed to a repository
 
-{% note %}
-
-**Note:** {% data reusables.gated-features.secret-scanning %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.gated-features.secret-scanning %}
 
 {% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
 
@@ -102,11 +99,8 @@ Besides your code, you probably need to use secrets in other places. For example
 
 ## Keep vulnerable coding patterns out of your repository
 
-{% note %}
-
-**Note:** {% data reusables.gated-features.code-scanning %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.gated-features.code-scanning %}
 
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
index b643b80e86..ced0527083 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
@@ -72,11 +72,9 @@ Here is a list of common configuration options.  For more information, and a ful
 | `external-repo-token` | {% octicon "x" aria-label="Optional" %} | Specifies a token for fetching the configuration file, if the file resides in a private external repository. The token must have read access to the repository.|
 
 {% ifversion dependency-review-action-licenses %}
-{% tip %}
 
-**Tip:** The  `allow-licenses` and  `deny-licenses` options are mutually exclusive.
-
-{% endtip %}
+> [!TIP]
+> The  `allow-licenses` and  `deny-licenses` options are mutually exclusive.
 
 ## Configuring the {% data variables.dependency-review.action_name %}
 
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
index ab3a0c75e9..4ae6c4b68d 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
@@ -65,11 +65,10 @@ Dependencies submitted to a project using the {% data variables.dependency-submi
 If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}.
 
 {% ifversion ghes %}
-{% note %}
 
-**Note:** {% data variables.product.product_name %} does not populate the **Dependents** view.
+> [!NOTE]
+> {% data variables.product.product_name %} does not populate the **Dependents** view.
 
-{% endnote %}
 {% endif %}
 
 {% ifversion fpt or ghec %}
diff --git a/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 74d75ca0c9..a727117fcd 100644
--- a/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -22,11 +22,8 @@ For information on choosing a machine type when you create a codespace, see "[AU
 
 ## Changing the machine type
 
-{% note %}
-
-**Note**: {% data reusables.codespaces.codespaces-machine-type-availability %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.codespaces.codespaces-machine-type-availability %}
 
 {% webui %}
 
diff --git a/content/codespaces/customizing-your-codespace/changing-the-shell-in-a-codespace.md b/content/codespaces/customizing-your-codespace/changing-the-shell-in-a-codespace.md
index d14d070da2..c2f120985a 100644
--- a/content/codespaces/customizing-your-codespace/changing-the-shell-in-a-codespace.md
+++ b/content/codespaces/customizing-your-codespace/changing-the-shell-in-a-codespace.md
@@ -68,11 +68,8 @@ If the shell you install isn't detected automatically, you can add a new termina
 
 You can set a default terminal profile to choose the default shell used for all new terminal windows you open in {% data variables.product.prodname_vscode_shortname %}. The default terminal profile is dependent on your operating system, so you can set a default profile for Linux, if you're using the {% data variables.product.prodname_vscode_shortname %} web client, or for your local operating system, if you're using the desktop application.
 
-{% note %}
-
-**Note:** Regardless of your default profile, codespaces opened in the web client always open with a `bash` session running initially.
-
-{% endnote %}
+> [!NOTE]
+> Regardless of your default profile, codespaces opened in the web client always open with a `bash` session running initially.
 
 {% data reusables.codespaces.access-user-settings %}
 1. Inside the JSON object, to set the default shell for the relevant operating system, add lines or edit existing lines like the following.
@@ -113,11 +110,8 @@ sudo apt-get install -y csh
 sudo chsh "$(id -un)" --shell "/usr/bin/csh"
 ```
 
-{% note %}
-
-**Note**: If you create a new codespace (for example by using `gh codespace create`), you must wait sufficient time to ensure the script has finished running before you connect to the codespace over SSH. If the script hasn't finished running, you will connect to a default `bash` session.
-
-{% endnote %}
+> [!NOTE]
+> If you create a new codespace (for example by using `gh codespace create`), you must wait sufficient time to ensure the script has finished running before you connect to the codespace over SSH. If the script hasn't finished running, you will connect to a default `bash` session.
 
 When you have connected to the codespace, for most shells, you can use the command `readlink /proc/$$/exe` to check the correct shell is running.
 
diff --git a/content/codespaces/developing-in-a-codespace/connecting-to-a-private-network.md b/content/codespaces/developing-in-a-codespace/connecting-to-a-private-network.md
index 47b27061b6..5d93259c62 100644
--- a/content/codespaces/developing-in-a-codespace/connecting-to-a-private-network.md
+++ b/content/codespaces/developing-in-a-codespace/connecting-to-a-private-network.md
@@ -25,11 +25,8 @@ There are currently two methods of accessing resources on a private network with
 
 ### Using the GitHub CLI extension to access remote resources
 
-{% warning %}
-
-**Warning**: The {% data variables.product.prodname_cli %} extension is {% data variables.release-phases.closing_down %} and is no longer supported.
-
-{% endwarning %}
+> [!WARNING]
+> The {% data variables.product.prodname_cli %} extension is {% data variables.release-phases.closing_down %} and is no longer supported.
 
 The {% data variables.product.prodname_cli %} extension allows you to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. The codespace uses your local machine as a network gateway to reach those resources. For more information, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)."
 
diff --git a/content/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository.md b/content/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository.md
index de72b9d31d..6fe81f2b77 100644
--- a/content/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository.md
+++ b/content/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository.md
@@ -34,20 +34,16 @@ Organizations can enable members and outside collaborators to create and use cod
 {% data reusables.codespaces.when-you-can-create-codespaces %}
 
 {% ifversion ghec %}
-{% note %}
 
-**Note:** {% data reusables.codespaces.emus-create-codespaces %}
+> [!NOTE]
+> {% data reusables.codespaces.emus-create-codespaces %}
 
-{% endnote %}
 {% endif %}
 
 {% data reusables.codespaces.starting-new-project-template %} For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template)."
 
-{% note %}
-
-**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide)."
-
-{% endnote %}
+> [!NOTE]
+> If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide)."
 
 If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch.
 
@@ -107,17 +103,12 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
 
          The options page may also display the names of one or more secrets that it's recommended you create in your {% data variables.product.prodname_codespaces %} settings. For more information, see "[Recommended secrets](#recommended-secrets)."
 
-         {% note %}
-
-         **Notes**
-
-         * You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
-         * The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
-         * For more information about dev container configuration files, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
-         * For more information about machine types, see "[AUTOTITLE](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
-         * {% data reusables.codespaces.codespaces-machine-type-availability %}
-
-         {% endnote %}
+         > [!NOTE]
+         > * You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
+         > * The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
+         > * For more information about dev container configuration files, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
+         > * For more information about machine types, see "[AUTOTITLE](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+         > * {% data reusables.codespaces.codespaces-machine-type-availability %}
 
       1. Click **Create codespace**.
 
diff --git a/content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md b/content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md
index c3d90ed0fc..7d30168946 100644
--- a/content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md
+++ b/content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md
@@ -27,11 +27,10 @@ If you're starting a new project, you can get started with development work quic
 You can start from a blank template, choose from templates maintained by {% data variables.product.company_short %} for popular technologies such as React or Jupyter Notebook, or launch a codespace from any template repository on {% data variables.product.prodname_dotcom %}.
 
 {% ifversion ghec %}
-{% note %}
 
-**Note:** If you have a {% data variables.enterprise.prodname_managed_user %}, you cannot use {% data variables.product.company_short %}'s public templates for {% data variables.product.prodname_github_codespaces %}, because you can only create codespaces that are owned and paid for by your organization or enterprise. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)."
+> [!NOTE]
+> If you have a {% data variables.enterprise.prodname_managed_user %}, you cannot use {% data variables.product.company_short %}'s public templates for {% data variables.product.prodname_github_codespaces %}, because you can only create codespaces that are owned and paid for by your organization or enterprise. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)."
 
-{% endnote %}
 {% endif %}
 
 With a blank template, you'll start with an empty directory, with access to cloud-based compute resources and the tools, languages, and runtime environments that come preinstalled with the default dev container image. With other templates, you'll get starter files for the technology you're working with, plus typically some extra files such as a README file, a `.gitignore` file, and dev container configuration files containing some custom environment configuration. For more information on dev containers and the default image, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
@@ -42,11 +41,8 @@ As an example, if you create a codespace from {% data variables.product.company_
 
 The files and configuration included in templates are defined in template repositories. The template repository is cloned into your codespace when you create the codespace. After that, the link is severed, and your codespace won't be linked to a remote repository until you publish to one.
 
-{% tip %}
-
-**Tip:** To help people get started with your framework, library, or other project, you can set up a template repository for use with {% data variables.product.prodname_github_codespaces %}. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/setting-up-a-template-repository-for-github-codespaces)."
-
-{% endtip %}
+> [!TIP]
+> To help people get started with your framework, library, or other project, you can set up a template repository for use with {% data variables.product.prodname_github_codespaces %}. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/setting-up-a-template-repository-for-github-codespaces)."
 
 ## Creating a codespace from a {% data variables.product.company_short %} template
 
@@ -69,11 +65,8 @@ You can create a codespace from any template repository, then publish your work
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.codespaces.use-this-template %}
 
-   {% note %}
-
-   **Note:** If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-hidden="true" %} Code** dropdown. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
-
-   {% endnote %}
+   > [!NOTE]
+   > If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-hidden="true" %} Code** dropdown. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
 
 {% data reusables.codespaces.template-codespaces-default-editor %}
 
diff --git a/content/codespaces/developing-in-a-codespace/default-environment-variables-for-your-codespace.md b/content/codespaces/developing-in-a-codespace/default-environment-variables-for-your-codespace.md
index 13dba8f1ab..561617e2b9 100644
--- a/content/codespaces/developing-in-a-codespace/default-environment-variables-for-your-codespace.md
+++ b/content/codespaces/developing-in-a-codespace/default-environment-variables-for-your-codespace.md
@@ -18,11 +18,8 @@ redirect_from:
 
 {% data variables.product.prodname_dotcom %} sets default environment variables for every codespace. Commands run in codespaces can create, read, and modify environment variables.
 
-{% note %}
-
-**Note**: Environment variables are case-sensitive.
-
-{% endnote %}
+> [!NOTE]
+> Environment variables are case-sensitive.
 
 ## List of default environment variables
 
diff --git a/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md b/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md
index 26d284a072..dd3e8ee781 100644
--- a/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md
+++ b/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md
@@ -27,11 +27,8 @@ You can manually delete a codespace in a variety of ways:
 
 Use the tabs at the top of this article to display instructions for each of these ways of deleting a codespace.
 
-{% note %}
-
-**Note**: You can't delete a codespace from within the JetBrains Gateway, or the JetBrains client application, or from within JupyterLab.
-
-{% endnote %}
+> [!NOTE]
+> You can't delete a codespace from within the JetBrains Gateway, or the JetBrains client application, or from within JupyterLab.
 
 ## Why you should delete unused codespaces
 
@@ -50,11 +47,8 @@ There are costs associated with storing codespaces. You should therefore delete
 
 {% endwebui %}
 
-{% note %}
-
-**Note**: You may have prebuild codespaces that are consuming additional storage which are not displayed on this dashboard. To delete them, follow the steps for “[Deleting a prebuild configuration](/codespaces/prebuilding-your-codespaces/managing-prebuilds#deleting-a-prebuild-configuration).”
-
-{% endnote %}
+> [!NOTE]
+> You may have prebuild codespaces that are consuming additional storage which are not displayed on this dashboard. To delete them, follow the steps for “[Deleting a prebuild configuration](/codespaces/prebuilding-your-codespaces/managing-prebuilds#deleting-a-prebuild-configuration).”
 
 {% vscode %}
 
diff --git a/content/codespaces/developing-in-a-codespace/forwarding-ports-in-your-codespace.md b/content/codespaces/developing-in-a-codespace/forwarding-ports-in-your-codespace.md
index 7ac72db934..04242a0b0f 100644
--- a/content/codespaces/developing-in-a-codespace/forwarding-ports-in-your-codespace.md
+++ b/content/codespaces/developing-in-a-codespace/forwarding-ports-in-your-codespace.md
@@ -162,11 +162,8 @@ Copy the address and paste it somewhere for later use.
 
 1. Copy the token.
 
-   {% note %}
-
-   **Important**: Don't share this access token with anyone.
-
-   {% endnote %}
+   > [!IMPORTANT]
+   > Don't share this access token with anyone.
 
 1. Exit the SSH session.
 
diff --git a/content/codespaces/developing-in-a-codespace/getting-started-with-github-codespaces-for-machine-learning.md b/content/codespaces/developing-in-a-codespace/getting-started-with-github-codespaces-for-machine-learning.md
index bb31d23f79..a3722a0933 100644
--- a/content/codespaces/developing-in-a-codespace/getting-started-with-github-codespaces-for-machine-learning.md
+++ b/content/codespaces/developing-in-a-codespace/getting-started-with-github-codespaces-for-machine-learning.md
@@ -63,11 +63,8 @@ You can open your codespace in JupyterLab from the "Your codespaces" page at [gi
 
 ## Configuring NVIDIA CUDA for your codespace
 
-{% note %}
-
-**Note**: This section only applies to customers who can create codespaces on machines that use a GPU. The ability to choose a machine type that uses a GPU was offered to selected customers during a trial period. This option is not generally available.
-
-{% endnote %}
+> [!NOTE]
+> This section only applies to customers who can create codespaces on machines that use a GPU. The ability to choose a machine type that uses a GPU was offered to selected customers during a trial period. This option is not generally available.
 
 Some software requires you to install NVIDIA CUDA to use your codespace’s GPU. Where this is the case, you can create your own custom configuration, by using a `devcontainer.json` file, and specify that CUDA should be installed. For more information on creating a custom configuration, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)."
 
diff --git a/content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md b/content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md
index 5de714bf15..75f0175ba4 100644
--- a/content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md
+++ b/content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md
@@ -52,11 +52,8 @@ You can quickly resume a codespace when you're viewing a repository on {% data v
 
    Alternatively, if you want to create a new codespace for this branch of the repository, click **Create a new one**.
 
-   {% note %}
-
-   **Note**: If you don't have an existing codespace for this branch, the page is titled "Create codespace" and a button labeled **Create a new codespace** is displayed.
-
-   {% endnote %}
+   > [!NOTE]
+   > If you don't have an existing codespace for this branch, the page is titled "Create codespace" and a button labeled **Create a new codespace** is displayed.
 
 You can bookmark the address of this page if you want to get back to it quickly to resume your codespace. Alternatively you can use the address in a link to provide other people with a quick way of creating and resuming their own codespaces for this repository.
 
@@ -91,11 +88,8 @@ You can bookmark the address of this page if you want to get back to it quickly
 
 ## Reopening an existing codespace
 
-{% note %}
-
-**Note:** {% data reusables.codespaces.using-codespaces-in-vscode %} See "[AUTOTITLE](/codespaces/developing-in-a-codespace/using-github-codespaces-in-visual-studio-code)."
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.codespaces.using-codespaces-in-vscode %} See "[AUTOTITLE](/codespaces/developing-in-a-codespace/using-github-codespaces-in-visual-studio-code)."
 
 1. In the {% data variables.product.prodname_vscode_shortname %} desktop application, open the Command Palette with <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
 1. Type "Codespaces" and select one of the following commands.
@@ -128,11 +122,8 @@ You can also access the commands listed above by navigating to the Remote Explor
      gh codespace code
      ```
 
-     {% note %}
-
-     **Note**: You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. See "[Setting up {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
-
-     {% endnote %}
+     > [!NOTE]
+     > You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. See "[Setting up {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
 
    * To open a codespace in the browser, enter:
 
@@ -146,11 +137,8 @@ You can also access the commands listed above by navigating to the Remote Explor
      gh codespace jupyter
      ```
 
-     {% note %}
-
-     **Note**: {% data reusables.codespaces.jupyterlab-installed-in-codespace %}
-
-     {% endnote %}
+     > [!NOTE]
+     > {% data reusables.codespaces.jupyterlab-installed-in-codespace %}
 
    * To access a codespace from the command line, over SSH, enter:
 
diff --git a/content/codespaces/developing-in-a-codespace/using-github-codespaces-in-visual-studio-code.md b/content/codespaces/developing-in-a-codespace/using-github-codespaces-in-visual-studio-code.md
index 59b96105fb..e91ece92b5 100644
--- a/content/codespaces/developing-in-a-codespace/using-github-codespaces-in-visual-studio-code.md
+++ b/content/codespaces/developing-in-a-codespace/using-github-codespaces-in-visual-studio-code.md
@@ -58,11 +58,8 @@ Use the {% data variables.product.prodname_vscode_marketplace %} to install the
 
 {% data reusables.codespaces.codespaces-machine-types %} You can change the machine type of your codespace at any time.
 
-{% note %}
-
-**Note**: {% data reusables.codespaces.codespaces-machine-type-availability %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.codespaces.codespaces-machine-type-availability %}
 
 {% data reusables.codespaces.changing-machine-type-in-vscode %}
 
diff --git a/content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md b/content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md
index 537c097d0b..fe2e290ba6 100644
--- a/content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md
+++ b/content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md
@@ -23,11 +23,8 @@ After installing the JetBrains Gateway, you can set JetBrains as your default ed
 
 When you work in a codespace, you use the JetBrains thin client application on your local computer. This provides the graphical interface for the full JetBrains IDE of your choice, which runs on the remote virtual machine that hosts your codespace. The thin client is always used, even if the full JetBrains IDE is installed locally. Any local JetBrains IDE settings are imported and used by the thin client.
 
-{% note %}
-
-**Note:** Only existing codespaces are available in the JetBrains Gateway. You can create codespaces in {% data variables.product.github %}, or by using {% data variables.product.prodname_cli %}. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository)."
-
-{% endnote %}
+> [!NOTE]
+> Only existing codespaces are available in the JetBrains Gateway. You can create codespaces in {% data variables.product.github %}, or by using {% data variables.product.prodname_cli %}. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository)."
 
 ### The JetBrains remote development connection process
 
@@ -72,11 +69,8 @@ You must have an existing codespace to connect to, and the virtual machine that
 
 For more information about the `devcontainer.json` file and the default container image, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
 
-{% note %}
-
-**Note**: For help with connecting to your codespace over SSH, see "[AUTOTITLE](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients?tool=jetbrains#ssh-connection-issues)."
-
-{% endnote %}
+> [!NOTE]
+> For help with connecting to your codespace over SSH, see "[AUTOTITLE](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients?tool=jetbrains#ssh-connection-issues)."
 
 ## Setting up the JetBrains Gateway
 
diff --git a/content/codespaces/developing-in-a-codespace/using-github-codespaces-with-github-cli.md b/content/codespaces/developing-in-a-codespace/using-github-codespaces-with-github-cli.md
index ac60d2869d..845ea364d4 100644
--- a/content/codespaces/developing-in-a-codespace/using-github-codespaces-with-github-cli.md
+++ b/content/codespaces/developing-in-a-codespace/using-github-codespaces-with-github-cli.md
@@ -63,11 +63,8 @@ The sections below give example commands for each of the available operations.
 
 For a complete reference of `gh` commands for {% data variables.product.prodname_github_codespaces %}, including details of all available options for each command, see the {% data variables.product.prodname_cli %} online help for "[gh codespace](https://cli.github.com/manual/gh_codespace)." Alternatively, on the command line, use `gh codespace --help` for general help or `gh codespace SUBCOMMAND --help` for help with a specific subcommand.
 
-{% note %}
-
-**Note**: The `-c CODESPACE_NAME` flag, used with many commands, is optional. If you omit it a list of codespaces is displayed for you to choose from.
-
-{% endnote %}
+> [!NOTE]
+> The `-c CODESPACE_NAME` flag, used with many commands, is optional. If you omit it a list of codespaces is displayed for you to choose from.
 
 ### List all of your codespaces
 
@@ -148,13 +145,10 @@ To run commands on the remote codespace machine, from your terminal, you can SSH
 gh codespace ssh -c CODESPACE-NAME
 ```
 
-{% note %}
-
-**Note**: {% data reusables.codespaces.ssh-server-installed %}
-
-<br>For more information about the `devcontainer.json` file and the default container image, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.codespaces.ssh-server-installed %}
+>
+> For more information about the `devcontainer.json` file and the default container image, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
 
 {% data variables.product.prodname_github_codespaces %} creates a local SSH key automatically to provide a seamless authentication experience. For more information on connecting with SSH, see [`gh codespace ssh`](https://cli.github.com/manual/gh_codespace_ssh).
 
@@ -254,11 +248,8 @@ For more information about the creation log, see "[AUTOTITLE](/codespaces/troubl
 
 You can use the {% data variables.product.prodname_cli %} extension to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. For more information on using the extension, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)."
 
-{% note %}
-
-**Note**: The {% data variables.product.prodname_cli %} extension is currently in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> The {% data variables.product.prodname_cli %} extension is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 ### Change the machine type of a codespace
 
diff --git a/content/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace.md b/content/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace.md
index 4b426c237d..46263a6270 100644
--- a/content/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace.md
+++ b/content/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace.md
@@ -44,11 +44,8 @@ A typical workflow for updating a file using {% data variables.product.prodname_
 * Commit the change.
 * Raise a pull request.
 
-{% note %}
-
-**Note:** By default, {% data variables.product.prodname_github_codespaces %} uses the HTTPS protocol to transfer data to and from a remote repository, and authenticates with a `GITHUB_TOKEN` configured with read and write access to the repository from which you create the codespace. If you're having issues with authentication, see "[AUTOTITLE](/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository)."
-
-{% endnote %}
+> [!NOTE]
+> By default, {% data variables.product.prodname_github_codespaces %} uses the HTTPS protocol to transfer data to and from a remote repository, and authenticates with a `GITHUB_TOKEN` configured with read and write access to the repository from which you create the codespace. If you're having issues with authentication, see "[AUTOTITLE](/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository)."
 
 ## About automatic forking
 
@@ -60,14 +57,9 @@ If you make a commit from the codespace, or push a new branch, {% data variables
 
 If you make a commit from the command line, you will see a prompt asking if you would like to proceed with linking your codespace to a new or existing fork. Enter `y` to proceed. If you commit changes from the **Source Control** view in {% data variables.product.prodname_vscode_shortname %}, or from the navigation bar in a JetBrains IDE, your codespace is automatically linked to a fork without you being prompted.
 
-{% note %}
-
-**Notes:**
-
-* If you delete your fork repository, then any codespaces linked to the fork are deleted, even if you originally created them from the upstream repository.
-* If you make a commit from the command line and refuse the new fork by entering `n`, you should push your changes from the command line rather than from {% data variables.product.prodname_vscode_shortname %}'s Source Control view. If you use the Source Control view, {% data variables.product.prodname_vscode_shortname %} will still try to create a fork for you on push.
-
-{% endnote %}
+> [!NOTE]
+> * If you delete your fork repository, then any codespaces linked to the fork are deleted, even if you originally created them from the upstream repository.
+> * If you make a commit from the command line and refuse the new fork by entering `n`, you should push your changes from the command line rather than from {% data variables.product.prodname_vscode_shortname %}'s Source Control view. If you use the Source Control view, {% data variables.product.prodname_vscode_shortname %} will still try to create a fork for you on push.
 
 When {% data variables.product.prodname_github_codespaces %} creates a fork, or links your codespace to an existing fork, the following things happen.
 
@@ -121,11 +113,8 @@ For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-re
 
      ![Screenshot of the branches pop-up menu with the "origin/templates" branch selected and "Checkout" selected in the submenu.](/assets/images/help/codespaces/jetbrains-checkout-submenu.png)
 
-     {% tip %}
-
-     **Tip**: If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace.
-
-     {% endtip %}
+     > [!TIP]
+     > If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace.
 
 ## Committing your changes
 
diff --git a/content/codespaces/developing-in-a-codespace/working-collaboratively-in-a-codespace.md b/content/codespaces/developing-in-a-codespace/working-collaboratively-in-a-codespace.md
index 5dc908a2cd..e1d8aac93a 100644
--- a/content/codespaces/developing-in-a-codespace/working-collaboratively-in-a-codespace.md
+++ b/content/codespaces/developing-in-a-codespace/working-collaboratively-in-a-codespace.md
@@ -43,11 +43,8 @@ For more information about Live Share, see "[What is {% data variables.product.p
 
 1. Send the link in your clipboard to anyone you want to join you in your Live Share session.
 
-   {% note %}
-
-   **Important**: Given the level of access Live Share sessions can provide to guests, you should only share with people you trust, and you should think through the implications of what you are sharing. For more information, see "[Security features of Live Share](https://learn.microsoft.com/en-us/visualstudio/liveshare/reference/security)" in the {% data variables.product.prodname_vs %} documentation.
-
-   {% endnote %}
+   > [!IMPORTANT]
+   > Given the level of access Live Share sessions can provide to guests, you should only share with people you trust, and you should think through the implications of what you are sharing. For more information, see "[Security features of Live Share](https://learn.microsoft.com/en-us/visualstudio/liveshare/reference/security)" in the {% data variables.product.prodname_vs %} documentation.
 
 ## Stopping a Live Share session
 
diff --git a/content/codespaces/getting-started/deep-dive.md b/content/codespaces/getting-started/deep-dive.md
index 30516c7a89..524137fcf0 100644
--- a/content/codespaces/getting-started/deep-dive.md
+++ b/content/codespaces/getting-started/deep-dive.md
@@ -28,11 +28,8 @@ Your codespace can be ephemeral if you need to test something or you can return
 
 For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository)," "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template)," and "[AUTOTITLE](/codespaces/developing-in-a-codespace/opening-an-existing-codespace)."
 
-{% note %}
-
-**Note**: You can create more than one codespace per repository or even per branch. However, there are limits to the number of codespaces you can create, and the number of codespaces you can run at the same time. If you reach the maximum number of codespaces and try to create another, a message is displayed telling you that you must remove an existing codespace before you can create a new one.
-
-{% endnote %}
+> [!NOTE]
+> You can create more than one codespace per repository or even per branch. However, there are limits to the number of codespaces you can create, and the number of codespaces you can run at the same time. If you reach the maximum number of codespaces and try to create another, a message is displayed telling you that you must remove an existing codespace before you can create a new one.
 
 ### The codespace creation process
 
@@ -48,13 +45,10 @@ A [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-cl
 
 {% data variables.product.prodname_github_codespaces %} uses a Docker container as the development environment. This container is created based on configurations that you can define in a `devcontainer.json` file and, optionally, a Dockerfile. If you create a codespace from {% data variables.product.company_short %}'s blank template, or from a repository with no `devcontainer.json` file, {% data variables.product.prodname_github_codespaces %} uses a default image, which has many languages and runtimes available. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)." For details of what the default image for dev containers includes, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal) repository.
 
-{% note %}
-
-**Note:** If you want to use Git hooks in your codespace and apply anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) to your codespace, then you must set up hooks during step 4 after the container is created.
-
-Since your repository is cloned onto the host VM before the container is created, anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) will not apply in your codespace unless you set up hooks in your `devcontainer.json` configuration file using the `postCreateCommand` in step 4. For more information, see "[Step 4: Post-creation setup](#step-4-post-creation-setup)."
-
-{% endnote %}
+> [!NOTE]
+> If you want to use Git hooks in your codespace and apply anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) to your codespace, then you must set up hooks during step 4 after the container is created.
+>
+> Since your repository is cloned onto the host VM before the container is created, anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) will not apply in your codespace unless you set up hooks in your `devcontainer.json` configuration file using the `postCreateCommand` in step 4. For more information, see "[Step 4: Post-creation setup](#step-4-post-creation-setup)."
 
 ### Step 3: Connecting to the codespace
 
@@ -128,11 +122,8 @@ If you're working in a codespace created from a template, Git is installed by de
 
 For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace)."
 
-{% note %}
-
-**Note:** Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate.
-
-{% endnote %}
+> [!NOTE]
+> Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate.
 
 ## Personalizing your codespace with extensions or plugins
 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md
index 73cbf0939f..189f12aca9 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md
@@ -41,11 +41,10 @@ If an organization chooses for codespaces to be **organization-owned**, the orga
 For more information about enabling {% data variables.product.prodname_github_codespaces %} for members and collaborators, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization)."
 
 {% ifversion ghec %}
-{% note %}
 
-**Note:** If you own an {% data variables.enterprise.prodname_emu_org %} and do not allow {% data variables.product.prodname_github_codespaces %} to be billed to your organization, members with {% data variables.enterprise.prodname_managed_users %} will not be able to use {% data variables.product.prodname_github_codespaces %}. See "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)."
+> [!NOTE]
+> If you own an {% data variables.enterprise.prodname_emu_org %} and do not allow {% data variables.product.prodname_github_codespaces %} to be billed to your organization, members with {% data variables.enterprise.prodname_managed_users %} will not be able to use {% data variables.product.prodname_github_codespaces %}. See "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)."
 
-{% endnote %}
 {% endif %}
 
 ## About ownership of codespaces
@@ -72,11 +71,8 @@ If you change from **user ownership** to **organization ownership**, existing co
 
 ## Choosing who owns and pays for codespaces
 
-{% note %}
-
-**Note:** If you cannot access the option to make codespaces **organization-owned**, this may be because you have disabled {% data variables.product.prodname_github_codespaces %} for all users in your organization's private{% ifversion ghec %} and internal{% endif %} repositories. See "[About choosing who pays for codespaces](#about-choosing-who-pays-for-codespaces)."
-
-{% endnote %}
+> [!NOTE]
+> If you cannot access the option to make codespaces **organization-owned**, this may be because you have disabled {% data variables.product.prodname_github_codespaces %} for all users in your organization's private{% ifversion ghec %} and internal{% endif %} repositories. See "[About choosing who pays for codespaces](#about-choosing-who-pays-for-codespaces)."
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/content/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization.md
index 082ef70583..d4d9f31fe6 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization.md
@@ -42,11 +42,10 @@ In addition, to allow users to create codespaces, you must ensure that{% ifversi
 * Your{% else %} your{% endif %} organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% ifversion fpt %}
-{% note %}
 
-**Note:** If you are a verified educator or a teacher, you must enable {% data variables.product.prodname_github_codespaces %} from a {% data variables.product.prodname_classroom %} to use your {% data variables.product.prodname_codespaces %} Education benefit. For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)."
+> [!NOTE]
+> If you are a verified educator or a teacher, you must enable {% data variables.product.prodname_github_codespaces %} from a {% data variables.product.prodname_classroom %} to use your {% data variables.product.prodname_codespaces %} Education benefit. For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)."
 
-{% endnote %}
 {% endif %}
 
 ## About changing your settings
@@ -59,11 +58,8 @@ Once a user loses access to a codespace, the codespace is retained for a period
 
 ## Enabling or disabling {% data variables.product.prodname_github_codespaces %}
 
-{% note %}
-
-**Note:** If you remove a user's access to {% data variables.product.prodname_github_codespaces %}, the user will immediately be unable to open existing codespaces they have created from your organization's private {% ifversion ghec %}and internal {% endif %}repositories. For more information, see "[About changing your settings](#about-changing-your-settings)."
-
-{% endnote %}
+> [!NOTE]
+> If you remove a user's access to {% data variables.product.prodname_github_codespaces %}, the user will immediately be unable to open existing codespaces they have created from your organization's private {% ifversion ghec %}and internal {% endif %}repositories. For more information, see "[About changing your settings](#about-changing-your-settings)."
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
index 1cb07c30b1..ef63316c68 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
@@ -41,11 +41,8 @@ To list all of the current codespaces for an organization that were created by a
 gh codespace list --org ORGANIZATION --user USER
 ```
 
-{% note %}
-
-**Note**: In the above commands, replace `ORGANIZATION` with the name of the organization you are querying. You must be an owner of the organization.
-
-{% endnote %}
+> [!NOTE]
+> In the above commands, replace `ORGANIZATION` with the name of the organization you are querying. You must be an owner of the organization.
 
 ### Using the REST API to list codespaces
 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization.md
index 70c8a38229..a36d1868af 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization.md
@@ -32,11 +32,8 @@ You can set a spending limit for {% data variables.product.prodname_github_codes
 
 You can check the compute and storage usage for {% data variables.product.prodname_github_codespaces %} for the current billing month. For information, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
 
-{% note %}
-
-**Note**: Prebuilds for {% data variables.product.prodname_github_codespaces %} are created and updated using {% data variables.product.prodname_actions %}. This may incur billable costs for {% data variables.product.prodname_actions %}. You can set a spending limit for {% data variables.product.prodname_actions %}. For more information, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces-prebuilds)" and "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)." Storage of the generated prebuilds is charged at the same rate as your codespaces, and is included in your {% data variables.product.prodname_github_codespaces %} spending limit.
-
-{% endnote %}
+> [!NOTE]
+> Prebuilds for {% data variables.product.prodname_github_codespaces %} are created and updated using {% data variables.product.prodname_actions %}. This may incur billable costs for {% data variables.product.prodname_actions %}. You can set a spending limit for {% data variables.product.prodname_actions %}. For more information, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces-prebuilds)" and "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)." Storage of the generated prebuilds is charged at the same rate as your codespaces, and is included in your {% data variables.product.prodname_github_codespaces %} spending limit.
 
 ## Disabling or limiting billing for {% data variables.product.prodname_codespaces %}
 
@@ -60,11 +57,8 @@ Your users can delete their own codespaces in https://github.com/codespaces and
 
 As an organization owner, you can delete any codespace in your organization. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace#deleting-codespaces-in-your-organization)."
 
-{% note %}
-
-**Note:** Codespaces are automatically deleted after they have been stopped and have remained inactive for a user-definable number of days. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces)." As an organization owner, you can set the maximum retention period for codespaces owned by your organization. This will override a user's personal retention setting. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)."
-
-{% endnote %}
+> [!NOTE]
+> Codespaces are automatically deleted after they have been stopped and have remained inactive for a user-definable number of days. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces)." As an organization owner, you can set the maximum retention period for codespaces owned by your organization. This will override a user's personal retention setting. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)."
 
 ## Further reading
 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
index 973a412f4c..8ff3511bfc 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -26,11 +26,8 @@ If there are existing codespaces that no longer conform to a policy you have def
 
 If you remove higher specification machine types that are required by the {% data variables.product.prodname_github_codespaces %} configuration for an individual repository in your organization, then it won't be possible to create a codespace for that repository. When someone attempts to create a codespace they will see a message telling them that there are no valid machine types available that meet the requirements of the repository's {% data variables.product.prodname_github_codespaces %} configuration.
 
-{% note %}
-
-**Note**: Anyone who can edit the `devcontainer.json` configuration file in a repository can set a minimum specification for machines that can be used for codespaces for that repository. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/setting-a-minimum-specification-for-codespace-machines)."
-
-{% endnote %}
+> [!NOTE]
+> Anyone who can edit the `devcontainer.json` configuration file in a repository can set a minimum specification for machines that can be used for codespaces for that repository. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/setting-a-minimum-specification-for-codespace-machines)."
 
 If setting a policy for machine types prevents people from using {% data variables.product.prodname_github_codespaces %} for a particular repository there are two options:
 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md
index 2ef7289af7..5d88cef103 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md
@@ -40,14 +40,10 @@ Using the CLI, the error message is:
 
 If the image for a codespace is specified in a Dockerfile, and does not match the policy, a codespace is created in recovery mode, using the default recovery container rather than the specified image. A message to this effect is included at the end of the creation log. For more information about the creation log, see "[AUTOTITLE](/codespaces/troubleshooting/github-codespaces-logs#creation-logs)."
 
-{% note %}
-
-**Notes**:
-* The dev container base image should not be confused with the host image. The host image is the image used to build the virtual machine on which the dev container runs. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image)."
-* The base image policy is applied when a codespace is created, and when you perform a full container rebuild. For more information, see "[AUTOTITLE](/codespaces/getting-started/understanding-the-codespace-lifecycle#rebuilding-a-codespace)."
-* The base image policy does not apply to the default image, or the image that's used to recover a codespace if an error is introduced into a dev container configuration which prevents the container from being rebuilt.
-
-{% endnote %}
+> [!NOTE]
+> * The dev container base image should not be confused with the host image. The host image is the image used to build the virtual machine on which the dev container runs. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image)."
+> * The base image policy is applied when a codespace is created, and when you perform a full container rebuild. For more information, see "[AUTOTITLE](/codespaces/getting-started/understanding-the-codespace-lifecycle#rebuilding-a-codespace)."
+> * The base image policy does not apply to the default image, or the image that's used to recover a codespace if an error is introduced into a dev container configuration which prevents the container from being rebuilt.
 
 ### Setting organization-wide and repository-specific policies
 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
index a4589ae21d..45d4e4b42b 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
@@ -20,11 +20,8 @@ The personal settings of a {% data variables.product.prodname_dotcom %} user all
 
 As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces created for repositories owned by your organization. This can help you to limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for the codespaces for all repositories owned by your organization, or for the codespaces of specific repositories.
 
-{% note %}
-
-**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization.
-
-{% endnote %}
+> [!NOTE]
+> Maximum idle timeout constraints only apply to codespaces that are owned by your organization.
 
 For more information about pricing for {% data variables.product.prodname_github_codespaces %} compute usage, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-number-of-organization-billed-codespaces-a-user-can-create.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-number-of-organization-billed-codespaces-a-user-can-create.md
index 281554de90..19d1485168 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-number-of-organization-billed-codespaces-a-user-can-create.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-number-of-organization-billed-codespaces-a-user-can-create.md
@@ -45,11 +45,8 @@ Policies with the "Maximum codespaces per user" constraint are applied to every
    * "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)"
    * "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)"
 
-   {% note %}
-
-   **Note**: When you add a constraint to a policy that already contains the "Maximum codespaces per user" constraint, you won't be able to restrict the additional constraint to specific repositories, as the "Maximum codespaces per user" constraint applies to all repositories in the organization.
-
-   {% endnote %}
+   > [!NOTE]
+   > When you add a constraint to a policy that already contains the "Maximum codespaces per user" constraint, you won't be able to restrict the additional constraint to specific repositories, as the "Maximum codespaces per user" constraint applies to all repositories in the organization.
 
 1. After you've finished adding constraints to your policy, click **Save**.
 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md
index ce0d4ff35f..2b00ccf197 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md
@@ -20,11 +20,8 @@ product: '{% data reusables.gated-features.codespaces-org %}'
 
 As an organization owner, you may want to configure constraints on the maximum retention period for codespaces created for the repositories owned by your organization. This can help you to limit the storage costs associated with codespaces that are stopped and then left unused until they are automatically deleted. For more information about storage charges, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." You can set a maximum retention period for all, or for specific, repositories owned by your organization.
 
-{% note %}
-
-**Note**: Setting a maximum retention policy for a repository prevents people from exempting a codespace from automatic deletion. The "Keep codespace" option will be unavailable for codespaces created for that repository. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces?tool=webui#avoiding-automatic-deletion-of-codespaces)."
-
-{% endnote %}
+> [!NOTE]
+> Setting a maximum retention policy for a repository prevents people from exempting a codespace from automatic deletion. The "Keep codespace" option will be unavailable for codespaces created for that repository. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces?tool=webui#avoiding-automatic-deletion-of-codespaces)."
 
 ### Setting organization-wide and repository-specific policies
 
@@ -45,14 +42,10 @@ If you add an organization-wide policy with a retention constraint, you should s
 
    ![Screenshot of a dropdown with a field labeled "Maximum value" set to 8 days. Below this are "Cancel" and "Save" buttons.](/assets/images/help/codespaces/maximum-days-retention.png)
 
-   {% note %}
-
-   **Notes**
-   * A day, in this context, is a 24-hour period, beginning at the time of day when the codespace was stopped.
-   * The valid range is 0-30 days.
-   * Setting the period to `0` will result in codespaces being immediately deleted when they are stopped, or when they timeout due to inactivity.
-
-   {% endnote %}
+   > [!NOTE]
+   > * A day, in this context, is a 24-hour period, beginning at the time of day when the codespace was stopped.
+   > * The valid range is 0-30 days.
+   > * Setting the period to `0` will result in codespaces being immediately deleted when they are stopped, or when they timeout due to inactivity.
 
 {% data reusables.codespaces.codespaces-policy-targets %}
 1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see:
diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
index 06044a8144..d05e8c8043 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
@@ -22,11 +22,8 @@ As an organization owner, you may want to configure constraints on the visibilit
 
 If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. When the user resumes the codespace, it will be subject to the policy constraints.
 
-{% note %}
-
-**Note**: You can't disable private port forwarding, as private port forwarding is required by {% data variables.product.prodname_github_codespaces %} to continue working as designed, for example to forward SSH on port 22.
-
-{% endnote %}
+> [!NOTE]
+> You can't disable private port forwarding, as private port forwarding is required by {% data variables.product.prodname_github_codespaces %} to continue working as designed, for example to forward SSH on port 22.
 
 ### Setting organization-wide and repository-specific policies
 
diff --git a/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md b/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md
index 4501a82885..3bfdf3c90a 100644
--- a/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md
+++ b/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md
@@ -26,11 +26,8 @@ By default, GPG verification is disabled for codespaces you create. If you enabl
 
 For more information about managing your preferences for Settings Sync, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/personalizing-github-codespaces-for-your-account#managing-your-preferences-for-settings-sync)."
 
-{% note %}
-
-**Note:** If you have linked a dotfiles repository with {% data variables.product.prodname_github_codespaces %}, the Git configuration in your dotfiles may conflict with the configuration that {% data variables.product.prodname_github_codespaces %} requires to sign commits. For more information, see "[AUTOTITLE](/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces)."
-
-{% endnote %}
+> [!NOTE]
+> If you have linked a dotfiles repository with {% data variables.product.prodname_github_codespaces %}, the Git configuration in your dotfiles may conflict with the configuration that {% data variables.product.prodname_github_codespaces %} requires to sign commits. For more information, see "[AUTOTITLE](/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces)."
 
 ## Enabling or disabling GPG verification
 
diff --git a/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
index 8ee068ca0f..7f59675bd0 100644
--- a/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
+++ b/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
@@ -24,11 +24,8 @@ For more information, see "[AUTOTITLE](/codespaces/reference/security-in-github-
 
 If your project needs additional permissions for other repositories, you can configure this in the `devcontainer.json` file, as described in "[Setting additional repository permissions](#setting-additional-repository-permissions)" later in this article. When permissions are listed in the `devcontainer.json` file, you will be prompted to review and authorize the additional permissions as part of codespace creation for that repository. Once you've authorized the listed permissions, {% data variables.product.prodname_github_codespaces %} will remember your choice and will not prompt you for authorization unless the permissions in the `devcontainer.json` file change.
 
-{% note %}
-
-**Note:** Updating the permissions in the `devcontainer.json` file does not change the permissions of existing codespaces. If you need additional permissions in an existing codespace, see "[AUTOTITLE](/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository#authenticating-to-repositories-that-you-didnt-create-the-codespace-from)."
-
-{% endnote %}
+> [!NOTE]
+> Updating the permissions in the `devcontainer.json` file does not change the permissions of existing codespaces. If you need additional permissions in an existing codespace, see "[AUTOTITLE](/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository#authenticating-to-repositories-that-you-didnt-create-the-codespace-from)."
 
 ## Creating codespaces with custom permissions
 
@@ -61,13 +58,9 @@ You configure repository permissions for {% data variables.product.prodname_gith
    }
    ```
 
-   {% note %}
-
-   **Notes:**
-   * You can only reference repositories that belong to the same personal account or organization as the repository you are currently working in.
-   * You can use the `*` wildcard to grant permissions to multiple repositories in an organization. For example, to grant permissions to all repositories in the `my_org` organization use `my_org/*`. This syntax is only valid for codespaces. In any `devcontainer.json` files that are used for prebuilds, you must define permissions for each repository separately. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)."
-
-   {% endnote %}
+   > [!NOTE]
+   > * You can only reference repositories that belong to the same personal account or organization as the repository you are currently working in.
+   > * You can use the `*` wildcard to grant permissions to multiple repositories in an organization. For example, to grant permissions to all repositories in the `my_org` organization use `my_org/*`. This syntax is only valid for codespaces. In any `devcontainer.json` files that are used for prebuilds, you must define permissions for each repository separately. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)."
 
    You can grant as many or as few of the following permissions for each repository listed:
    * `actions` - read / write
diff --git a/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
index 421daf5d10..ac5a756453 100644
--- a/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
+++ b/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
@@ -26,11 +26,8 @@ When prebuilds are available for a particular branch of a repository, a particul
 
 When you create a codespace from a template on the "Your codespaces" page, {% data variables.product.prodname_dotcom %} may automatically use a prebuild to speed up creation time. For more information on templates, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template)."
 
-{% note %}
-
-**Note**: Each prebuild that's created consumes storage space that will either incur a billable charge or, for repositories owned by your personal {% data variables.product.prodname_dotcom %} account, will use some of your monthly included storage. For more information, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces-prebuilds)."
-
-{% endnote %}
+> [!NOTE]
+> Each prebuild that's created consumes storage space that will either incur a billable charge or, for repositories owned by your personal {% data variables.product.prodname_dotcom %} account, will use some of your monthly included storage. For more information, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces-prebuilds)."
 
 ## The prebuild process
 
diff --git a/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
index d6ab85169f..4341c60ea6 100644
--- a/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
+++ b/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
@@ -19,14 +19,9 @@ By default, the {% data variables.product.prodname_actions %} workflow for a pre
 
 You can configure read access to other {% data variables.product.prodname_dotcom %} repositories, with the same repository owner, by specifying permissions in the `devcontainer.json` file used by your prebuild configuration. For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
 
-{% note %}
-
-**Notes**:
-
-* You can only authorize read permissions in this way, and the owner of the target repository must be the same as the owner of the repository for which you're creating a prebuild. For example, if you're creating a prebuild configuration for the `octo-org/octocatrepository`, then you'll be able to grant read permissions for other repositories, such `asocto-org/octodemo`, if this is specified in the `devcontainer.json` file, and provided you have the permissions yourself.
-* You can't use wildcards to specify repositories. You must define permissions for each repository for which you want to grant access.
-
-{% endnote %}
+> [!NOTE]
+> * You can only authorize read permissions in this way, and the owner of the target repository must be the same as the owner of the repository for which you're creating a prebuild. For example, if you're creating a prebuild configuration for the `octo-org/octocatrepository`, then you'll be able to grant read permissions for other repositories, such `asocto-org/octodemo`, if this is specified in the `devcontainer.json` file, and provided you have the permissions yourself.
+> * You can't use wildcards to specify repositories. You must define permissions for each repository for which you want to grant access.
 
 When you create or edit a prebuild configuration for a `devcontainer.json` file that sets up read access to other repositories with the same repository owner, you'll be prompted to grant these permissions when you click **Create** or **Update**. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
 
@@ -38,11 +33,9 @@ You will need to create a new personal account and then use this account to crea
 
 1. Create a new personal account on {% data variables.product.prodname_dotcom %}.
 
-   {% warning %}
+   > [!WARNING]
+   > Although you can generate the {% data variables.product.pat_v1 %} using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github)" and "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)."
 
-   **Warning**: Although you can generate the {% data variables.product.pat_v1 %} using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github)" and "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)."
-
-   {% endwarning %}
 1. Give the new account read access to the required repositories. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository)."
 1. While signed into the new account, create a {% data variables.product.pat_v1 %} with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)."
 
diff --git a/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
index b1fc2d3b03..c38fdf2157 100644
--- a/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
+++ b/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -25,11 +25,8 @@ Prebuilds are created using {% data variables.product.prodname_actions %}. As a
 
 You can set up prebuilds in any repository owned by a personal account. The prebuild will consume storage space that will either incur a billable charge or, for repositories owned by your personal account, will use some of your monthly included storage.
 
-{% note %}
-
-**Note**: {% data reusables.codespaces.prebuilds-billing-for-forks %} See "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#how-billing-is-handled-for-forked-repositories)."
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.codespaces.prebuilds-billing-for-forks %} See "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#how-billing-is-handled-for-forked-repositories)."
 
 For repositories owned by an organization, you can set up prebuilds if the organization is on a {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} plan. Additionally, you must have added a payment method and set a spending limit for {% data variables.product.prodname_github_codespaces %} on the organization account or its parent enterprise. See "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-the-github-codespaces-spending-limit-for-your-organization-account)" and "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)."
 
@@ -44,11 +41,8 @@ For repositories owned by an organization, you can set up prebuilds if the organ
 
    ![Screenshot of the "Configuration" settings for a prebuild with a dropdown menu listing branches to select. The "main" branch is currently selected.](/assets/images/help/codespaces/prebuilds-choose-branch.png)
 
-   {% note %}
-
-   **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
-
-   {% endnote %}
+   > [!NOTE]
+   > Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
 
 1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. See "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#devcontainerjson)."
 
@@ -61,11 +55,8 @@ For repositories owned by an organization, you can set up prebuilds if the organ
    * **On configuration change** - With this setting, prebuilds will be updated every time any of the following files is changed:
      * `.devcontainer/devcontainer.json`
 
-       {% note %}
-
-       **Note**: Prebuild updates are not triggered by changes to `devcontainer.json` files within subdirectories of `.devcontainer`.
-
-       {% endnote %}
+       > [!NOTE]
+       > Prebuild updates are not triggered by changes to `devcontainer.json` files within subdirectories of `.devcontainer`.
 
      * The Dockerfile referenced in the `build.dockerfile` property of the `.devcontainer/devcontainer.json` file.
 
@@ -81,13 +72,9 @@ For repositories owned by an organization, you can set up prebuilds if the organ
 
    ![Screenshot of the "Region availability" settings. "Reduce prebuild available to only specific regions" is selected with two regions selected.](/assets/images/help/codespaces/prebuilds-regions.png)
 
-   {% note %}
-
-   **Notes**:
-   * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. See "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces-prebuilds)."
-   * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. See "[AUTOTITLE](/codespaces/setting-your-user-preferences/setting-your-default-region-for-github-codespaces)."
-
-   {% endnote %}
+   > [!NOTE]
+   > * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. See "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces-prebuilds)."
+   > * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. See "[AUTOTITLE](/codespaces/setting-your-user-preferences/setting-your-default-region-for-github-codespaces)."
 
 1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved.
 
@@ -103,11 +90,8 @@ For repositories owned by an organization, you can set up prebuilds if the organ
 
    ![Screenshot of the "Failure notifications" setting. The team named "octocat-team" has been added.](/assets/images/help/codespaces/prebuilds-failure-notification-setting.png)
 
-   {% note %}
-
-   **Note**: People will only receive notifications of failed prebuilds if they have enabled notifications for failed Actions workflows in their personal settings. See "[AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#github-actions-notification-options)."
-
-   {% endnote %}
+   > [!NOTE]
+   > People will only receive notifications of failed prebuilds if they have enabled notifications for failed Actions workflows in their personal settings. See "[AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#github-actions-notification-options)."
 
 1. Optionally, at the bottom of the page, click **Show advanced options**.
 
diff --git a/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
index 3f351084e6..2f0ad7107b 100644
--- a/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
+++ b/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
@@ -75,11 +75,8 @@ Disabling the workflow runs for a prebuild configuration is useful if you need t
 
 ## Deleting a prebuild configuration
 
-{% note %}
-
-**Note**: You can find a list of the repositories that contain a prebuild by obtaining a copy of your “[usage report](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage).”
-
-{% endnote %}
+> [!NOTE]
+> You can find a list of the repositories that contain a prebuild by obtaining a copy of your “[usage report](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage).”
 
 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.
 
diff --git a/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md b/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md
index 4da4c4e70d..b2d6294132 100644
--- a/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md
+++ b/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md
@@ -25,8 +25,5 @@ For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-c
 1. Apply the changes by rebuilding the container. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
 1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch or an active feature branch, triggering an update of the prebuild for that branch.
 
-   {% note %}
-
-   **Note**: Creating this codespace will take longer than usual because it will not be created from a prebuild.
-
-   {% endnote %}
+   > [!NOTE]
+   > Creating this codespace will take longer than usual because it will not be created from a prebuild.
diff --git a/content/codespaces/reference/disaster-recovery-for-github-codespaces.md b/content/codespaces/reference/disaster-recovery-for-github-codespaces.md
index abc3ad41d7..33ba5244ca 100644
--- a/content/codespaces/reference/disaster-recovery-for-github-codespaces.md
+++ b/content/codespaces/reference/disaster-recovery-for-github-codespaces.md
@@ -18,11 +18,8 @@ Although disaster recovery scenarios are rare occurrences, we recommend that you
 
 The following guidance provides options on how to handle service disruption to the entire region where your codespace is deployed.
 
-{% note %}
-
-**Note:** You can reduce the potential impact of service-wide outages by pushing to remote repositories frequently.
-
-{% endnote %}
+> [!NOTE]
+> You can reduce the potential impact of service-wide outages by pushing to remote repositories frequently.
 
 ## Option 1: Create a new codespace in another region
 
@@ -46,8 +43,5 @@ While this option does not configure a development environment for you, it will
 
 If your repository has a `devcontainer.json`, consider using the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup. For more information, see "[Developing inside a container](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
 
-{% note %}
-
-**Note:** Be sure your local setup meets the [minimum requirements](https://code.visualstudio.com/docs/remote/containers#_system-requirements) before attempting this option.
-
-{% endnote %}
+> [!NOTE]
+> Be sure your local setup meets the [minimum requirements](https://code.visualstudio.com/docs/remote/containers#_system-requirements) before attempting this option.
diff --git a/content/codespaces/reference/security-in-github-codespaces.md b/content/codespaces/reference/security-in-github-codespaces.md
index f7365cf6d7..56915d8381 100644
--- a/content/codespaces/reference/security-in-github-codespaces.md
+++ b/content/codespaces/reference/security-in-github-codespaces.md
@@ -97,13 +97,10 @@ When you create a codespace from a PR branch from a fork, the token in the codes
 
 We also further protect you in these scenarios by not injecting any of your codespace secrets into the environment. For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-your-account-specific-secrets-for-github-codespaces)."
 
-{% note %}
-
-**Note:** The scope of the token in the codespace can change if you create a codespace from a fork to which you only have read access, then make a commit or push a new branch in the codespace. In this situation, as with any other repository, {% data variables.product.prodname_github_codespaces %} automatically creates a new fork, or links your codespace to an existing fork owned by your account, and updates the token to have read and write access to the newly linked fork. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace#about-automatic-forking)."
-
-When {% data variables.product.prodname_github_codespaces %} links your codespace to an existing fork, this existing fork can be either a fork of the fork from which you created a codespace, or your own fork of the shared upstream repository.
-
-{% endnote %}
+> [!NOTE]
+> The scope of the token in the codespace can change if you create a codespace from a fork to which you only have read access, then make a commit or push a new branch in the codespace. In this situation, as with any other repository, {% data variables.product.prodname_github_codespaces %} automatically creates a new fork, or links your codespace to an existing fork owned by your account, and updates the token to have read and write access to the newly linked fork. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace#about-automatic-forking)."
+>
+> When {% data variables.product.prodname_github_codespaces %} links your codespace to an existing fork, this existing fork can be either a fork of the fork from which you created a codespace, or your own fork of the shared upstream repository.
 
 ### Additional good practices
 
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers.md b/content/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers.md
index a5969c6104..30e3cfb199 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers.md
@@ -65,11 +65,8 @@ The Dockerfile is a text file that contains the instructions needed to create a
 
 The Dockerfile for a dev container is typically located in the `.devcontainer` folder, alongside the `devcontainer.json` in which it is referenced.
 
-{% note %}
-
-**Note**: As an alternative to using a Dockerfile you can use the `image` property in the `devcontainer.json` file to refer directly to an existing image you want to use. The image you specify here must be allowed by any organization image policy that has been set. See "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)." If neither a Dockerfile nor an image is found then the default container image is used. See "[Using the default dev container configuration](#using-the-default-dev-container-configuration)."
-
-{% endnote %}
+> [!NOTE]
+> As an alternative to using a Dockerfile you can use the `image` property in the `devcontainer.json` file to refer directly to an existing image you want to use. The image you specify here must be allowed by any organization image policy that has been set. See "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)." If neither a Dockerfile nor an image is found then the default container image is used. See "[Using the default dev container configuration](#using-the-default-dev-container-configuration)."
 
 #### Simple Dockerfile example
 
@@ -100,11 +97,8 @@ COPY ./script-in-your-repo.sh /tmp/scripts/script-in-codespace.sh
 RUN apt-get update && bash /tmp/scripts/script-in-codespace.sh
 ```
 
-{% note %}
-
-**Note**: In the above example, the script that's copied to the codespace (`script-in-your-repo.sh`) must exist in your repository.
-
-{% endnote %}
+> [!NOTE]
+> In the above example, the script that's copied to the codespace (`script-in-your-repo.sh`) must exist in your repository.
 
 For more information about Dockerfile instructions, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder)" in the Docker documentation.
 
@@ -130,11 +124,8 @@ If you don't add a dev container configuration to your repository, or if your co
 
 The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_github_codespaces %} provides.
 
-{% note %}
-
-**Note**: {% data variables.product.prodname_dotcom %} does not charge for storage of containers built from the default dev container image. For more information about billing for codespace storage, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-storage-usage)." {% data reusables.codespaces.check-for-default-image %}
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_dotcom %} does not charge for storage of containers built from the default dev container image. For more information about billing for codespace storage, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-storage-usage)." {% data reusables.codespaces.check-for-default-image %}
 
 ## Using a predefined dev container configuration
 
@@ -174,13 +165,9 @@ If none of the predefined configurations meets your needs, you can create a cust
 * If you're adding a single `devcontainer.json` file that will be used by everyone who creates a codespace from your repository, create the file within a `.devcontainer` directory at the root of the repository.
 * If you want to offer users a choice of configuration, you can create multiple custom `devcontainer.json` files, each located within a separate subdirectory of the `.devcontainer` directory.
 
-   {% note %}
-
-   **Notes**:
-  * You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not.
-  * {% data reusables.codespaces.configuration-choice-templates %} See "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/setting-up-a-template-repository-for-github-codespaces)."
-
-   {% endnote %}
+  > [!NOTE]
+  > * You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not.
+  > * {% data reusables.codespaces.configuration-choice-templates %} See "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/setting-up-a-template-repository-for-github-codespaces)."
 
    If multiple `devcontainer.json` files are found in the repository, they are listed in the **Dev container configuration** dropdown on the codespace creation options page. See "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
 
@@ -212,11 +199,8 @@ You can add and edit the supported configuration keys in the `devcontainer.json`
 
 The `devcontainer.json` file is written using the JSONC (JSON with comments) format. This allows you to include comments within the configuration file. See "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
 
-{% note %}
-
-**Note**: If you use a linter to validate the `devcontainer.json` file, make sure it is set to JSONC and not JSON or comments will be reported as errors.
-
-{% endnote %}
+> [!NOTE]
+> If you use a linter to validate the `devcontainer.json` file, make sure it is set to JSONC and not JSON or comments will be reported as errors.
 
 ### Interface settings for {% data variables.product.prodname_vscode_shortname %}
 
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/automatically-opening-files-in-the-codespaces-for-a-repository.md b/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/automatically-opening-files-in-the-codespaces-for-a-repository.md
index 724a1a56a6..263c4922f0 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/automatically-opening-files-in-the-codespaces-for-a-repository.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/automatically-opening-files-in-the-codespaces-for-a-repository.md
@@ -20,11 +20,8 @@ If there's a particular file that's useful for people to see when they create a
 
 The file, or files, you specify are only opened the first time a codespace is opened in the web client. If the person closes the specified files, those files are not automatically reopened the next time that person opens or restarts the codespace.
 
-{% note %}
-
-**Note**: This automation only applies to the {% data variables.product.prodname_vscode_shortname %} web client, not to the {% data variables.product.prodname_vscode_shortname %} desktop application, or other supported editors.
-
-{% endnote %}
+> [!NOTE]
+> This automation only applies to the {% data variables.product.prodname_vscode_shortname %} web client, not to the {% data variables.product.prodname_vscode_shortname %} desktop application, or other supported editors.
 
 ## Setting files to be opened automatically
 
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/setting-a-minimum-specification-for-codespace-machines.md b/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/setting-a-minimum-specification-for-codespace-machines.md
index d031ea95e7..0ab35e2819 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/setting-a-minimum-specification-for-codespace-machines.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/setting-a-minimum-specification-for-codespace-machines.md
@@ -22,11 +22,8 @@ If your project needs a certain level of compute power, you can configure {% dat
 
 {% data reusables.codespaces.machine-types-for-unpublished-codespaces %}
 
-{% note %}
-
-**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
-
-{% endnote %}
+> [!IMPORTANT]
+> Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
 
 ## Setting a minimum machine specification
 
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/specifying-recommended-secrets-for-a-repository.md b/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/specifying-recommended-secrets-for-a-repository.md
index 0df9ded528..dc1391d862 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/specifying-recommended-secrets-for-a-repository.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/specifying-recommended-secrets-for-a-repository.md
@@ -24,11 +24,8 @@ Recommended secrets are listed at the bottom of the page.
 
 <img src="/assets/images/help/codespaces/recommended-secrets.png" style="max-height:50rem"  alt='Screenshot of the "Create codespace" page with four recommended secrets highlighted with a dark orange outline.' />
 
-{% note %}
-
-**Note**: The names of the recommended secrets are only listed on this page when the container configuration on the selected branch specifies these secrets.
-
-{% endnote %}
+> [!NOTE]
+> The names of the recommended secrets are only listed on this page when the container configuration on the selected branch specifies these secrets.
 
 Each recommended secret is displayed in one of three ways:
 
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces.md b/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces.md
index 4d2933d8d2..bc74a102a5 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces.md
@@ -66,14 +66,9 @@ For example, the URL `https://codespaces.new/octo-org/octo-repo?quickstart=1` op
 
 ![Screenshot of the "Resume codespace" page showing the "Resume this codespace" and "Create a new one" buttons.](/assets/images/help/codespaces/resume-codespace.png)
 
-{% note %}
-
-**Notes**:
-
-* If the `codespaces.new` URL already contains a query string, add `&quickstart=1` at the end of the query string.
-* This type of URL will always open a codespace in the {% data variables.product.prodname_vscode_shortname %} web client, even if this is not set as your default editor for {% data variables.product.prodname_github_codespaces %}.
-
-{% endnote %}
+> [!NOTE]
+> * If the `codespaces.new` URL already contains a query string, add `&quickstart=1` at the end of the query string.
+> * This type of URL will always open a codespace in the {% data variables.product.prodname_vscode_shortname %} web client, even if this is not set as your default editor for {% data variables.product.prodname_github_codespaces %}.
 
 If no matching codespaces are found, the page is titled "Create codespace" and a button is displayed for creating a new codespace with matching parameters.
 
@@ -81,11 +76,8 @@ This type of URL is useful, for instance, in a README for your repository as it
 
 ## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge
 
-{% tip %}
-
-**Tip:** You can use the "Share a deep link" option to create a Markdown or HTML snippet that includes an "Open in {% data variables.product.prodname_github_codespaces %}" badge with a custom URL. For more information, see "[Configuring more options](#configuring-more-options)."
-
-{% endtip %}
+> [!TIP]
+> You can use the "Share a deep link" option to create a Markdown or HTML snippet that includes an "Open in {% data variables.product.prodname_github_codespaces %}" badge with a custom URL. For more information, see "[Configuring more options](#configuring-more-options)."
 
 1. Get the URL to the codespace creation page, or the "Resume codespace" page, as described in the previous sections.
 1. Add the following Markdown to, for example, the `README.md` file of your repository:
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/setting-up-a-template-repository-for-github-codespaces.md b/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/setting-up-a-template-repository-for-github-codespaces.md
index 17125b0f8f..55c022a0d6 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/setting-up-a-template-repository-for-github-codespaces.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/setting-up-a-template-repository-for-github-codespaces.md
@@ -49,11 +49,8 @@ For guidance on the kinds of files to include, you can look at the starter files
 
 You can add dev container configuration files to your template repository to customize the development environment for people using your template with {% data variables.product.prodname_github_codespaces %}. You can choose from a list of predefined configuration settings in {% data variables.product.prodname_vscode %}, or you can create a custom configuration by writing your own `devcontainer.json` file. If you don't add configuration files, the default container image will be used. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)" and "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration)."
 
-{% note %}
-
-**Note:** {% data reusables.codespaces.configuration-choice-templates %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.codespaces.configuration-choice-templates %}
 
 You should configure your dev container with the tools and customization to give users the best experience with your template. For example, in your `devcontainer.json` file:
 * You can use the `openFiles` property to define a list of files to be opened automatically in the {% data variables.product.prodname_vscode_shortname %} web client when a codespace is created from your template.
diff --git a/content/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image.md b/content/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image.md
index 70e3b37a4b..763ce96843 100644
--- a/content/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image.md
+++ b/content/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image.md
@@ -19,14 +19,9 @@ The VM for a codespace is built using a host image that defines the operating sy
 
 The stable image is the default selected setting. Changing the setting to the beta host image gives you early access to improvements and new features on the host VM, but may also introduce incompatibilities with your current dev container configuration. This gives you the opportunity to alter your dev container configuration to avoid problems before the beta image is promoted to the stable image. If you do encounter problems with the beta host image, you can switch back to the stable host image at any time.
 
-{% note %}
-
-**Notes**:
-
-* It's unlikely you will encounter problems using the beta host image unless your dev container configuration has dependencies on components of the VM host kernel.
-* The virtual machine host image should not be confused with the dev container image, which provides the environment of your codespace. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces#overview)."
-
-{% endnote %}
+> [!NOTE]
+> * It's unlikely you will encounter problems using the beta host image unless your dev container configuration has dependencies on components of the VM host kernel.
+> * The virtual machine host image should not be confused with the dev container image, which provides the environment of your codespace. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces#overview)."
 
 If you choose to use the beta host image but no beta image is currently available, your codespaces will be built using the stable host image.
 
diff --git a/content/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces.md b/content/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces.md
index 8d81ff8053..0aeee6165c 100644
--- a/content/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces.md
+++ b/content/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces.md
@@ -16,11 +16,8 @@ By default, {% data variables.product.prodname_github_codespaces %} are automati
 
 However, because {% data variables.product.prodname_github_codespaces %} incurs storage charges, you may prefer to reduce the retention period by changing your default period in your personal settings for {% data variables.product.prodname_github_codespaces %}. For more information about storage charges, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
 
-{% note %}
-
-**Note**: Whether or not you have set a personal codespace retention period, it's a good idea to get into the habit of deleting codespaces that you no longer need. See "[AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace)."
-
-{% endnote %}
+> [!NOTE]
+> Whether or not you have set a personal codespace retention period, it's a good idea to get into the habit of deleting codespaces that you no longer need. See "[AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace)."
 
 Automatic deletion happens irrespective of whether a codespace contains unpushed changes. To prevent automatic deletion of a codespace, just open the codespace again. The retention period is reset every time you connect to a codespace, and the retention countdown restarts when the codespace is stopped.
 
@@ -31,11 +28,8 @@ Each codespace has its own retention period. You may, therefore, have codespaces
 * You created a codespace using {% data variables.product.prodname_cli %} and specified a different retention period.
 * You created a codespace for an organization-owned repository that has a retention period configured in the organization settings. The ownership of the codespaces you create is shown on the "[Your codespaces](https://github.com/settings/codespaces)" page.
 
-{% note %}
-
-**Note**: The retention period is specified in days. A day represents a 24-hour period, beginning at the time of day when you stop a codespace.
-
-{% endnote %}
+> [!NOTE]
+> The retention period is specified in days. A day represents a 24-hour period, beginning at the time of day when you stop a codespace.
 
 {% webui %}
 
@@ -49,11 +43,8 @@ Each codespace has its own retention period. You may, therefore, have codespaces
 
    You can set your default retention period between `0` and `30` days.
 
-   {% warning %}
-
-   **Warning**: Setting the period to `0` will result in your codespaces being immediately deleted when you stop them, or when they timeout due to inactivity. See "[AUTOTITLE](/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces)."
-
-   {% endwarning %}
+   > [!WARNING]
+   > Setting the period to `0` will result in your codespaces being immediately deleted when you stop them, or when they timeout due to inactivity. See "[AUTOTITLE](/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces)."
 
 1. Click **Save**.
 
@@ -73,11 +64,8 @@ When an inactive codespace is approaching the end of its retention period, this
 
 You may have a codespace that you want to keep for longer than the retention period defined in your personal settings. You can do this by using the "Keep codespace" option. When you select this option, your codespace will be retained indefinitely, until you delete it manually.
 
-{% note %}
-
-**Note**: The "Keep codespace" option is not available for organization-owned codespaces affected by an organization retention policy.
-
-{% endnote %}
+> [!NOTE]
+> The "Keep codespace" option is not available for organization-owned codespaces affected by an organization retention policy.
 
 Codespaces incur storage costs, or consume your included storage allowance if the codespace is owned by your personal {% data variables.product.prodname_dotcom %} account. You should therefore be aware of the cost implications of storing codespaces indefinitely. See "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-storage-usage)."
 
diff --git a/content/codespaces/setting-your-user-preferences/personalizing-github-codespaces-for-your-account.md b/content/codespaces/setting-your-user-preferences/personalizing-github-codespaces-for-your-account.md
index 57653792df..f922a6f829 100644
--- a/content/codespaces/setting-your-user-preferences/personalizing-github-codespaces-for-your-account.md
+++ b/content/codespaces/setting-your-user-preferences/personalizing-github-codespaces-for-your-account.md
@@ -81,22 +81,16 @@ Your updates will take effect in new codespaces. However, you can turn on Settin
 
 ### Turning on Settings Sync in a codespace
 
-{% note %}
-
-**Note:** You should only turn on Settings Sync in codespaces created from repositories you trust. For more information, see "[AUTOTITLE](/codespaces/reference/security-in-github-codespaces#using-settings-sync)."
-
-{% endnote %}
+> [!NOTE]
+> You should only turn on Settings Sync in codespaces created from repositories you trust. For more information, see "[AUTOTITLE](/codespaces/reference/security-in-github-codespaces#using-settings-sync)."
 
 The following procedure describes how to turn on Settings Sync in a codespace opened in the web client. For information about turning on Settings Sync in the {% data variables.product.prodname_vscode_shortname %} desktop application, see [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync#_turning-on-settings-sync) in the {% data variables.product.prodname_vscode_shortname %} documentation.
 
 1. In {% data variables.product.prodname_vscode_shortname %}, at the bottom of the Activity Bar, select {% octicon "gear" aria-label="Manage" %}, then click **Sign in to Sync Settings**.
 1. If the repository from which you created the codespace is not in your list of trusted repositories, a browser window will open asking you to authorize additional permissions for Settings Sync. If you trust the repository, click **Authorize**, then close the browser window. The codespace will reload and display your latest synced settings.
 
-   {% note %}
-
-   **Note:** If you have Settings Sync disabled in your user preferences, and have set your trusted repositories to all repositories, you will see a warning about enabling Settings Sync for all repositories. Review the warning and choose whether to enable Settings Sync for all repositories or revise your list of trusted repositories.
-
-   {% endnote %}
+   > [!NOTE]
+   > If you have Settings Sync disabled in your user preferences, and have set your trusted repositories to all repositories, you will see a warning about enabling Settings Sync for all repositories. Review the warning and choose whether to enable Settings Sync for all repositories or revise your list of trusted repositories.
 
 1. To configure which settings you want to sync, open the Command Palette with <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux), then start typing "Settings Sync". Click **Settings Sync: Configure...**.
 1. Select the settings you want to sync, then click **OK**.
@@ -130,21 +124,15 @@ If none of these files are found, then any files or folders in your selected dot
 
 Any changes to your selected dotfiles repository will apply only to each new codespace, and do not affect any existing codespace.
 
-{% note %}
-
-**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the User-scoped settings for {% data variables.product.prodname_vscode_shortname %} with your `dotfiles` repository. You can set default Workspace and Remote [Codespaces] settings for a specific project in the project's repository. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)."
-
-{% endnote %}
+> [!NOTE]
+> Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the User-scoped settings for {% data variables.product.prodname_vscode_shortname %} with your `dotfiles` repository. You can set default Workspace and Remote [Codespaces] settings for a specific project in the project's repository. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)."
 
 ### Enabling your dotfiles repository for {% data variables.product.prodname_codespaces %}
 
 You can use your selected dotfiles repository to personalize your {% data variables.product.prodname_github_codespaces %} environment. Once you choose your dotfiles repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_github_codespaces %} settings page.
 
-{% warning %}
-
-**Warning:** Dotfiles have the ability to run arbitrary scripts, which may contain unexpected or malicious code. Before installing a dotfiles repo, we recommend checking scripts to ensure they don't perform any unexpected actions.
-
-{% endwarning %}
+> [!WARNING]
+> Dotfiles have the ability to run arbitrary scripts, which may contain unexpected or malicious code. Before installing a dotfiles repo, we recommend checking scripts to ensure they don't perform any unexpected actions.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.codespaces-tab %}
diff --git a/content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md b/content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md
index 256ec78152..66f5ca6405 100644
--- a/content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md
+++ b/content/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces.md
@@ -17,11 +17,8 @@ type: how_to
 
 A codespace will stop running after a period of inactivity. By default this period is 30 minutes, but you can specify a longer or shorter default timeout period in your personal settings on {% data variables.product.prodname_dotcom %}. The updated setting will apply to any new codespaces you create, or to existing codespaces the next time you start them. You can also specify a timeout when you use {% data variables.product.prodname_cli %} to create a codespace.
 
-{% warning %}
-
-**Warning**: Codespaces compute usage is billed for the duration for which a codespace is active. If you're not using a codespace but it remains running, and hasn't yet timed out, you are billed for the total time that the codespace was active, irrespective of whether you were using it. For more information, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
-
-{% endwarning %}
+> [!WARNING]
+> Codespaces compute usage is billed for the duration for which a codespace is active. If you're not using a codespace but it remains running, and hasn't yet timed out, you are billed for the total time that the codespace was active, irrespective of whether you were using it. For more information, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
 
 ### Inactivity defined
 
diff --git a/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
index e2edd4595c..724466497e 100644
--- a/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
+++ b/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
@@ -20,11 +20,8 @@ You can export your changes in one of several ways, depending on how you created
 * If you created the codespace from a repository to which you only have read access, you can export your changes to a fork of the repository. {% data variables.product.prodname_github_codespaces %} will create a new fork for you, or link your codespace to an existing fork if you already have one for the repository, and export your changes to a new branch of the fork. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace#about-automatic-forking)."
 * If you created the codespace from a template, and have not yet published it, you can publish the codespace to a new repository.
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_dotcom %} blocks pushes containing files larger than 100 MiB. If your codespace contains large files you will not be able to export your changes to a branch or fork. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github)."
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_dotcom %} blocks pushes containing files larger than 100 MiB. If your codespace contains large files you will not be able to export your changes to a branch or fork. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github)."
 
 ## Exporting changes to a branch
 
diff --git a/content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md b/content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md
index 18d82283ef..a773fc7932 100644
--- a/content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md
+++ b/content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md
@@ -60,8 +60,5 @@ To use the token to authenticate in your codespace, you have the following optio
 
   This will store the access token for the specific repository, so you will be able to push to and pull from the repository without overriding the existing credential helper.
 
-  {% note %}
-
-  **Note:** If you clone in this way, the token will be visible in your Git configuration. You should only use this method when working in a codespace created from a repository you trust, and you should limit the scope of the access token as much as possible.
-
-  {% endnote %}
+  > [!NOTE]
+  > If you clone in this way, the token will be visible in your Git configuration. You should only use this method when working in a codespace created from a repository you trust, and you should limit the scope of the access token as much as possible.
diff --git a/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
index b3e25a2b17..60fa85fdab 100644
--- a/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
+++ b/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
@@ -49,11 +49,8 @@ If you still cannot create a codespace for a repository where {% data variables.
 
 If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is canceled and codespace creation will fail.
 
-{% note %}
-
-**Note:** A codespace that was not successfully created is never going to be usable and should be deleted. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace)."
-
-{% endnote %}
+> [!NOTE]
+> A codespace that was not successfully created is never going to be usable and should be deleted. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace)."
 
 If you create a codespace and the creation fails:
 
@@ -63,20 +60,18 @@ If you create a codespace and the creation fails:
 
    One common scenario where this could happen is if you have a script running that is prompting for user input and waiting for an answer. If this is the case, remove the interactive prompt so that the build can complete non-interactively.
 
-   {% note %}
+  > [!NOTE]
+  > To view the logs during a build:
+  > * **In the browser**, if the initial steps of the build process take more than a few seconds, the "Setting up your codespace" page is displayed. Click **View logs.**
+  >
+  >   ![Screenshot of the "Setting up your codespace" page in a browser. The link "View logs" is highlighted with a dark orange outline.](/assets/images/help/codespaces/web-ui-view-logs.png)
+  >
+  > * **In the {% data variables.product.prodname_vscode_shortname %} desktop application**, click **Building codespace** in the "Setting up remote connection" popup message that's displayed.
+  >
+  >   ![Screenshot of a popup message in {% data variables.product.prodname_vscode_shortname %}, reading "Setting up remote connection: Building codespace."](/assets/images/help/codespaces/vs-code-building-codespace.png)
+  >
+  >   Log messages are printed to the Terminal in {% data variables.product.prodname_vscode_shortname %}
 
-   **Note**: To view the logs during a build:
-   * **In the browser**, if the initial steps of the build process take more than a few seconds, the "Setting up your codespace" page is displayed. Click **View logs.**
-
-     ![Screenshot of the "Setting up your codespace" page in a browser. The link "View logs" is highlighted with a dark orange outline.](/assets/images/help/codespaces/web-ui-view-logs.png)
-
-   * **In the {% data variables.product.prodname_vscode_shortname %} desktop application**, click **Building codespace** in the "Setting up remote connection" popup message that's displayed.
-
-     ![Screenshot of a popup message in {% data variables.product.prodname_vscode_shortname %}, reading "Setting up remote connection: Building codespace."](/assets/images/help/codespaces/vs-code-building-codespace.png)
-
-     Log messages are printed to the Terminal in {% data variables.product.prodname_vscode_shortname %}
-
-    {% endnote %}
 1. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
 
 ## Deleting codespaces
diff --git a/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md b/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md
index 83e6f84012..47fd9cfb90 100644
--- a/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md
+++ b/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md
@@ -73,11 +73,8 @@ If you want to keep automatic GPG verification for {% data variables.product.pro
 
 For example, if the global `.gitconfig` file on your local machine contains a `gpg.program` value, and you have pushed this file to a dotfiles repository that is linked with {% data variables.product.prodname_github_codespaces %}, then you may want to remove `gpg.program` from this file and set it at the system level on your local machine instead.
 
-{% note %}
-
-**Note:** Any changes to your dotfiles repository will apply to new codespaces you create, but not to your existing codespaces.
-
-{% endnote %}
+> [!NOTE]
+> Any changes to your dotfiles repository will apply to new codespaces you create, but not to your existing codespaces.
 
 1. On your local machine, open a terminal.
 1. To remove the conflicting value from `~/.gitconfig` (Mac/Linux) or `C:\Users\YOUR-USER\.gitconfig` (Windows), use the `git config --global --unset` command.
diff --git a/content/codespaces/troubleshooting/troubleshooting-included-usage.md b/content/codespaces/troubleshooting/troubleshooting-included-usage.md
index 6ffce5e2ca..c5f03d0021 100644
--- a/content/codespaces/troubleshooting/troubleshooting-included-usage.md
+++ b/content/codespaces/troubleshooting/troubleshooting-included-usage.md
@@ -13,11 +13,8 @@ topics:
 
 Personal {% data variables.product.prodname_dotcom %} accounts include a quota of free use of {% data variables.product.prodname_github_codespaces %} every month.
 
-{% note %}
-
-**Note**: Free use of {% data variables.product.prodname_github_codespaces %} is included in personal accounts only. It is not included in organization or enterprise accounts.
-
-{% endnote %}
+> [!NOTE]
+> Free use of {% data variables.product.prodname_github_codespaces %} is included in personal accounts only. It is not included in organization or enterprise accounts.
 
 There are two types of {% data variables.product.prodname_codespaces %} usage: compute and storage. During your monthly billing period, as you use {% data variables.product.prodname_codespaces %}, your compute and storage usage is deducted from the quota of free usage that's included in your personal {% data variables.product.prodname_dotcom %} account, until either compute or storage is consumed. Once one of those limits is reached, your use of {% data variables.product.prodname_github_codespaces %} will be restricted, unless you've set up a spending limit and a payment method. You will not be able to create new codespaces or open existing codespaces, that you would be billed for, until your quota renews. If you have access to repositories owned by an organization that pays for use of {% data variables.product.prodname_github_codespaces %}, you may still be able to create codespaces for those repositories.
 
@@ -35,11 +32,8 @@ You can see the storage usage for each of your codespaces on the "Your codespace
 
 ![Screenshot of a list of three codespaces on the https://github.com/codespaces page."](/assets/images/help/codespaces/your-codespaces-list.png)
 
-{% note %}
-
-**Note**: If the dev container for a codespace was built from the default image, the size of the codespace shown on this page does not include the size of the base dev container. Storage for the base dev container is provided free of charge. See "[Storage usage for your base dev container](#storage-usage-for-your-base-dev-container)".
-
-{% endnote %}
+> [!NOTE]
+> If the dev container for a codespace was built from the default image, the size of the codespace shown on this page does not include the size of the base dev container. Storage for the base dev container is provided free of charge. See "[Storage usage for your base dev container](#storage-usage-for-your-base-dev-container)".
 
 For billing purposes, {% data variables.product.prodname_codespaces %} storage is counted in GB-months. This is a cumulative measure of the total storage each codespace consumes from creation to deletion, plus the storage for prebuilds. See the "Billing for storage usage" section of "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-storage-usage)."
 
@@ -85,11 +79,10 @@ If the dev container for the current codespace was built from the default image,
 * Your codespaces consume compute usage while they are running. If you're not using a codespace, stopping the codespace prevents unnecessary compute usage. See "[AUTOTITLE](/codespaces/developing-in-a-codespace/stopping-and-starting-a-codespace)."
 * You can reduce the idle timeout for {% data variables.product.prodname_codespaces %} in your personal settings to less than the default 30 minutes. This will shorten the period of inactivity before your codespaces are automatically stopped. This can save on compute usage. See "[AUTOTITLE](/codespaces/setting-your-user-preferences/setting-your-timeout-period-for-github-codespaces)."
 * Your codespaces consume storage while they exist. You should delete a codespace you have finished using and know that you will not use again. See "[AUTOTITLE](/codespaces/developing-in-a-codespace/deleting-a-codespace)."
-  {% note %}
 
-  **Note**: Deleting a codespace will not reduce your used storage amount for the billing current month as this is a cumulative figure.
+  > [!NOTE]
+  > Deleting a codespace will not reduce your used storage amount for the billing current month as this is a cumulative figure.
 
-  {% endnote %}
 * Configure your retention period to ensure codespaces you forget to delete are deleted automatically. The default retention period is 30 days. See "[AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces)."
 * {% data variables.product.prodname_vscode %} extensions consume storage. Make sure you are only installing extensions that you need. You can find out how much space is being used by extensions by running this command in your codespace.
 
@@ -98,17 +91,15 @@ If the dev container for the current codespace was built from the default image,
   ```
 
 * Monitor your compute and storage usage by going to your billing page on {% data variables.product.github %}, https://github.com/settings/billing, and reviewing the figures in the "{% data variables.product.prodname_codespaces %}" section.
-  {% note %}
 
-  **Note**: Storage is calculated hourly and added to your existing storage usage. Consumed storage is therefore cumulative for the duration of your month-long billing cycle. This means that, during the billing period, the value you see on your billing page will only increase or remain the same. Usage will be reset to zero when a new billing cycle starts. Deleting a codespace, or a prebuild, will not reduce the usage figure for the current month, but it will reduce the rate at which storage usage accumulates.
+  > [!NOTE]
+  > Storage is calculated hourly and added to your existing storage usage. Consumed storage is therefore cumulative for the duration of your month-long billing cycle. This means that, during the billing period, the value you see on your billing page will only increase or remain the same. Usage will be reset to zero when a new billing cycle starts. Deleting a codespace, or a prebuild, will not reduce the usage figure for the current month, but it will reduce the rate at which storage usage accumulates.
 
-  {% endnote %}
 * Ensure that you are using prebuilds for only as many versions and as many regions as you need. See "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)" and "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces-prebuilds)."
-  {% note %}
 
-  **Note**: If your included storage usage is exhausted, new prebuilds are disabled until you set up a spending limit or your included usage quota renews.
+  > [!NOTE]
+  > If your included storage usage is exhausted, new prebuilds are disabled until you set up a spending limit or your included usage quota renews.
 
-  {% endnote %}
 * If you have configured prebuilds in a repository's settings, but you're not using {% data variables.product.prodname_github_codespaces %} for that repository, consider deleting the prebuild configuration to avoid prebuilds for that repository consuming your included storage allowance unnecessarily. When you delete a prebuild configuration all the associated prebuilds are deleted, reducing your storage consumption from that point onward. See "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/managing-prebuilds#deleting-a-prebuild-configuration)."
 
   You can check for prebuild configurations in the "{% data variables.product.prodname_codespaces %}" page of a repository's settings. See "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
diff --git a/content/communities/documenting-your-project-with-wikis/about-wikis.md b/content/communities/documenting-your-project-with-wikis/about-wikis.md
index af517d29fd..d8a0b4b714 100644
--- a/content/communities/documenting-your-project-with-wikis/about-wikis.md
+++ b/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -25,20 +25,16 @@ If you create a wiki in a public repository, the wiki is available to {% ifversi
 You can edit wikis directly on {% data variables.product.product_name %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.location.product_location %} to contribute to a wiki in a public repository. For more information, see "[AUTOTITLE](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)."
 
 {% ifversion fpt or ghec %}
-{% note %}
 
-**Note:** Search engines will only index wikis with 500 or more stars that you configure to prevent public editing. For more information, see "[AUTOTITLE](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)."
+> [!NOTE]
+> Search engines will only index wikis with 500 or more stars that you configure to prevent public editing. For more information, see "[AUTOTITLE](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)."
+>
+> If you need search engines to index your content, you can use {% data variables.product.prodname_pages %} in a public repository. For more information, see "[{% data variables.product.prodname_pages %}](/pages)."
 
-If you need search engines to index your content, you can use {% data variables.product.prodname_pages %} in a public repository. For more information, see "[{% data variables.product.prodname_pages %}](/pages)."
-
-{% endnote %}
 {% endif %}
 
-{% note %}
-
-**Note:** For performance reasons, wikis have a soft limit of 5,000 total files, regardless of file type. If you exceed this limit, some pages may be inaccessible to users. If you need a larger wiki, we recommend using {% data variables.product.prodname_pages %}. For more information, see "[{% data variables.product.prodname_pages %}](/pages)."
-
-{% endnote %}
+> [!NOTE]
+> For performance reasons, wikis have a soft limit of 5,000 total files, regardless of file type. If you exceed this limit, some pages may be inaccessible to users. If you need a larger wiki, we recommend using {% data variables.product.prodname_pages %}. For more information, see "[{% data variables.product.prodname_pages %}](/pages)."
 
 ## Further reading
 
diff --git a/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index 93cc84e179..ee3882bf94 100644
--- a/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -16,11 +16,8 @@ You can block non-members from within your organization's settings or from a spe
 
 {% data reusables.organizations.blocking-a-user %}
 
-{% tip %}
-
-**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[AUTOTITLE](/communities/moderating-comments-and-conversations/locking-conversations)."
-
-{% endtip %}
+> [!TIP]
+> If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[AUTOTITLE](/communities/moderating-comments-and-conversations/locking-conversations)."
 
 At the time that you block a user from your organization:
 * The user stops watching your organization's repositories
diff --git a/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
index 959caf4ee6..e406d7cd13 100644
--- a/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
+++ b/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
@@ -16,11 +16,8 @@ shortTitle: Block from your account
 
 You can block a user in your account settings or from the user's profile. {% data variables.product.prodname_dotcom %} will not notify the user when you block them. If you want to avoid contributing to the same project as someone you've blocked, you can choose to display a warning on any repositories with prior contributions from a blocked user. For more information, see "[Blocking a user in your account settings](#blocking-a-user-in-your-account-settings)." You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content.
 
-{% tip %}
-
-**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[AUTOTITLE](/communities/moderating-comments-and-conversations/locking-conversations)."
-
-{% endtip %}
+> [!TIP]
+> If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[AUTOTITLE](/communities/moderating-comments-and-conversations/locking-conversations)."
 
 When you block a user:
 * The user stops following you
diff --git a/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
index 8d9b4a725f..c381d8ce6e 100644
--- a/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
+++ b/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
@@ -80,14 +80,9 @@ If reported content is enabled for a public repository, you can also report cont
 1. In the lower-right corner of the template chooser, click **Report abuse**.
 1. Complete the contact form to tell {% data variables.contact.github_support %} about the contact link's behavior, then click **Send request**.
 
-{% note %}
-
-**Notes:**
-
-* In order to get accurate information about the abuse, the abuse report form will direct you to use the in-product abuse report links. If an in-product link is not available, contact {% data variables.contact.contact_support %} to report abuse or report content.
-* Users in India can contact {% data variables.product.prodname_dotcom %}'s Grievance Officer for India through [support.github.com/contact/india-grievance-officer](https://support.github.com/contact/india-grievance-officer).
-
-{% endnote %}
+> [!NOTE]
+> * In order to get accurate information about the abuse, the abuse report form will direct you to use the in-product abuse report links. If an in-product link is not available, contact {% data variables.contact.contact_support %} to report abuse or report content.
+> * Users in India can contact {% data variables.product.prodname_dotcom %}'s Grievance Officer for India through [support.github.com/contact/india-grievance-officer](https://support.github.com/contact/india-grievance-officer).
 
 ## Further reading
 
diff --git a/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index e22bf5e668..25ad3fb450 100644
--- a/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -16,11 +16,8 @@ After unblocking a user from your organization, they'll be able to contribute to
 
 If you selected a specific amount of time to block the user, they will be automatically unblocked when that period of time ends. For more information, see "[AUTOTITLE](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
 
-{% tip %}
-
-**Tip**: Any settings that were removed when you blocked the user from your organization, such as collaborator status, stars, and watches, will not be restored when you unblock the user.
-
-{% endtip %}
+> [!TIP]
+> Any settings that were removed when you blocked the user from your organization, such as collaborator status, stars, and watches, will not be restored when you unblock the user.
 
 ## Unblocking a user in a comment
 
diff --git a/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md b/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
index ee3d4ac084..28b0a8c6f3 100644
--- a/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
+++ b/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
@@ -32,11 +32,8 @@ You can unblock a user in your account settings or from the user's profile page.
    ![Screenshot of the sidebar of a user's profile page. A link, labeled "Unblock or report", is outlined in dark orange.](/assets/images/help/profile/profile-unblock-or-report-user.png)
 1. Click **Unblock user**.
 
-{% tip %}
-
-**Tip**: Settings that were removed when you blocked the user, such as collaborator status, stars, and follows, are not restored when you unblock the user.
-
-{% endtip %}
+> [!TIP]
+> Settings that were removed when you blocked the user, such as collaborator status, stars, and follows, are not restored when you unblock the user.
 
 ## Further reading
 
diff --git a/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
index a380d21061..9fdf47d0c8 100644
--- a/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
+++ b/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -82,11 +82,8 @@ Deleting a comment creates a timeline event that is visible to anyone with read
 
 ![Screenshot of a timeline event, which says "octo-org deleted a comment from hubot 6 minutes ago."](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png)
 
-{% note %}
-
-**Note:** The initial comment (or body) of an issue or pull request can't be deleted. Instead, you can edit issue and pull request bodies to remove unwanted content.
-
-{% endnote %}
+> [!NOTE]
+> The initial comment (or body) of an issue or pull request can't be deleted. Instead, you can edit issue and pull request bodies to remove unwanted content.
 
 ### Steps to delete a comment
 
diff --git a/content/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md b/content/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md
index ee8ce2484e..63854ef21e 100644
--- a/content/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md
+++ b/content/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md
@@ -19,11 +19,8 @@ To direct people to specific support resources, you can add a SUPPORT file to yo
 
 You can create default support resources for your organization or personal account. For more information, see "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
 
-{% tip %}
-
-**Tip:** To help people find your support guidelines, you can link to your SUPPORT file from other places in your repository, such as your [README file](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes).
-
-{% endtip %}
+> [!TIP]
+> To help people find your support guidelines, you can link to your SUPPORT file from other places in your repository, such as your [README file](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes).
 
 ## Adding support resources to your project
 
diff --git a/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
index ffd0cff405..871514c0e6 100644
--- a/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
+++ b/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -25,11 +25,8 @@ For both owners and contributors, contribution guidelines save time and hassle c
 
 You can create default contribution guidelines for your organization or personal account. For more information, see "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
 
-{% tip %}
-
-**Tip:** Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
-
-{% endtip %}
+> [!TIP]
+> Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
 
 ## Adding a _CONTRIBUTING_ file
 
diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
index 81e885accc..0627277491 100644
--- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
+++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
@@ -67,11 +67,8 @@ Here is the rendered version of the issue form.
 
 You can encourage contributors to use issue templates by setting `blank_issues_enabled` to `false`. If you set `blank_issues_enabled` to `true`, people will have the option to open a blank issue.
 
-{% note %}
-
-**Note:** If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your _config.yml_ file, the template in `issue_template.md` will be used when people choose to open a blank issue. If you disable blank issues, the template will never be used.
-
-{% endnote %}
+> [!NOTE]
+> If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your _config.yml_ file, the template in `issue_template.md` will be used when people choose to open a blank issue. If you disable blank issues, the template will never be used.
 
 If you prefer to receive certain reports outside of {% data variables.product.product_name %}, you can direct people to external sites with `contact_links`.
 
diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
index c29aadfec0..90d881d195 100644
--- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
+++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
@@ -32,11 +32,8 @@ assignees: octocat
 ---
 ```
 
-{% note %}
-
-**Note:** If a front matter value includes a YAML-reserved character such as `:` , you must put the whole value in quotes. For example, `":bug: Bug"` or `":new: triage needed, :bug: bug"`.
-
-{% endnote %}
+> [!NOTE]
+> If a front matter value includes a YAML-reserved character such as `:` , you must put the whole value in quotes. For example, `":bug: Bug"` or `":new: triage needed, :bug: bug"`.
 
 {% ifversion fpt or ghec %}
 
diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
index f3c081b051..6643c6c306 100644
--- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
+++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
@@ -9,11 +9,8 @@ topics:
   - Community
 ---
 
-{% note %}
-
-**Note:** {% data variables.product.company_short %}'s form schema is currently in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.company_short %}'s form schema is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 ## About {% data variables.product.company_short %}'s form schema
 
@@ -89,13 +86,10 @@ You can use a `markdown` element to display Markdown in your form that provides
 | --- | ----------- | -------- | ---- | ------- | ------- |
 | `value` | The text that is rendered. Markdown formatting is supported. | {% octicon "check" aria-label="Required" %} | String | {% octicon "dash" aria-label="Not applicable" %} | {% octicon "dash" aria-label="Not applicable" %} |
 
-{% tip %}
-
-**Tips:** YAML processing will treat the hash symbol as a comment. To insert Markdown headers, wrap your text in quotes.
-
-For multi-line text, you can use the pipe operator.
-
-{% endtip %}
+> [!TIP]
+> YAML processing will treat the hash symbol as a comment. To insert Markdown headers, wrap your text in quotes.
+>
+> For multi-line text, you can use the pipe operator.
 
 #### Example of `markdown`
 
diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
index 3cf52041d2..90428e7d59 100644
--- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
+++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
@@ -19,11 +19,8 @@ Issue forms are not supported for pull requests. You can create pull request tem
 
 This example YAML configuration file defines an issue form using several inputs to report a bug.
 
-{% note %}
-
-**Note:** The `required` field key is only supported in public repositories. In private and internal repositories, all fields are optional.
-
-{% endnote %}
+> [!NOTE]
+> The `required` field key is only supported in public repositories. In private and internal repositories, all fields are optional.
 
 {% data reusables.community.issue-forms-sample %}
 
diff --git a/content/contributing/collaborating-on-github-docs/about-contributing-to-github-docs.md b/content/contributing/collaborating-on-github-docs/about-contributing-to-github-docs.md
index c0a2bd0c9d..b575b809d5 100644
--- a/content/contributing/collaborating-on-github-docs/about-contributing-to-github-docs.md
+++ b/content/contributing/collaborating-on-github-docs/about-contributing-to-github-docs.md
@@ -16,11 +16,8 @@ The documentation repository is the place to discuss and collaborate on the docu
 
 If you've found something in the documentation content, or something about the docs.github.com website, that should be updated, search the open issues to see if someone else has reported the same thing. If it's something new, open an issue using a [template](https://github.com/github/docs/issues/new/choose). We'll use the issue to have a conversation about the problem you'd like to be fixed.<!-- markdownlint-disable-line search-replace -->
 
-{% note %}
-
-**Note**: {% data variables.product.prodname_dotcom %} employees should open issues in the private `docs-content` repository.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_dotcom %} employees should open issues in the private `docs-content` repository.
 
 ## Pull requests
 
diff --git a/content/contributing/collaborating-on-github-docs/using-git-on-github-docs.md b/content/contributing/collaborating-on-github-docs/using-git-on-github-docs.md
index 7ddf10da31..b82d560cbe 100644
--- a/content/contributing/collaborating-on-github-docs/using-git-on-github-docs.md
+++ b/content/contributing/collaborating-on-github-docs/using-git-on-github-docs.md
@@ -39,15 +39,12 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
      git checkout -b YOUR-TOPIC-BRANCH
      ```
 
-     {% note %}
-
-     **Note**: You can use forward slashes as part of the branch name, for example to include your user name:
-
-     ```shell
-     git checkout -b my-username/new-codespace-policy
-     ```
-
-     {% endnote %}
+     > [!NOTE]
+     > You can use forward slashes as part of the branch name, for example to include your user name:
+     >
+     > ```shell
+     > git checkout -b my-username/new-codespace-policy
+     > ```
 
    * To work on an existing project, switch to your topic branch and merge changes from `main`.
 
@@ -128,11 +125,10 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
 * Favor commits that contain small, focused groups of changes over commits with large, unfocused groups of changes, since this will help you write commit messages that other people can easily understand. An exception is the initial commit for a new project or category. These commits are sometimes large, as they often introduce the bare versions of many articles at once to provide an organizational scheme for subsequent work.
 * If you are incorporating feedback or want to address a set of changes to a particular person or team for review, @mention the person whose suggestions you are incorporating. For example: "Incorporating feedback from @octocat," or "Updating billing configuration steps - cc @monalisa for accuracy."
 * If a commit addresses an issue, you can reference the issue number in the commit, and a link to the commit will appear in the issue conversation timeline: "Addresses #1234 - adds steps for backing up the VM before upgrading."
-  {% note %}
 
-  **Note**: We generally don't close an issue via a commit. To close an issue, open a pull request and add "Closes #1234" to the description. The linked issue will be closed when the pull request is merged. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)."
+  > [!NOTE]
+  > We generally don't close an issue via a commit. To close an issue, open a pull request and add "Closes #1234" to the description. The linked issue will be closed when the pull request is merged. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)."
 
-  {% endnote %}
 * Make commit messages clear, detailed, and imperative. For example: "Adds a conceptual article about 2FA," not "Add info."
 * Try not to leave uncommitted changes in your local branch when you finish working for the day. Get to a good stopping point and commit and push your changes so your work is backed up to the remote repository.
 * Only push up to {% data variables.product.prodname_dotcom %} after you've made a few commits. Pushing after every commit adds noise to our ops channels on Slack and causes unnecessary builds to run.
@@ -167,11 +163,8 @@ There are two ways to handle merge conflicts:
 
    If there are multiple files with merge conflicts, repeat the previous steps until you resolve all conflicts.
 
-   {% note %}
-
-   **Note**: You should apply care when resolving merge conflicts. Sometimes you will simply accept your own changes, sometimes you will use the upstream changes from the `main` branch, and sometimes you will combine both sets of changes. If you're unsure of the best resolution, be wary of replacing the changes from upstream as these may have been made for specific reasons that you're not aware of.
-
-   {% endnote %}
+   > [!NOTE]
+   > You should apply care when resolving merge conflicts. Sometimes you will simply accept your own changes, sometimes you will use the upstream changes from the `main` branch, and sometimes you will combine both sets of changes. If you're unsure of the best resolution, be wary of replacing the changes from upstream as these may have been made for specific reasons that you're not aware of.
 
 1. In the terminal, stage the file, or files, that you just modified.
 
@@ -195,10 +188,7 @@ There are two ways to handle merge conflicts:
 
 We recommend you open your pull request on {% data variables.product.prodname_dotcom %} early. Create the pull request as a draft until you are ready for it to be reviewed. Each time you push changes, your commits will be added to the pull request.
 
-{% note %}
-
-**Note**: You can quickly access pull requests you've created by clicking **Pull requests** at the top of every page on {% data variables.product.prodname_dotcom %}.
-
-{% endnote %}
+> [!NOTE]
+> You can quickly access pull requests you've created by clicking **Pull requests** at the top of every page on {% data variables.product.prodname_dotcom %}.
 
 For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request?tool=webui#creating-the-pull-request)."
diff --git a/content/contributing/collaborating-on-github-docs/using-the-todocs-placeholder-to-leave-notes.md b/content/contributing/collaborating-on-github-docs/using-the-todocs-placeholder-to-leave-notes.md
index 00e79db955..0e7824c51f 100644
--- a/content/contributing/collaborating-on-github-docs/using-the-todocs-placeholder-to-leave-notes.md
+++ b/content/contributing/collaborating-on-github-docs/using-the-todocs-placeholder-to-leave-notes.md
@@ -13,11 +13,8 @@ Sometimes technical writers use placeholders while writing documentation to remi
 
 To prevent slips, use the string `TODOCS` as your placeholder. The Docs test suite includes a [linting test](https://github.com/github/docs/tree/main/src/content-linter) that will fail if it finds this string anywhere in a Markdown or YAML file.
 
-{% note %}
-
-**Note**: If you use {% data variables.product.prodname_vscode_shortname %} as your text editor, the "[TODO Highlight](https://marketplace.visualstudio.com/items?itemName=wayou.vscode-todo-highlight)" extension is useful for highlighting instances of "TODOCS" in your files. Add "TODOCS" and other varieties of casing, such as "todocs," to the settings for this extension.
-
-{% endnote %}
+> [!NOTE]
+> If you use {% data variables.product.prodname_vscode_shortname %} as your text editor, the "[TODO Highlight](https://marketplace.visualstudio.com/items?itemName=wayou.vscode-todo-highlight)" extension is useful for highlighting instances of "TODOCS" in your files. Add "TODOCS" and other varieties of casing, such as "todocs," to the settings for this extension.
 
 ### Example
 
diff --git a/content/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment.md b/content/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment.md
index 8bba1b296e..e0d915d710 100644
--- a/content/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment.md
+++ b/content/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment.md
@@ -53,13 +53,9 @@ You should now have a running server. To access your local preview environment,
 
 When you're ready to stop your local server, type <kbd>Ctrl</kbd>+<kbd>C</kbd> in your terminal window.
 
-{% note %}
-
-**Note:** You should typically only need to run `npm ci` and `npm run build` each time you pull the latest version of a branch.
- * `npm ci` does a clean install of dependencies, without updating the `package-lock.json` file.
- * `npm run build` creates static assets, such as JavaScript and CSS files.
-
-{% endnote %}
+> [!NOTE] You should typically only need to run `npm ci` and `npm run build` each time you pull the latest version of a branch.
+> * `npm ci` does a clean install of dependencies, without updating the `package-lock.json` file.
+> * `npm run build` creates static assets, such as JavaScript and CSS files.
 
 If you would like to read more about debugging and troubleshooting the {% data variables.product.prodname_docs %} application, see "[AUTOTITLE](/contributing/setting-up-your-environment-to-work-on-github-docs/troubleshooting-your-environment)" in the github/docs repository.
 
@@ -73,11 +69,8 @@ By default, the local server does not run with all supported languages enabled.
 
 For example, to enable Japanese and Portuguese in addition to English, you can edit `package.json` and set `ENABLED_LANGUAGES='en,ja,pt'` in the `start` script. Then restart the server for the change to take effect.
 
-{% note %}
-
-**Note:** Before you commit your changes, you should revert the `package.json` file to its original state.
-
-{% endnote %}
+> [!NOTE]
+> Before you commit your changes, you should revert the `package.json` file to its original state.
 
 The supported language codes are defined in [`src/languages/lib/languages.js`](https://github.com/github/docs/blob/main/src/languages/lib/languages.js).
 
diff --git a/content/contributing/writing-for-github-docs/creating-screenshots.md b/content/contributing/writing-for-github-docs/creating-screenshots.md
index a5bdd83798..7843846401 100644
--- a/content/contributing/writing-for-github-docs/creating-screenshots.md
+++ b/content/contributing/writing-for-github-docs/creating-screenshots.md
@@ -150,21 +150,16 @@ The stroke is the color `fg.severe` in the [Primer Design System](https://primer
    * Pixel depth: 144dpi (equivalent to "2x" on Snagit for Mac)
    * Pixel width: 1000 pixels maximum
 
-   {% note %}
+   > [!NOTE]
+   > On Windows, you may need to select **Advanced** to change the resolution. Ensure **Use resampling** is disabled.
 
-   **Note:** On Windows, you may need to select **Advanced** to change the resolution. Ensure **Use resampling** is disabled.
-
-   {% endnote %}
 1. With the {% data variables.product.prodname_docs %} theme open in the Shapes sidebar, select the dark orange rectangle.
 1. Drag and drop across the image to create a rectangle.
 1. Adjust the rectangle's height and width by dragging edges. Do not adjust the corner rounding, which should remain 4 px. Adjust the space between the UI element and the stroke so it's about the width of the stroke itself.
 1. Export image to PNG.
 
-{% note %}
-
-**Note:** A bug in Snagit may corrupt the corner rounding, causing rectangles to become ovals. If this occurs, delete and reinstall the {% data variables.product.prodname_docs %} theme (Windows and Mac), or click and drag the yellow dot at the top right of the shape to reset corner rounding to 4 px (Mac only).
-
-{% endnote %}
+> [!NOTE]
+> A bug in Snagit may corrupt the corner rounding, causing rectangles to become ovals. If this occurs, delete and reinstall the {% data variables.product.prodname_docs %} theme (Windows and Mac), or click and drag the yellow dot at the top right of the shape to reset corner rounding to 4 px (Mac only).
 
 ## Replacing screenshots
 
diff --git a/content/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs.md b/content/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs.md
index 21035b8b9f..bd5ac15967 100644
--- a/content/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs.md
+++ b/content/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs.md
@@ -394,11 +394,8 @@ For more information about links, see "[AUTOTITLE](/contributing/style-guide-and
 
 Because the site is dynamic, it does not build HTML files for each different version of an article. Instead it generates a "permalink" for every version of the article. It does this based on the article's [`versions` frontmatter](/contributing/syntax-and-versioning-for-github-docs/using-yaml-frontmatter#versions).
 
-{% note %}
-
-**Note**: As of early 2021, the `free-pro-team@latest` version is not included in URLs. A helper function called `lib/remove-fpt-from-path.js` removes the version from URLs.
-
-{% endnote %}
+> [!NOTE]
+> As of early 2021, the `free-pro-team@latest` version is not included in URLs. A helper function called `lib/remove-fpt-from-path.js` removes the version from URLs.
 
 For example, an article that is available in currently supported versions will have permalink URLs like the following:
 
@@ -414,11 +411,8 @@ An article that is not available in {% data variables.product.prodname_ghe_serve
 
 * `/en/get-started/getting-started-with-git/set-up-git`
 
-{% note %}
-
-**Note:** If you are a content contributor, you don't need to worry about supported versions when adding a link to a document. Following the examples above, if you want to reference an article, you can just use its relative location: `/github/getting-started-with-github/set-up-git`.
-
-{% endnote %}
+> [!NOTE]
+> If you are a content contributor, you don't need to worry about supported versions when adding a link to a document. Following the examples above, if you want to reference an article, you can just use its relative location: `/github/getting-started-with-github/set-up-git`.
 
 ### Internal links with AUTOTITLE
 
@@ -430,11 +424,8 @@ When linking to another {% data variables.product.prodname_docs %} page, use sta
 * `For more information, see "[AUTOTITLE](/path/to/page#section-link)."`
 * `For more information, see the TOOLNAME documentation in "[AUTOTITLE](/path/to/page?tool=TOOLNAME)."`
 
-{% note %}
-
-**Note:** Same-page section links do not work with this keyword. Type out the full header text instead.
-
-{% endnote %}
+> [!NOTE]
+> Same-page section links do not work with this keyword. Type out the full header text instead.
 
 ### Linking to the current article in a different version of the docs
 
diff --git a/content/contributing/writing-for-github-docs/using-yaml-frontmatter.md b/content/contributing/writing-for-github-docs/using-yaml-frontmatter.md
index 1d68707961..ef4dc4be9a 100644
--- a/content/contributing/writing-for-github-docs/using-yaml-frontmatter.md
+++ b/content/contributing/writing-for-github-docs/using-yaml-frontmatter.md
@@ -228,11 +228,8 @@ defaultTool: cli
 * Type: `String`. This should reference learning tracks' names defined in [`data/learning-tracks/*.yml`](https://github.com/github/docs/tree/main/data/learning-tracks).
 * Optional
 
-{% note %}
-
-**Note:** the featured track is set by a specific property in the learning tracks YAML. See that [README](https://github.com/github/docs/blob/main/data/learning-tracks/README.md) for details.
-
-{% endnote %}
+> [!NOTE]
+> The featured track is set by a specific property in the learning tracks YAML. See that [README](https://github.com/github/docs/blob/main/data/learning-tracks/README.md) for details.
 
 ### `includeGuides`
 
@@ -274,11 +271,8 @@ includeGuides:
 * Type: `string` YEAR-MONTH-DAY e.g. 2021-10-04 is October 4th, 2021
 * Optional.
 
-{% note %}
-
-**Note:** The `effectiveDate` frontmatter value is for use by {% data variables.product.company_short %} staff only.
-
-{% endnote %}
+> [!NOTE]
+> The `effectiveDate` frontmatter value is for use by {% data variables.product.company_short %} staff only.
 
 ## Escaping single quotes
 
@@ -304,11 +298,8 @@ When adding a new article, make sure the filename is a [kebab-cased](https://en.
 
 Index pages are the table of contents files for the Docs site. Every product, category, and map topic subdirectory has an `index.md` file that provides an overview of the content and links to every child article. Each `index.md` must contain a `children` frontmatter property with a list of relative links to the child pages of the product, category, or map topic. Index pages require a `versions` frontmatter property, and the actual value will be computed at runtime based on the versions of children articles.
 
-{% note %}
-
-**Note**: The site only knows about paths included in `children` frontmatter. If a directory or article exists but is **not** included in `children`, its path will return a 404.
-
-{% endnote %}
+> [!NOTE]
+> The site only knows about paths included in `children` frontmatter. If a directory or article exists but is **not** included in `children`, its path will return a 404.
 
 ## Homepage
 
diff --git a/content/contributing/writing-for-github-docs/versioning-documentation.md b/content/contributing/writing-for-github-docs/versioning-documentation.md
index 347622a71f..97c5301953 100644
--- a/content/contributing/writing-for-github-docs/versioning-documentation.md
+++ b/content/contributing/writing-for-github-docs/versioning-documentation.md
@@ -106,15 +106,10 @@ We use the [Liquid template language](https://shopify.github.io/liquid/basics/in
 
 If you define multiple products in the `versions` key within a page's YAML frontmatter, you can use the conditional operators `ifversion`/`else` (or `ifversion`/`elsif`/`else`) in the Markdown to control how the site renders content on the page for a particular product. For example, a feature may have more options on {% data variables.product.prodname_dotcom_the_website %} than on {% data variables.product.prodname_ghe_server %}, so you can version the content appropriately via the `versions` frontmatter, and use Liquid conditionals to describe the additional options for {% data variables.product.prodname_dotcom_the_website %}.
 
-{% note %}
-
-**Notes:**
-
-* Use `ifversion` for product-based versioning and [feature-based versioning](#about-feature-based-versioning).
-* Do not use `if` or `unless`.
-* Make sure to use `elsif` and not `else if`. Liquid does not recognize `else if` and will not render content inside an `else if` block.
-
-{% endnote %}
+> [!NOTE]
+> * Use `ifversion` for product-based versioning and [feature-based versioning](#about-feature-based-versioning).
+> * Do not use `if` or `unless`.
+> * Make sure to use `elsif` and not `else if`. Liquid does not recognize `else if` and will not render content inside an `else if` block.
 
 ### Comparison operators
 
@@ -195,11 +190,8 @@ Feature-based versioning provides named "feature flags" that simplify the mainte
 
 Each feature is managed through individual YAML files in `data/features/`.
 
-{% note %}
-
-**Note**: Do not delete `data/features/placeholder.yml` because it is used by tests.
-
-{% endnote %}
+> [!NOTE]
+> Do not delete `data/features/placeholder.yml` because it is used by tests.
 
 To create a new feature, first create a new YAML file with the feature name you want to use in this directory. For a feature named `meow`, that would be `data/features/meow.yml`.
 
diff --git a/content/desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md b/content/desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md
index ea5398be80..ec0e481313 100644
--- a/content/desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md
+++ b/content/desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md
@@ -9,11 +9,9 @@ versions:
   feature: desktop
 shortTitle: Add a repository
 ---
-{% tip %}
 
-**Tip:** You can add a Git repository from your local computer to GitHub Desktop by dragging the folder onto the {% data variables.product.prodname_desktop %} window. If you drag multiple Git folders into {% data variables.product.prodname_desktop %} at the same time, each folder will be added as a separate Git repository.
-
-{% endtip %}
+> [!TIP]
+> You can add a Git repository from your local computer to GitHub Desktop by dragging the folder onto the {% data variables.product.prodname_desktop %} window. If you drag multiple Git folders into {% data variables.product.prodname_desktop %} at the same time, each folder will be added as a separate Git repository.
 
 {% mac %}
 
diff --git a/content/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md b/content/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md
index 51e5b4705f..5209b00830 100644
--- a/content/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md
+++ b/content/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md
@@ -9,11 +9,9 @@ versions:
   feature: desktop
 shortTitle: Clone a GitHub repo
 ---
-{% tip %}
 
-**Tip:**  You also can use {% data variables.product.prodname_desktop %} to clone repositories that exist on {% data variables.product.prodname_dotcom %}.  For more information, see "[AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop)."
-
-{% endtip %}
+> [!TIP]
+> You also can use {% data variables.product.prodname_desktop %} to clone repositories that exist on {% data variables.product.prodname_dotcom %}.  For more information, see "[AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop)."
 
 1. Sign in to {% data variables.product.github %} and {% data variables.product.prodname_desktop %} before you start to clone.
 {% data reusables.repositories.navigate-to-repo %}
@@ -22,10 +20,7 @@ shortTitle: Clone a GitHub repo
 
    ![Screenshot of the "URL" tab of the "Clone a Repository" window. Next to the "Local Path" field, a button, labeled "Choose", is highlighted with an orange outline.](/assets/images/help/desktop/clone-choose-button-url-mac.png)
 
-   {% note %}
-
-   **Note:** If the repository is configured to use LFS, you will be prompted to initialize {% data variables.large_files.product_name_short %}.
-
-   {% endnote %}
+   > [!NOTE]
+   > If the repository is configured to use LFS, you will be prompted to initialize {% data variables.large_files.product_name_short %}.
 
 1. Click **Clone**.
diff --git a/content/desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor-in-github-desktop.md b/content/desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor-in-github-desktop.md
index a9dd91c591..e7ad0bfc37 100644
--- a/content/desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor-in-github-desktop.md
+++ b/content/desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor-in-github-desktop.md
@@ -122,22 +122,20 @@ If you want to open another repository in the default editor, you can use the re
 1. In the upper-left corner of {% data variables.product.prodname_desktop %}, to the right of the current repository name, click {% octicon "triangle-down" aria-label="The triangle-down icon" %}.
 1. Right-click the repository, then click **Open in default editor**.
 
-{% tip %}
-
 {% mac %}
 
-**Tip:** You can use the <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>A</kbd> keyboard shortcut to open a repository in the default editor.
+> [!TIP]
+> You can use the <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>A</kbd> keyboard shortcut to open a repository in the default editor.
 
 {% endmac %}
 
 {% windows %}
 
-**Tip:** You can use the <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>A</kbd> keyboard shortcut to open a repository in the default editor.
+> [!TIP]
+> You can use the <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>A</kbd> keyboard shortcut to open a repository in the default editor.
 
 {% endwindows %}
 
-{% endtip %}
-
 ## Opening a file in the default editor
 
 1. Navigate to the "Changes" tab in the left sidebar.
diff --git a/content/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md b/content/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md
index c2416ab7ea..a0c4a2535e 100644
--- a/content/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md
+++ b/content/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md
@@ -19,11 +19,8 @@ If the email address that has been set in your Git configuration does not match
 
 {% data variables.product.prodname_desktop %} also allows you to change the default branch name that you would like to use when creating new repositories. By default, {% data variables.product.prodname_desktop %} uses `main` as the default branch name in any new repositories you create.
 
-{% tip %}
-
-**Tip**: Anyone will be able to see the email address in your Git configuration if you make public commits. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)."
-
-{% endtip %}
+> [!TIP]
+> Anyone will be able to see the email address in your Git configuration if you make public commits. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)."
 
 ## Configuring your global author information
 
diff --git a/content/desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md b/content/desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
index b4c0920688..39fa1cae38 100644
--- a/content/desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
+++ b/content/desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
@@ -44,11 +44,8 @@ You can install {% data variables.product.prodname_desktop %} on {% data variabl
 
 You can install {% data variables.product.prodname_desktop %} on {% data variables.desktop.windows-versions %}.
 
-{% warning %}
-
-**Warning**: You must have a 64-bit operating system to run {% data variables.product.prodname_desktop %}.
-
-{% endwarning %}
+> [!WARNING]
+> You must have a 64-bit operating system to run {% data variables.product.prodname_desktop %}.
 
 {% data reusables.desktop.download-desktop-page %}
 1. Click **Download for Windows**.
diff --git a/content/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md b/content/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md
index 3c4bc9114e..e194979698 100644
--- a/content/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md
+++ b/content/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md
@@ -88,11 +88,8 @@ Discarded changes are saved in a dated file in the Trash. You can recover discar
 
 You can discard one or more changed lines that are uncommitted.
 
-{% note %}
-
-**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines.
-
-{% endnote %}
+> [!NOTE]
+> Discarding single lines is disabled in a group of changes that adds and removes lines.
 
 To discard one added line, in the list of changed lines, right-click the line number of the line you want to discard, then select **Discard Added Line**.
 
@@ -106,11 +103,8 @@ To discard a group of changed lines, right-click the vertical bar to the right o
 
 Once you're satisfied with the changes you've chosen to include in your commit, write your commit message and push your changes. If you've collaborated on a commit, you can also attribute a commit to more than one author.
 
-{% note %}
-
-**Note**: {% data reusables.desktop.tags-push-with-commits %} For more information, see "[AUTOTITLE](/desktop/managing-commits/managing-tags-in-github-desktop)."
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.desktop.tags-push-with-commits %} For more information, see "[AUTOTITLE](/desktop/managing-commits/managing-tags-in-github-desktop)."
 
 {% data reusables.desktop.commit-message %}
 
diff --git a/content/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md b/content/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md
index 416450259a..586ad7423d 100644
--- a/content/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md
+++ b/content/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md
@@ -35,11 +35,8 @@ Repository administrators can also enable rulesets. Rulesets can be used to requ
 
 ## Creating a branch
 
-{% tip %}
-
-**Tip:** The first new branch you create will be based on the default branch. If you have more than one branch, you can choose to base the new branch on the currently checked out branch or the default branch.
-
-{% endtip %}
+> [!TIP]
+> The first new branch you create will be based on the default branch. If you have more than one branch, you can choose to base the new branch on the currently checked out branch or the default branch.
 
 {% data reusables.desktop.click-base-branch-in-drop-down %}
 {% data reusables.desktop.create-new-branch %}
@@ -72,11 +69,9 @@ If you create a branch on {% data variables.product.product_name %}, you'll need
 ## Switching between branches
 
 You can view and make commits to any of your repository's branches. If you have uncommitted, saved changes, you'll need to decide what to do with your changes before you can switch branches. You can commit your changes on the current branch, stash your changes to temporarily save them on the current branch, or bring the changes to your new branch. If you want to commit your changes before switching branches, see "[AUTOTITLE](/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop)."
-{% tip %}
 
-**Tip**: You can set a default behavior for switching branches in the **Prompts** settings. For more information, see "[AUTOTITLE](/desktop/configuring-and-customizing-github-desktop/configuring-basic-settings-in-github-desktop)."
-
-{% endtip %}
+> [!TIP]
+> You can set a default behavior for switching branches in the **Prompts** settings. For more information, see "[AUTOTITLE](/desktop/configuring-and-customizing-github-desktop/configuring-basic-settings-in-github-desktop)."
 
 1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to switch to.
    ![Screenshot of the "Current Branch" dropdown view. Under "Recent Branches", a branch, named "my-feature", is highlighted with an orange outline.](/assets/images/help/desktop/select-branch-from-dropdown.png)
diff --git a/content/desktop/making-changes-in-a-branch/pushing-changes-to-github-from-github-desktop.md b/content/desktop/making-changes-in-a-branch/pushing-changes-to-github-from-github-desktop.md
index f7fb03c0ef..8ea356794f 100644
--- a/content/desktop/making-changes-in-a-branch/pushing-changes-to-github-from-github-desktop.md
+++ b/content/desktop/making-changes-in-a-branch/pushing-changes-to-github-from-github-desktop.md
@@ -27,16 +27,13 @@ Repository administrators can also enable rulesets for a branch, which will prev
 
 ## Pushing changes to {% data variables.product.prodname_dotcom %}
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_desktop %} will reject a push if it exceeds certain limits.
-
-* A push contains a large file over {% data variables.large_files.max_github_size %} in size.
-* A push is over {% data variables.large_files.max_file_size %} in total size.
-
-If you configure {% data variables.large_files.product_name_long %} to track your large files, you can push large files that would normally be rejected. For more information, see "[AUTOTITLE](/desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop)."
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_desktop %} will reject a push if it exceeds certain limits.
+>
+> * A push contains a large file over {% data variables.large_files.max_github_size %} in size.
+> * A push is over {% data variables.large_files.max_file_size %} in total size.
+>
+> If you configure {% data variables.large_files.product_name_long %} to track your large files, you can push large files that would normally be rejected. For more information, see "[AUTOTITLE](/desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop)."
 
 {% data reusables.desktop.push-origin %}
 1. If there are commits on the remote branch that you don't have on your local branch, {% data variables.product.prodname_desktop %} prompts you to fetch new commits from the remote. In the "New Commits on Remote" window, click **Fetch**.
diff --git a/content/desktop/managing-commits/checking-out-a-commit-in-github-desktop.md b/content/desktop/managing-commits/checking-out-a-commit-in-github-desktop.md
index f4bedf3caf..adf86f3567 100644
--- a/content/desktop/managing-commits/checking-out-a-commit-in-github-desktop.md
+++ b/content/desktop/managing-commits/checking-out-a-commit-in-github-desktop.md
@@ -14,11 +14,8 @@ Checking out a commit allows you to view your repository in a previous state wit
 
 Checking out a commit puts your repository in a "detached HEAD" state. In Git terminology "HEAD" is the reference that points to the tip, or latest commit, of a named branch in your repository. A "detached HEAD" state means that HEAD refers to a specific commit, but not on a named branch in your repository.
 
-{% note %}
-
-**Note:** Any commits made in a "detached HEAD" state will be lost when switching branches, since these commits have not been made on a named branch. If you need to recover the lost commits, see "[Troubleshooting](#troubleshooting)."
-
-{% endnote %}
+> [!NOTE]
+> Any commits made in a "detached HEAD" state will be lost when switching branches, since these commits have not been made on a named branch. If you need to recover the lost commits, see "[Troubleshooting](#troubleshooting)."
 
 ## Checking out a commit
 
diff --git a/content/desktop/managing-commits/managing-tags-in-github-desktop.md b/content/desktop/managing-commits/managing-tags-in-github-desktop.md
index bb7d6d2dd5..f59465d7a3 100644
--- a/content/desktop/managing-commits/managing-tags-in-github-desktop.md
+++ b/content/desktop/managing-commits/managing-tags-in-github-desktop.md
@@ -27,11 +27,9 @@ versions:
 
 {% data reusables.desktop.history-tab %}
 1. Click the commit.
-   {% note %}
 
-   **Note**: {% data variables.product.prodname_desktop %} displays an arrow {% octicon "arrow-up" aria-label="The up arrow icon" %} if the tag has not been pushed to the remote repository.
-
-   {% endnote %}
+   > [!NOTE]
+   > {% data variables.product.prodname_desktop %} displays an arrow {% octicon "arrow-up" aria-label="The up arrow icon" %} if the tag has not been pushed to the remote repository.
 
    ![Screenshot of a list of commits in the "History" tab. Next to a commit, a "hello-tag" label and an "up arrow" icon are outlined in orange.](/assets/images/help/desktop/viewing-tags-in-history.png)
 
@@ -41,11 +39,8 @@ versions:
 
 ## Deleting tags
 
-{% note %}
-
-**Note**: You can only delete tags associated with commits that have not yet been pushed.
-
-{% endnote %}
+> [!NOTE]
+> You can only delete tags associated with commits that have not yet been pushed.
 
 {% data reusables.desktop.history-tab %}
 {% data reusables.desktop.delete-tag %}
diff --git a/content/desktop/managing-commits/options-for-managing-commits-in-github-desktop.md b/content/desktop/managing-commits/options-for-managing-commits-in-github-desktop.md
index e6199597dd..f92403a3b9 100644
--- a/content/desktop/managing-commits/options-for-managing-commits-in-github-desktop.md
+++ b/content/desktop/managing-commits/options-for-managing-commits-in-github-desktop.md
@@ -16,11 +16,8 @@ When you're contributing changes to a repository, your commit history should tel
 
 Often, it is difficult to follow these best practices perfectly at the point where you're making changes. You might realize you need to undo the changes in a commit you've made, edit a commit message, or reorder your commits to tell a clearer story. With {% data variables.product.prodname_desktop %}, you can manage your commit history directly from the user interface.
 
-{% note %}
-
-**Note:** Where possible, you should avoid changing the history of commits that have already been pushed to the remote repository. Other contributors may have already based work on these commits.
-
-{% endnote %}
+> [!NOTE]
+> Where possible, you should avoid changing the history of commits that have already been pushed to the remote repository. Other contributors may have already based work on these commits.
 
 ## Options for managing commit history in {% data variables.product.prodname_desktop %}
 
diff --git a/content/desktop/managing-commits/reverting-a-commit-in-github-desktop.md b/content/desktop/managing-commits/reverting-a-commit-in-github-desktop.md
index 59c2475cc1..5ad99b60d9 100644
--- a/content/desktop/managing-commits/reverting-a-commit-in-github-desktop.md
+++ b/content/desktop/managing-commits/reverting-a-commit-in-github-desktop.md
@@ -12,11 +12,8 @@ versions:
 ---
 When you revert to a previous commit, the revert is also a commit. The original commit also remains in the repository's history.
 
-{% tip %}
-
-**Tip:** When you revert multiple commits, it's best to revert in order from newest to oldest. If you revert commits in a different order, you may see merge conflicts.
-
-{% endtip %}
+> [!TIP]
+> When you revert multiple commits, it's best to revert in order from newest to oldest. If you revert commits in a different order, you may see merge conflicts.
 
 {% data reusables.desktop.history-tab %}
 {% data reusables.desktop.revert-commit %}
diff --git a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md
index 4ce51daa76..480e724325 100644
--- a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md
+++ b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md
@@ -43,11 +43,8 @@ Before you create a pull request, you'll need to push changes to a branch on {%
 
 1. On {% data variables.product.prodname_dotcom %}, click **Get started** to open an issue template or click **Open a blank issue**.
 
-{% note %}
-
-**Note**: If issue templates aren't enabled in your current repository, {% data variables.product.prodname_desktop %} will direct you to a blank issue on {% data variables.product.prodname_dotcom %}.
-
-{% endnote %}
+> [!NOTE]
+> If issue templates aren't enabled in your current repository, {% data variables.product.prodname_desktop %} will direct you to a blank issue on {% data variables.product.prodname_dotcom %}.
 
 ## Creating a pull request
 
diff --git a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/syncing-your-branch-in-github-desktop.md b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/syncing-your-branch-in-github-desktop.md
index 391f50f439..b2e58c4eee 100644
--- a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/syncing-your-branch-in-github-desktop.md
+++ b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/syncing-your-branch-in-github-desktop.md
@@ -40,11 +40,9 @@ Some workflows require or benefit from rebasing instead of merging. By rebasing
 {% data reusables.desktop.choose-a-branch-to-merge %}
 {% data reusables.desktop.confirm-merging-branch %}
 
-   {% note %}
+   > [!NOTE]
+   > If there are merge conflicts, {% data variables.product.prodname_desktop %} will warn you above the **Merge BRANCH into BRANCH** button. You will not be able to merge the branches until you have resolved all conflicts.
 
-   **Note:** If there are merge conflicts, {% data variables.product.prodname_desktop %} will warn you above the **Merge BRANCH into BRANCH** button. You will not be able to merge the branches until you have resolved all conflicts.
-
-   {% endnote %}
 {% data reusables.desktop.push-origin %}
 
 ## Rebasing your project branch onto another branch
@@ -88,11 +86,9 @@ Some workflows require or benefit from rebasing instead of merging. By rebasing
 
 1. In the "Squash and merge" window, click the branch you want to merge into the current branch, then click **Squash and merge**.
 
-   {% note %}
+   > [!NOTE]
+   > If there are merge conflicts, {% data variables.product.prodname_desktop %} will warn you above the **Squash and merge** button. You will not be able to squash and merge the branch until you have resolved all conflicts.
 
-   **Note:** If there are merge conflicts, {% data variables.product.prodname_desktop %} will warn you above the **Squash and merge** button. You will not be able to squash and merge the branch until you have resolved all conflicts.
-
-   {% endnote %}
 {% data reusables.desktop.push-origin %}
 
 ## Further Reading
diff --git a/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
index 7c51d1db68..d777a0ad94 100644
--- a/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
+++ b/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
@@ -20,11 +20,10 @@ versions:
 It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion. {% ifversion discussions-lock-allow-reactions %}You can also allow emoji reactions to a locked discussion.{% endif %}
 
 {% ifversion discussions-closable %}
-{% note %}
 
-**Note:** You can also close a discussion. For more information, see "[Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion)."
+> [!NOTE]
+> You can also close a discussion. For more information, see "[Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion)."
 
-{% endnote %}
 {% endif %}
 
 {% data reusables.discussions.navigate-to-repo-or-org %}
diff --git a/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
index 9425871fa1..a72570d981 100644
--- a/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
+++ b/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
@@ -19,11 +19,8 @@ You can use discussions insights to help understand the contribution activity, p
 
 ![Screenshot of the "Community insights" page. A dashboard displays graphs for data related to Discussions, such as page views.](/assets/images/help/discussions/discussions-dashboard.png)
 
-{% note %}
-
-**Note:** To view the exact data for a time period, hover over that time period in the graph.
-
-{% endnote %}
+> [!NOTE]
+> To view the exact data for a time period, hover over that time period in the graph.
 
 ## Viewing discussions insights
 
diff --git a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/about-github-education-for-students.md b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/about-github-education-for-students.md
index 892aaa1a4f..483593afd7 100644
--- a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/about-github-education-for-students.md
+++ b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/about-github-education-for-students.md
@@ -37,11 +37,8 @@ Once you are a verified {% data variables.product.prodname_global_campus %} stud
 * **{% data variables.product.prodname_copilot %}**: Verified students receive a free subscription for {% data variables.product.prodname_copilot %}. See "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-free-access-to-copilot-as-a-student-teacher-or-maintainer)."
 * **{% data variables.product.prodname_github_codespaces %}**: {% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[AUTOTITLE](/codespaces/overview)."
 
-{% note %}
-
-**Note:** {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)."
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)."
 
 ## Further reading
 
diff --git a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/apply-to-github-education-as-a-student.md b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/apply-to-github-education-as-a-student.md
index 8806eafbcf..5d20ddcc4b 100644
--- a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/apply-to-github-education-as-a-student.md
+++ b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/apply-to-github-education-as-a-student.md
@@ -26,11 +26,8 @@ Documents that prove your current student status include a picture of your schoo
 
 During your tenure as a student, you may be prompted to periodically re-verify your current academic status.
 
-{% note %}
-
-**Note:** You cannot transfer academic discounts from one account to another. If you have more than one account you want to apply the discount to, consider [merging](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/merging-multiple-personal-accounts) your personal accounts and [renaming](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) the retained account if desired.
-
-{% endnote %}
+> [!NOTE]
+> You cannot transfer academic discounts from one account to another. If you have more than one account you want to apply the discount to, consider [merging](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/merging-multiple-personal-accounts) your personal accounts and [renaming](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) the retained account if desired.
 
 For information about renewing your {% data variables.product.prodname_global_campus %} access, see "[AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student#expiration-and-renewals)."
 
diff --git a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/why-wasnt-my-application-to-github-education-for-students-approved.md b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/why-wasnt-my-application-to-github-education-for-students-approved.md
index 81e653600b..b9590b209c 100644
--- a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/why-wasnt-my-application-to-github-education-for-students-approved.md
+++ b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/why-wasnt-my-application-to-github-education-for-students-approved.md
@@ -14,11 +14,9 @@ versions:
   fpt: '*'
 shortTitle: Application not approved
 ---
-{% tip %}
 
-**Tip:** {% data reusables.education.about-github-education-link %}
-
-{% endtip %}
+> [!TIP]
+> {% data reusables.education.about-github-education-link %}
 
 ## Unclear academic affiliation documents
 
@@ -46,11 +44,8 @@ If you have other questions or concerns about the school domain please ask your
 
 If your academic email address was already used to request a {% data variables.product.prodname_student_pack %} for a different {% data variables.product.prodname_dotcom %} account, you cannot reuse the academic email address to successfully apply for another {% data variables.product.prodname_student_pack %}.
 
-{% note %}
-
-**Note:** It is against the {% data variables.product.prodname_dotcom %} [Terms of Service](/site-policy/github-terms/github-terms-of-service#3-account-requirements) to maintain more than one individual account.
-
-{% endnote %}
+> [!NOTE]
+> It is against the {% data variables.product.prodname_dotcom %} [Terms of Service](/site-policy/github-terms/github-terms-of-service#3-account-requirements) to maintain more than one individual account.
 
 If you have more than one personal account, you must merge your accounts. To retain the discount, keep the account that was granted the discount. You can rename the retained account and keep your contribution history by adding all your email addresses to the retained account.
 
diff --git a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/why-wasnt-my-application-to-github-education-for-teachers-approved.md b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/why-wasnt-my-application-to-github-education-for-teachers-approved.md
index 015ded6693..3072c1ffe5 100644
--- a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/why-wasnt-my-application-to-github-education-for-teachers-approved.md
+++ b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/why-wasnt-my-application-to-github-education-for-teachers-approved.md
@@ -14,11 +14,9 @@ versions:
   fpt: '*'
 shortTitle: Application not approved
 ---
-{% tip %}
 
-**Tip:** {% data reusables.education.about-github-education-link %}
-
-{% endtip %}
+> [!TIP]
+> {% data reusables.education.about-github-education-link %}
 
 ## Unclear proof of affiliation documents
 
diff --git a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/applying-to-be-a-github-campus-expert.md b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/applying-to-be-a-github-campus-expert.md
index cac0a9790b..f757796e8b 100644
--- a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/applying-to-be-a-github-campus-expert.md
+++ b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/applying-to-be-a-github-campus-expert.md
@@ -10,15 +10,12 @@ shortTitle: Apply to Campus Experts
 
 To apply to the {% data variables.product.prodname_student_leader_program %} program, you must first submit an application form, then submit a video resume. Applications to the program open in February and August, and you’ll have a full month to apply.
 
-{% note %}
-
-**Note:** The application process helps us get to know the applicant. Here are some things we want to learn about you:
-* Motivation: What makes you tick? What drives you?
-* Interest: Why do you want to be part of the program?
-* Growth and potential: What skills do you want to learn, and how will they help you grow personally and professionally?
-* Contribution: What impact do you want to make on your campus?
-
-{% endnote %}
+> [!NOTE]
+> The application process helps us get to know the applicant. Here are some things we want to learn about you:
+> * Motivation: What makes you tick? What drives you?
+> * Interest: Why do you want to be part of the program?
+> * Growth and potential: What skills do you want to learn, and how will they help you grow personally and professionally?
+> * Contribution: What impact do you want to make on your campus?
 
 ### Eligibility criteria
 
@@ -48,11 +45,8 @@ In the application form, we’re looking for students to tell us about the chall
 
 In your video resume, we look forward to getting to know you as an individual.
 
-{% note %}
-
-**Note:** A video using your webcam and computer microphone is more than enough! We understand this process might not be accessible to all students. If you require an alternative method to make your submission, please reach out to the GitHub Education team.
-
-{% endnote %}
+> [!NOTE]
+> A video using your webcam and computer microphone is more than enough! We understand this process might not be accessible to all students. If you require an alternative method to make your submission, please reach out to the GitHub Education team.
 
 1. Open the email you received after submitting your application form.
 1. Using the guidelines included in the application status email, record your video resume.
diff --git a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
index d8b56e95cd..71c25a8164 100644
--- a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
+++ b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
@@ -8,11 +8,8 @@ redirect_from:
   - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom
 ---
 
-{% note %}
-
-**Note:** The [{% data variables.product.prodname_classroom %} extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext) is no longer in active development. The **Open in {% data variables.product.prodname_vscode_shortname %}** badge in student repositories still works, but other features of the extension may not function as expected.
-
-{% endnote %}
+> [!NOTE]
+> The [{% data variables.product.prodname_classroom %} extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext) is no longer in active development. The **Open in {% data variables.product.prodname_vscode_shortname %}** badge in student repositories still works, but other features of the extension may not function as expected.
 
 ## About {% data variables.product.prodname_vscode %}
 
@@ -32,11 +29,8 @@ When creating an assignment, {% data variables.product.prodname_vscode_shortname
 
 This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click.
 
-{% note %}
-
-**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. The student can download Git from [Git download](https://git-scm.com/downloads).
-
-{% endnote %}
+> [!NOTE]
+> The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. The student can download Git from [Git download](https://git-scm.com/downloads).
 
 ### How to use {% data variables.product.prodname_classroom %} extension pack
 
diff --git a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
index cad6fcdad5..538120623a 100644
--- a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
+++ b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
@@ -19,19 +19,13 @@ Setting {% data variables.product.prodname_github_codespaces %} as the preferred
 
 For assignments with complex setup environments, teachers can customize the dev container configuration for a repository's codespaces. This ensures that when a student creates a codespace, it automatically opens with the development environment configured by the teacher. For more information on dev containers, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
 
-{% note %}
-
-**Note**: Individual codespaces are automatically deleted if they are stopped and left unused for a prolonged period. See "[AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces)."
-
-{% endnote %}
+> [!NOTE]
+> Individual codespaces are automatically deleted if they are stopped and left unused for a prolonged period. See "[AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces)."
 
 {% data reusables.education.student-codespaces-benefit %}
 
-{% note %}
-
-**Note:** {% data reusables.education.note-on-student-codespaces-usage %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.education.note-on-student-codespaces-usage %}
 
 ## About the {% data variables.product.prodname_codespaces %} Education benefit for verified teachers
 
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/about-assignments.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/about-assignments.md
index a7e67d4078..50f9914121 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/about-assignments.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/about-assignments.md
@@ -23,11 +23,8 @@ With {% data variables.product.prodname_classroom %}, you can create individual
 
 {% data reusables.classroom.reuse-assignment-link %}
 
-{% note %}
-
-**Note:** {% data reusables.classroom.assignments-classroom-prerequisite %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.classroom.assignments-classroom-prerequisite %}
 
 ## Types of assignments
 
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md
index 779f4b3445..98a655360e 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md
@@ -23,11 +23,8 @@ You can connect a learning management system (LMS) to {% data variables.product.
 
 Before you can connect your LMS to a classroom, an administrator for your LMS instance needs to register your LMS with GitHub Classroom to initiate the OAuth handshake. An admin only needs to do this registration process once, then any teacher who uses their LMS instance may sync their LMS courses to classrooms. For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom)."
 
-{% note %}
-
-**Note:** {% data reusables.classroom.google-classroom-note %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.classroom.google-classroom-note %}
 
 To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms#creating-a-classroom)."
 
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index a94ccb2a59..03722a6b51 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -61,15 +61,9 @@ Under "Individual or group assignment", select the drop-down menu, then click **
 
 If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
 
-{% note %}
-
-**Note**:
-
-* We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
-
-* If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
-
-{% endnote %}
+> [!NOTE]
+> * We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+> * If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
 
 ### Choosing a visibility for assignment repositories
 
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/editing-an-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/editing-an-assignment.md
index f23abb6ba3..8c7bd891b7 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/editing-an-assignment.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/editing-an-assignment.md
@@ -16,20 +16,14 @@ After creating an assignment, you can edit many aspects of the assignment to bet
 {% data reusables.classroom.click-classroom-in-list %}
 1. In the {% octicon "repo" aria-hidden="true" %} **Assignments** tab, next to the assignment you would like to edit, click {% octicon "pencil" aria-label="The pencil icon" %}.
 
-    {% note %}
-
-    **Note:** You can also edit an assignment from the assignment's page. To access the assignment's page, in the **Assignments** tab, click the assignment name.
-
-    {% endnote %}
+    > [!NOTE]
+    > You can also edit an assignment from the assignment's page. To access the assignment's page, in the **Assignments** tab, click the assignment name.
 
 1. Under "Assignment title," click in the text field, then delete the existing text and type the new assignment title.
 1. Optionally, to edit the default prefix for each student's assignment repository, next to the name of the prefix, click {% octicon "pencil" aria-label="The pencil icon" %}.
 
-    {% note %}
-
-    **Note:** Editing an assignment's title or default repository prefix will not change the name of existing assignment repositories.
-
-    {% endnote %}
+    > [!NOTE]
+    > Editing an assignment's title or default repository prefix will not change the name of existing assignment repositories.
 
     Then, type the new prefix under "Custom repository prefix."
 
@@ -39,27 +33,18 @@ After creating an assignment, you can edit many aspects of the assignment to bet
 
 1. To change the status of an assignment, select the **Assignment status** dropdown menu, then click **Active** or **Inactive**.
 
-    {% note %}
-
-    **Note:** Inactive assignments cannot be accepted by students. You should change an assignment status to inactive once no more students should accept an assignment or the assignment deadline has passed.
-
-    {% endnote %}
+    > [!NOTE]
+    > Inactive assignments cannot be accepted by students. You should change an assignment status to inactive once no more students should accept an assignment or the assignment deadline has passed.
 
 1. Under "Repository visibility," select a visibility. If you use private repositories, only the student or team can see the feedback you provide.
 
-    {% note %}
-
-    **Note:** Changing the visibility for assignment repositories will not retroactively change the visibility of existing assignment repositories.
-
-    {% endnote %}
+    > [!NOTE]
+    > Changing the visibility for assignment repositories will not retroactively change the visibility of existing assignment repositories.
 
 1. Optionally, select or deselect **Grant students admin access to their repository**. For more information on admin permissions for repositories, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" and "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)."
 
-    {% note %}
-
-    **Note:** Granting or revoking student admin access after an assignment has been created will not retroactively change the permissions for existing assignment repositories.
-
-    {% endnote %}
+    > [!NOTE]
+    > Granting or revoking student admin access after an assignment has been created will not retroactively change the permissions for existing assignment repositories.
 
 1. To set up or change the template repository for your assignment, in the "Add a template repository to give students starter code" section, select the **Select a repository** dropdown menu.
    * To choose a template repository, begin typing the repository name in the text field, then click the repository in the search results.
@@ -67,11 +52,8 @@ After creating an assignment, you can edit many aspects of the assignment to bet
 
   You cannot change the template repository after a student has accepted the assignment. If you wish to provide updates to the starter code after students have accepted the assignment, see "[Making changes to assignment starter code](#making-changes-to-assignment-starter-code)."
 
-   {% note %}
-
-   **Note:** By default, an assignment will create an empty repository for each student on the roster for the classroom.
-
-   {% endnote %}
+   > [!NOTE]
+   > By default, an assignment will create an empty repository for each student on the roster for the classroom.
 
 1. To add a new autograding test, in the "Add autograding tests" section, select the **Add test** dropdown menu, then click a grading method from the options that appear. For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding)."
 
@@ -81,19 +63,13 @@ After creating an assignment, you can edit many aspects of the assignment to bet
 
     Additionally, delete existing protected paths by clicking {% octicon "trash" aria-label="The trash icon" %}.
 
-    {% note %}
-
-    **Note:** If you remove a protected file path, the "Protected file(s) modified" label will be removed from any submissions that edited files in that path
-
-    {% endnote %}
+    > [!NOTE]
+    > If you remove a protected file path, the "Protected file(s) modified" label will be removed from any submissions that edited files in that path
 
 1. To turn feedback pull requests on or off, select or deselect **Enable feedback pull requests**.
 
-    {% note %}
-
-    **Note:** Enabling or disabling feedback pull requests for an assignment will not create or delete feedback pull requests for existing assignment repositories.
-
-    {% endnote %}
+    > [!NOTE]
+    > Enabling or disabling feedback pull requests for an assignment will not create or delete feedback pull requests for existing assignment repositories.
 
 {% data reusables.classroom.update-assignment %}
 
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/extending-an-assignments-deadline-for-an-individual-or-group.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/extending-an-assignments-deadline-for-an-individual-or-group.md
index d44f1d4acf..d7c0cbeebc 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/extending-an-assignments-deadline-for-an-individual-or-group.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/extending-an-assignments-deadline-for-an-individual-or-group.md
@@ -10,13 +10,9 @@ shortTitle: Extend deadline
 
 If you set a cutoff date for an assignment in {% data variables.product.prodname_classroom %}, individual students and groups will lose write access to their assignment repositories once that date has passed. To extend access to assignment repositories for specific students or groups, you can grant those students or groups an extension for that assignment. Extensions extend the cutoff date indefinitely, allowing students to submit an assignment at any time. For more information on setting a cutoff date, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment#assigning-a-deadline-for-an-assignment)" and "[AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment#assigning-a-deadline-for-an-assignment)."
 
-{% note %}
-
-**Notes:**
-* If your assignment has a deadline, but it does not have a cutoff date, you will not be able to grant students extensions. Instead, you can inform the student or group of their extension directly and ignore the "Late" label applied to the student or group's entry on the assignment overview.
-* If you grant a student or group an extension, and they submit their work after the initial cutoff date, the assignment will still be marked "Late". You can ignore the "Late" label, as it will not affect the student or group's grade, or write access to their assignment repository.
-
-{% endnote %}
+> [!NOTE]
+> * If your assignment has a deadline, but it does not have a cutoff date, you will not be able to grant students extensions. Instead, you can inform the student or group of their extension directly and ignore the "Late" label applied to the student or group's entry on the assignment overview.
+> * If you grant a student or group an extension, and they submit their work after the initial cutoff date, the assignment will still be marked "Late". You can ignore the "Late" label, as it will not affect the student or group's grade, or write access to their assignment repository.
 
 ## Extending an assignment's deadline
 
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
index 203d4caebf..c56e982f16 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
@@ -58,11 +58,8 @@ If your course already has a roster, you can update the students on the roster o
 {% data reusables.classroom.click-students %}
 1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, your LMS administrator will first need to register your LMS instance and then you will need to connect your LMS course to your classroom. Once connected, you can click the **Import from...** button to import a roster from your LMS course. For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)."
 
-   {% note %}
-
-   **Note:** {% data reusables.classroom.google-classroom-note %}
-
-   {% endnote %}
+   > [!NOTE]
+   > {% data reusables.classroom.google-classroom-note %}
 
 1. Provide the student identifiers for your roster.
 
@@ -81,11 +78,10 @@ Your classroom must have an existing roster to add students to the roster. For m
 1. To the right of "Classroom roster", click **Update students**. If you have already linked your classroom to an LMS course, then you will see a **Sync from...** button instead.
 1. Follow the instructions to add students to the roster.
    * To import students from an LMS, your LMS administrator will first need to register your LMS instance and then you will need to connect your LMS course to your classroom. Once connected, you can click the **Sync from...** button. For more information, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)."
-     {% note %}
 
-     **Note:** {% data reusables.classroom.google-classroom-note %}
+     > [!NOTE]
+     > {% data reusables.classroom.google-classroom-note %}
 
-     {% endnote %}
    * To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**.
 
 ## Renaming a classroom
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md
index 8cca103f86..636becc130 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md
@@ -10,11 +10,8 @@ shortTitle: Register an LMS
 
 Before you can connect your LMS to a classroom, an administrator for your LMS instance needs to configure your LMS to allow {% data variables.product.prodname_classroom %} and then register your LMS with {% data variables.product.prodname_classroom %} to initiate the OAuth handshake. An admin only needs to do this registration process once, then any teacher who uses their LMS instance may sync their LMS courses to classrooms. For more information on connecting an LMS course to a classroom, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)."
 
-{% note %}
-
-**Note:** {% data reusables.classroom.google-classroom-note %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.classroom.google-classroom-note %}
 
 ## Supported LMSes
 
@@ -35,7 +32,7 @@ You can register your Canvas installation with {% data variables.product.prodnam
     | Field in Canvas app configuration | Value or setting |
     | :- | :- |
     | **Method** | `Manual Entry` |
-    | **Title** | `GitHub Classroom` <br/><br/>**Note**: You can use any name, but if you set this to something else, be sure this is communicated to teachers.  |
+    | **Title** | `GitHub Classroom` <br/><br/>**Note:** You can use any name, but if you set this to something else, be sure this is communicated to teachers.  |
     | **Description** | `Sync Canvas course rosters to GitHub Classroom` (or something similar) |
     | **Target Link URI** | `https://classroom.github.com/context-link` |
     | **OpenID Connect Initiation URL** | `https://classroom.github.com/lti1p3/openid-connect/auth` |
@@ -44,7 +41,7 @@ You can register your Canvas installation with {% data variables.product.prodnam
     | **Redirect URIs** | `https://classroom.github.com/lti1p3/openid-connect/redirect` |
     | **LTI Advantage Services** dropdown | Select the "Can retrieve user data associated with the context the tool is installed in" checkbox. |
     | **Additional Settings** dropdown | Under "Privacy Level", select `Public` |
-    | **Placements** | Select `Course Settings Sub Navigation`. <br/><br/>**Note**: If you set the placement to something else, this must be communicated to teachers. Our documentation will expect that this is the placement of the button. |
+    | **Placements** | Select `Course Settings Sub Navigation`. <br/><br/>**Note:** If you set the placement to something else, this must be communicated to teachers. Our documentation will expect that this is the placement of the button. |
 1. Click **Save**.
 1. In the table on the "Developer Keys" page, in the row for the GitHub Classroom developer key, take note of the value of the client ID in the "Details" column -- this must be communicated to teachers for them to finish setup.
 1. In the table on the "Developer Keys" page, under the "State" column, toggle the state of the key to "On".
@@ -91,7 +88,7 @@ You must be using Moodle version 3.0 or greater.
 
     | Field in Moodle app configuration | Value or setting |
     | :- | :- |
-    | **Tool name** | `GitHub Classroom` <br/><br/>**Note**: You can use any name, but if you set this to something else, be sure this is communicated to teachers. |
+    | **Tool name** | `GitHub Classroom` <br/><br/>**Note:** You can use any name, but if you set this to something else, be sure this is communicated to teachers. |
     | **Tool URL** | `https://classroom.github.com` |
     | **LTI version** | `LTI 1.3` |
     | **Public Key type** | `Keyset URL` |
@@ -133,7 +130,7 @@ You must be using Moodle version 3.0 or greater.
 
     | Field in Sakai app configuration | Value or setting |
     | :- | :- |
-    | **Tool name** | GitHub Classroom - [Your Course Name] <br/><br/>**Note**: You can use any name, but if you set this to something else, be sure this is communicated to teachers. |
+    | **Tool name** | GitHub Classroom - [Your Course Name] <br/><br/>**Note:** You can use any name, but if you set this to something else, be sure this is communicated to teachers. |
     | **Button Text** (Text in tool menu) | What the teacher will see on the button to launch to {% data variables.product.prodname_classroom %}. For example, the value could be `sync`. |
     | **Launch URL** | `https://classroom.github.com/context-link` |
     | **Send User Names to External Tool** | Select this checkbox. |
diff --git a/content/education/quickstart.md b/content/education/quickstart.md
index 4c715c42b5..21118adbd7 100644
--- a/content/education/quickstart.md
+++ b/content/education/quickstart.md
@@ -13,11 +13,8 @@ Educators who teach a course on software development can use discounts, partners
 
 In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}.
 
-{% tip %}
-
-**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/apply-to-github-education-as-a-student)."
-
-{% endtip %}
+> [!TIP]
+> If you're a student and you'd like to take advantage of an academic discount, see "[AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/apply-to-github-education-as-a-student)."
 
 ## Creating accounts on {% data variables.product.product_name %}
 
@@ -39,11 +36,8 @@ For more information, see "[AUTOTITLE](/get-started/learning-about-github/types-
 
 Next, you'll sign up for teacher benefits and resources from {% data variables.product.company_short %} by applying to {% data variables.product.prodname_global_campus %}, a portal that allows you to access your education benefits all in one place.  {% data reusables.education.educator-requirements %}
 
-{% tip %}
-
-**Tip** In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website.
-
-{% endtip %}
+> [!TIP]
+> In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website.
 
 {% data reusables.education.benefits-page %}
 {% data reusables.education.click-get-teacher-benefits %}
@@ -63,11 +57,8 @@ With your personal account and organization account, you're ready to get started
 1. To authorize {% data variables.product.prodname_classroom %} to access your personal account on {% data variables.product.prodname_dotcom %}, review the information, then click **Authorize {% data variables.product.prodname_classroom %}**.
 1. Review the information. To authorize {% data variables.product.prodname_classroom %} to access your organization account on {% data variables.product.prodname_dotcom %}, click **Grant**.
 
-   {% tip %}
-
-   **Tip**: If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. For more information, see "[AUTOTITLE](/apps/oauth-apps/using-oauth-apps/authorizing-oauth-apps#oauth-apps-and-organizations)."
-
-   {% endtip %}
+   > [!TIP]
+   > If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. For more information, see "[AUTOTITLE](/apps/oauth-apps/using-oauth-apps/authorizing-oauth-apps#oauth-apps-and-organizations)."
 
 1. Click **Authorize github**.
 
diff --git a/content/get-started/accessibility/github-command-palette.md b/content/get-started/accessibility/github-command-palette.md
index be2c9ab3da..6682e40a54 100644
--- a/content/get-started/accessibility/github-command-palette.md
+++ b/content/get-started/accessibility/github-command-palette.md
@@ -40,13 +40,9 @@ When you open the command palette, it shows your location at the top left and us
 
 ![Screenshot of the command palette. "octo-org" is highlighted with an orange outline.](/assets/images/help/command-palette/command-palette-launch.png)
 
-{% note %}
-
-**Notes:**
-* If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).{% ifversion projects-v2 %}
-* If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view)."{% endif %}
-
-{% endnote %}
+> [!NOTE]
+> * If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).{% ifversion projects-v2 %}
+> * If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view)."{% endif %}
 
 ### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts
 
diff --git a/content/get-started/accessibility/managing-your-theme-settings.md b/content/get-started/accessibility/managing-your-theme-settings.md
index b9a0c85d1b..32a607a672 100644
--- a/content/get-started/accessibility/managing-your-theme-settings.md
+++ b/content/get-started/accessibility/managing-your-theme-settings.md
@@ -39,11 +39,8 @@ If you have low vision, you may benefit from a high contrast theme, with greater
 
 {% ifversion command-palette %}
 
-{% note %}
-
-**Note:** You can also change your theme settings with the command palette. For more information, see "[AUTOTITLE](/get-started/accessibility/github-command-palette)."
-
-{% endnote %}
+> [!NOTE]
+> You can also change your theme settings with the command palette. For more information, see "[AUTOTITLE](/get-started/accessibility/github-command-palette)."
 
 {% endif %}
 
diff --git a/content/get-started/exploring-integrations/featured-github-integrations.md b/content/get-started/exploring-integrations/featured-github-integrations.md
index 252e12bdb4..24ed639b4d 100644
--- a/content/get-started/exploring-integrations/featured-github-integrations.md
+++ b/content/get-started/exploring-integrations/featured-github-integrations.md
@@ -22,11 +22,10 @@ shortTitle: Featured integrations
 You can connect to {% data variables.product.product_name %} repositories within third-party editor tools such as {% data variables.product.prodname_vs %}.
 
 {% ifversion fpt %}
-{% note %}
 
-**Note:** To see an example of how third-party editor tools connect to repositories for {% data variables.product.prodname_classroom %}, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)."
+> [!NOTE]
+> To see an example of how third-party editor tools connect to repositories for {% data variables.product.prodname_classroom %}, see "[AUTOTITLE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)."
 
-{% endnote %}
 {% endif %}
 
 ### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %}
diff --git a/content/get-started/exploring-projects-on-github/contributing-to-a-project.md b/content/get-started/exploring-projects-on-github/contributing-to-a-project.md
index 89b48c9766..a56b9cb680 100644
--- a/content/get-started/exploring-projects-on-github/contributing-to-a-project.md
+++ b/content/get-started/exploring-projects-on-github/contributing-to-a-project.md
@@ -41,11 +41,8 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
     For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. If you do not select this option, all branches will be copied into the new fork.
 1. Click **Create fork**.
 
-{% note %}
-
-**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
-
-{% endnote %}
+> [!NOTE]
+> If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
 
 ## Cloning a fork
 
diff --git a/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
index cfbc8a753a..bed3ae1001 100644
--- a/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
+++ b/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
@@ -49,11 +49,8 @@ To view everyone who has starred a repository, add `/stargazers` to the end of t
 
 ## Organizing starred repositories with lists
 
-{% note %}
-
-**Note:** Lists are currently in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> Lists are currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 Curate repositories that you've starred with public lists. You can create public lists that appear on your stars page at `https://github.com/USERNAME?tab=stars`.
 
diff --git a/content/get-started/getting-started-with-git/about-remote-repositories.md b/content/get-started/getting-started-with-git/about-remote-repositories.md
index fd0d255c06..d02ba55d1e 100644
--- a/content/get-started/getting-started-with-git/about-remote-repositories.md
+++ b/content/get-started/getting-started-with-git/about-remote-repositories.md
@@ -56,13 +56,9 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit
 
 {% data reusables.command_line.provide-an-access-token %}
 
-{% tip %}
-
-**Tips**:
-* You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)."
-* To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop)."
-
-{% endtip %}
+> [!TIP]
+> * You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)."
+> * To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop)."
 
  {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[AUTOTITLE](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port)."{% endif %}
 
@@ -74,11 +70,8 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit
 
 {% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[AUTOTITLE](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
 
-{% tip %}
-
-**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[AUTOTITLE](/authentication/connecting-to-github-with-ssh/using-ssh-agent-forwarding)."
-
-{% endtip %}
+> [!TIP]
+> You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[AUTOTITLE](/authentication/connecting-to-github-with-ssh/using-ssh-agent-forwarding)."
 
 ## Cloning with {% data variables.product.prodname_cli %}
 
diff --git a/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
index 427928e2cf..f92a3ec252 100644
--- a/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
+++ b/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
@@ -15,11 +15,8 @@ versions:
 shortTitle: Caching credentials
 ---
 
-{% tip %}
-
-**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[AUTOTITLE](/authentication/connecting-to-github-with-ssh)."
-
-{% endtip %}
+> [!TIP]
+> If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[AUTOTITLE](/authentication/connecting-to-github-with-ssh)."
 
 ## {% data variables.product.prodname_cli %}
 
@@ -70,17 +67,11 @@ Once you've authenticated successfully, your credentials are stored in the Windo
 
 <br>
 
-{% warning %}
+> [!WARNING]
+> Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest).
 
-**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest).
-
-{% endwarning %}
-
-{% warning %}
-
-**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it.
-
-{% endwarning %}
+> [!WARNING]
+> If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it.
 
 {% endwindows %}
 
diff --git a/content/get-started/getting-started-with-git/managing-remote-repositories.md b/content/get-started/getting-started-with-git/managing-remote-repositories.md
index a5ab27ee76..48f378cb56 100644
--- a/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -70,11 +70,8 @@ To fix this, you can:
 
 The `git remote set-url` command changes an existing remote repository URL.
 
-{% tip %}
-
-**Tip:** For information on the difference between HTTPS and SSH URLs, see "[AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)."
-
-{% endtip %}
+> [!TIP]
+> For information on the difference between HTTPS and SSH URLs, see "[AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)."
 
 The `git remote set-url` command takes two arguments:
 
@@ -234,12 +231,8 @@ $ git remote -v
 > origin  https://{% data variables.product.product_url %}/OWNER/REPOSITORY.git (push)
 ```
 
-{% warning %}
-
-**Note**: `git remote rm` does not delete the remote repository from the server. It simply
-removes the remote and its references from your local repository.
-
-{% endwarning %}
+> [!NOTE]
+> `git remote rm` does not delete the remote repository from the server. It simply removes the remote and its references from your local repository.
 
 ### Troubleshooting: Could not remove config section 'remote.[name]'
 
diff --git a/content/get-started/getting-started-with-git/set-up-git.md b/content/get-started/getting-started-with-git/set-up-git.md
index f2008586e8..aaaf45db4c 100644
--- a/content/get-started/getting-started-with-git/set-up-git.md
+++ b/content/get-started/getting-started-with-git/set-up-git.md
@@ -40,16 +40,13 @@ If you do not need to work with files locally, {% data variables.product.product
 
 1. [Download and install the latest version of Git](https://git-scm.com/downloads).
 
-   {% note %}
-
-   **Note**: Most Chrome OS devices from 2020 onwards now have a built-in Linux environment, which includes Git. To enable it, go to the Launcher, search for Linux, and click **Turn on**.
-
-   If you are using an older Chrome OS device, another method is required:
-
-   1. Install a terminal emulator such as Termux from the Google Play Store on your Chrome OS device.
-   1. From the terminal emulator that you installed, install Git. For example, in Termux, enter `apt install git` and then type `y` when prompted.
-
-   {% endnote %}
+   > [!NOTE]
+   > Most Chrome OS devices from 2020 onwards now have a built-in Linux environment, which includes Git. To enable it, go to the Launcher, search for Linux, and click **Turn on**.
+   >
+   > If you are using an older Chrome OS device, another method is required:
+   >
+   > 1. Install a terminal emulator such as Termux from the Google Play Store on your Chrome OS device.
+   > 1. From the terminal emulator that you installed, install Git. For example, in Termux, enter `apt install git` and then type `y` when prompted.
 
 1. [Set your username in Git](/get-started/getting-started-with-git/setting-your-username-in-git).
 1. [Set your commit email address in Git](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address).
@@ -58,11 +55,8 @@ If you do not need to work with files locally, {% data variables.product.product
 
 When you connect to a {% data variables.product.prodname_dotcom %} repository from Git, you will need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH.
 
-{% note %}
-
-**Note:** You can authenticate to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %}, for either HTTP or SSH. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
-
-{% endnote %}
+> [!NOTE]
+> You can authenticate to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %}, for either HTTP or SSH. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
 
 ### Connecting over HTTPS (recommended)
 
diff --git a/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
index 7fd6685149..cd3f410656 100644
--- a/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
+++ b/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
@@ -13,19 +13,18 @@ versions:
   ghec: '*'
 shortTitle: macOS Keychain credentials
 ---
-{% note %}
 
-**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a {% data variables.product.pat_generic %} using the `osxkeychain` helper that is built-in to macOS.
-
-We recommend you either [configure SSH](/authentication/connecting-to-github-with-ssh) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth).
-
-{% endnote %}
+> [!NOTE]
+> Updating credentials from the macOS Keychain only applies to users who manually configured a {% data variables.product.pat_generic %} using the `osxkeychain` helper that is built-in to macOS.
+>
+> We recommend you either [configure SSH](/authentication/connecting-to-github-with-ssh) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth).
 
 {% data reusables.user-settings.password-authentication-deprecation %}
 
 {% ifversion ghec %}
 
-> [!NOTE] {% data reusables.enterprise-data-residency.access-domain %}
+> [!NOTE]
+> {% data reusables.enterprise-data-residency.access-domain %}
 
 {% endif %}
 
diff --git a/content/get-started/learning-about-github/about-github-advanced-security.md b/content/get-started/learning-about-github/about-github-advanced-security.md
index a4f5279c1c..965531427e 100644
--- a/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -22,11 +22,8 @@ shortTitle: GitHub Advanced Security
 
 {% ifversion ghes %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghec %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/signing-up-for-github-advanced-security)."{% elsif fpt %}To purchase a {% data variables.product.prodname_GH_advanced_security %} license, you must be using {% data variables.product.prodname_enterprise %}. For information about upgrading to {% data variables.product.prodname_enterprise %} with {% data variables.product.prodname_GH_advanced_security %}, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)" and "[AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
 
-{% note %}
-
-**Note:** If you want to use {% data variables.product.prodname_GH_advanced_security %} with Azure Repos, see [{% data variables.product.prodname_GH_advanced_security %} & Azure DevOps](https://resources.github.com/ghazdo/) in our resources site. For documentation, see [Configure {% data variables.product.prodname_ghas_azdo %}](https://learn.microsoft.com/en-us/azure/devops/repos/security/configure-github-advanced-security-features) in Microsoft Learn.
-
-{% endnote %}
+> [!NOTE]
+> If you want to use {% data variables.product.prodname_GH_advanced_security %} with Azure Repos, see [{% data variables.product.prodname_GH_advanced_security %} & Azure DevOps](https://resources.github.com/ghazdo/) in our resources site. For documentation, see [Configure {% data variables.product.prodname_ghas_azdo %}](https://learn.microsoft.com/en-us/azure/devops/repos/security/configure-github-advanced-security-features) in Microsoft Learn.
 
 ## About {% data variables.product.prodname_advanced_security %} features
 
diff --git a/content/get-started/learning-about-github/github-language-support.md b/content/get-started/learning-about-github/github-language-support.md
index 6e9c2ed3b1..d814c83fd8 100644
--- a/content/get-started/learning-about-github/github-language-support.md
+++ b/content/get-started/learning-about-github/github-language-support.md
@@ -41,12 +41,7 @@ Some features are supported for additional languages or package managers. If you
 {% data reusables.supported-languages.swift %}
 {% data reusables.supported-languages.typescript %}
 
-{% note %}
-
-**Notes:**
-
-{% ifversion fpt or ghec %}- The language support for {% data variables.product.prodname_copilot %} varies depending on the volume and diversity of training data for that language.{% endif %}
-* The support of Gradle for the dependency graph and {% data variables.product.prodname_dependabot_alerts %} is limited to the upload of data obtained using the {% data variables.dependency-submission-api.name %}.
-* PHP, Rust, and Scala are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
-
-{% endnote %}
+> [!NOTE]
+{% ifversion fpt or ghec %}> * The language support for {% data variables.product.prodname_copilot %} varies depending on the volume and diversity of training data for that language.{% endif %}
+> * The support of Gradle for the dependency graph and {% data variables.product.prodname_dependabot_alerts %} is limited to the upload of data obtained using the {% data variables.dependency-submission-api.name %}.
+> * PHP, Rust, and Scala are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
diff --git a/content/get-started/learning-about-github/githubs-plans.md b/content/get-started/learning-about-github/githubs-plans.md
index 140de53386..9b0988ced7 100644
--- a/content/get-started/learning-about-github/githubs-plans.md
+++ b/content/get-started/learning-about-github/githubs-plans.md
@@ -60,11 +60,8 @@ In addition to the features available with {% data variables.product.prodname_fr
   * Auto-linked references
   * {% data variables.product.prodname_pages %}
 
-    {% note %}
-
-    **Note:** To publish a {% data variables.product.prodname_pages %} site privately, you need to have an organization account. Additionally, your organization must use {% data variables.product.prodname_ghe_cloud %}.
-
-    {% endnote %}
+    > [!NOTE]
+    > To publish a {% data variables.product.prodname_pages %} site privately, you need to have an organization account. Additionally, your organization must use {% data variables.product.prodname_ghe_cloud %}.
 
   * Wikis
   * Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
@@ -97,11 +94,8 @@ In addition to the features available with {% data variables.product.prodname_fr
   * Scheduled reminders
   * {% data variables.product.prodname_pages %}
 
-    {% note %}
-
-    **Note:** To publish a {% data variables.product.prodname_pages %} site privately, you need to have an organization account. Additionally, your organization must use {% data variables.product.prodname_ghe_cloud %}.
-
-    {% endnote %}
+    > [!NOTE]
+    > To publish a {% data variables.product.prodname_pages %} site privately, you need to have an organization account. Additionally, your organization must use {% data variables.product.prodname_ghe_cloud %}.
 
   * Wikis
   * Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
diff --git a/content/get-started/showcase-your-expertise-with-github-certifications/about-github-certifications.md b/content/get-started/showcase-your-expertise-with-github-certifications/about-github-certifications.md
index e7bca0574b..09f047d434 100644
--- a/content/get-started/showcase-your-expertise-with-github-certifications/about-github-certifications.md
+++ b/content/get-started/showcase-your-expertise-with-github-certifications/about-github-certifications.md
@@ -8,11 +8,8 @@ versions:
 
 {% ifversion ghec %}
 
-{% note %}
-
-**Note:** {% data variables.enterprise.prodname_managed_users_caps %} do not have access to the {% data variables.product.prodname_certifications %} program.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.enterprise.prodname_managed_users_caps %} do not have access to the {% data variables.product.prodname_certifications %} program.
 
 {% endif %}
 
diff --git a/content/get-started/showcase-your-expertise-with-github-certifications/registering-for-a-github-certifications-exam.md b/content/get-started/showcase-your-expertise-with-github-certifications/registering-for-a-github-certifications-exam.md
index 79e8103e15..a60b3e2495 100644
--- a/content/get-started/showcase-your-expertise-with-github-certifications/registering-for-a-github-certifications-exam.md
+++ b/content/get-started/showcase-your-expertise-with-github-certifications/registering-for-a-github-certifications-exam.md
@@ -9,11 +9,8 @@ shortTitle: Registering for an exam
 
 {% ifversion ghec %}
 
-{% note %}
-
-**Note:** {% data variables.enterprise.prodname_managed_users_caps %} do not have access to the {% data variables.product.prodname_certifications %} program.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.enterprise.prodname_managed_users_caps %} do not have access to the {% data variables.product.prodname_certifications %} program.
 
 {% endif %}
 
diff --git a/content/get-started/start-your-journey/setting-up-your-profile.md b/content/get-started/start-your-journey/setting-up-your-profile.md
index bb783fac29..17459e170b 100644
--- a/content/get-started/start-your-journey/setting-up-your-profile.md
+++ b/content/get-started/start-your-journey/setting-up-your-profile.md
@@ -46,11 +46,9 @@ Next, we'll add some basic information about yourself to share with other {% dat
 1. On your profile page, under your profile picture, click **Edit profile**.
 1. Under "Bio", write one or two sentences about yourself, such as who you are and what you do.
 
-   {% note %}
+   > [!NOTE]
+   > Keep the bio short; we'll add a longer description of your interests in your profile README in the section below.
 
-   **Note:** Keep the bio short; we'll add a longer description of your interests in your profile README in the section below.
-
-   {% endnote %}
 1. To add an emoji to your bio, visit "[Emoji cheat sheet](https://www.webfx.com/tools/emoji-cheat-sheet/)" and copy and paste an emoji into the "Bio" dialog box.
 1. Optionally, add your {% ifversion profile-pronouns %}preferred pronouns,{% endif %} workplace, location and timezone{% ifversion profile-social-links %}, and any links to your personal website and social accounts{% endif %}. {% ifversion profile-pronouns %}{% data reusables.profile.pronouns-visibility %}{% endif %}
 1. Click **Save**.
diff --git a/content/get-started/start-your-journey/uploading-a-project-to-github.md b/content/get-started/start-your-journey/uploading-a-project-to-github.md
index e105f0c23a..42cc8dbe77 100644
--- a/content/get-started/start-your-journey/uploading-a-project-to-github.md
+++ b/content/get-started/start-your-journey/uploading-a-project-to-github.md
@@ -64,13 +64,12 @@ In this step, we'll edit your project's `README.md` using Markdown so that it in
 1. Delete the existing text apart from `#`, then type a proper title for your project.
    * Example: `# About my first project on GitHub`.
 1. Next, add some information about your project, such as a description of the project's purpose or its main features.
-   {% note %}
 
-   **Note:** If you're not sure what to write, take a look at other repositories on {% data variables.product.product_name %} to see how other people describe their projects.
+   > [!NOTE]
+   > If you're not sure what to write, take a look at other repositories on {% data variables.product.product_name %} to see how other people describe their projects.
+   >
+   > To apply more sophisticated formatting, such as adding images, links, and footnotes, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
 
-   To apply more sophisticated formatting, such as adding images, links, and footnotes, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
-
-   {% endnote %}
 {% data reusables.files.preview_change %}
 1. Take a look at how the file will render once we save our changes, then toggle back to "Edit".
 1. Continue to edit and preview the text until you're happy with the content of your README.
diff --git a/content/get-started/using-git/about-git-rebase.md b/content/get-started/using-git/about-git-rebase.md
index fd5f69289b..542b64935f 100644
--- a/content/get-started/using-git/about-git-rebase.md
+++ b/content/get-started/using-git/about-git-rebase.md
@@ -19,11 +19,8 @@ Typically, you would use `git rebase` to:
 * Combine multiple commits into one
 * Delete or revert commits that are no longer necessary
 
-{% warning %}
-
-**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
-
-{% endwarning %}
+> [!WARNING]
+> Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
 
 ## Rebasing commits against a branch
 
diff --git a/content/get-started/using-git/about-git-subtree-merges.md b/content/get-started/using-git/about-git-subtree-merges.md
index 4772c59d68..dc3a2bd65b 100644
--- a/content/get-started/using-git/about-git-subtree-merges.md
+++ b/content/get-started/using-git/about-git-subtree-merges.md
@@ -101,11 +101,8 @@ The best way to explain subtree merges is to show by example. We will:
 
 Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
 
-{% tip %}
-
-**Tip**: If you create a fresh clone of the repository in the future,  the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/get-started/getting-started-with-git/managing-remote-repositories).
-
-{% endtip %}
+> [!TIP]
+> If you create a fresh clone of the repository in the future,  the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/get-started/getting-started-with-git/managing-remote-repositories).
 
 ## Synchronizing with updates and changes
 
diff --git a/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
index 337d3a57f6..78089feda7 100644
--- a/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
+++ b/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
@@ -14,11 +14,8 @@ versions:
 shortTitle: Splitting a subfolder
 ---
 
-{% note %}
-
-**Note:** You need Git version 2.22.0 or later to follow these instructions, otherwise `git filter-repo` will not work.
-
-{% endnote %}
+> [!NOTE]
+> You need Git version 2.22.0 or later to follow these instructions, otherwise `git filter-repo` will not work.
 
 If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.  However, note that the new repository won't have the branches and tags of the original repository.
 
@@ -43,11 +40,8 @@ If you create a new clone of the repository, you won't lose any of your Git hist
 
    {% windows %}
 
-   {% tip %}
-
-   **Tip:** Windows users should use `/` to delimit folders.
-
-   {% endtip %}
+   > [!TIP]
+   > Windows users should use `/` to delimit folders.
 
    {% endwindows %}
 
@@ -71,11 +65,8 @@ If you create a new clone of the repository, you won't lose any of your Git hist
 
    ![Screenshot of the "Quick Setup" header in a repository. Next to the remote URL, an icon of two overlapping squares is highlighted with an orange outline.](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
 
-   {% tip %}
-
-   **Tip:** For information on the difference between HTTPS and SSH URLs, see "[AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)."
-
-   {% endtip %}
+   > [!TIP]
+   > For information on the difference between HTTPS and SSH URLs, see "[AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)."
 
 1. Add a new remote name with the URL you copied for your repository. For example, `origin` or `upstream` are two common choices.
 
diff --git a/content/get-started/using-github-docs/about-versions-of-github-docs.md b/content/get-started/using-github-docs/about-versions-of-github-docs.md
index a5b624acba..6ae994a37e 100644
--- a/content/get-started/using-github-docs/about-versions-of-github-docs.md
+++ b/content/get-started/using-github-docs/about-versions-of-github-docs.md
@@ -20,11 +20,8 @@ At the top of a page on {% data variables.product.prodname_docs %}, select the d
 
 ![Screenshot of the header of {% data variables.product.prodname_docs %}. The "Version" dropdown menu is expanded and highlighted with an orange outline.](/assets/images/help/docs/version-picker.png)
 
-{% note %}
-
-**Note**: You can try changing the version now. You're viewing {% ifversion ghes %}a{% else %}the{% endif %} **{% ifversion fpt %}Free, Pro, & Team{% else %}{% data variables.product.product_name %}{% endif %}** version of this article.
-
-{% endnote %}
+> [!NOTE]
+> You can try changing the version now. You're viewing {% ifversion ghes %}a{% else %}the{% endif %} **{% ifversion fpt %}Free, Pro, & Team{% else %}{% data variables.product.product_name %}{% endif %}** version of this article.
 
 ## Determining which {% data variables.product.company_short %} product you use
 
diff --git a/content/get-started/using-github/allowing-access-to-githubs-services-from-a-restricted-network.md b/content/get-started/using-github/allowing-access-to-githubs-services-from-a-restricted-network.md
index 3480678f31..8e26b190ae 100644
--- a/content/get-started/using-github/allowing-access-to-githubs-services-from-a-restricted-network.md
+++ b/content/get-started/using-github/allowing-access-to-githubs-services-from-a-restricted-network.md
@@ -15,10 +15,7 @@ In rare cases, an institution's network access policy may restrict access to spe
 
 You can use the REST API to retrieve a list of {% data variables.product.company_short %}'s domain names.
 
-{% warning %}
-
-**Warning**: The list of domains from the REST API is not intended to be comprehensive. If you block access to services using DNS, but selectively allow access to {% data variables.product.company_short %}'s domain names, any or all of {% data variables.product.prodname_dotcom %} and related services may not function properly or at all for your end users.
-
-{% endwarning %}
+> [!WARNING]
+> The list of domains from the REST API is not intended to be comprehensive. If you block access to services using DNS, but selectively allow access to {% data variables.product.company_short %}'s domain names, any or all of {% data variables.product.prodname_dotcom %} and related services may not function properly or at all for your end users.
 
 For more information, see "[AUTOTITLE](/rest/meta)."
diff --git a/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md b/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
index 50826bfe6f..31fe92e86d 100644
--- a/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
+++ b/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
@@ -18,7 +18,7 @@ shortTitle: Feature preview
 
 | Phase | Description |
 |-------|-------------|
-| {% data variables.release-phases.private_preview_caps %} | The product or feature is under heavy development and often has changing requirements and scope. The feature is available for demonstration and test purposes but may not be documented. {% data variables.release-phases.private_preview_caps %} releases are not necessarily feature complete, no service level agreements (SLAs) are provided, and there are no technical support obligations. <br><br> **Note**: A product or feature released as a "Technology Preview" is considered to be in the {% data variables.release-phases.private_preview %} release stage. Technology Preview releases share the same characteristics of {% data variables.release-phases.private_preview %} releases as described above.|
+| {% data variables.release-phases.private_preview_caps %} | The product or feature is under heavy development and often has changing requirements and scope. The feature is available for demonstration and test purposes but may not be documented. {% data variables.release-phases.private_preview_caps %} releases are not necessarily feature complete, no service level agreements (SLAs) are provided, and there are no technical support obligations. <br><br> **Note:** A product or feature released as a "Technology Preview" is considered to be in the {% data variables.release-phases.private_preview %} release stage. Technology Preview releases share the same characteristics of {% data variables.release-phases.private_preview %} releases as described above.|
 | {% data variables.release-phases.public_preview_caps %} | The product or feature is ready for broader distribution. {% data variables.release-phases.public_preview_caps %} releases can be public or private, are documented, but do not have any SLAs or technical support obligations. |
 | General availability (GA) | The product or feature is fully tested and open publicly to all users. GA releases are ready for production use, and associated SLA and technical support obligations apply. |
 
diff --git a/content/get-started/using-github/github-flow.md b/content/get-started/using-github/github-flow.md
index 900de92ef2..3b232f56ac 100644
--- a/content/get-started/using-github/github-flow.md
+++ b/content/get-started/using-github/github-flow.md
@@ -27,11 +27,8 @@ To follow {% data variables.product.prodname_dotcom %} flow, you will need a {%
 
 ## Following {% data variables.product.prodname_dotcom %} flow
 
-{% tip %}
-
-**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through the {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/free-pro-team@latest/desktop). For more information about the tools you can use to connect to {% data variables.product.prodname_dotcom %}, see "[AUTOTITLE](/get-started/using-github/connecting-to-github)."
-
-{% endtip %}
+> [!TIP]
+> You can complete all steps of {% data variables.product.prodname_dotcom %} flow through the {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/free-pro-team@latest/desktop). For more information about the tools you can use to connect to {% data variables.product.prodname_dotcom %}, see "[AUTOTITLE](/get-started/using-github/connecting-to-github)."
 
 ### Create a branch
 
@@ -53,11 +50,8 @@ By committing and pushing your changes, you back up your work to remote storage.
 
 Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
 
-{% tip %}
-
-**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
-
-{% endtip %}
+> [!TIP]
+> Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
 
 ### Create a pull request
 
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists.md b/content/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists.md
index 4f6abbcbc0..dfcd965113 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists.md
@@ -43,11 +43,8 @@ If you add a task list to the body of an issue, the list has added functionality
 
 {% data reusables.repositories.task-list-markdown %}
 
-{% tip %}
-
-**Tip:** You cannot create task list items within closed issues or issues with linked pull requests.
-
-{% endtip %}
+> [!TIP]
+> You cannot create task list items within closed issues or issues with linked pull requests.
 
 ## Reordering tasks
 
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md b/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
index ffd94df152..4ca98307f8 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -16,21 +16,16 @@ topics:
 ---
 
 {% ifversion ghes %}
-{% warning %}
 
-**Warning:** When you upload an image or video to a pull request or issue comment, or upload a file to a ticket in the {% data variables.contact.landing_page_portal %}, anyone can view the anonymized URL without authentication, even if the pull request or issue is in a private repository, or if private mode is enabled. To keep sensitive media files private, serve them from a private network or server that requires authentication.
+> [!WARNING]
+> When you upload an image or video to a pull request or issue comment, or upload a file to a ticket in the {% data variables.contact.landing_page_portal %}, anyone can view the anonymized URL without authentication, even if the pull request or issue is in a private repository, or if private mode is enabled. To keep sensitive media files private, serve them from a private network or server that requires authentication.
 
-{% endwarning %}
 {% endif %}
 
 {% ifversion fpt or ghec %}
 
-{% note %}
-
-**Note:** For public repositories, uploaded files can be accessed without authentication.
-In the case of private and internal repositories, only people with access to the repository can view the uploaded files.
-
-{% endnote %}
+> [!NOTE]
+> For public repositories, uploaded files can be accessed without authentication. In the case of private and internal repositories, only people with access to the repository can view the uploaded files.
 
 {% endif %}
 
@@ -48,11 +43,8 @@ To attach a file to an issue or pull request conversation, drag and drop it into
 
 When you attach a file, it is uploaded immediately to {% data variables.product.product_name %} and the text field is updated to show the anonymized URL for the file. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/about-anonymized-urls)."{% endif %}
 
-{% note %}
-
-**Note:** In many browsers, you can copy-and-paste images directly into the box.
-
-{% endnote %}
+> [!NOTE]
+> In many browsers, you can copy-and-paste images directly into the box.
 
 The maximum file size is:
 
@@ -62,11 +54,8 @@ The maximum file size is:
 * 100MB for videos{% endif %}
 * 25MB for all other files
 
-{% note %}
-
-**Note:** To upload videos greater than 10MB to a repository owned by a user or organization on a paid {% data variables.product.prodname_dotcom %} plan, you must either be an organization member or outside collaborator, or be on a paid plan.
-
-{% endnote %}
+> [!NOTE]
+> To upload videos greater than 10MB to a repository owned by a user or organization on a paid {% data variables.product.prodname_dotcom %} plan, you must either be an organization member or outside collaborator, or be on a paid plan.
 
 We support these files:
 
@@ -82,18 +71,12 @@ We support these files:
 * Text files (`.txt`)
 * Patch files (`.patch`)
 
-  {% note %}
-
-  **Note:** If you use Linux and try to upload a `.patch` file, you will receive an error message. This is a known issue.
-
-  {% endnote %}
+  > [!NOTE]
+  > If you use Linux and try to upload a `.patch` file, you will receive an error message. This is a known issue.
 
 * PDFs (`.pdf`)
 * ZIP (`.zip`, `.gz`, `.tgz`)
 * Video (`.mp4`, `.mov`, `.webm`)
 
-  {% note %}
-
-  **Note:** Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using H.264 for greatest compatibility.
-
-  {% endnote %}
+  > [!NOTE]
+  > Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using H.264 for greatest compatibility.
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md b/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
index 7bba20ce96..e45a367d9f 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
@@ -25,11 +25,8 @@ For more information on creating links, see "[AUTOTITLE](/get-started/writing-on
 
 Within conversations on {% data variables.product.product_name %}, references to issues and pull requests are automatically converted to shortened links.
 
-{% note %}
-
-**Note:** Autolinked references are not created in wikis or files in a repository.
-
-{% endnote %}
+> [!NOTE]
+> Autolinked references are not created in wikis or files in a repository.
 
 | Reference type | Raw reference | Short link |
 | --- | --- | --- |
@@ -53,11 +50,8 @@ The URL of a label can be found by navigating to the labels page and clicking on
 https://github.com/github/docs/labels/enhancement
 ```
 
-{% note %}
-
-**Note:** If the label name contains a period (`.`), the label will not automatically render from the label URL.
-
-{% endnote %}
+> [!NOTE]
+> If the label name contains a period (`.`), the label will not automatically render from the label URL.
 
 ## Commit SHAs
 
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md
index 3cea2901e4..a5ed14520d 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md
@@ -21,11 +21,8 @@ This type of permanent link will render as a code snippet only in the repository
 
 ![Screenshot of an issue comment. A code snippet has a header that lists the file name and line numbers, and a body that lists the code on those lines.](/assets/images/help/repository/rendered-code-snippet.png)
 
-{% tip %}
-
-**Tip:** To create a permalink for an entire file, see "[AUTOTITLE](/repositories/working-with-files/using-files/getting-permanent-links-to-files)."
-
-{% endtip %}
+> [!TIP]
+> To create a permalink for an entire file, see "[AUTOTITLE](/repositories/working-with-files/using-files/getting-permanent-links-to-files)."
 
 {% data reusables.repositories.navigate-to-repo %}
 1. Locate the code you'd like to link to:
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index c2748493e1..b2744b949f 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -26,11 +26,8 @@ function test() {
 
 ![Screenshot of rendered {% data variables.product.prodname_dotcom %} Markdown showing how triple backticks render code blocks in raw formatting. The block begins with "function test() {."](/assets/images/help/writing/fenced-code-block-rendered.png)
 
-{% tip %}
-
-**Tip:** To preserve your formatting within a list, make sure to indent non-fenced code blocks by eight spaces.
-
-{% endtip %}
+> [!TIP]
+> To preserve your formatting within a list, make sure to indent non-fenced code blocks by eight spaces.
 
 To display triple backticks in a fenced code block, wrap them inside quadruple backticks.
 
diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
index c558578f90..f622325403 100644
--- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
+++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
@@ -32,11 +32,8 @@ graph TD;
 
 ![Screenshot of a rendered Mermaid flow chart with four lavender boxes labeled A, B, C, and D. Arrows extend from A to B, B to D, A to C, and C to D.](/assets/images/help/writing/mermaid-flow-chart.png)
 
-{% note %}
-
-**Note:** You may observe errors if you run a third-party Mermaid plugin when using Mermaid syntax on {% data variables.product.company_short %}.
-
-{% endnote %}
+> [!NOTE]
+> You may observe errors if you run a third-party Mermaid plugin when using Mermaid syntax on {% data variables.product.company_short %}.
 
 ### Checking your version of Mermaid
 
diff --git a/content/get-started/writing-on-github/working-with-saved-replies/using-saved-replies.md b/content/get-started/writing-on-github/working-with-saved-replies/using-saved-replies.md
index 7bb933dc86..ed481a5e53 100644
--- a/content/get-started/writing-on-github/working-with-saved-replies/using-saved-replies.md
+++ b/content/get-started/writing-on-github/working-with-saved-replies/using-saved-replies.md
@@ -18,13 +18,9 @@ versions:
 1. From the list, select the saved reply you'd like to add to your comment. Optionally, edit the content of the saved reply.  
 1. Select **Comment** to add your comment.
 
-{% tip %}
-
-**Tips:**
-* You can use a keyboard shortcut to autofill the comment with a saved reply. For more information, see "[AUTOTITLE](/get-started/accessibility/keyboard-shortcuts#comments)."
-* You can filter the list by typing the title of the saved reply.
-
-{% endtip %}
+> [!TIP]
+> * You can use a keyboard shortcut to autofill the comment with a saved reply. For more information, see "[AUTOTITLE](/get-started/accessibility/keyboard-shortcuts#comments)."
+> * You can filter the list by typing the title of the saved reply.
 
 ## Further reading
 
diff --git a/content/github-cli/github-cli/creating-github-cli-extensions.md b/content/github-cli/github-cli/creating-github-cli-extensions.md
index 5c998b437f..34ee5c5975 100644
--- a/content/github-cli/github-cli/creating-github-cli-extensions.md
+++ b/content/github-cli/github-cli/creating-github-cli-extensions.md
@@ -15,19 +15,13 @@ topics:
 
 You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. The repository must have an executable file at its root with the same name as the repository or a set of precompiled binary executables attached to a release.
 
-{% note %}
-
-**Note**: When relying on an executable script, we recommend using a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. If you would prefer to not rely on users having interpreters installed, consider a precompiled extension.
-
-{% endnote %}
+> [!NOTE]
+> When relying on an executable script, we recommend using a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. If you would prefer to not rely on users having interpreters installed, consider a precompiled extension.
 
 ## Creating an interpreted extension with `gh extension create`
 
-{% note %}
-
-**Note**: Running `gh extension create` with no arguments will start an interactive wizard.
-
-{% endnote %}
+> [!NOTE]
+> Running `gh extension create` with no arguments will start an interactive wizard.
 
 You can use the `gh extension create` command to create a project for your extension, including a bash script that contains some starter code.
 
@@ -73,11 +67,8 @@ You can use the `--precompiled=other` argument to create a project for your non-
 
 1. In the directory that you created, add an executable file with the same name as the directory.
 
-   {% note %}
-
-   **Note:** Make sure that your file is executable. On Unix, you can execute `chmod +x file_name` in the command line to make `file_name` executable. On Windows, you can run `git init -b main`, `git add file_name`, then `git update-index --chmod=+x file_name`.
-
-   {% endnote %}
+   > [!NOTE]
+   > Make sure that your file is executable. On Unix, you can execute `chmod +x file_name` in the command line to make `file_name` executable. On Windows, you can run `git init -b main`, `git add file_name`, then `git update-index --chmod=+x file_name`.
 
 1. Write your script in the executable file. For example:
 
@@ -229,11 +220,8 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
 
 1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
 
-   {% note %}
-
-   **Note:** Be careful not to commit the binary produced by your compilation step to version control.
-
-   {% endnote %}
+   > [!NOTE]
+   > Be careful not to commit the binary produced by your compilation step to version control.
 
    ```shell
     git init -b main
@@ -246,11 +234,8 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
 
    For example, an extension named `whoami` compiled for Windows 64bit would have the name `gh-whoami-windows-amd64.exe` while the same extension compiled for Linux 32bit would have the name `gh-whoami-linux-386`. To see an exhaustive list of OS and architecture combinations recognized by `gh`, see [this source code](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
 
-   {% note %}
-
-   **Note:** For your extension to run properly on Windows, its asset file must have a `.exe` extension. No extension is needed for other operating systems.
-
-   {% endnote %}
+   > [!NOTE]
+   > For your extension to run properly on Windows, its asset file must have a `.exe` extension. No extension is needed for other operating systems.
 
    Releases can be created from the command line. For example:
 
diff --git a/content/github-cli/github-cli/quickstart.md b/content/github-cli/github-cli/quickstart.md
index aeba5b1882..67f728c3ef 100644
--- a/content/github-cli/github-cli/quickstart.md
+++ b/content/github-cli/github-cli/quickstart.md
@@ -22,11 +22,8 @@ shortTitle: Quickstart
 
 ## Some useful commands
 
-{% note %}
-
-**Note**: When you use some commands for the first time - for example, `gh codespace SUBCOMMAND` - you'll be prompted to add extra scopes to your authentication token. Follow the onscreen instructions.
-
-{% endnote %}
+> [!NOTE]
+> When you use some commands for the first time - for example, `gh codespace SUBCOMMAND` - you'll be prompted to add extra scopes to your authentication token. Follow the onscreen instructions.
 
 ### Viewing your status
 
diff --git a/content/github-cli/github-cli/using-github-cli-extensions.md b/content/github-cli/github-cli/using-github-cli-extensions.md
index b32bc83ab4..8b51212570 100644
--- a/content/github-cli/github-cli/using-github-cli-extensions.md
+++ b/content/github-cli/github-cli/using-github-cli-extensions.md
@@ -11,11 +11,8 @@ topics:
 
 ## About {% data variables.product.prodname_cli %} extensions
 
-{% note %}
-
-**Note:** Extensions outside of {% data variables.product.product_name %} and {% data variables.product.prodname_cli %} are not certified by {% data variables.product.product_name %} and are governed by separate terms of service, privacy policy, and support documentation. To mitigate risk when using third-party extensions, audit the source code of the extension before installing or updating the extension.
-
-{% endnote %}
+> [!NOTE]
+> Extensions outside of {% data variables.product.product_name %} and {% data variables.product.prodname_cli %} are not certified by {% data variables.product.product_name %} and are governed by separate terms of service, privacy policy, and support documentation. To mitigate risk when using third-party extensions, audit the source code of the extension before installing or updating the extension.
 
 {% data reusables.cli.cli-extensions %} For more information about how to create {% data variables.product.prodname_cli %} extensions, see "[AUTOTITLE](/github-cli/github-cli/creating-github-cli-extensions)."
 
diff --git a/content/graphql/guides/forming-calls-with-graphql.md b/content/graphql/guides/forming-calls-with-graphql.md
index f131daffae..cfc9778c39 100644
--- a/content/graphql/guides/forming-calls-with-graphql.md
+++ b/content/graphql/guides/forming-calls-with-graphql.md
@@ -63,11 +63,8 @@ curl -H "Authorization: bearer TOKEN" -X POST -d " \
 " {% data variables.product.graphql_url %}
 ```
 
-{% tip %}
-
-**Note**: The string value of `"query"` must escape newline characters or the schema will not parse it correctly. For the `POST` body, use outer double quotes and escaped inner double quotes.
-
-{% endtip %}
+> [!NOTE]
+> The string value of `"query"` must escape newline characters or the schema will not parse it correctly. For the `POST` body, use outer double quotes and escaped inner double quotes.
 
 ### About query and mutation operations
 
@@ -115,11 +112,8 @@ For a real-world example, see "[Example mutation](#example-mutation)."
 
 [Variables](https://graphql.org/learn/queries/#variables) can make queries more dynamic and powerful, and they can reduce complexity when passing mutation input objects.
 
-{% note %}
-
-**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/graphql/guides/using-the-explorer#using-the-variable-pane), and do not include the word `variables` before the JSON object.
-
-{% endnote %}
+> [!NOTE]
+> If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/graphql/guides/using-the-explorer#using-the-variable-pane), and do not include the word `variables` before the JSON object.
 
 Here's an example query with a single variable:
 
@@ -319,11 +313,8 @@ Let's examine the query line by line:
 
 When we run the query, we get the `id`: `MDU6SXNzdWUyMzEzOTE1NTE=`
 
-{% tip %}
-
-**Note**: The `id` returned in the query is the value we'll pass as the `subjectID` in the mutation. Neither the docs nor schema introspection will indicate this relationship; you'll need to understand the concepts behind the names to figure this out.
-
-{% endtip %}
+> [!NOTE]
+> The `id` returned in the query is the value we'll pass as the `subjectID` in the mutation. Neither the docs nor schema introspection will indicate this relationship; you'll need to understand the concepts behind the names to figure this out.
 
 With the ID known, we can proceed with the mutation:
 
diff --git a/content/graphql/guides/introduction-to-graphql.md b/content/graphql/guides/introduction-to-graphql.md
index 6ceae788fe..349ba9ea73 100644
--- a/content/graphql/guides/introduction-to-graphql.md
+++ b/content/graphql/guides/introduction-to-graphql.md
@@ -118,11 +118,9 @@ GraphQL is [introspective](https://graphql.org/learn/introspection/). This means
   curl -H "Authorization: bearer TOKEN" {% data variables.product.graphql_url %}
   ```
 
-  {% note %}
-
-  **Note**: If you get the response `"message": "Bad credentials"` or `401 Unauthorized`, check that you are using a valid token. If you receive a `403` error with `Resource not accessible by {% data variables.product.pat_generic %}`, ensure that your {% data variables.product.pat_v2 %} is targeted to the correct resource owner. For example, it must target the organization that owns the repository you are trying to access.
-  {% endnote %}
-
+  > [!NOTE]
+  > If you get the response `"message": "Bad credentials"` or `401 Unauthorized`, check that you are using a valid token. If you receive a `403` error with `Resource not accessible by {% data variables.product.pat_generic %}`, ensure that your {% data variables.product.pat_v2 %} is targeted to the correct resource owner. For example, it must target the organization that owns the repository you are trying to access.
+  
   The results are in JSON, so we recommend pretty-printing them for easier reading and searching. You can use a command-line tool like [jq](https://stedolan.github.io/jq/) or pipe the results into `python -m json.tool` for this purpose.
 
   Alternatively, you can pass the `idl` media type to return the results in IDL format, which is a condensed version of the schema:
@@ -132,10 +130,7 @@ GraphQL is [introspective](https://graphql.org/learn/introspection/). This means
   {% data variables.product.graphql_url %}
   ```
 
-  {% note %}
-
-  **Note**: The introspection query is probably the only `GET` request you'll run in GraphQL. If you're passing a body, the GraphQL request method is `POST`, whether it's a query or a mutation.
-
-  {% endnote %}
+  > [!NOTE]
+  > The introspection query is probably the only `GET` request you'll run in GraphQL. If you're passing a body, the GraphQL request method is `POST`, whether it's a query or a mutation.
 
   For more information about performing queries, see "[AUTOTITLE](/graphql/guides/forming-calls-with-graphql)."
diff --git a/content/graphql/guides/using-global-node-ids.md b/content/graphql/guides/using-global-node-ids.md
index e4f96ff46d..26c4fb3554 100644
--- a/content/graphql/guides/using-global-node-ids.md
+++ b/content/graphql/guides/using-global-node-ids.md
@@ -13,11 +13,8 @@ topics:
 
 You can access most objects in GitHub (users, issues, pull requests, etc.) using either the REST API or the GraphQL API. You can find the **global node ID** of many objects from within the REST API and use these IDs in your GraphQL operations. For more information, see "[Preview GraphQL API Node IDs in REST API resources](https://developer.github.com/changes/2017-12-19-graphql-node-id/)."
 
-{% note %}
-
-**Note:** In REST, the global node ID field is named `node_id`. In GraphQL, it's an `id` field on the `node` interface. For a refresher on what "node" means in GraphQL, see "[AUTOTITLE](/graphql/guides/introduction-to-graphql#node)."
-
-{% endnote %}
+> [!NOTE]
+> In REST, the global node ID field is named `node_id`. In GraphQL, it's an `id` field on the `node` interface. For a refresher on what "node" means in GraphQL, see "[AUTOTITLE](/graphql/guides/introduction-to-graphql#node)."
 
 ## Putting global node IDs to use
 
diff --git a/content/graphql/guides/using-the-explorer.md b/content/graphql/guides/using-the-explorer.md
index df5ff864d4..fd7d137b03 100644
--- a/content/graphql/guides/using-the-explorer.md
+++ b/content/graphql/guides/using-the-explorer.md
@@ -14,11 +14,10 @@ topics:
 ## About the GraphQL Explorer
 
 {% ifversion ghec %}
-{% note %}
 
-**Note**: If your {% data variables.product.prodname_ghe_cloud %} organization uses {% data variables.product.prodname_dotcom %}'s IP allow list, you won't be able to use the GraphQL Explorer. Instead, we recommend using an alternative GraphQL client IDE.
+> [!NOTE]
+> If your {% data variables.product.prodname_ghe_cloud %} organization uses {% data variables.product.prodname_dotcom %}'s IP allow list, you won't be able to use the GraphQL Explorer. Instead, we recommend using an alternative GraphQL client IDE.
 
-{% endnote %}
 {% endif %}
 
 {% ifversion fpt or ghec %}
@@ -92,11 +91,8 @@ There are many open source GraphQL client IDEs. For example, you can use Altair
 1. In Altair, click on **Docs** on the top right, then the three dots and **Load Schema...**
 1. Select the file public schema that you downloaded in an earlier step.
 
-{% note %}
-
-**Note**: For more information about why `POST` is the method, see "[AUTOTITLE](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)."
-
-{% endnote %}
+> [!NOTE]
+> For more information about why `POST` is the method, see "[AUTOTITLE](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)."
 
 You can test your access by querying yourself:
 
@@ -155,8 +151,5 @@ It's possible you might run into an unexpected error that is not related to the
 }
 ```
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_dotcom %} recommends checking for errors before using data in a production environment. In GraphQL, failure is not total: portions of GraphQL queries may succeed while others fail.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.product.prodname_dotcom %} recommends checking for errors before using data in a production environment. In GraphQL, failure is not total: portions of GraphQL queries may succeed while others fail.
diff --git a/content/graphql/overview/explorer.md b/content/graphql/overview/explorer.md
index d46b0399ad..9879809723 100644
--- a/content/graphql/overview/explorer.md
+++ b/content/graphql/overview/explorer.md
@@ -16,11 +16,10 @@ autogenerated: graphql
 For more information about how to use the explorer, see "[AUTOTITLE](/graphql/guides/using-the-explorer)."
 
 {% ifversion ghec %}
-{% note %}
 
-**Note**: If your {% data variables.product.prodname_ghe_cloud %} organization uses {% data variables.product.prodname_dotcom %}'s IP allow list, you won't be able to use the GraphQL Explorer. Instead, we recommend using an alternative GraphQL client IDE.
+> [!NOTE]
+> If your {% data variables.product.prodname_ghe_cloud %} organization uses {% data variables.product.prodname_dotcom %}'s IP allow list, you won't be able to use the GraphQL Explorer. Instead, we recommend using an alternative GraphQL client IDE.
 
-{% endnote %}
 {% endif %}
 
 <!-- Content after this section is automatically generated -->
diff --git a/content/graphql/overview/rate-limits-and-node-limits-for-the-graphql-api.md b/content/graphql/overview/rate-limits-and-node-limits-for-the-graphql-api.md
index 7877ef9e56..38824ab950 100644
--- a/content/graphql/overview/rate-limits-and-node-limits-for-the-graphql-api.md
+++ b/content/graphql/overview/rate-limits-and-node-limits-for-the-graphql-api.md
@@ -212,11 +212,8 @@ You can also roughly calculate the point value of a query before you make the qu
 1. Add up the number of requests needed to fulfill each unique connection in the call. Assume every request will reach the `first` or `last` argument limits.
 1. Divide the number by **100** and round the result to the nearest whole number to get the final aggregate point value. This step normalizes large numbers.
 
-{% note %}
-
-**Note**: The minimum point value of a call to the GraphQL API is **1**.
-
-{% endnote %}
+> [!NOTE]
+> The minimum point value of a call to the GraphQL API is **1**.
 
 Here's an example query and score calculation:
 
diff --git a/content/graphql/overview/schema-previews.md b/content/graphql/overview/schema-previews.md
index 22b86552f4..5e66caac15 100644
--- a/content/graphql/overview/schema-previews.md
+++ b/content/graphql/overview/schema-previews.md
@@ -16,10 +16,7 @@ During the preview period, we may change some features based on developer feedba
 
 To access a schema preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide.
 
-{% note %}
+> [!NOTE]
+> The GraphQL schema members under preview cannot be accessed via the Explorer at this time.
 
-**Note:** The GraphQL schema members under preview cannot be accessed via the Explorer at this time.
-
-{% endnote %}
-
-<!-- Content after this section is automatically generated -->
\ No newline at end of file
+<!-- Content after this section is automatically generated -->
diff --git a/content/graphql/reference/queries.md b/content/graphql/reference/queries.md
index 21ed51e8e2..69985f7c2b 100644
--- a/content/graphql/reference/queries.md
+++ b/content/graphql/reference/queries.md
@@ -19,10 +19,7 @@ Every GraphQL schema has a root type for both queries and mutations. The [query
 
 For more information, see "[AUTOTITLE](/graphql/guides/forming-calls-with-graphql#about-queries)."
 
-{% note %}
-
-**Note:** For {% data variables.product.prodname_github_app %} requests made with user access tokens, you should use separate queries for issues and pull requests. For example, use the `is:issue` or `is:pull-request` filters and their equivalents. Using the `search` connection to return a combination of issues and pull requests in a single query will result in an empty set of nodes.
-
-{% endnote %}
+> [!NOTE]
+> For {% data variables.product.prodname_github_app %} requests made with user access tokens, you should use separate queries for issues and pull requests. For example, use the `is:issue` or `is:pull-request` filters and their equivalents. Using the `search` connection to return a combination of issues and pull requests in a single query will result in an empty set of nodes.
 
 <!-- Content after this section is automatically generated -->
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
index 0cfb7d0eee..34ad7ef922 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
@@ -24,11 +24,8 @@ allowTitleToDifferFromFilename: true
 
 {% data reusables.project-management.resync-automation %}
 
-{% tip %}
-
-**Tip**: To edit columns that already have configured automation, click **Manage** at the bottom of the column.
-
-{% endtip %}
+> [!TIP]
+> To edit columns that already have configured automation, click **Manage** at the bottom of the column.
 
 1. Navigate to the {% data variables.projects.projects_v1_board %} you want to automate.
 1. In the column you want to automate, click {% octicon "kebab-horizontal" aria-label="Column menu" %}.
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index a4f089084b..735ba93ea3 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -60,11 +60,10 @@ You can also configure workflow automations to keep your {% data variables.proje
 {% data reusables.projects.classic-project-creation %}
 
 {% ifversion classic-project-visibility-permissions %}
-{% note %}
 
-**Note:** {% data reusables.projects.owners-can-limit-visibility-permissions %}
+> [!NOTE]
+> {% data reusables.projects.owners-can-limit-visibility-permissions %}
 
-{% endnote %}
 {% endif %}
 
 {% data reusables.profile.access_org %}
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index b00530b431..ab01f9219d 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -14,11 +14,8 @@ allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-{% tip %}
-
-**Tip**: If you'd like to retain access to a completed or unneeded {% data variables.projects.projects_v1_board %} without losing access to its contents, you can [close the {% data variables.projects.projects_v1_board %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board) instead of deleting it.
-
-{% endtip %}
+> [!TIP]
+> If you'd like to retain access to a completed or unneeded {% data variables.projects.projects_v1_board %} without losing access to its contents, you can [close the {% data variables.projects.projects_v1_board %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board) instead of deleting it.
 
 1. Navigate to the {% data variables.projects.projects_v1_board %} you want to delete.
 {% data reusables.project-management.click-menu %}
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index a03a688c7b..917ca25bb0 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -17,11 +17,8 @@ allowTitleToDifferFromFilename: true
 
 {% ifversion projects-v1-can-create %}
 
-{% tip %}
-
-**Tip:** For details on adding, removing, or editing columns in your {% data variables.projects.projects_v1_board %}, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)."
-
-{% endtip %}
+> [!TIP]
+> For details on adding, removing, or editing columns in your {% data variables.projects.projects_v1_board %}, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)."
 
 {% endif %}
 
diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
index 7f4b73cb1c..ef5749ad69 100644
--- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
@@ -26,11 +26,8 @@ Anyone with write permissions to a {% data variables.projects.projects_v1_board
 1. Search for the repository you'd like to link.
 1. Click **Link**. To unlink, click **Unlink**.
 
-{% note %}
-
-**Note:** In order to link a repository to your organization or user owned {% data variables.projects.projects_v1_board %} the repository needs to have issues enabled. That is, the repository has an "Issues" tab (in forked repositories issues are disabled by default).  For information on how to enable or disable issues for a repository, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues)."
-
-{% endnote %}
+> [!NOTE]
+> In order to link a repository to your organization or user owned {% data variables.projects.projects_v1_board %} the repository needs to have issues enabled. That is, the repository has an "Issues" tab (in forked repositories issues are disabled by default).  For information on how to enable or disable issues for a repository, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues)."
 
 ## Further reading
 
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index 364bca00c1..8849d3fefc 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -22,11 +22,8 @@ You can add issue or pull request cards to your {% data variables.projects.proje
 
 You can put a maximum of 2,500 cards into each project column. If a column has reached the maximum number of cards, no cards can be moved into that column.
 
-{% note %}
-
-**Note:** You can also add notes to your {% data variables.projects.projects_v1_board %} to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your {% data variables.projects.projects_v1_board %}. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board)."
-
-{% endnote %}
+> [!NOTE]
+> You can also add notes to your {% data variables.projects.projects_v1_board %} to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your {% data variables.projects.projects_v1_board %}. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board)."
 
 {% data reusables.project-management.edit-in-project %}
 
@@ -39,20 +36,14 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
 ![Screenshot showing the header of a project. The "Add cards" button is highlighted with an orange outline.](/assets/images/help/projects/add-cards-button.png)
 1. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers such as `is:issue is:open`. For more information on search qualifiers you can use, see "[AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests)."
 
-   {% tip %}
+   > [!TIP]
+   > * You can also add an issue or pull request by typing the URL in a card.
+   > * If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your {% data variables.projects.projects_v1_board %} by searching for the label name. For more information, see "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels)."
 
-   **Tips:**
-   * You can also add an issue or pull request by typing the URL in a card.
-   * If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your {% data variables.projects.projects_v1_board %} by searching for the label name. For more information, see "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels)."
-
-   {% endtip %}
 1. From the filtered list of issues and pull requests, drag the card you'd like to add to your {% data variables.projects.projects_v1_board %} and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
-    {% tip %}
-
-    **Tip:** You can drag and drop or use keyboard shortcuts to reorder cards and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
-
-    {% endtip %}
+    > [!TIP]
+    > You can drag and drop or use keyboard shortcuts to reorder cards and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
 ## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} from the sidebar
 
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index 8a6b94ed0f..318650fe62 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -15,14 +15,10 @@ allowTitleToDifferFromFilename: true
 ---
 {% data reusables.projects.project_boards_old %}
 
-{% tip %}
-
-**Tips:**
-* You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
-* You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
-* Your {% data variables.projects.projects_v1_board %} must have at least one column before you can add notes.{% ifversion projects-v1-can-create %} For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)."{% endif %}
-
-{% endtip %}
+> [!TIP]
+> * You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
+> * You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+> * Your {% data variables.projects.projects_v1_board %} must have at least one column before you can add notes.{% ifversion projects-v1-can-create %} For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)."{% endif %}
 
 When you add a URL for an issue, pull request, or another {% data variables.projects.projects_v1_board %} to a note, you'll see a preview in a summary card below your text.
 
@@ -33,11 +29,8 @@ When you add a URL for an issue, pull request, or another {% data variables.proj
    ![Screenshot showing a project column. The 'add a note to this column' button is highlighted with an orange outline.](/assets/images/help/projects/add-note-button.png)
 1. Type your note, then click **Add**.
 
-   {% tip %}
-
-   **Tip:** You can reference an issue or pull request in your note by typing its URL in the card.
-
-   {% endtip %}
+   > [!TIP]
+   > You can reference an issue or pull request in your note by typing its URL in the card.
 
 ## Converting a note to an issue
 
@@ -45,11 +38,8 @@ If you've created a note and find that it isn't sufficient for your needs, you c
 
 When you convert a note to an issue, the issue is automatically created using the content from the note. The first line of the note will be the issue title and any additional content from the note will be added to the issue description.
 
-{% tip %}
-
-**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within {% data variables.projects.projects_v1_board %} notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github)."
-
-{% endtip %}
+> [!TIP]
+> You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within {% data variables.projects.projects_v1_board %} notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github)."
 
 1. Navigate to the note that you want to convert to an issue.
 {% data reusables.project-management.project-note-more-options %}
diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
index 93f95f105a..1348893679 100644
--- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
+++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
@@ -33,11 +33,8 @@ You can also use the "Filter cards" search bar at the top of each {% data variab
 1. Navigate to the {% data variables.projects.projects_v1_board %} that contains the cards you want to filter.
 1. Above the project card columns, click into the "Filter cards" search bar and type a search query to filter the cards.
 
-{% tip %}
-
-**Tip:** You can drag and drop filtered cards or use keyboard shortcuts to move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
-
-{% endtip %}
+> [!TIP]
+> You can drag and drop filtered cards or use keyboard shortcuts to move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
 ## Further reading
 
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
index f3650c92c6..63b63699fe 100644
--- a/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
@@ -28,11 +28,8 @@ For more information about other changes you can make to your project through th
 
 You may also want to use the **actions/add-to-project** workflow, which is maintained by {% data variables.product.company_short %} and will add the current issue or pull request to the project specified. For more information, see the [actions/add-to-project](https://github.com/actions/add-to-project) repository and README.
 
-{% note %}
-
-**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a {% data variables.product.pat_generic %} (recommended for user projects). Workflow examples for both approaches are shown below.
-
-{% endnote %}
+> [!NOTE]
+> `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a {% data variables.product.pat_generic %} (recommended for user projects). Workflow examples for both approaches are shown below.
 
 ## Example workflow authenticating with a {% data variables.product.prodname_github_app %}
 
@@ -41,25 +38,21 @@ For more information about authenticating in a {% data variables.product.prodnam
 1. Create a {% data variables.product.prodname_github_app %} or choose an existing {% data variables.product.prodname_github_app %} owned by your organization. For more information, see "[AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/creating-a-github-app)."
 1. Give your {% data variables.product.prodname_github_app %} read and write permissions to organization projects.  For this specific example, your {% data variables.product.prodname_github_app %} will also need read permissions to repository pull requests and repository issues. For more information, see "[AUTOTITLE](/apps/maintaining-github-apps/editing-a-github-apps-permissions)."
 
-   {% note %}
-
-   **Note:** You can control your app's permission to organization projects and to repository projects. You must give permission to read and write organization projects; permission to read and write repository projects will not be sufficient.
-
-   {% endnote %}
+   > [!NOTE]
+   > You can control your app's permission to organization projects and to repository projects. You must give permission to read and write organization projects; permission to read and write repository projects will not be sufficient.
 
 1. Install the {% data variables.product.prodname_github_app %} in your organization. Install it for all repositories that your project needs to access. For more information, see "[AUTOTITLE](/apps/maintaining-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)."
 1. Store your {% data variables.product.prodname_github_app %}'s ID as a configuration variable in your repository or organization. In the following workflow, replace `APP_ID` with the name of the configuration variable. You can find your app ID on the settings page for your app or through the App API. For more information, see "[AUTOTITLE](/rest/apps#get-an-app)." For more information about configuration variables, see "[AUTOTITLE](/actions/learn-github-actions/variables#defining-configuration-variables-for-multiple-workflows)."
 1. Generate a private key for your app. Store the contents of the resulting file as a secret in your repository or organization. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following workflow, replace `APP_PEM` with the name of the secret. For more information, see "[AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/managing-private-keys-for-github-apps)." For more information about storing secrets, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
 1. In the following workflow, replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.  In order for this specific example to work, your project must also have a "Date posted" date field.
 
-   {% ifversion ghes < 3.12 %}{% note %}
+   {% ifversion ghes < 3.12 %}
 
-   **Notes:**
+   > [!NOTE]
+   > * {% data reusables.actions.actions-not-certified-by-github %}
+   > * {% data reusables.actions.actions-use-sha-pinning %}
 
-   * {% data reusables.actions.actions-not-certified-by-github %}
-   * {% data reusables.actions.actions-use-sha-pinning %}
-
-   {% endnote %}{% endif %}
+   {% endif %}
 
 ```yaml annotate copy
 #
@@ -259,7 +252,7 @@ jobs:
           # - To get the ID of a field called `Team`, add `echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV`.
           # - To get the ID of an option called `Octoteam` for the `Team` single select field, add `echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") |.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV`.
           #
-          # **Note**: This workflow assumes that you have a project with a single select field called "Status" that includes an option called "Todo" and a date field called "Date posted". You must modify this section to match the fields that are present in your table.
+          # **Note:** This workflow assumes that you have a project with a single select field called "Status" that includes an option called "Todo" and a date field called "Date posted". You must modify this section to match the fields that are present in your table.
           
           echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV
           echo 'DATE_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Date posted") | .id' project_data.json) >> $GITHUB_ENV
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
index 3790c02320..2095b49853 100644
--- a/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
@@ -459,11 +459,8 @@ A project may contain items that a user does not have permission to view. In thi
 
 Use mutations to update projects. For more information, see "[AUTOTITLE](/graphql/guides/forming-calls-with-graphql#about-mutations)."
 
-{% note %}
-
-**Note:** You cannot add and update an item in the same call. You must use `addProjectV2ItemById` to add the item and then use `updateProjectV2ItemFieldValue` to update the item.
-
-{% endnote %}
+> [!NOTE]
+> You cannot add and update an item in the same call. You must use `addProjectV2ItemById` to add the item and then use `updateProjectV2ItemFieldValue` to update the item.
 
 ### Adding an item to a project
 
@@ -635,19 +632,16 @@ gh api graphql -f query='
 
 {% endcli %}
 
-{% note %}
-
-**Note:** You cannot use `updateProjectV2ItemFieldValue` to change `Assignees`, `Labels`, `Milestone`, or `Repository` because these fields are properties of pull requests and issues, not of project items. Instead, you may use the following mutations:
-
-* [addAssigneesToAssignable](/graphql/reference/mutations#addassigneestoassignable)
-* [removeAssigneesFromAssignable](/graphql/reference/mutations#removeassigneesfromassignable)
-* [addLabelsToLabelable](/graphql/reference/mutations#addlabelstolabelable)
-* [removeLabelsFromLabelable](/graphql/reference/mutations#removelabelsfromlabelable)
-* [updateIssue](/graphql/reference/mutations#updateissue)
-* [updatePullRequest](/graphql/reference/mutations#updatepullrequest)
-* [transferIssue](/graphql/reference/mutations#transferissue)
-
-{% endnote %}
+> [!NOTE]
+> You cannot use `updateProjectV2ItemFieldValue` to change `Assignees`, `Labels`, `Milestone`, or `Repository` because these fields are properties of pull requests and issues, not of project items. Instead, you may use the following mutations:
+>
+> * [addAssigneesToAssignable](/graphql/reference/mutations#addassigneestoassignable)
+> * [removeAssigneesFromAssignable](/graphql/reference/mutations#removeassigneesfromassignable)
+> * [addLabelsToLabelable](/graphql/reference/mutations#addlabelstolabelable)
+> * [removeLabelsFromLabelable](/graphql/reference/mutations#removelabelsfromlabelable)
+> * [updateIssue](/graphql/reference/mutations#updateissue)
+> * [updatePullRequest](/graphql/reference/mutations#updatepullrequest)
+> * [transferIssue](/graphql/reference/mutations#transferissue)
 
 ### Updating a single select field
 
diff --git a/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 752419ccdc..93de7d16eb 100644
--- a/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
+++ b/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -11,18 +11,13 @@ topics:
 allowTitleToDifferFromFilename: true
 ---
 
-{% note %}
-
-**Notes:**
-
-* If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
-* Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view#showing-and-hiding-fields)."
-* Automation will not be migrated.
-* Triage, archive, and activity will not be migrated.
-* After migration, the new migrated project and old project will not be kept in sync.
-* {% data reusables.projects.migration-permissions-warning %}
-
-{% endnote %}
+> [!NOTE]
+> * If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
+> * Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view#showing-and-hiding-fields)."
+> * Automation will not be migrated.
+> * Triage, archive, and activity will not be migrated.
+> * After migration, the new migrated project and old project will not be kept in sync.
+> * {% data reusables.projects.migration-permissions-warning %}
 
 ## About project migration
 
@@ -49,11 +44,8 @@ You can migrate your {% data variables.projects.projects_v1_boards %} to the new
 
 ## Migrating a repository {% data variables.projects.projects_v1_board %}
 
-{% note %}
-
-**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository {% data variables.projects.projects_v1_board %}, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
-
-{% endnote %}
+> [!NOTE]
+> {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository {% data variables.projects.projects_v1_board %}, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
 
 {% data reusables.repositories.navigate-to-repo %}
 1. Under your repository name, click {% octicon "table" aria-hidden="true" %} **Projects**.
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout.md
index a59f7ba129..e19aec0792 100644
--- a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout.md
+++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout.md
@@ -71,11 +71,8 @@ In the board layout, you can choose which columns to display. The available colu
 
 You can sort items by a field value.
 
-{% note %}
-
-**Note:** When a board is sorted, you cannot manually reorder items within a column. You can continue to move items from column to column.
-
-{% endnote %}
+> [!NOTE]
+> When a board is sorted, you cannot manually reorder items within a column. You can continue to move items from column to column.
 
 {% data reusables.projects.customize.sort %}
 
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout.md
index 6f13f34af2..861963b419 100644
--- a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout.md
+++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout.md
@@ -67,11 +67,8 @@ You can sort items by a field value.
 
 {% ifversion projects-v2-consistent-sorting %}{% else %}
 
-{% note %}
-
-**Note:** When a table is sorted, you cannot manually reorder rows.
-
-{% endnote %}
+> [!NOTE]
+> When a table is sorted, you cannot manually reorder rows.
 
 {% endif %}
 
diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
index 1d533ff7c0..88bcfa991b 100644
--- a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
@@ -10,11 +10,8 @@ topics:
 allowTitleToDifferFromFilename: true
 ---
 
-{% note %}
-
-**Note:** A project can contain a maximum of {% data variables.projects.item_limit %} items and {% data variables.projects.archived_item_limit %} archived items. To learn more about automatically archiving items when they meet specific criteria, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."
-
-{% endnote %}
+> [!NOTE]
+> A project can contain a maximum of {% data variables.projects.item_limit %} items and {% data variables.projects.archived_item_limit %} archived items. To learn more about automatically archiving items when they meet specific criteria, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."
 
 ## Adding issues and pull requests to a project
 
@@ -22,11 +19,8 @@ You have several options for adding issues and pull requests to your project. Yo
 
 {% ifversion projects-v2-timeline-events %}
 
-{% note %}
-
-**Note:** Timeline events for Projects is currently in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> Timeline events for Projects is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 When you add an issue or pull request to your project, an event will be added to the issue or pull request's timeline. Timeline events will also be added when you remove issues or pull requests and when changes are made to its `status` field for those items. Timeline events are only visible to people who have at least read permission for the project. If a change is made by a built-in workflow, the activity will be attributed to **@github-project-automation**.
 
@@ -119,8 +113,5 @@ Draft issues are useful to quickly capture ideas. Unlike issues and pull request
 
 Draft issues can have a title, text body, assignees, and any custom fields from your project. In order to populate the repository, labels, or milestones for a draft issue, you must first convert the draft issue to an issue. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues)."
 
-{% note %}
-
-**Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue.
-
-{% endnote %}
+> [!NOTE]
+> Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue.
diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
index b784f010d5..90af3af3a4 100644
--- a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
@@ -10,11 +10,8 @@ topics:
 allowTitleToDifferFromFilename: true
 ---
 
-{% note %}
-
-**Note:** A project can contain a maximum of {% data variables.projects.item_limit %} items and {% data variables.projects.archived_item_limit %} archived items.
-
-{% endnote %}
+> [!NOTE]
+> A project can contain a maximum of {% data variables.projects.item_limit %} items and {% data variables.projects.archived_item_limit %} archived items.
 
 ## Archiving items
 
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md
index 99bf3cc416..2a4e62ce86 100644
--- a/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md
@@ -29,11 +29,8 @@ Teams are granted read permissions on any project they are added to. This permis
 1. Click **Link a project**.
 1. In the search field, start typing the name of the project you want to add and then select the project in the list of matches.
 
-   {% note %}
-
-   **Note:** If this change will result in increased project permissions for the team's members, {% data variables.product.product_name %} will prompt you to confirm your choice.
-
-   {% endnote %}
+   > [!NOTE]
+   > If this change will result in increased project permissions for the team's members, {% data variables.product.product_name %} will prompt you to confirm your choice.
 
 ## Removing a project from a team
 
diff --git a/content/issues/tracking-your-work-with-issues/administering-issues/closing-an-issue.md b/content/issues/tracking-your-work-with-issues/administering-issues/closing-an-issue.md
index 87cabeb716..825d277bc5 100644
--- a/content/issues/tracking-your-work-with-issues/administering-issues/closing-an-issue.md
+++ b/content/issues/tracking-your-work-with-issues/administering-issues/closing-an-issue.md
@@ -14,11 +14,8 @@ redirect_from:
   - /issues/tracking-your-work-with-issues/closing-an-issue
 ---
 
-{% note %}
-
-**Note:** You can also close issues automatically with keywords in pull requests and commit messages. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword#linking-a-pull-request-to-an-issue-using-a-keyword)."
-
-{% endnote %}
+> [!NOTE]
+> You can also close issues automatically with keywords in pull requests and commit messages. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword#linking-a-pull-request-to-an-issue-using-a-keyword)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
diff --git a/content/issues/tracking-your-work-with-issues/administering-issues/transferring-an-issue-to-another-repository.md b/content/issues/tracking-your-work-with-issues/administering-issues/transferring-an-issue-to-another-repository.md
index 2f9d78b689..503729544f 100644
--- a/content/issues/tracking-your-work-with-issues/administering-issues/transferring-an-issue-to-another-repository.md
+++ b/content/issues/tracking-your-work-with-issues/administering-issues/transferring-an-issue-to-another-repository.md
@@ -17,11 +17,8 @@ shortTitle: Transfer an issue
 ---
 To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)."
 
-{% note %}
-
-**Note**: You can only transfer issues between repositories owned by the same user or organization account. A private repository issue cannot be transferred to a public repository.
-
-{% endnote %}
+> [!NOTE]
+> You can only transfer issues between repositories owned by the same user or organization account. A private repository issue cannot be transferred to a public repository.
 
 When you transfer an issue, comments and assignees are retained. Labels and milestones are also retained if they're present in the target repository, with labels matching by name and milestones matching by both name and due date. {% ifversion projects-v1 %}This issue will stay on any user-owned or organization-wide {% data variables.projects.projects_v1_boards %} and be removed from any repository {% data variables.projects.projects_v1_boards %}. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."{% endif %}
 
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/about-slash-commands.md b/content/issues/tracking-your-work-with-issues/using-issues/about-slash-commands.md
index ff2bc9c63b..5fa65792a8 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/about-slash-commands.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/about-slash-commands.md
@@ -8,11 +8,8 @@ redirect_from:
   - /issues/tracking-your-work-with-issues/about-slash-commands
 ---
 
-{% note %}
-
-**Note:** Slash commands are currently in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> Slash commands are currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 ## About slash commands
 
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/creating-a-branch-for-an-issue.md b/content/issues/tracking-your-work-with-issues/using-issues/creating-a-branch-for-an-issue.md
index 5b07db81b4..293394da02 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/creating-a-branch-for-an-issue.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/creating-a-branch-for-an-issue.md
@@ -13,11 +13,8 @@ redirect_from:
   - /issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue
 ---
 
-{% note %}
-
-**Note:** The ability to create a branch for an issue is currently in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> The ability to create a branch for an issue is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 ## About branches connected to an issue
 
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md b/content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md
index f76ffcd08f..69a493ff7a 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md
@@ -148,11 +148,8 @@ Within an issue, you can use task lists to break work into smaller tasks and tra
 
 You can use query parameters to open issues. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or an issue template on {% data variables.product.prodname_dotcom %}. To create your own query parameters, you must match the key and value pair.
 
-{% tip %}
-
-**Tip:** You can also create issue templates that open with default labels, assignees, and an issue title. For more information, see "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
-
-{% endtip %}
+> [!TIP]
+> You can also create issue templates that open with default labels, assignees, and an issue title. For more information, see "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
 
 You must have the proper permissions for any action to use the equivalent query parameter. For example, you must have permission to add a label to an issue to use the `labels` query parameter. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)."
 
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md b/content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md
index 6927c66b1e..36a11bc968 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -135,11 +135,8 @@ Once you've [applied labels to an issue or pull request](/issues/using-labels-an
 {% data reusables.project-management.labels %}
 1. In the list of labels, click a label.
 
-{% tip %}
-
-**Tip:** To clear your filter selection, click **Clear current search query, filters, and sorts**.
-
-{% endtip %}
+> [!TIP]
+> To clear your filter selection, click **Clear current search query, filters, and sorts**.
 
 {% ifversion issue-types %}
 
@@ -192,11 +189,8 @@ The issues and pull requests search bar allows you to define your own custom fil
 
 ![Screenshot of the list of issues for a repository. Above the list, a search field, containing the query "is:issue is:open", is outlined in dark orange.](/assets/images/help/issues/issues-search-bar.png)
 
-{% tip %}
-
-**Tip:** {% data reusables.search.search_issues_and_pull_requests_shortcut %}
-
-{% endtip %}
+> [!TIP]
+> {% data reusables.search.search_issues_and_pull_requests_shortcut %}
 
 {% endwebui %}
 
@@ -230,13 +224,10 @@ With issue and pull request search terms, you can:
 * Filter issues and pull requests by label: `state:open type:issue label:"bug"`
 * Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat`
 
-{% tip %}
-
-**Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
-* To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`.
-* To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
-
-{% endtip %}
+> [!TIP]
+> You can filter issues and pull requests by label using logical OR or using logical AND.
+> * To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`.
+> * To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
 
 For issues, you can also use search to:
 
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue.md b/content/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue.md
index b852c70a0d..48b3d23613 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue.md
@@ -18,11 +18,9 @@ topics:
   - Pull requests
 shortTitle: Link PR to issue
 ---
-{% note %}
 
-**Note:** The special keywords in a pull request description are interpreted when the pull request targets the repository's _default_ branch. However, if the PR's base is _any other branch_, then these keywords are ignored, no links are created and merging the PR has no effect on the issues. **If you want to link a pull request to an issue using a keyword, the PR must be on the default branch.**
-
-{% endnote %}
+> [!NOTE]
+> The special keywords in a pull request description are interpreted when the pull request targets the repository's _default_ branch. However, if the PR's base is _any other branch_, then these keywords are ignored, no links are created and merging the PR has no effect on the issues. **If you want to link a pull request to an issue using a keyword, the PR must be on the default branch.**
 
 ## About linked issues and pull requests
 
diff --git a/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md b/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
index 0f0c732fde..2cb86f5a52 100644
--- a/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
+++ b/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
@@ -28,8 +28,5 @@ Additionally, you can edit the milestone from the milestone page and create new
 
 You can prioritize open issues and pull requests in a milestone by clicking to the left of an issue or pull request's checkbox, dragging it to a new location, and dropping it.
 
-{% note %}
-
-**Note:** If there are more than 500 open issues in a milestone, you won't be able to prioritize issues.
-
-{% endnote %}
+> [!NOTE]
+> If there are more than 500 open issues in a milestone, you won't be able to prioritize issues.
diff --git a/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md b/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md
index 48785a6160..00cd18d4cd 100644
--- a/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md
+++ b/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md
@@ -13,15 +13,11 @@ topics:
   - Pull requests
 shortTitle: Filter by milestone
 ---
-{% tip %}
 
-**Tips:**
-
-* If you'd rather filter issues and pull requests using the Search bar, you can use the milestone search syntax. For a milestone called My Milestone, the search syntax would be: `milestone:"My Milestone"`.
-* To clear your filter selection, click **Clear current search query, filters, and sorts**.
-* You can also filter issues or pull requests using the {% data variables.product.prodname_cli %}. For more information, see "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" or "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)" in the {% data variables.product.prodname_cli %} documentation.
-
-{% endtip %}
+> [!TIP]
+> * If you'd rather filter issues and pull requests using the Search bar, you can use the milestone search syntax. For a milestone called My Milestone, the search syntax would be: `milestone:"My Milestone"`.
+> * To clear your filter selection, click **Clear current search query, filters, and sorts**.
+> * You can also filter issues or pull requests using the {% data variables.product.prodname_cli %}. For more information, see "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" or "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)" in the {% data variables.product.prodname_cli %} documentation.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
diff --git a/content/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository.md b/content/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository.md
index 3eff10d8d0..4301b6dcc6 100644
--- a/content/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository.md
+++ b/content/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository.md
@@ -14,11 +14,8 @@ We recommend using Azure Repos to convert your Team Foundation Version Control (
 
 ## Migrating with Azure Repos (recommended)
 
-{% note %}
-
-**Note:** Azure Repos only migrates up to 180 days of history. The state of your repository before the 180-day threshold will be migrated in a single initial commit. To retain more history, see "[Migrating with `git-tfs`](#migrating-with-git-tfs)."
-
-{% endnote %}
+> [!NOTE]
+> Azure Repos only migrates up to 180 days of history. The state of your repository before the 180-day threshold will be migrated in a single initial commit. To retain more history, see "[Migrating with `git-tfs`](#migrating-with-git-tfs)."
 
 To follow these steps, you must use a macOS or Linux system and have the following tools installed:
 
diff --git a/content/migrations/overview/about-locked-repositories.md b/content/migrations/overview/about-locked-repositories.md
index 21707489a3..ccc4c198fa 100644
--- a/content/migrations/overview/about-locked-repositories.md
+++ b/content/migrations/overview/about-locked-repositories.md
@@ -28,11 +28,8 @@ While a migration is in progress, access to the destination repository is locked
 
 {% data variables.product.prodname_importer_proper_name %} does not lock source repositories by default. Source repositories will only be locked if you specify the `--lock-source-repo` option in the {% data variables.product.prodname_cli %}, or the `lockSource` attribute in the `startRepositoryMigration` GraphQL mutation.
 
-{% note %}
-
-**Note:** We do not recommend locking source repositories unless you are certain you will not want to unlock them later. Consider archiving the repositories instead. For more information, see "[AUTOTITLE](/repositories/archiving-a-github-repository/archiving-repositories)."
-
-{% endnote %}
+> [!NOTE]
+> We do not recommend locking source repositories unless you are certain you will not want to unlock them later. Consider archiving the repositories instead. For more information, see "[AUTOTITLE](/repositories/archiving-a-github-repository/archiving-repositories)."
 
 For information about how to unlock repositories that were locked by {% data variables.product.prodname_importer_proper_name %}, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#locked-repositories)."
 
diff --git a/content/migrations/using-ghe-migrator/about-ghe-migrator.md b/content/migrations/using-ghe-migrator/about-ghe-migrator.md
index 83de17af9b..cba4766d30 100644
--- a/content/migrations/using-ghe-migrator/about-ghe-migrator.md
+++ b/content/migrations/using-ghe-migrator/about-ghe-migrator.md
@@ -24,11 +24,8 @@ There are three types of migrations you can perform:
 * A migration from a {% data variables.product.prodname_dotcom_the_website %} organization to a {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by the organization. Before performing a migration, you must have [administrative access](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization) to the {% data variables.product.prodname_dotcom_the_website %} organization as well as site administrator access to the target instance.
 * _Trial runs_ are migrations that import data to a [staging instance]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance). These can be useful to see what _would_ happen if a migration were applied to {% data variables.location.product_location %}. **We strongly recommend that you perform a trial run on a staging instance before importing data to your production instance.**
 
-{% note %}
-
-**Note:** The use of ghe-migrator is **not recommended** for transferring a {% data variables.product.prodname_ghe_server %} instance between hypervisors. Instead, we suggest either backing up and restoring to the new location with {% data variables.product.prodname_enterprise_backup_utilities %}, or creating a replica in the new location and then failing over to the replica appliance. For more information, see "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)", "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica)" and "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance)."
-
-{% endnote %}
+> [!NOTE]
+> The use of ghe-migrator is **not recommended** for transferring a {% data variables.product.prodname_ghe_server %} instance between hypervisors. Instead, we suggest either backing up and restoring to the new location with {% data variables.product.prodname_enterprise_backup_utilities %}, or creating a replica in the new location and then failing over to the replica appliance. For more information, see "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)", "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica)" and "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance)."
 
 ## Migrated data
 
diff --git a/content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md b/content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md
index eaac1efe00..eacdbe8db0 100644
--- a/content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md
+++ b/content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md
@@ -262,11 +262,8 @@ After your migration is applied to your target instance and you have reviewed th
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
 
-{% warning %}
-
-**Warning:** If your repository contains {% data variables.product.prodname_actions %} workflows using the `schedule` trigger, the workflows will not run automatically after an import. To start the scheduled workflows once again, push a commit to the repository. For more information, see "[AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#schedule)."
-
-{% endwarning %}
+> [!WARNING]
+> If your repository contains {% data variables.product.prodname_actions %} workflows using the `schedule` trigger, the workflows will not run automatically after an import. To start the scheduled workflows once again, push a commit to the repository. For more information, see "[AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#schedule)."
 
 ## Unlocking repositories on the source
 
diff --git a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer.md b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer.md
index 48a7c192af..f15c582b8a 100644
--- a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer.md
+++ b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer.md
@@ -88,11 +88,8 @@ gh gei download-logs --github-target-org DESTINATION --target-repo REPOSITORY --
 
 To ensure you have access to migration logs for all your migrated repositories, you can use the `--download-migration-logs` flag when generating a migration script for repository migrations. When you use this flag, the script will include the `download-logs` command for each repository migrated in the script. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-repositories-with-github-enterprise-importer)."
 
-{% note %}
-
-**Note:** You can only use the `--download-migration-logs` flag with repository migrations, not with organization migrations.
-
-{% endnote %}
+> [!NOTE]
+> You can only use the `--download-migration-logs` flag with repository migrations, not with organization migrations.
 
 ## Accessing an organization migration log
 
@@ -106,8 +103,5 @@ The `README.md` file in the root of the repository includes the following inform
 
 The`/success` and `/failure` directories contain one file for each repository that was successfully migrated or that failed to migrate, respectively. These files follow the naming convention `REPO_NAME.md`.
 
-{% note %}
-
-**Note:** The `gei-migration-results` repository is created at the beginning of the migration process but is only updated with your migration logs after the migration finishes.
-
-{% endnote %}
+> [!NOTE]
+> The `gei-migration-results` repository is created at the beginning of the migration process but is only updated with your migration logs after the migration finishes.
diff --git a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer.md b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer.md
index 4c147de9a6..40e22483fa 100644
--- a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer.md
+++ b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer.md
@@ -39,13 +39,9 @@ The target user can choose to accept or reject the invitation. After a user acce
 
 If your organization uses {% data variables.product.prodname_emus %} and you choose to reclaim mannequins with the {% data variables.product.prodname_cli %}, you can optionally skip the invitation process, immediately reclaiming the mannequin without the user's approval.
 
-{% note %}
-
-**Notes:**
-* You cannot reclaim mannequins after you have transferred a repository to another organization. If you wish to transfer a repository to another organization after your migration, you must reclaim the mannequins before the transfer.
-* When reclaiming mannequins, you can only target existing organization members. Before attempting to reclaim a mannequin, verify that the {% data variables.product.prodname_dotcom %} user you want to invite is already added to the organization.
-
-{% endnote %}
+> [!NOTE]
+> * You cannot reclaim mannequins after you have transferred a repository to another organization. If you wish to transfer a repository to another organization after your migration, you must reclaim the mannequins before the transfer.
+> * When reclaiming mannequins, you can only target existing organization members. Before attempting to reclaim a mannequin, verify that the {% data variables.product.prodname_dotcom %} user you want to invite is already added to the organization.
 
 {% data variables.product.prodname_importer_proper_name %} does not migrate user access to repositories. After reclaiming mannequins, if any of the users do not already have appropriate access to the repository via team membership, you must separately give the users access to the repository. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)."
 
@@ -134,11 +130,9 @@ If your migration source is Azure DevOps, you can reclaim mannequins with the {%
 1. To the right of the mannequin you want to reclaim, click **Reattribute**.
 1. In the search field, type the username of the organization member you want to attribute the mannequin's contributions to, then click the member.
 
-   {% note %}
+   > [!NOTE]
+   > You can only send attribution invitations to user accounts that are already members of the organization.
 
-   **Note:** You can only send attribution invitations to user accounts that are already members of the organization.
-
-   {% endnote %}
 1. Click **Invite**.
 {% data reusables.enterprise-migration-tool.mannequin-reclaim-must-accept %}
 
diff --git a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md
index c6486ddff0..672fd734c5 100644
--- a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md
+++ b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md
@@ -53,11 +53,9 @@ The log contains a record of each command you issued and all of the API requests
 ### Unable to run migrations
 
 If you see an error like `No access to createMigrationMutation` or `Missing permissions`, your personal account does not have the required access to run the migration. Make sure you're either an organization owner or have been granted the migrator role. For more information about granting the migrator role, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-repositories-with-github-enterprise-importer)."
-{% note %}
 
-**Note:** If you're migrating between {% data variables.product.company_short %} products, make sure you're an organization owner or have been granted the migrator role for both the source and target organizations.
-
-{% endnote %}
+> [!NOTE]
+> If you're migrating between {% data variables.product.company_short %} products, make sure you're an organization owner or have been granted the migrator role for both the source and target organizations.
 
 ### Resource is protected by organization SAML enforcement
 
@@ -153,11 +151,8 @@ If you see "Repository metadata too big to migrate" in the "Migration Log" issue
 
 If you're migrating from Azure DevOps, pull request comments on lines that were never changed in the pull request cannot be migrated to {% data variables.product.prodname_dotcom %}. You'll see this warning for every comment that cannot be migrated for this reason.
 
-{% note %}
-
-**Note:** Only comments on lines that weren't changed in a pull request are affected by this limitation. Comments on lines that were changed in a pull request are migrated.
-
-{% endnote %}
+> [!NOTE]
+> Only comments on lines that weren't changed in a pull request are affected by this limitation. Comments on lines that were changed in a pull request are migrated.
 
 Be aware that the affected comments will not be in the migrated repository, but these warnings do not require further action from you.
 
@@ -186,11 +181,8 @@ The process for unlocking a repository depends on the {% data variables.product.
 * If the locked repository is on {% data variables.product.prodname_ghe_server %}, a site administrator can unlock the repository using the site admin dashboard. For more information, see "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-repositories-in-your-enterprise/locking-a-repository){% ifversion ghes %}."{% else %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% endif %}
 * If the locked repository is on {% data variables.product.prodname_dotcom_the_website %}, you can contact {% data variables.contact.contact_support %} to unlock the repository.
 
-{% note %}
-
-**Note:** If your migration failed, not all of your data was migrated. If you choose to unlock and use the repository, there will be data loss. Deleting the locked repository and retrying the migration may be a better option.
-
-{% endnote %}
+> [!NOTE]
+> If your migration failed, not all of your data was migrated. If you choose to unlock and use the repository, there will be data loss. Deleting the locked repository and retrying the migration may be a better option.
 
 ## Contacting {% data variables.contact.github_support %}
 
diff --git a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md
index efcd3a5d28..434e7cfdac 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md
@@ -107,11 +107,8 @@ All repositories are migrated with private visibility. If you want to set a repo
 
 Team membership is **not** migrated. After the migration, you'll need to add members to migrated teams. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#recreating-teams)."
 
-{% note %}
-
-**Note:** {% data reusables.enterprise-migration-tool.team-references %} For more information about how to prevent and resolve these issues, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#team-references-are-broken-after-an-organization-migration)."
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.enterprise-migration-tool.team-references %} For more information about how to prevent and resolve these issues, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#team-references-are-broken-after-an-organization-migration)."
 
 ### Migrated data for a repository
 
diff --git a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products.md
index 19ca1f68cd..75dea9ea41 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products.md
@@ -45,15 +45,10 @@ If you're migrating from {% data variables.product.prodname_ghe_server %} 3.8 or
 
 {% data reusables.enterprise-migration-tool.about-the-migrator-role %}
 
-{% note %}
-
-**Notes:**
-
-* If you're migrating a repository between two organizations, you can grant the migrator role to the same person or team for both organizations, but you must grant each separately.
-* You cannot grant the migrator role for enterprise accounts. Therefore, you can only run an organization migration if you're an owner of the destination enterprise. However, you can grant the migrator role to that enterprise owner for the source organization.
-* The {% data variables.product.prodname_cli %} does not support granting the migrator role for organizations on {% data variables.product.prodname_ghe_server %}, so you must be an organization owner of the source organization to migrate repositories from {% data variables.product.prodname_ghe_server %}.
-
-{% endnote %}
+> [!NOTE]
+> * If you're migrating a repository between two organizations, you can grant the migrator role to the same person or team for both organizations, but you must grant each separately.
+> * You cannot grant the migrator role for enterprise accounts. Therefore, you can only run an organization migration if you're an owner of the destination enterprise. However, you can grant the migrator role to that enterprise owner for the source organization.
+> * The {% data variables.product.prodname_cli %} does not support granting the migrator role for organizations on {% data variables.product.prodname_ghe_server %}, so you must be an organization owner of the source organization to migrate repositories from {% data variables.product.prodname_ghe_server %}.
 
 ## Required roles
 
@@ -88,11 +83,8 @@ For other tasks, such as downloading a migration log, you only need one {% data
 
 The scopes that are required for your {% data variables.product.prodname_dotcom %} {% data variables.product.pat_v1 %} depend on your role and the task you want to complete.
 
-{% note %}
-
-**Note**: {% data reusables.user-settings.generic-classic-pat-only %} This means that you cannot use {% data variables.product.prodname_importer_proper_name %} if your organization uses the "Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations" policy. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise#restricting-access-by-personal-access-tokens)."
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.user-settings.generic-classic-pat-only %} This means that you cannot use {% data variables.product.prodname_importer_proper_name %} if your organization uses the "Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations" policy. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise#restricting-access-by-personal-access-tokens)."
 
 Task | Enterprise owner | Organization owner | Migrator
 ---- | ------------------ | -------- | ----- |
diff --git a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md
index 0fd3d1f225..085aaa4be5 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md
@@ -211,13 +211,10 @@ Content-Type: application/json
 
 For more information, see "[Get an organization migration status](/rest/migrations/orgs#get-an-organization-migration-status)".
 
-{% note %}
-
-**Note:** If your migration moves to the `failed` state rather than the `exported` state, try starting the migration again. If the migration fails repeatedly, we recommend generating the archives using `ghe-migrator` instead of the API.
-
-Follow the steps in "[Exporting migration data from your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise)," adding only one repository to the migration. At the end of the process, you will have a single migration archive with your Git source and metadata, and you can move to step 6 in this article.
-
-{% endnote %}
+> [!NOTE]
+> If your migration moves to the `failed` state rather than the `exported` state, try starting the migration again. If the migration fails repeatedly, we recommend generating the archives using `ghe-migrator` instead of the API.
+>
+>Follow the steps in "[Exporting migration data from your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise)," adding only one repository to the migration. At the end of the process, you will have a single migration archive with your Git source and metadata, and you can move to step 6 in this article.
 
 After the `state` of a migration moves to `exported`, you can fetch the migration's URL using the "Download an organization migration archive" API.
 
@@ -361,23 +358,17 @@ After you set up blob storage with a supported cloud provider, you must configur
 
 #### Configuring blob storage in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}
 
-{% note %}
-
-**Note:** You only need to configure blob storage in the {% data variables.enterprise.management_console %} if you use {% data variables.product.prodname_ghe_server %} 3.8 or higher. If you use 3.7 or lower, configure your credentials in the {% data variables.product.prodname_cli %} instead.
-
-{% endnote %}
+> [!NOTE]
+> You only need to configure blob storage in the {% data variables.enterprise.management_console %} if you use {% data variables.product.prodname_ghe_server %} 3.8 or higher. If you use 3.7 or lower, configure your credentials in the {% data variables.product.prodname_cli %} instead.
 
 {% data reusables.enterprise-migration-tool.blob-storage-management-console %}
 
 ### Configuring your blob storage credentials in the {% data variables.product.prodname_cli %}
 
-{% note %}
-
-**Note:** You only need to configure your blob storage credentials in the {% data variables.product.prodname_cli %} if you use {% data variables.product.prodname_ghe_server %} 3.7 or lower. If you use 3.8 or higher, configure blob storage in the {% data variables.enterprise.management_console %} instead.
-
-If you configure your blob storage credentials in the {% data variables.product.prodname_cli %}, you will not be able to perform migrations where your Git source or metadata exports exceed 2GB. To perform these migrations, upgrade to {% data variables.product.prodname_ghe_server %} 3.8 or higher.
-
-{% endnote %}
+> [!NOTE]
+> You only need to configure your blob storage credentials in the {% data variables.product.prodname_cli %} if you use {% data variables.product.prodname_ghe_server %} 3.7 or lower. If you use 3.8 or higher, configure blob storage in the {% data variables.enterprise.management_console %} instead.
+>
+> If you configure your blob storage credentials in the {% data variables.product.prodname_cli %}, you will not be able to perform migrations where your Git source or metadata exports exceed 2GB. To perform these migrations, upgrade to {% data variables.product.prodname_ghe_server %} 3.8 or higher.
 
 #### Configuring AWS S3 credentials in the {% data variables.product.prodname_cli %}
 
diff --git a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
index 3a60489640..5d3e912d4d 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md
@@ -32,11 +32,8 @@ If you're migrating between {% data variables.product.company_short %} products,
 
 First, if your migration source is {% data variables.product.prodname_dotcom_the_website %}, decide whether you want to migrate on an organization-by-organization basis or on a repository-by-repository basis.
 
-{% note %}
-
-**Note:** If you're migrating from {% data variables.product.prodname_ghe_server %}, you can only migrate repositories.
-
-{% endnote %}
+> [!NOTE]
+> If you're migrating from {% data variables.product.prodname_ghe_server %}, you can only migrate repositories.
 
 If you choose repository-by-repository migrations, only repository-level data is migrated. If you pick the organization-by-organization migration strategy, selected organization-level data is also migrated, including teams and their access to repositories.
 
@@ -88,11 +85,9 @@ To migrate a repository, you must be an organization owner for both the source o
 1. Decide whether you want an organization owner to perform your migrations, or whether you need to grant the migrator role to someone else.
 {% data reusables.enterprise-migration-tool.grant-migrator-tasks %} For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#about-the-migrator-role)."
 
-   {% note %}
+   > [!NOTE]
+   > Remember to grant the migrator role for both the source organization and the destination organization.
 
-   **Note:** Remember to grant the migrator role for both the source organization and the destination organization.
-
-   {% endnote %}
 {% data reusables.enterprise-migration-tool.confirm-migrator-has-correct-pats %} For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products#required-scopes-for-personal-access-tokens)."
 
 ### Do we want to maintain a similar organization structure after migrating?
@@ -103,11 +98,8 @@ If you intend to change your organizational structure, consider other batching f
 
 Even if you change your organizational structure, you can still prepare a script for your migration. Use the {% data variables.product.prodname_cli %} command, then move the lines for each repository into different scripts as needed.
 
-{% note %}
-
-**Note:** You can run multiple batches simultaneously. For example, if you're batching by teams, you could run the migrations for multiple teams in the same time window.
-
-{% endnote %}
+> [!NOTE]
+> You can run multiple batches simultaneously. For example, if you're batching by teams, you could run the migrations for multiple teams in the same time window.
 
 {% data reusables.enterprise-migration-tool.organization-structure-tasks %}
 
@@ -165,11 +157,8 @@ During the migration process, {% data variables.product.prodname_actions %} is d
 
 If you were using {% data variables.actions.hosted_runner %}s, self-hosted runners, or encrypted secrets, you must reconfigure them.
 
-{% note %}
-
-**Note:** Workflow run history for {% data variables.product.prodname_actions %} is not included in migrations.
-
-{% endnote %}
+> [!NOTE]
+> Workflow run history for {% data variables.product.prodname_actions %} is not included in migrations.
 
 1. If you use self-hosted runners, reconfigure your runners.
 
diff --git a/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md
index 2f54231836..e9b46dc417 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md
@@ -74,11 +74,8 @@ Next, plan the organizational structure you'll create in {% data variables.produ
 * ADO: Organization > team project > repositories
 * {% data variables.product.prodname_dotcom %}: Enterprise > organization > repositories
 
-{% note %}
-
-**Note:** The concept of a team project, which is used to group repositories in ADO, does not exist in {% data variables.product.prodname_dotcom %}. We do not recommend treating organizations in {% data variables.product.product_name %} as the equivalent of team projects in ADO.
-
-{% endnote %}
+> [!NOTE]
+> The concept of a team project, which is used to group repositories in ADO, does not exist in {% data variables.product.prodname_dotcom %}. We do not recommend treating organizations in {% data variables.product.product_name %} as the equivalent of team projects in ADO.
 
 After migrating to {% data variables.product.prodname_dotcom %}, you should have only one enterprise account and a small number of organizations owned by that enterprise. Each organization from ADO should correspond to a single organization on {% data variables.product.prodname_dotcom %}. We do not recommend creating an organization on {% data variables.product.prodname_dotcom %} for each team project on ADO.
 
diff --git a/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md
index 6361801710..b5b598f502 100644
--- a/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md
+++ b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md
@@ -162,11 +162,8 @@ gh bbs2gh migrate-repo --bbs-server-url BBS-SERVER-URL \
 {% data reusables.enterprise-migration-tool.aws-bucket-name-placeholder %}
 {% data reusables.enterprise-migration-tool.archive-download-host-placeholder %}
 
-{% note %}
-
-**Note:** If you get an error mentioning `Renci.SshNet`, then the CLI is having issues making an SFTP connection to your server to download your migration archive. For information about how to troubleshoot these issues, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#cipher-name-is-not-supported)."
-
-{% endnote %}
+> [!NOTE]
+> If you get an error mentioning `Renci.SshNet`, then the CLI is having issues making an SFTP connection to your server to download your migration archive. For information about how to troubleshoot these issues, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#cipher-name-is-not-supported)."
 
 ### Downloading the migration archive manually