diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
index a1eaa097b789..6d6bb1604ba4 100644
--- a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
+++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -44,7 +44,7 @@ If you use Gravatar, and your Gravatar image is associated with the email you us
### Resetting your profile picture to the identicon
{% data reusables.user-settings.access_settings %}
-1. Under "Profile Picture", select **{% octicon "pencil" aria-hidden="true" %} Edit**, then click **Remove photo** to revert to your identicon.
+1. Under "Profile Picture", select **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit**, then click **Remove photo** to revert to your identicon.
If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
@@ -149,7 +149,7 @@ If you select the "Busy" option, when people @mention your username, assign you
-1. In the top right corner of {% data variables.product.prodname_dotcom %}, select your profile photo, then click **{% octicon "smiley" aria-hidden="true" %} Set status** or, if you already have a status set, click your current status.
+1. In the top right corner of {% data variables.product.prodname_dotcom %}, select your profile photo, then click **{% octicon "smiley" aria-hidden="true" aria-label="smiley" %} Set status** or, if you already have a status set, click your current status.
diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index 69526f6bb472..265b74467ebe 100644
--- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -45,7 +45,7 @@ You can send an invitation to collaborate in your repository directly to someone
1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github).{% endif %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" %} Collaborators**.
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" aria-label="people" %} Collaborators**.
1. Click **Add people**.
1. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
1. Click **Add NAME to REPOSITORY**.
diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index a5388f11162b..2ec766ed7f1c 100644
--- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -20,6 +20,6 @@ topics:
shortTitle: Remove yourself
---
{% data reusables.user-settings.access_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-hidden="true" %} Repositories**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Repositories**.
1. Next to the repository you want to leave, click **Leave**.
1. Read the warning carefully, then click **I understand, leave this repository.**
diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/about-your-personal-dashboard.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/about-your-personal-dashboard.md
index bf6180a8a0ce..87861657d61d 100644
--- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/about-your-personal-dashboard.md
+++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/about-your-personal-dashboard.md
@@ -49,7 +49,7 @@ You can also find a list of your recently visited repositories, teams, and proje
The feed is designed to help you discover relevant content from projects you follow, keep up with your friends and community members, and track recent activity in your communities.
-You can use the **{% octicon "filter" aria-hidden="true" %} Filter** dropdown in the upper right corner to filter the feed to show only the exact event types you'd like to see. For example, you'll see updates when someone you follow:
+You can use the **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter** dropdown in the upper right corner to filter the feed to show only the exact event types you'd like to see. For example, you'll see updates when someone you follow:
* Stars a repository
* Follows another user
diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
index 57454c0130ba..4ff78e34217f 100644
--- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
+++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -16,5 +16,5 @@ redirect_from:
If you feel that tabbed indentation in code rendered on {% data variables.product.github %} takes up too much, or too little space, you can change this in your settings.
{% data reusables.user-settings.access_settings %}
-1. In the left sidebar, click **{% octicon "paintbrush" aria-hidden="true" %} Appearance**.
+1. In the left sidebar, click **{% octicon "paintbrush" aria-hidden="true" aria-label="paintbrush" %} Appearance**.
1. Scroll down to "Tab size preference" and use the dropdown menu to choose your preference.
diff --git a/content/actions/administering-github-actions/making-retired-namespaces-available-on-ghecom.md b/content/actions/administering-github-actions/making-retired-namespaces-available-on-ghecom.md
index b8b6c1f08d7b..0cf4cdfeddc5 100644
--- a/content/actions/administering-github-actions/making-retired-namespaces-available-on-ghecom.md
+++ b/content/actions/administering-github-actions/making-retired-namespaces-available-on-ghecom.md
@@ -22,7 +22,7 @@ After using an action from {% data variables.product.prodname_dotcom_the_website
{% data reusables.enterprise-accounts.access-enterprise-emu %}
{% data reusables.enterprise-accounts.settings-tab %}
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Retired namespaces**.
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Retired namespaces**.
1. To the right of the namespace that you want use in your enterprise, click **Unretire**.
1. Go to the relevant organization and create a new repository.
diff --git a/content/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment.md b/content/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment.md
index 5935717404aa..5443e87d2def 100644
--- a/content/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment.md
+++ b/content/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment.md
@@ -186,7 +186,7 @@ Variables stored in an environment are only available to workflow jobs that refe
1. Optionally, specify what branches and tags can deploy to this environment. For more information, see [Deployment branches and tags](/actions/deployment/targeting-different-environments/managing-environments-for-deployment#deployment-branches-and-tags).
1. Select the desired option in the **Deployment branches** dropdown.
1. If you chose **Selected branches and tags**, to add a new rule, click **Add deployment branch or tag rule**
- 1. In the "Ref type" dropdown menu, depending on what rule you want to apply, click **{% octicon "git-branch" aria-hidden="true" %} Branch** or **{% octicon "tag" aria-hidden="true" %} Tag**.
+ 1. In the "Ref type" dropdown menu, depending on what rule you want to apply, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Branch** or **{% octicon "tag" aria-hidden="true" aria-label="tag" %} Tag**.
1. Enter the name pattern for the branch or tag that you want to allow.
{% data reusables.actions.branch-and-tag-deployment-rules-configuration %}
diff --git a/content/actions/managing-workflow-runs-and-deployments/managing-deployments/viewing-deployment-history.md b/content/actions/managing-workflow-runs-and-deployments/managing-deployments/viewing-deployment-history.md
index 72b13e2cba92..76e32a345cdf 100644
--- a/content/actions/managing-workflow-runs-and-deployments/managing-deployments/viewing-deployment-history.md
+++ b/content/actions/managing-workflow-runs-and-deployments/managing-deployments/viewing-deployment-history.md
@@ -42,9 +42,9 @@ By default, the deployments page shows currently active deployments from select
* **To view the URL for a deployment**, to the right of the commit message in the deployment history list, click {% octicon "link-external" aria-label="Navigate to deployment URL" %}.
* **To navigate to the workflow run logs associated with a deployment**, to the right of the commit message in the deployment history list, click {% octicon "kebab-horizontal" aria-label="View logs" %}, then click **View logs**.{% ifversion deployment-dashboard-filter %}
1. Optionally, to filter the deployment history list, create a filter.
- 1. Click on the **{% octicon "filter" aria-hidden="true" %} Filter** button.
- 1. Click **{% octicon "plus" aria-hidden="true" %} Add a filter**.
+ 1. Click on the **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter** button.
+ 1. Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a filter**.
1. Choose a qualifier you would like to filter the deployment history by.
1. Depending on the qualifier you chose, fill out information in the "Operator" and "Value" columns.
- 1. Optionally, click **{% octicon "plus" aria-hidden="true" %} Add a filter** to add another filter.
+ 1. Optionally, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a filter** to add another filter.
1. Click **Apply**.{% endif %}
diff --git a/content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md b/content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md
index 26865a478f4e..841b3fbf3a98 100644
--- a/content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md
+++ b/content/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -28,7 +28,7 @@ Re-running a workflow or jobs in a workflow uses the same `GITHUB_SHA` (commit S
{% data reusables.repositories.view-run %}
1. In the upper-right corner of the workflow, re-run jobs.
- * If any jobs failed, select the **{% octicon "sync" aria-hidden="true" %} Re-run jobs** dropdown menu and click **Re-run all jobs**.
+ * If any jobs failed, select the **{% octicon "sync" aria-hidden="true" aria-label="sync" %} Re-run jobs** dropdown menu and click **Re-run all jobs**.
* If no jobs failed, click **Re-run all jobs**.
@@ -70,7 +70,7 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
{% data reusables.repositories.actions-tab %}
{% data reusables.repositories.navigate-to-workflow %}
{% data reusables.repositories.view-run %}
-1. In the upper-right corner of the workflow, select the **{% octicon "sync" aria-hidden="true" %} Re-run jobs** dropdown menu, and click **Re-run failed jobs**.
+1. In the upper-right corner of the workflow, select the **{% octicon "sync" aria-hidden="true" aria-label="sync" %} Re-run jobs** dropdown menu, and click **Re-run failed jobs**.
{% data reusables.actions.enable-debug-logging %}
{% endwebui %}
diff --git a/content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/adding-a-workflow-status-badge.md b/content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/adding-a-workflow-status-badge.md
index 9db1f33cb94e..74f4fb597db5 100644
--- a/content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/adding-a-workflow-status-badge.md
+++ b/content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/adding-a-workflow-status-badge.md
@@ -30,7 +30,7 @@ You can create a workflow status badge directly on the UI using the workflow fil
1. On the right side of the page, next to the "Filter workflow runs" field, click {% octicon "kebab-horizontal" aria-label="Show workflow options" %} to display a dropdown menu and click **Create status badge**.
1. Optionally, select a branch if you want to display the status badge for a branch different from the default branch.
1. Optionally, select the event that will trigger the workflow.
-1. Click **{% octicon "copy" aria-hidden="true" %} Copy status badge Markdown**.
+1. Click **{% octicon "copy" aria-hidden="true" aria-label="copy" %} Copy status badge Markdown**.
1. Copy the Markdown into your `README.md` file.
## Using the workflow file name
diff --git a/content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/viewing-job-execution-time.md b/content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/viewing-job-execution-time.md
index 5a014f1ce99c..1ee464b4107e 100644
--- a/content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/viewing-job-execution-time.md
+++ b/content/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/viewing-job-execution-time.md
@@ -19,7 +19,7 @@ Billable job execution minutes are only shown for jobs run on private repositori
{% data reusables.repositories.navigate-to-workflow %}
{% data reusables.repositories.view-run %}
1. Under the job summary, you can view the job's execution time.
-1. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-hidden="true" %} Usage**.
+1. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-hidden="true" aria-label="stopwatch" %} Usage**.
> [!NOTE]
> The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see [AUTOTITLE](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage).
diff --git a/content/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows.md b/content/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows.md
index 09b606cea244..22ab262fa89d 100644
--- a/content/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows.md
+++ b/content/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows.md
@@ -11,8 +11,8 @@ If a workflow run fails, you can open a chat with {% data variables.product.prod
To open a chat about a failed workflow run, you can either:
-* Next to the failed check in the merge box, click **{% octicon "kebab-horizontal" aria-hidden="true" %}**, then click **{% octicon "copilot" aria-hidden="true" %} Explain error**.
-* In the merge box, click on the failed check. At the top of the workflow run summary page, click **{% octicon "copilot" aria-hidden="true" %} Explain error**.
+* Next to the failed check in the merge box, click **{% octicon "kebab-horizontal" aria-hidden="true" aria-label="kebab-horizontal" %}**, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Explain error**.
+* In the merge box, click on the failed check. At the top of the workflow run summary page, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Explain error**.
This opens a chat window with {% data variables.product.prodname_copilot %}, where it will provide instructions to resolve the issue.
diff --git a/content/actions/writing-workflows/quickstart.md b/content/actions/writing-workflows/quickstart.md
index 22072df36d2e..499b8ad13ecc 100644
--- a/content/actions/writing-workflows/quickstart.md
+++ b/content/actions/writing-workflows/quickstart.md
@@ -41,7 +41,7 @@ This guide assumes that:
* You have a repository on {% data variables.product.github %} where you can add files.
* You have access to {% data variables.product.prodname_actions %}.
- > [!NOTE] If the **{% octicon "play" aria-hidden="true" %} Actions** tab is not displayed under the name of your repository on {% data variables.product.prodname_dotcom %}, it may be because Actions is disabled for the repository. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository).
+ > [!NOTE] If the **{% octicon "play" aria-hidden="true" aria-label="play" %} Actions** tab is not displayed under the name of your repository on {% data variables.product.prodname_dotcom %}, it may be because Actions is disabled for the repository. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository).
## Creating your first workflow
diff --git a/content/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md b/content/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md
index 8ce714bbc9e4..77871beab06d 100644
--- a/content/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md
+++ b/content/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md
@@ -32,6 +32,6 @@ You can enable the `same-origin` referrer policy to instruct modern browsers to
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Authentication security**.
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Authentication security**.
1. Under "User Agent Referrer Policy", select **Enable same origin referrer policy for all organizations**.
1. Click **Save**.
diff --git a/content/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-access-to-githubcom-using-a-corporate-proxy.md b/content/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-access-to-githubcom-using-a-corporate-proxy.md
index 027637e6d6a0..c149268206a8 100644
--- a/content/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-access-to-githubcom-using-a-corporate-proxy.md
+++ b/content/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-access-to-githubcom-using-a-corporate-proxy.md
@@ -41,7 +41,7 @@ An enterprise owner can identify the correct enterprise ID to use in the header
{% data reusables.enterprise-accounts.access-enterprise-emu %}
{% data reusables.enterprise-accounts.settings-tab %}
-1. Under {% octicon "gear" aria-hidden="true" %} **Settings**, click **Authentication security**.
+1. Under {% octicon "gear" aria-hidden="true" aria-label="gear" %} **Settings**, click **Authentication security**.
1. In the "Enterprise access restrictions" section, find the header for your enterprise. This section is only visible for enterprises with the feature enabled.
## Using the header
diff --git a/content/admin/data-residency/about-github-enterprise-cloud-with-data-residency.md b/content/admin/data-residency/about-github-enterprise-cloud-with-data-residency.md
index 7b2613e2d3b5..45a2a74957b6 100644
--- a/content/admin/data-residency/about-github-enterprise-cloud-with-data-residency.md
+++ b/content/admin/data-residency/about-github-enterprise-cloud-with-data-residency.md
@@ -16,7 +16,7 @@ By default, {% data variables.product.company_short %} stores data for {% data v
You can **get started with data residency** by setting up a trial of {% data variables.product.prodname_ghe_cloud %}.
-Set up a trial of {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 %}
+Set up a trial of {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 aria-label="link-external" %}
## What is {% data variables.product.prodname_ghe_cloud %}?
diff --git a/content/admin/data-residency/getting-started-with-data-residency-for-github-enterprise-cloud.md b/content/admin/data-residency/getting-started-with-data-residency-for-github-enterprise-cloud.md
index 5b16cc6bff46..9d2b36885fc9 100644
--- a/content/admin/data-residency/getting-started-with-data-residency-for-github-enterprise-cloud.md
+++ b/content/admin/data-residency/getting-started-with-data-residency-for-github-enterprise-cloud.md
@@ -41,7 +41,7 @@ To get started with {% data variables.enterprise.data_residency_short %}, you wi
* Includes access to most {% data variables.product.prodname_enterprise %} features, though not the features listed in [Features not included in the trial](/admin/overview/setting-up-a-trial-of-github-enterprise-cloud#features-not-included-in-the-trial)
* Allows you to create up to **three new organizations**
-Set up a trial of {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 %}
+Set up a trial of {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 aria-label="link-external" %}
1. Visit the trial page by clicking the link above.
1. Select **Get started with managed users**.
diff --git a/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-codespaces-in-your-enterprise.md b/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-codespaces-in-your-enterprise.md
index bc2245f1fea6..f902e48fa7c9 100644
--- a/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-codespaces-in-your-enterprise.md
+++ b/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-codespaces-in-your-enterprise.md
@@ -34,7 +34,7 @@ If you're an organization owner, you can enable {% data variables.product.prodna
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
-1. Under "{% octicon "law" aria-hidden="true" %} Policies," click **Codespaces**.
+1. Under "{% octicon "law" aria-hidden="true" aria-label="law" %} Policies," click **Codespaces**.
1. On the {% data variables.product.prodname_github_codespaces %} policies page, under "Manage organization access to {% data variables.product.prodname_github_codespaces %}," select whether to enable {% data variables.product.prodname_github_codespaces %} in your organizations' private and internal repositories.
You can enable for all organizations, enable for specific organizations, or disable for all organizations.
diff --git a/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-sponsors-in-your-enterprise.md b/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-sponsors-in-your-enterprise.md
index 098f560be8c3..a3cc4d02813c 100644
--- a/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-sponsors-in-your-enterprise.md
+++ b/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-sponsors-in-your-enterprise.md
@@ -26,7 +26,7 @@ Organizations that belong to an enterprise that pays by invoice can either pay f
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
-1. Under {% octicon "law" aria-hidden="true" %} "Policies", click **Sponsors**.
+1. Under {% octicon "law" aria-hidden="true" aria-label="law" %} "Policies", click **Sponsors**.
1. Under "Sponsors", click **Add organization**.
1. Begin typing the name of the organization you'd like to enable sponsorships for, then click the name of the organization in the list.
1. Click **Enable sponsorships**.
@@ -37,5 +37,5 @@ You can disallow the use of {% data variables.product.prodname_sponsors %} for a
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
-1. Under {% octicon "law" aria-hidden="true" %} "Policies", click **Sponsors**.
+1. Under {% octicon "law" aria-hidden="true" aria-label="law" %} "Policies", click **Sponsors**.
1. Under "Sponsors", to the right of the organization's name, click **Disable**.
diff --git a/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md b/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md
index 64955fd8a6f8..432ba594a684 100644
--- a/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md
+++ b/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md
@@ -23,7 +23,7 @@ Regardless of the chosen policy, {% data variables.product.pat_generic_caps_plur
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
-1. Under **{% octicon "law" aria-hidden="true" %} Policies**, click **{% data variables.product.pat_generic_caps_plural %}**. {% ifversion tabbed-pat-settings-ui %}
+1. Under **{% octicon "law" aria-hidden="true" aria-label="law" %} Policies**, click **{% data variables.product.pat_generic_caps_plural %}**. {% ifversion tabbed-pat-settings-ui %}
1. Select either the **Fine-grained tokens** or **Tokens (classic)** tab to enforce this policy based on the token type. {% endif %}
1. Under **{% data variables.product.pat_v2_caps_plural %}** or **Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations**, select your access policy.
1. Click **Save**.
@@ -47,7 +47,7 @@ When you set a policy, tokens with non-compliant lifetimes will be blocked from
### Setting a maximum lifetime policy
{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.policies-tab %}, then click **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**.
+{% data reusables.enterprise-accounts.policies-tab %}, then click **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**.
1. Select either the **Fine-grained tokens** or **Tokens (classic)** tab to enforce this policy based on the token type.
1. Under **Set maximum lifetimes for {% data variables.product.pat_generic_plural %}**, set the maximum lifetime. Tokens must be created with a lifetime less than or equal to this many days.
1. Optionally, to exempt your enterprise administrators from this policy, check the **Exempt administrators** checkbox. You should exempt them from this policy if you use SCIM for user provisioning or have automation that has not migrated to {% data variables.product.prodname_github_app %} yet.
@@ -70,7 +70,7 @@ By default, organizations require approval of {% data variables.product.pat_v2_p
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
-1. Under **{% octicon "law" aria-hidden="true" %} Policies**, click **{% data variables.product.pat_generic_caps_plural %}**. {% ifversion tabbed-pat-settings-ui %}
+1. Under **{% octicon "law" aria-hidden="true" aria-label="law" %} Policies**, click **{% data variables.product.pat_generic_caps_plural %}**. {% ifversion tabbed-pat-settings-ui %}
1. Select the **Fine-grained tokens** tab. {% endif %}
1. Under **Require approval of {% data variables.product.pat_v2_plural %}**, select your approval policy:
1. Click **Save**.
diff --git a/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/managing-policies-for-code-governance.md b/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/managing-policies-for-code-governance.md
index 84b87f29c3b1..43e40e2d3354 100644
--- a/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/managing-policies-for-code-governance.md
+++ b/content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/managing-policies-for-code-governance.md
@@ -42,7 +42,7 @@ You can edit a ruleset to change parts of the ruleset, such as the name, bypass
{% data reusables.enterprise-accounts.access-enterprise %}
1. In the left sidebar, in the "Policies" section, click **Code**, then click **Rulesets**.
-1. To the right of the ruleset's name, select {% octicon "kebab-horizontal" aria-label="Open additional options" %}, then click **{% octicon "trash" aria-hidden="true" %} Delete ruleset**.
+1. To the right of the ruleset's name, select {% octicon "kebab-horizontal" aria-label="Open additional options" %}, then click **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete ruleset**.
## Using ruleset history
@@ -52,7 +52,7 @@ You can edit a ruleset to change parts of the ruleset, such as the name, bypass
{% data reusables.enterprise-accounts.access-enterprise %}
1. In the left sidebar, in the "Policies" section, click **Code**, then click **Rulesets**.
-1. To view the history of changes to the ruleset, select {% octicon "kebab-horizontal" aria-label="Open additional options" %} to the right of the ruleset's name, then click **{% octicon "history" aria-hidden="true" %} History**.
+1. To view the history of changes to the ruleset, select {% octicon "kebab-horizontal" aria-label="Open additional options" %} to the right of the ruleset's name, then click **{% octicon "history" aria-hidden="true" aria-label="history" %} History**.
1. To the right of the specific iteration, select {% octicon "kebab-horizontal" aria-label="Open additional options" %}, then click **Compare changes**, **Restore**, or **Download**.
## Importing a ruleset
diff --git a/content/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-your-instance.md b/content/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-your-instance.md
index 148219d4583c..f89ef38df013 100644
--- a/content/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-your-instance.md
+++ b/content/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-your-instance.md
@@ -61,5 +61,5 @@ A repository owner can only configure a hook if the site administrator selected
{% data reusables.profile.enterprise_access_profile %}
1. Navigate to the repository that you want to configure pre-receive hooks for.
{% data reusables.repositories.sidebar-settings %}
-1. In the left sidebar, click **{% octicon "webhook" aria-hidden="true" %} Hooks**.
+1. In the left sidebar, click **{% octicon "webhook" aria-hidden="true" aria-label="webhook" %} Hooks**.
1. Next to the pre-receive hook that you want to configure, select the **Hook permissions** dropdown menu, then click whether to enable or disable the pre-receive hook.
diff --git a/content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers.md b/content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers.md
index 3c3ca6437575..ab9c712b129a 100644
--- a/content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers.md
+++ b/content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers.md
@@ -22,7 +22,7 @@ You can configure the web UI for your enterprise to display a custom footer with
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Profile**.
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Profile**.
1. At the top of the page, under the navigation bar, click **Custom footer**.
diff --git a/content/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-requests-for-copilot-business-from-organizations-in-your-enterprise.md b/content/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-requests-for-copilot-business-from-organizations-in-your-enterprise.md
index be41c2ba0f0a..2c41c09dc869 100644
--- a/content/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-requests-for-copilot-business-from-organizations-in-your-enterprise.md
+++ b/content/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-requests-for-copilot-business-from-organizations-in-your-enterprise.md
@@ -23,5 +23,5 @@ As an enterprise owner, you can view or dismiss these requests from your notific
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
-1. Under "{% octicon "law" aria-hidden="true" %} Policies", click **Copilot**.
+1. Under "{% octicon "law" aria-hidden="true" aria-label="law" %} Policies", click **Copilot**.
1. In the "Access management" section, next to the organization you want to give access, select the dropdown menu and click **Enabled**.
diff --git a/content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md b/content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
index 4f769e204f8b..cdfa3d102965 100644
--- a/content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
+++ b/content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
@@ -30,7 +30,7 @@ Restoring a repository will not restore release attachments or team permissions.
{% data reusables.enterprise_site_admin_settings.access-settings %}
{% data reusables.enterprise_site_admin_settings.search-user-or-org %}
{% data reusables.enterprise_site_admin_settings.click-user-or-org %}
-1. In the **{% octicon "repo" aria-hidden="true" %} Repositories** section, click the **{% octicon "trash" aria-hidden="true" %} Deleted repositories** link.
+1. In the **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Repositories** section, click the **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Deleted repositories** link.
1. Find the repository you want to restore in the deleted repositories list, then to the right of the repository name click **Restore**.
1. To confirm you would like to restore the named repository, click **Restore**.
diff --git a/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md b/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md
index 06922e860dc3..5f911ea30b01 100644
--- a/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md
+++ b/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md
@@ -42,7 +42,7 @@ You can download a CSV file containing the membership information report for you
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.people-tab %}
-1. To the right of "Members", click **{% octicon "download" aria-hidden="true" %} CSV Report**.
+1. To the right of "Members", click **{% octicon "download" aria-hidden="true" aria-label="download" %} CSV Report**.
* If your enterprise has less than 1,000 members, the report will download immediately.
* If your enterprise has 1,000 or more members, you'll soon receive an email with a link to download the report.
diff --git a/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-dormant-users.md b/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-dormant-users.md
index 2cc8926f6894..7c0e0a50ae50 100644
--- a/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-dormant-users.md
+++ b/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-dormant-users.md
@@ -56,7 +56,7 @@ Dormant users are not automatically suspended. Consider suspending dormant users
{% data reusables.enterprise_site_admin_settings.access-settings %}
{% data reusables.enterprise_site_admin_settings.search-user %}
{% data reusables.enterprise_site_admin_settings.click-user %}
-1. In the **User info** section, view the status of the user's account. Any users labeled with "{% octicon "hourglass" aria-hidden="true" %} Dormant" are dormant, and users labeled with "{% octicon "hourglass" aria-hidden="true" %} "Active" are not.
+1. In the **User info** section, view the status of the user's account. Any users labeled with "{% octicon "hourglass" aria-hidden="true" aria-label="hourglass" %} Dormant" are dormant, and users labeled with "{% octicon "hourglass" aria-hidden="true" aria-label="hourglass" %} "Active" are not.
@@ -79,5 +79,5 @@ Dormant users are not automatically suspended. Consider suspending dormant users
{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
1. Scroll to "Reports".
1. Optionally, to generate a new report, next to "Dormant Users", click **New report**.
-1. Under "Recent reports", next to the report you want to download, click **{% octicon "download" aria-hidden="true" %} Download**.
+1. Under "Recent reports", next to the report you want to download, click **{% octicon "download" aria-hidden="true" aria-label="download" %} Download**.
{% endif %}
diff --git a/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-invitations-to-organizations-within-your-enterprise.md b/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-invitations-to-organizations-within-your-enterprise.md
index 1305c3baa424..27afc3591415 100644
--- a/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-invitations-to-organizations-within-your-enterprise.md
+++ b/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-invitations-to-organizations-within-your-enterprise.md
@@ -26,7 +26,7 @@ Invitations expire after 7 days. You can retry or cancel expired invitations, ei
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.people-tab %}
-1. Under "{% octicon "person" aria-hidden="true" %} People", click **Failed invitations**.
+1. Under "{% octicon "person" aria-hidden="true" aria-label="person" %} People", click **Failed invitations**.
1. Optionally, retry or cancel a single invitation.
* To the right of the invitation you want to cancel or retry, select the {% octicon "kebab-horizontal" aria-label="Show actions" %} dropdown menu and click **Retry invitation** or **Cancel invitation**.
diff --git a/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 4768ea3e5621..e5b31a7757e3 100644
--- a/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -181,7 +181,7 @@ You can view a list of all dormant users {% ifversion ghes %} who have not been
{% data reusables.enterprise-accounts.access-enterprise %}
1. Under "Organizations", in the search bar, begin typing the organization's name until it appears in the search results.
1. Select the name of the organization.
-1. Above the organization name, select **{% octicon "person" aria-hidden="true" %} People**.
+1. Above the organization name, select **{% octicon "person" aria-hidden="true" aria-label="person" %} People**.
1. Above the list of members, select **Type**, then select the type of members you want to view.
@@ -219,7 +219,7 @@ You can view a list of members in your enterprise who don't have an email addres
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.verified-domains-tab %}
-1. Under "Notification preferences", select the **{% octicon "eye" aria-hidden="true" %} View enterprise members without an approved or verified domain email** link.
+1. Under "Notification preferences", select the **{% octicon "eye" aria-hidden="true" aria-label="eye" %} View enterprise members without an approved or verified domain email** link.
## Viewing whether members in your enterprise have 2FA enabled
diff --git a/content/admin/managing-code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/content/admin/managing-code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
index 88c002d65887..6f0c535e0a44 100644
--- a/content/admin/managing-code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
+++ b/content/admin/managing-code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
@@ -21,5 +21,5 @@ You can manually sync vulnerability data from {% data variables.product.prodname
Before you can view vulnerability data, you must enable {% data variables.product.prodname_dependabot_alerts %}. For more information, see [AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).
{% data reusables.enterprise_site_admin_settings.access-settings %}
-1. In the left sidebar, under **{% octicon "rocket" aria-hidden="true" %} Site admin**, click **Vulnerabilities**.
+1. In the left sidebar, under **{% octicon "rocket" aria-hidden="true" aria-label="rocket" %} Site admin**, click **Vulnerabilities**.
1. To sync vulnerability data, click **Sync Vulnerabilities Now**.
diff --git a/content/admin/managing-code-security/securing-your-enterprise/applying-a-custom-security-configuration-to-your-enterprise.md b/content/admin/managing-code-security/securing-your-enterprise/applying-a-custom-security-configuration-to-your-enterprise.md
index 40edb5c2439d..c6ca7793cd31 100644
--- a/content/admin/managing-code-security/securing-your-enterprise/applying-a-custom-security-configuration-to-your-enterprise.md
+++ b/content/admin/managing-code-security/securing-your-enterprise/applying-a-custom-security-configuration-to-your-enterprise.md
@@ -22,7 +22,7 @@ After you create a {% data variables.product.prodname_custom_security_configurat
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.advanced-security-tab %}
-1. To the right of the configuration you want to apply, select the **Apply to** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **All repositories** or **All repositories without configurations**.
+1. To the right of the configuration you want to apply, select the **Apply to** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **All repositories** or **All repositories without configurations**.
{% data reusables.security-configurations.apply-configuration-by-default %}
{% data reusables.security-configurations.apply-configuration %}
diff --git a/content/admin/managing-code-security/securing-your-enterprise/applying-the-github-recommended-security-configuration-to-your-enterprise.md b/content/admin/managing-code-security/securing-your-enterprise/applying-the-github-recommended-security-configuration-to-your-enterprise.md
index a2b4eedc05eb..1c2399e4aab4 100644
--- a/content/admin/managing-code-security/securing-your-enterprise/applying-the-github-recommended-security-configuration-to-your-enterprise.md
+++ b/content/admin/managing-code-security/securing-your-enterprise/applying-the-github-recommended-security-configuration-to-your-enterprise.md
@@ -24,7 +24,7 @@ The {% data variables.product.prodname_github_security_configuration %} includes
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.advanced-security-tab %}
-1. In the "{% data variables.product.github %} recommended" row of the configurations table for your enterprise, select the **Apply to** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **All repositories** or **All repositories without configurations**.
+1. In the "{% data variables.product.github %} recommended" row of the configurations table for your enterprise, select the **Apply to** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **All repositories** or **All repositories without configurations**.
{% data reusables.security-configurations.apply-configuration-by-default %}
{% data reusables.security-configurations.apply-configuration %}
diff --git a/content/admin/managing-code-security/securing-your-enterprise/configuring-additional-secret-scanning-settings-for-your-enterprise.md b/content/admin/managing-code-security/securing-your-enterprise/configuring-additional-secret-scanning-settings-for-your-enterprise.md
index c88f0d6c3fa5..414a529f6a7c 100644
--- a/content/admin/managing-code-security/securing-your-enterprise/configuring-additional-secret-scanning-settings-for-your-enterprise.md
+++ b/content/admin/managing-code-security/securing-your-enterprise/configuring-additional-secret-scanning-settings-for-your-enterprise.md
@@ -31,7 +31,7 @@ These additional settings apply only to repositories with {% data variables.prod
To provide context for developers when {% data variables.product.prodname_secret_scanning %} blocks a commit, you can display a link with more information on why the commit was blocked.
-1. Under "Additional settings", to the right of "Resource link for push protection", click **{% octicon "pencil" aria-hidden="true" %}**.
+1. Under "Additional settings", to the right of "Resource link for push protection", click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %}**.
1. In the text box, type the link to the desired resource, then click **{% octicon "check" aria-label="Save" %}**.
### Controlling features for new repositories created in a user namespace
diff --git a/content/admin/managing-code-security/securing-your-enterprise/creating-a-custom-security-configuration-for-your-enterprise.md b/content/admin/managing-code-security/securing-your-enterprise/creating-a-custom-security-configuration-for-your-enterprise.md
index 1a01399f8a8f..5d849faa36d8 100644
--- a/content/admin/managing-code-security/securing-your-enterprise/creating-a-custom-security-configuration-for-your-enterprise.md
+++ b/content/admin/managing-code-security/securing-your-enterprise/creating-a-custom-security-configuration-for-your-enterprise.md
@@ -71,7 +71,7 @@ When creating a security configuration, keep in mind that:
* **Security updates**. To learn about security updates, see [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates).{% ifversion fpt or ghec %}
1. For "Private vulnerability reporting", choose whether you want to enable, disable, or keep the existing settings. To learn about private vulnerability reporting, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository).{% endif %}
1. Optionally, in the "Policy" section, you can use additional options to control how the configuration is applied:
- * **Use as default for newly created repositories**. Select the **None** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Public**, **Private and internal**, or **All repositories**.
+ * **Use as default for newly created repositories**. Select the **None** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Public**, **Private and internal**, or **All repositories**.
{% data reusables.security-configurations.default-configuration-exception-repo-transfers %}
* **Enforce configuration**. Block repository owners from changing features that are enabled or disabled by the configuration (features that are not set aren't enforced). Select **Enforce** from the dropdown menu.
@@ -109,7 +109,7 @@ When creating a security configuration, keep in mind that:
* **Security updates**. To learn about security updates, see [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates).{% ifversion fpt or ghec %}
1. For "Private vulnerability reporting", choose whether you want to enable, disable, or keep the existing settings. To learn about private vulnerability reporting, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository).{% endif %}
1. Optionally, in the "Policy" section, you can use additional options to control how the configuration is applied:
- * **Use as default for newly created repositories**. Select the **None** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Public**, **Private and internal**, or **All repositories**.
+ * **Use as default for newly created repositories**. Select the **None** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Public**, **Private and internal**, or **All repositories**.
{% data reusables.security-configurations.default-configuration-exception-repo-transfers %}
* **Enforce configuration**. Block repository owners from changing features that are enabled or disabled by the configuration (features that are not set aren't enforced). Select **Enforce** from the dropdown menu.
@@ -141,7 +141,7 @@ When creating a security configuration, keep in mind that:
* **Alerts**. To learn about {% data variables.secret-scanning.alerts %}, see [AUTOTITLE](/code-security/secret-scanning/introduction/about-secret-scanning).{% ifversion org-npp-enablement-security-configurations %}
* **Non-provider patterns**. To learn more about scanning for non-provider patterns, see [AUTOTITLE](/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#non-provider-patterns) and [AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/viewing-alerts).{% endif %}
* **Push protection**. To learn about push protection, see [AUTOTITLE](/code-security/secret-scanning/introduction/about-push-protection).
-1. Optionally, in the "Policy" section, you can choose to automatically apply the {% data variables.product.prodname_security_configuration %} to newly created repositories depending on their visibility. Select the **None** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Public**, or **Private and internal**, or **All repositories**.
+1. Optionally, in the "Policy" section, you can choose to automatically apply the {% data variables.product.prodname_security_configuration %} to newly created repositories depending on their visibility. Select the **None** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Public**, or **Private and internal**, or **All repositories**.
1. Optionally, in the "Policy" section, you can enforce the configuration and block repository owners from changing features that are enabled or disabled by the configuration (features that are not set aren't enforced). Next to "Enforce configuration", select **Enforce** from the dropdown menu.
diff --git a/content/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/content/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
index dca5231dc1a8..4d3a3ccd0ffc 100644
--- a/content/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
+++ b/content/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
@@ -89,7 +89,7 @@ You can create a runner group to manage access to the runner that you added to y
1. Click the "Runners" tab.
1. In the list of runners, click the runner that you deployed in the previous section.
1. Click **Edit**.
-1. Click **Runner groups {% octicon "gear" aria-hidden="true" %}**.
+1. Click **Runner groups {% octicon "gear" aria-hidden="true" aria-label="gear" %}**.
1. In the list of runner groups, click the name of the group that you previously created.
1. Click **Save** to move the runner to the group.
diff --git a/content/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/content/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
index e9f53b15313b..efd324eb03df 100644
--- a/content/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/content/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
@@ -31,7 +31,7 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can
1. From an enterprise owner account on {% data variables.product.prodname_ghe_server %}, navigate to the repository you want to delete from the _actions_ organization (in this example `checkout`).
1. By default, site administrators are not owners of the bundled _actions_ organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="Site admin" %} in the upper-right corner of any page in that repository.
-1. Click **{% octicon "shield-lock" aria-hidden="true" %} Security** to see an overview of the security for the repository.
+1. Click **{% octicon "shield-lock" aria-hidden="true" aria-label="shield-lock" %} Security** to see an overview of the security for the repository.
1. Under "Privileged access", click **Unlock**.
diff --git a/content/admin/managing-your-enterprise-account/creating-an-enterprise-account.md b/content/admin/managing-your-enterprise-account/creating-an-enterprise-account.md
index da83171816eb..4c27569ae36e 100644
--- a/content/admin/managing-your-enterprise-account/creating-an-enterprise-account.md
+++ b/content/admin/managing-your-enterprise-account/creating-an-enterprise-account.md
@@ -54,7 +54,7 @@ The following changes also apply to single organizations that are automatically
* **Enterprise account name:** During the upgrade, the new enterprise account name will match your organization name or be as close as possible if taken. You can rename it after the upgrade.
* **SAML SSO:** Existing SAML SSO will stay at the organization level after being added to the new enterprise account. You can configure SSO at the enterprise level post-upgrade, which will override the organization level. Existing PATs and SAML-authorized tokens will remain unchanged.
* **Policies:** The new enterprise account starts with no policies, so existing organization policies won't be overridden.
-* **Spending limits:** Existing organization spending limits transfer to the new enterprise account. Post-upgrade, billing is handled at the enterprise level. To adjust spending limits, at the top of the page, click {% octicon "credit-card" aria-hidden="true" %} **Billing & Licensing**.
+* **Spending limits:** Existing organization spending limits transfer to the new enterprise account. Post-upgrade, billing is handled at the enterprise level. To adjust spending limits, at the top of the page, click {% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} **Billing & Licensing**.
* **Coupons:** Existing coupons will carry over to the new enterprise account with no interruptions.
* **Workflow permissions:** The new enterprise account will inherit your organization's workflow permissions. If the organization has a permissive setting ("Read and write"), the enterprise account will also default to permissive. Otherwise, it defaults to restrictive ("Read repository contents and packages"). For workflows with the id-token permission, the default changes to read-only due to a February 2023 update. Add an explicit permissions block in these workflows to grant the required permissions.
diff --git a/content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md b/content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md
index 86f0be6a95fd..4e0edceda444 100644
--- a/content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md
+++ b/content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md
@@ -37,7 +37,7 @@ You must remove, transfer, or delete all organizations in the enterprise before
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
1. If you are not trialing {% data variables.product.prodname_ghe_cloud %}, delete your enterprise account:
- 1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Profile**.
+ 1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Profile**.
1. In the "Danger Zone" section, click **Delete this enterprise**.
1. In the text box, type the enterprise slug to confirm the deletion, then click **Delete this enterprise**.
1. If you are trialing {% data variables.product.prodname_ghe_cloud %}, cancel your trial, or delete the expired trial:
diff --git a/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
index e2eb7723191a..a804ec1c999f 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
@@ -24,7 +24,7 @@ To learn more about {% data variables.product.prodname_github_connect %}, see [A
{% data reusables.enterprise-accounts.access-enterprise %}
-1. {% ifversion horizontal-nav %}At the top of the page, in the enterprise account sidebar, click {% octicon "plug" aria-hidden="true" %} **GitHub Connect**.{% else %}On the left side of the page, in the enterprise account sidebar, click {% octicon "plug" aria-hidden="true" %} **GitHub Connect**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, in the enterprise account sidebar, click {% octicon "plug" aria-hidden="true" aria-label="plug" %} **GitHub Connect**.{% else %}On the left side of the page, in the enterprise account sidebar, click {% octicon "plug" aria-hidden="true" aria-label="plug" %} **GitHub Connect**.{% endif %}
{% data reusables.server-statistics.csv-download %}
diff --git a/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/activity-dashboard.md b/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/activity-dashboard.md
index efdb7803ac9e..6c843d56cc46 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/activity-dashboard.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/activity-dashboard.md
@@ -28,10 +28,10 @@ The Activity dashboard provides weekly, monthly, and yearly graphs of the number
## Accessing the Activity dashboard
-1. In the top-left corner of any page, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "telescope" aria-hidden="true" %} Explore**.
+1. In the top-left corner of any page, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "telescope" aria-hidden="true" aria-label="telescope" %} Explore**.
-1. In the upper-right corner of the page, click **{% octicon "pulse" aria-hidden="true" %} Activity**.
+1. In the upper-right corner of the page, click **{% octicon "pulse" aria-hidden="true" aria-label="pulse" %} Activity**.
1. To view activity over different periods, click **This week**, **This month**, or **This year**.
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
index e880b819ec39..5bad010b9a3b 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
@@ -32,7 +32,7 @@ As an alternative to exporting log events, you can use the API to retrieve audit
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.audit-log-tab %}
1. Optionally, to only export filtered results, search by one or more supported qualifiers or log filters.
-1. Select the **{% octicon "download" aria-hidden="true" %} Export** dropdown menu, and click a file format.
+1. Select the **{% octicon "download" aria-hidden="true" aria-label="download" %} Export** dropdown menu, and click a file format.
## Exporting Git events data
@@ -41,8 +41,8 @@ You can also export Git events data by date range. The data is exported as a com
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.audit-log-tab %}
-1. Select the **{% octicon "download" aria-hidden="true" %} Export Git Events** dropdown menu and choose a date range to export log events for.
-1. Click **{% octicon "file-zip" aria-hidden="true" %} Download Results**.
+1. Select the **{% octicon "download" aria-hidden="true" aria-label="download" %} Export Git Events** dropdown menu and choose a date range to export log events for.
+1. Click **{% octicon "file-zip" aria-hidden="true" aria-label="file-zip" %} Download Results**.
1. To extract the JSON data, uncompress the file using an archive utility client or command. For example:
```shell
diff --git a/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
index 1f2768a80aaf..4e45b25320ef 100644
--- a/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
+++ b/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
@@ -22,7 +22,7 @@ You can access {% data variables.product.company_short %}'s compliance reports i
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
-1. Under "Resources", to the right of the report you want to access, click **{% octicon "download" aria-hidden="true" %} Download** or **{% octicon "link-external" aria-hidden="true" %} View**.
+1. Under "Resources", to the right of the report you want to access, click **{% octicon "download" aria-hidden="true" aria-label="download" %} Download** or **{% octicon "link-external" aria-hidden="true" aria-label="link-external" %} View**.
{% data reusables.security.compliance-report-screenshot %}
diff --git a/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md b/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md
index bf78286c1269..ca88446a572f 100644
--- a/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -18,7 +18,7 @@ shortTitle: Enterprise Cloud trial
To set up a trial, you must be signed in to a personal account. If you don't have a personal account, see [AUTOTITLE](/free-pro-team@latest/get-started/start-your-journey/creating-an-account-on-github).
-Set up a trial of {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 %}
+Set up a trial of {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 aria-label="link-external" %}
{% data reusables.enterprise.enterprise-types %}
@@ -111,7 +111,7 @@ You can cancel a trial at any time. Once the trial has expired, you can delete t
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Profile**.
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Profile**.
1. At the bottom of the page, in the "Danger zone" section, click **Cancel trial** or **Delete trial**.
## Further reading
diff --git a/content/apps/using-github-apps/reviewing-and-modifying-installed-github-apps.md b/content/apps/using-github-apps/reviewing-and-modifying-installed-github-apps.md
index 40c3929e1f08..c802382ff6db 100644
--- a/content/apps/using-github-apps/reviewing-and-modifying-installed-github-apps.md
+++ b/content/apps/using-github-apps/reviewing-and-modifying-installed-github-apps.md
@@ -38,7 +38,7 @@ In addition to reviewing {% data variables.product.prodname_github_apps %} that
> In the following steps, you will be taken to the account settings for the organization or personal account where the {% data variables.product.prodname_github_app %} is installed. The settings will affect all repositories where the app is installed under that account, not just the repository where you navigated from.
1. Navigate to the main page of the organization or repository.
- 1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
+ 1. Click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. Under "Integrations," click **GitHub Apps**. A list of the {% data variables.product.prodname_github_apps %} that have been granted access to your repository will be displayed.
1. Next to the {% data variables.product.prodname_github_app %} you want to review or modify, click **Configure**.
diff --git a/content/authentication/authenticating-with-a-passkey/signing-in-with-a-passkey.md b/content/authentication/authenticating-with-a-passkey/signing-in-with-a-passkey.md
index db9faf82e764..aad9667c813b 100644
--- a/content/authentication/authenticating-with-a-passkey/signing-in-with-a-passkey.md
+++ b/content/authentication/authenticating-with-a-passkey/signing-in-with-a-passkey.md
@@ -21,13 +21,13 @@ Some authenticators allow passkeys to be used with nearby devices. For example,
## Signing in with a passkey linked to your primary device
1. Navigate to the login page for {% data variables.product.prodname_dotcom %} at {% ifversion fpt or ghec %}[https://github.com/login?passkey=true](https://github.com/login?passkey=true){% else %}`https://HOSTNAME/login?passkey=true`{% endif %}.
-1. Click **{% octicon "passkey-fill" aria-hidden="true" %} Sign in with a passkey**.
+1. Click **{% octicon "passkey-fill" aria-hidden="true" aria-label="passkey-fill" %} Sign in with a passkey**.
1. Follow the prompts on your browser or platform to select a passkey that is accessible from the device you are using, and complete the authentication process. For example, when prompted, you might touch a fingerprint sensor or enter your PIN.
## Signing in with a passkey using a nearby device
1. Navigate to the login page for {% data variables.product.prodname_dotcom %} at {% ifversion fpt or ghec %}[https://github.com/login?passkey=true](https://github.com/login?passkey=true){% else %}`https://HOSTNAME/login?passkey=true`{% endif %}.
-1. Click **{% octicon "passkey-fill" aria-hidden="true" %} Sign in with a passkey**.
+1. Click **{% octicon "passkey-fill" aria-hidden="true" aria-label="passkey-fill" %} Sign in with a passkey**.
1. Follow the prompts on your browser or platform to select a passkey that is accessible as a nearby device (such as a phone or a tablet).
1. Continue to follow the prompts to start the authentication process. For example, you might choose to scan a QR code, or trigger a push notification to the nearby device.
1. On your nearby device, follow the prompts to complete the authentication process. For example, if you are using an iPhone, you might perform Face ID or enter your passcode.
diff --git a/content/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens.md b/content/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens.md
index fb0661d2b96f..b4e3ab6ab99a 100644
--- a/content/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens.md
+++ b/content/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens.md
@@ -101,7 +101,7 @@ For more information about best practices, see [AUTOTITLE](/rest/overview/keepin
{% ifversion fpt or ghec %}1. [Verify your email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.developer_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**.
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**.
1. Click **Generate new token**.
1. Under **Token name**, enter a name for the token.
1. Under **Expiration**, select an expiration for the token. Infinite lifetimes are allowed but may be blocked by a maximum lifetime policy set by your organization or enterprise owner. For more information, See [Enforcing a maximum lifetime policy for {% data variables.product.pat_generic_plural %}](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization#enforcing-a-maximum-lifetime-policy-for-personal-access-tokens).
@@ -129,7 +129,7 @@ If you selected an organization as the resource owner and the organization requi
{% ifversion fpt or ghec %}1. [Verify your email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.developer_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.
1. Select **Generate new token**, then click **Generate new token (classic)**.
1. In the "Note" field, give your token a descriptive name.
1. To give your token an expiration, select **Expiration**, then choose a default option or click **Custom** to enter a date.
@@ -146,7 +146,7 @@ You should delete a {% data variables.product.pat_generic %} if it is no longer
{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.developer_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click either **Fine-grained tokens** or **Tokens (classic)**, depending on which type of {% data variables.product.pat_generic %} you'd like to delete.
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click either **Fine-grained tokens** or **Tokens (classic)**, depending on which type of {% data variables.product.pat_generic %} you'd like to delete.
1. To the right of the {% data variables.product.pat_generic %} you want to delete, click **Delete**.
{% ifversion ghec or fpt %}> [!NOTE] If you find a leaked {% data variables.product.pat_generic %} belonging to someone else, you can submit a revocation request through the REST API. See [AUTOTITLE](/code-security/getting-started/best-practices-for-preventing-data-leaks-in-your-organization#mitigate-data-leaks).
diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index 71be381094e5..570db9f702bd 100644
--- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -16,7 +16,7 @@ shortTitle: Deploy keys
---
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Security" section of the sidebar, click **{% octicon "key" aria-hidden="true" %} Deploy keys**.
+1. In the "Security" section of the sidebar, click **{% octicon "key" aria-hidden="true" aria-label="key" %} Deploy keys**.
1. On the "Deploy keys" page, take note of the deploy keys associated with your account. For those that you don't recognize, or that are out of date, click **Delete**. If there are valid deploy keys you'd like to keep, click **Approve**.
For more information, see [AUTOTITLE](/authentication/connecting-to-github-with-ssh/managing-deploy-keys).
diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index ce6017cb43a3..54201e0823eb 100644
--- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -20,7 +20,7 @@ shortTitle: Review security log
The security log lists all actions performed within the last 90 days.
{% data reusables.user-settings.access_settings %}
-1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-hidden="true" %} Security log**.
+1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-hidden="true" aria-label="log" %} Security log**.
## Searching your security log
diff --git a/content/authentication/keeping-your-account-and-data-secure/switching-between-accounts.md b/content/authentication/keeping-your-account-and-data-secure/switching-between-accounts.md
index d255cc665e94..0edb692f9fda 100644
--- a/content/authentication/keeping-your-account-and-data-secure/switching-between-accounts.md
+++ b/content/authentication/keeping-your-account-and-data-secure/switching-between-accounts.md
@@ -23,8 +23,8 @@ Your SSO sessions will persist when you switch away from an account and return.
When you add a new account to the account switcher, both the account you are currently signed in to and the account you have added will become available in the account switcher. You will be signed in to the new account immediately.
1. In the upper-right corner of any page, click your profile photo to open the menu.
-1. If you have previously added an account to the account switcher, click **{% octicon "arrow-switch" aria-hidden="true" %} Switch account** to open the menu.
-1. In the menu, click **{% octicon "person-add" aria-hidden="true" %} Add account**.
+1. If you have previously added an account to the account switcher, click **{% octicon "arrow-switch" aria-hidden="true" aria-label="arrow-switch" %} Switch account** to open the menu.
+1. In the menu, click **{% octicon "person-add" aria-hidden="true" aria-label="person-add" %} Add account**.
1. Sign in to the account you want to add to the account switcher.
## Switching between accounts
@@ -32,10 +32,10 @@ When you add a new account to the account switcher, both the account you are cur
When you have added accounts to the account switcher, you can quickly change between them without always needing to reauthenticate.
> [!NOTE]
-> The "{% octicon "arrow-switch" aria-hidden="true" %} Switch account" option will not be available if all sessions have expired. You can instead click on **{% octicon "arrow-switch" aria-hidden="true" %} See all accounts** in the menu to reauthenticate.
+> The "{% octicon "arrow-switch" aria-hidden="true" aria-label="arrow-switch" %} Switch account" option will not be available if all sessions have expired. You can instead click on **{% octicon "arrow-switch" aria-hidden="true" aria-label="arrow-switch" %} See all accounts** in the menu to reauthenticate.
1. In the upper-right corner of any page, click your profile photo to open the menu.
-1. In the menu, click **{% octicon "arrow-switch" aria-hidden="true" %} Switch account**.
+1. In the menu, click **{% octicon "arrow-switch" aria-hidden="true" aria-label="arrow-switch" %} Switch account**.
1. In the submenu, click on the account that you want to switch to.
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
index 98ee093212e8..40b063e68632 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
@@ -119,10 +119,10 @@ You can download a CSV report of license usage through the {% data variables.pro
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar click **{% octicon "credit-card" aria-hidden="true" %} Billing & licensing** and then **Usage**.
+1. In the "Access" section of the sidebar click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & licensing** and then **Usage**.
1. Filter the metered usage to show `product:ghas` and choose "Group: SKU".
1. Optionally, use the "Time Frame" field to set the period to report on.
-1. Click **{% octicon "download" aria-hidden="true" %}Get usage report** to download the report.
+1. Click **{% octicon "download" aria-hidden="true" aria-label="download" %}Get usage report** to download the report.
{% endif %}
@@ -131,22 +131,22 @@ You can download a CSV report of license usage through the {% data variables.pro
#### For an enterprise
{% data reusables.enterprise-accounts.access-enterprise %}
-1. Click **{% octicon "credit-card" aria-hidden="true" %} Billing & licensing** to display an overview.
+1. Click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & licensing** to display an overview.
**License consumption:**
- 1. Click **{% octicon "law" aria-hidden="true" %} Licensing**.
- 1. Under "{% data variables.product.prodname_GHAS %}," click the **Download report** dropdown and then click either **{% octicon "download" aria-hidden="true" %} {% data variables.product.prodname_code_security %}** or **{% octicon "download" aria-hidden="true" %} {% data variables.product.prodname_secret_protection %}**.
+ 1. Click **{% octicon "law" aria-hidden="true" aria-label="law" %} Licensing**.
+ 1. Under "{% data variables.product.prodname_GHAS %}," click the **Download report** dropdown and then click either **{% octicon "download" aria-hidden="true" aria-label="download" %} {% data variables.product.prodname_code_security %}** or **{% octicon "download" aria-hidden="true" aria-label="download" %} {% data variables.product.prodname_secret_protection %}**.
**Metered usage:**
1. Scroll to the tabbed usage information at the bottom of the "Overview" page and click **{% data variables.product.prodname_AS %}** to show usage.
1. In the summary box, click "View details" to show metered usage for {% data variables.product.prodname_AS %} grouped by SKU.
- 1. Select a time frame and click **{% octicon "download" aria-hidden="true" %}Get usage report** to download a detailed report.
+ 1. Select a time frame and click **{% octicon "download" aria-hidden="true" aria-label="download" %}Get usage report** to download a detailed report.
{% elsif ghes %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.license-tab %}
-1. Under "{% data variables.product.prodname_GHAS %}," click **{% octicon "download" aria-hidden="true" %} CSV report**.
+1. Under "{% data variables.product.prodname_GHAS %}," click **{% octicon "download" aria-hidden="true" aria-label="download" %} CSV report**.
diff --git a/content/billing/managing-billing-for-your-products/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md b/content/billing/managing-billing-for-your-products/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
index 7b6184085486..d65de3ce2c26 100644
--- a/content/billing/managing-billing-for-your-products/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
+++ b/content/billing/managing-billing-for-your-products/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
@@ -42,6 +42,6 @@ Organizations that pay for {% data variables.product.prodname_sponsors %} by inv
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
1. Under "{% data variables.product.prodname_sponsors %}", in the yellow banner with the start date, click **Undo**.
1. Review the alert about undoing the activation of the sponsorship, then click **OK**.
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 939b017e6b2b..0f0ce6411ca1 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,7 +92,7 @@ To connect your Azure subscription, you must have owner permissions to the Azure
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
1. Under "Billing Management", to the right of "Metered billing via Azure", click **Add Azure Subscription**.
1. To sign in to your Microsoft account, follow the prompts.
1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**.
@@ -135,7 +135,7 @@ After you disconnect your Azure subscription from your organization account, you
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
1. Under "Billing Management", then under "Metered billing via Azure", to the right of the subscription ID you want to disconnect, click **{% octicon "trash" aria-label="The trash icon" %}**.
1. Review the prompt, then click **Remove**.
diff --git a/content/billing/managing-the-plan-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/content/billing/managing-the-plan-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 2bd3704b61d7..994e6011cc78 100644
--- a/content/billing/managing-the-plan-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/content/billing/managing-the-plan-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -54,7 +54,7 @@ You can view the subscription and usage for your enterprise and download a file
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.license-tab %}
1. Under "User licenses", view your total licenses, number of consumed licenses, and your subscription expiration date.
-1. Optionally, to view details for license usage or download a {% ifversion ghec %}CSV{% elsif ghes %}JSON{% endif %} file with license details{% ifversion ghec %}, to the right of "User Licenses"{% endif %}, click **View {% ifversion ghec %}details{% elsif ghes %}users{% endif %}** or {% ifversion ghec %}**{% octicon "download" aria-hidden="true" %} CSV report**{% elsif ghes %}**Export license usage**{% endif %}.
+1. Optionally, to view details for license usage or download a {% ifversion ghec %}CSV{% elsif ghes %}JSON{% endif %} file with license details{% ifversion ghec %}, to the right of "User Licenses"{% endif %}, click **View {% ifversion ghec %}details{% elsif ghes %}users{% endif %}** or {% ifversion ghec %}**{% octicon "download" aria-hidden="true" aria-label="download" %} CSV report**{% elsif ghes %}**Export license usage**{% endif %}.
{%- ifversion ghec %}
1. Optionally, to view usage details for other features, in the left sidebar, click **Billing**.
{% endif %}
diff --git a/content/billing/managing-your-billing/about-billing-for-your-enterprise.md b/content/billing/managing-your-billing/about-billing-for-your-enterprise.md
index bdf26d9c3e7a..640bd142a918 100644
--- a/content/billing/managing-your-billing/about-billing-for-your-enterprise.md
+++ b/content/billing/managing-your-billing/about-billing-for-your-enterprise.md
@@ -59,7 +59,7 @@ Administrators for your enterprise account on {% data variables.product.prodname
To access the billing platform for your enterprise:
{% data reusables.enterprise-accounts.access-enterprise %}
-1. {% ifversion horizontal-nav %}At the top of the page,{% else %}In the enterprise account sidebar,{% endif %} click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. {% ifversion horizontal-nav %}At the top of the page,{% else %}In the enterprise account sidebar,{% endif %} click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
## Further reading
diff --git a/content/billing/managing-your-billing/about-billing-on-github.md b/content/billing/managing-your-billing/about-billing-on-github.md
index 9927ac0abfb5..dea442259cb0 100644
--- a/content/billing/managing-your-billing/about-billing-on-github.md
+++ b/content/billing/managing-your-billing/about-billing-on-github.md
@@ -139,4 +139,4 @@ If you're an organization or enterprise owner, you can switch between settings f
1. Start typing the name of the account you want to switch to, then click the name of the account.
-1. In the left sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. In the left sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
diff --git a/content/billing/managing-your-billing/about-the-new-billing-platform.md b/content/billing/managing-your-billing/about-the-new-billing-platform.md
index 239c80b5446a..385edfe5cfde 100644
--- a/content/billing/managing-your-billing/about-the-new-billing-platform.md
+++ b/content/billing/managing-your-billing/about-the-new-billing-platform.md
@@ -86,7 +86,7 @@ With the new billing platform, you can:
{% elsif ghec %}
{% data reusables.enterprise-accounts.access-enterprise %}
-1. {% ifversion horizontal-nav %}At the top of the page,{% else %}In the enterprise account sidebar,{% endif %} click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. {% ifversion horizontal-nav %}At the top of the page,{% else %}In the enterprise account sidebar,{% endif %} click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
{% endif %}
diff --git a/content/billing/managing-your-billing/estimating-spending.md b/content/billing/managing-your-billing/estimating-spending.md
index 52d9ee5e5174..5a25aece2b13 100644
--- a/content/billing/managing-your-billing/estimating-spending.md
+++ b/content/billing/managing-your-billing/estimating-spending.md
@@ -23,7 +23,7 @@ The new billing platform provides a high-level view of your spending trends base
## Viewing your spending for your personal account
{% data reusables.user-settings.access_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
On this page, you can view your usage in the following categories:
diff --git a/content/billing/managing-your-billing/gathering-insights-on-your-spending.md b/content/billing/managing-your-billing/gathering-insights-on-your-spending.md
index 636797ddd80e..613680a4eb40 100644
--- a/content/billing/managing-your-billing/gathering-insights-on-your-spending.md
+++ b/content/billing/managing-your-billing/gathering-insights-on-your-spending.md
@@ -28,7 +28,7 @@ The new billing platform provides you with the tools to:
You can view the usage of your personal account and download the usage data for further analysis.
{% data reusables.user-settings.access_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
1. Click **Usage**.
1. To search or filter the graph, click the search bar. Then click the filter you want to use.
1. To further filter the graph, use the dropdown menus.
@@ -112,7 +112,7 @@ You can also view your active {% data variables.product.prodname_enterprise %} i
{% endif %}
1. Click **Licensing**.
-1. To download a CSV report of the license usage, click {% octicon "kebab-horizontal" aria-label="Licensing dropdown" %} to the right of the usage you want to download, then click **{% octicon "download" aria-hidden="true" %} CSV report**.
+1. To download a CSV report of the license usage, click {% octicon "kebab-horizontal" aria-label="Licensing dropdown" %} to the right of the usage you want to download, then click **{% octicon "download" aria-hidden="true" aria-label="download" %} CSV report**.
## Further reading
diff --git a/content/billing/managing-your-billing/managing-your-payment-and-billing-information.md b/content/billing/managing-your-billing/managing-your-payment-and-billing-information.md
index a4c2aa0eb10d..371532f164af 100644
--- a/content/billing/managing-your-billing/managing-your-payment-and-billing-information.md
+++ b/content/billing/managing-your-billing/managing-your-payment-and-billing-information.md
@@ -80,8 +80,8 @@ You can view and edit your billing information and update your payment method.
1. In the upper-right corner of any page on {% data variables.product.prodname_dotcom %}, select your profile photo.
- * For **personal accounts**, click **Settings**, then in the **Access** section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
- * For **organizations**, click **Your organizations**, then next to the organization, click **Settings**. In the organization sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+ * For **personal accounts**, click **Settings**, then in the **Access** section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
+ * For **organizations**, click **Your organizations**, then next to the organization, click **Settings**. In the organization sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
{% elsif ghec %}
diff --git a/content/billing/managing-your-billing/preventing-overspending.md b/content/billing/managing-your-billing/preventing-overspending.md
index ddf884eb6255..ea6980fe77de 100644
--- a/content/billing/managing-your-billing/preventing-overspending.md
+++ b/content/billing/managing-your-billing/preventing-overspending.md
@@ -35,7 +35,7 @@ For license-based products such as {% data variables.product.prodname_copilot %}
You can set spending limits and receive alerts when your usage reaches 75%, 90%, or 100% of your defined budget. Budgets can be scoped at the repository or product level, depending on the product.
{% data reusables.user-settings.access_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
1. Click **Budgets and alerts**.
1. To create a new budget, click **New budget**.
1. Under "Budget Type" select either **Product-level budget** or **SKU-level budget**.
@@ -149,5 +149,5 @@ You can edit or delete a budget at any time, but you cannot change the budget sc
{% endif %}
1. Click **Budgets and alerts**.
-1. To edit a budget, in the list of budgets, click {% octicon "kebab-horizontal" aria-label="View actions" %} next to the budget you want to edit, and click **{% octicon "pencil" aria-hidden="true" %} Edit** or **{% octicon "trash" aria-hidden="true" %} Delete**.
+1. To edit a budget, in the list of budgets, click {% octicon "kebab-horizontal" aria-label="View actions" %} next to the budget you want to edit, and click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit** or **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete**.
1. Follow the prompts.
diff --git a/content/billing/managing-your-billing/roles-for-the-new-billing-platform.md b/content/billing/managing-your-billing/roles-for-the-new-billing-platform.md
index 0369b8f8c12d..f1a005a79d12 100644
--- a/content/billing/managing-your-billing/roles-for-the-new-billing-platform.md
+++ b/content/billing/managing-your-billing/roles-for-the-new-billing-platform.md
@@ -60,11 +60,11 @@ You can:
The invited person will receive an invitation email asking them to become a billing manager for your {% ifversion ghec %}enterprise{% endif %}{% ifversion fpt %} organization{% endif %}. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the {% ifversion ghec %}enterprise{% endif %}{% ifversion fpt %} organization{% endif %} as a billing manager. If they don't already have a {% data variables.product.prodname_dotcom %} account, they will be directed to sign up for one, and they will be automatically added to the {% ifversion ghec %}enterprise{% endif %}{% ifversion fpt %} organization{% endif %} as a billing manager after they create an account.
{% data reusables.user-settings.access_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organizations**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Organizations**.
{% data reusables.profile.org_settings %}
-1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
1. Click the link in the text box, **Enterprise account billing settings**, which will direct you to your organizations billing settings page.
-1. {% ifversion horizontal-nav %}At the top of the page, click {% octicon "person" aria-hidden="true" %} **People**{% else %}On the left side of the page, in the enterprise account sidebar, click {% octicon "person" aria-hidden="true" %} **People**{% endif %}.
+1. {% ifversion horizontal-nav %}At the top of the page, click {% octicon "person" aria-hidden="true" aria-label="person" %} **People**{% else %}On the left side of the page, in the enterprise account sidebar, click {% octicon "person" aria-hidden="true" aria-label="person" %} **People**{% endif %}.
1. Under "People", click **Administrators**.
1. Above the list of administrators, click **Invite admin**.
1. Type the username, full name, or email address of the person you want to invite, then select the appropriate person from the results.
diff --git a/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md b/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
index 31cd6a64aefb..fdc147c7e817 100644
--- a/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
+++ b/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
@@ -34,6 +34,6 @@ If you have any questions about downloading your license, contact {% data variab
{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.license-tab %}
-1. Under "Enterprise Server licenses", next to the license you want to download, click **{% octicon "download" aria-hidden="true" %} Download**.
+1. Under "Enterprise Server licenses", next to the license you want to download, click **{% octicon "download" aria-hidden="true" aria-label="download" %} Download**.
After you download your license file, you can upload the file to {% data variables.location.product_location_enterprise %} to validate your application. For more information, see {% ifversion ghec %}[AUTOTITLE](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server) in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}[AUTOTITLE](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server).{% endif %}
diff --git a/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
index 5da190bf1fd4..46d54591a97d 100644
--- a/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -40,7 +40,7 @@ After you enable {% data variables.product.prodname_github_connect %}, license d
{% data reusables.enterprise-accounts.access-enterprise-ghes %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.license-tab %}
-1. Under "License sync", click **{% octicon "sync" aria-hidden="true" %} Sync now**.
+1. Under "License sync", click **{% octicon "sync" aria-hidden="true" aria-label="sync" %} Sync now**.
## Manually uploading GitHub Enterprise Server license usage
diff --git a/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md b/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
index 1024944331b1..0a6fc1596074 100644
--- a/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
+++ b/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
@@ -53,7 +53,7 @@ You can view the license usage for your enterprise and download a file with lice
* If you purchased {% data variables.product.prodname_AS %}, you can review your total license usage. To learn about the information displayed, see [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage).
-1. To download a CSV report of the license usage, click {% octicon "kebab-horizontal" aria-label="Licensing dropdown" %} to the right of the usage you want to download, then click **{% octicon "download" aria-hidden="true" %} CSV report**.
+1. To download a CSV report of the license usage, click {% octicon "kebab-horizontal" aria-label="Licensing dropdown" %} to the right of the usage you want to download, then click **{% octicon "download" aria-hidden="true" aria-label="download" %} CSV report**.
{% elsif ghes %}
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 867f7da5a37e..b999a9491f9f 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
@@ -63,10 +63,10 @@ You can customize your {% data variables.product.prodname_codeql %} analysis by
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
-1. Scroll down to "{% data variables.product.UI_code_security_scanning %}", in the "{% data variables.product.prodname_codeql %} analysis" row select **Set up** {% octicon "triangle-down" aria-hidden="true" %}, then click **Advanced**.
+1. Scroll down to "{% data variables.product.UI_code_security_scanning %}", in the "{% data variables.product.prodname_codeql %} analysis" row select **Set up** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click **Advanced**.
> [!NOTE]
- > If you are switching from default setup to advanced setup, in the "{% data variables.product.prodname_codeql %} analysis" row, 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 %}**.
+ > If you are switching from default setup to advanced setup, in the "{% data variables.product.prodname_codeql %} analysis" row, select {% octicon "kebab-horizontal" aria-label="Menu" %}, then click **{% octicon "workflow" aria-hidden="true" aria-label="workflow" %} Switch to advanced**. In the pop-up window that appears, click **Disable {% data variables.product.prodname_codeql %}**.
{% ifversion ghas-products %}
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 44554e4edf69..bdd06a0aaac7 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
@@ -38,7 +38,7 @@ You can run {% data variables.product.prodname_code_scanning %} on {% data varia
With advanced setup for {% data variables.product.prodname_code_scanning %}, you can customize a {% data variables.product.prodname_code_scanning %} workflow for granular control over your configuration. For more information, see [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning).
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% ifversion fpt or ghec %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-hidden="true" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.code-scanning.codeql_workflow %} file.
+{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% ifversion fpt or ghec %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.code-scanning.codeql_workflow %} file.
## Editing a {% data variables.product.prodname_code_scanning %} workflow
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 ed71d8be647b..fa000d7fa160 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
@@ -154,7 +154,7 @@ You can select all of the displayed repositories, or a subset of them, and enabl
- If you're blocked from enabling {% data variables.product.prodname_code_scanning %} due to an enterprise policy, you will still be able to see the affected repository in the "Security Coverage" view and access the side panel from the **{% octicon "gear" aria-hidden="true" %} Security settings** button. However, you will see a message in the side panel indicating that you cannot enable {% data variables.product.prodname_code_scanning %} for the selected repositories. For more information about enterprise policies, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise).
+ If you're blocked from enabling {% data variables.product.prodname_code_scanning %} due to an enterprise policy, you will still be able to see the affected repository in the "Security Coverage" view and access the side panel from the **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Security settings** button. However, you will see a message in the side panel indicating that you cannot enable {% data variables.product.prodname_code_scanning %} for the selected repositories. For more information about enterprise policies, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise).
{% endif %}
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 743d88b4da91..20aa5ea1d3a7 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
@@ -70,7 +70,7 @@ Compiled languages are not automatically included in default setup configuration
{% data reusables.repositories.navigate-to-repo %}
> [!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.
+ > 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" aria-label="play" %} 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.repositories.navigate-to-code-security-and-analysis %}
@@ -91,7 +91,7 @@ Compiled languages are not automatically included in default setup configuration
> [!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**.
+1. Optionally, to customize your {% data variables.product.prodname_code_scanning %} setup, click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit**.
* To add or remove a language from the analysis performed by default setup, select or deselect that language in the "Languages" section. If you would like to analyze a {% data variables.product.prodname_codeql %}-supported compiled language with default setup, select that language here.
* To specify the {% data variables.product.prodname_codeql %} query suite you would like to use, select your preferred query suite in the "Query suites" section.
@@ -100,7 +100,7 @@ Compiled languages are not automatically included in default setup configuration
> [!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**.
+1. Optionally, to view your default setup configuration after enablement, select {% octicon "kebab-horizontal" aria-label="Menu" %}, then click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} View {% data variables.product.prodname_codeql %} configuration**.
## Assigning labels to runners
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/best-practices-for-participating-in-a-security-campaign.md b/content/code-security/code-scanning/managing-code-scanning-alerts/best-practices-for-participating-in-a-security-campaign.md
index 8eb261d2a930..f4feb16f1a0b 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/best-practices-for-participating-in-a-security-campaign.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/best-practices-for-participating-in-a-security-campaign.md
@@ -92,7 +92,7 @@ When fixing security alerts as part of a campaign, it may be helpful to group an
You can ask {% data variables.product.prodname_copilot_chat_short %} for help in understanding the vulnerability, the suggested fix, and how to test that the fix is comprehensive. To access {% data variables.product.prodname_copilot_chat_short %}, navigate to https://github.com/copilot.
-Alternatively, when viewing a specific alert, in the top right corner of the page, click the {% data variables.product.prodname_copilot_chat_short %} icon ({% octicon "copilot" aria-hidden="true" %}) to open a chat window, and ask {% data variables.product.prodname_copilot_short %} questions about the alert.
+Alternatively, when viewing a specific alert, in the top right corner of the page, click the {% data variables.product.prodname_copilot_chat_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) to open a chat window, and ask {% data variables.product.prodname_copilot_short %} questions about the alert.
For example:
@@ -114,7 +114,7 @@ To find the contact URL:
1. Open the **Security** tab for your repository.
1. On the left sidebar, click the name of the campaign you are participating in.
-1. On the campaign tracking page, to the right of the campaign manager's name, click **{% octicon "comment" aria-hidden="true" %}**.
+1. On the campaign tracking page, to the right of the campaign manager's name, click **{% octicon "comment" aria-hidden="true" aria-label="comment" %}**.
## Next steps
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/fixing-alerts-in-security-campaign.md b/content/code-security/code-scanning/managing-code-scanning-alerts/fixing-alerts-in-security-campaign.md
index ae44a3f2292d..be0e02afa957 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/fixing-alerts-in-security-campaign.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/fixing-alerts-in-security-campaign.md
@@ -32,7 +32,7 @@ This view shows the alerts in the current repository for a campaign called "SQL
If you want to see the code that triggered the security alert and the suggested fix, click on the alert name to show the alert view.
1. When you are ready to work on one or more security alerts, check that no one else is working on those alerts already. In the campaign view, git icons are displayed on alerts where a fix may already be in progress. Click an icon to display the linked work:
- * {% octicon "git-pull-request-draft" aria-hidden="Draft pull request" %} an open draft pull request may fix this alert.
+ * {% octicon "git-pull-request-draft" aria-hidden="Draft pull request" aria-label="git-pull-request-draft" %} an open draft pull request may fix this alert.
* {% octicon "git-pull-request" aria-label="Pull request" %} an open pull request may fix this alert.
* {% octicon "git-branch" aria-label="Branch" %} a branch may contain changes to fix this alert.
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 1831ca98d4b1..20d8cbe3943d 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
@@ -44,7 +44,7 @@ With a {% data variables.product.prodname_copilot_enterprise %} license, you can
{% data reusables.repositories.sidebar-security %}
{% data reusables.repositories.sidebar-code-scanning-alerts %}
1. Click the name of an alert.
-1. If {% data variables.product.prodname_copilot_autofix_short %} can suggest a fix, at the top of the page, click **{% octicon "shield-check" aria-hidden="true" %} Generate fix**.
+1. If {% data variables.product.prodname_copilot_autofix_short %} can suggest a fix, at the top of the page, click **{% octicon "shield-check" aria-hidden="true" aria-label="shield-check" %} Generate fix**.
1. Once the suggested fix has been generated, at the bottom of the page, you can click **Create PR with fix** to automatically generate a pull request with the suggested fix.
A new branch is created from the default branch, the generated fix is committed and a draft pull request is created. You can test and edit the suggested fix as you would with any other fix.
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 78c03c8a70d8..73836a2f8d26 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
@@ -145,7 +145,7 @@ Each {% data variables.product.prodname_copilot_autofix_short %} suggestion demo
{% data reusables.rai.code-scanning.copilot-workspaces-prs-autofix-note %}
-1. Optionally, if you prefer to apply the fix on a local repository or branch, select the {% octicon "copy" aria-hidden="true" %} dropdown menu on the suggestion.
+1. Optionally, if you prefer to apply the fix on a local repository or branch, select the {% octicon "copy" aria-hidden="true" aria-label="copy" %} dropdown menu on the suggestion.
* Select **View autofix patch** to display instructions for applying the suggested fix to any local repository or branch.
* Select **Copy modified line LINE_NUMBER** to copy a specific line of the suggestion.
1. Test and modify the suggested fix as needed.
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 7e3231894f16..d56aaba40e9c 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
@@ -89,13 +89,13 @@ You can download the list of rules that {% data variables.product.prodname_code_
* The SARIF identifier.
* How many alerts were found.
-To download a report, select a configuration you're interested in. Then click **{% octicon "kebab-horizontal" aria-label="Configuration menu" %}** on the top right of the page, and select **{% octicon "download" aria-hidden="true" %} Download list of rules used**.
+To download a report, select a configuration you're interested in. Then click **{% octicon "kebab-horizontal" aria-label="Configuration menu" %}** on the top right of the page, and select **{% octicon "download" aria-hidden="true" aria-label="download" %} Download list of rules used**.
### Removing configurations
You can remove stale, duplicate, or unwanted configurations for the default branch of your repository.
-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.
+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" aria-label="trash" %} Delete configuration**. Once you have read the warning about alerts, to confirm the deletion, click the **Delete** button.
> [!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).
diff --git a/content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md b/content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md
index b122a22d51cb..73faae5afe78 100644
--- a/content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md
+++ b/content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md
@@ -29,14 +29,14 @@ If you need to change any other aspects of your {% data variables.product.prodna
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
-1. In the "{% data variables.product.prodname_codeql %} analysis" row of the "{% data variables.product.UI_code_security_scanning %}" section, select {% octicon "kebab-horizontal" aria-label="Menu" %}, then click **{% octicon "gear" aria-hidden="true" %} View {% data variables.product.prodname_codeql %} configuration**.
-1. In the "{% data variables.product.prodname_codeql %} default configuration" window, click **{% octicon "pencil" aria-hidden="true" %} Edit**.
+1. In the "{% data variables.product.prodname_codeql %} analysis" row of the "{% data variables.product.UI_code_security_scanning %}" section, select {% octicon "kebab-horizontal" aria-label="Menu" %}, then click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} View {% data variables.product.prodname_codeql %} configuration**.
+1. In the "{% data variables.product.prodname_codeql %} default configuration" window, click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit**.
1. Optionally, in the "Languages" section, select or deselect languages for analysis.
1. Optionally, in the "Query suite" row of the "Scan settings" section, select a different query suite to run against your code.
{% ifversion code-scanning-default-setup-customize-labels %}
-1. Optionally, to use labeled runners, in the "Runner type" section of the "{% data variables.product.prodname_codeql %} default configuration" modal dialog, select **Standard {% data variables.product.company_short %} runner** {% octicon "triangle-down" aria-hidden="true" %} to open a dropdown menu, then select **Labeled runner**. Then, next to "Runner label", enter the label of an existing self-hosted or {% data variables.product.company_short %}-hosted runner. For more information, see [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning#assigning-labels-to-runners).
+1. Optionally, to use labeled runners, in the "Runner type" section of the "{% data variables.product.prodname_codeql %} default configuration" modal dialog, select **Standard {% data variables.product.company_short %} runner** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} to open a dropdown menu, then select **Labeled runner**. Then, next to "Runner label", enter the label of an existing self-hosted or {% data variables.product.company_short %}-hosted runner. For more information, see [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning#assigning-labels-to-runners).
{% endif %}
diff --git a/content/code-security/code-scanning/troubleshooting-code-scanning/advanced-security-must-be-enabled.md b/content/code-security/code-scanning/troubleshooting-code-scanning/advanced-security-must-be-enabled.md
index 44b2c5250d52..b2c6d1a66cba 100644
--- a/content/code-security/code-scanning/troubleshooting-code-scanning/advanced-security-must-be-enabled.md
+++ b/content/code-security/code-scanning/troubleshooting-code-scanning/advanced-security-must-be-enabled.md
@@ -37,7 +37,7 @@ If you are on a **{% data variables.product.prodname_free_team %}** or **{% data
1. On the settings page, scroll down to "{% data variables.product.prodname_code_security %}."
1. If there is an associated and active **Enable** button, {% data variables.product.prodname_GH_code_security %} is available for this repository but not yet enabled.
{% ifversion ghas-products %}
-1. If use of {% data variables.product.prodname_GH_code_security %} is blocked by a policy, "{% octicon "shield" aria-hidden="true" %} Disabled" is shown in place of the **Enable** button.
+1. If use of {% data variables.product.prodname_GH_code_security %} is blocked by a policy, "{% octicon "shield" aria-hidden="true" aria-label="shield" %} Disabled" is shown in place of the **Enable** button.
{% else %}
diff --git a/content/code-security/code-scanning/troubleshooting-code-scanning/cannot-enable-codeql-in-a-private-repository.md b/content/code-security/code-scanning/troubleshooting-code-scanning/cannot-enable-codeql-in-a-private-repository.md
index 19bfeaba3416..3341a87b57fb 100644
--- a/content/code-security/code-scanning/troubleshooting-code-scanning/cannot-enable-codeql-in-a-private-repository.md
+++ b/content/code-security/code-scanning/troubleshooting-code-scanning/cannot-enable-codeql-in-a-private-repository.md
@@ -26,7 +26,7 @@ If you are on a **{% data variables.product.prodname_free_team %}** or **{% data
1. If there is an associated and active **Enable** button, {% data variables.product.prodname_code_security %} is available for this repository but not yet enabled.
{% ifversion ghas-products %}
-1. If use of {% data variables.product.prodname_GH_code_security %} is blocked by a policy, "{% octicon "shield" aria-hidden="true" %} Disabled" is shown in place of the **Enable** button.
+1. If use of {% data variables.product.prodname_GH_code_security %} is blocked by a policy, "{% octicon "shield" aria-hidden="true" aria-label="shield" %} Disabled" is shown in place of the **Enable** button.
{% else %}
diff --git a/content/code-security/code-scanning/troubleshooting-code-scanning/enabling-default-setup-takes-too-long.md b/content/code-security/code-scanning/troubleshooting-code-scanning/enabling-default-setup-takes-too-long.md
index 0adf9bbe5802..1eba1d0b2007 100644
--- a/content/code-security/code-scanning/troubleshooting-code-scanning/enabling-default-setup-takes-too-long.md
+++ b/content/code-security/code-scanning/troubleshooting-code-scanning/enabling-default-setup-takes-too-long.md
@@ -13,4 +13,4 @@ When you enable default setup, a workflow is triggered with the automatically ge
You can check on the progress of the test run for default setup on the **Actions** tab. If the run is taking too long, try canceling the workflow run and restarting the configuration process.
-To restart your configuration, navigate to the main page of your repository, then click **{% octicon "play" aria-hidden="true" %} Actions**. Click the **{% data variables.product.prodname_codeql %}** workflow run that's in progress, then click **Cancel workflow**. Once {% octicon "stop" aria-label="cancelled" %} appears beside the workflow run name, navigate back to the **{% data variables.product.UI_advanced_security %}** settings and re-enable default setup. If default setup continues to stall, please contact {% data variables.contact.contact_support %} or try enabling advanced setup. For more information, see [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning).
+To restart your configuration, navigate to the main page of your repository, then click **{% octicon "play" aria-hidden="true" aria-label="play" %} Actions**. Click the **{% data variables.product.prodname_codeql %}** workflow run that's in progress, then click **Cancel workflow**. Once {% octicon "stop" aria-label="cancelled" %} appears beside the workflow run name, navigate back to the **{% data variables.product.UI_advanced_security %}** settings and re-enable default setup. If default setup continues to stall, please contact {% data variables.contact.contact_support %} or try enabling advanced setup. For more information, see [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning).
diff --git a/content/code-security/code-scanning/troubleshooting-code-scanning/results-different-than-expected.md b/content/code-security/code-scanning/troubleshooting-code-scanning/results-different-than-expected.md
index 821000f46b75..a0dc68b961fa 100644
--- a/content/code-security/code-scanning/troubleshooting-code-scanning/results-different-than-expected.md
+++ b/content/code-security/code-scanning/troubleshooting-code-scanning/results-different-than-expected.md
@@ -13,8 +13,8 @@ redirect_from:
If your {% data variables.product.prodname_code_scanning %} results are different than you expected, you may have both default and advanced setup configured for your repository. When you enable default setup, this disables the existing {% data variables.product.prodname_codeql %} workflow file and blocks any {% data variables.product.prodname_codeql %} API analysis from uploading results.
-To check if default setup is enabled, navigate to the main page of the repository, then click **{% octicon "gear" aria-hidden="true" %} Settings**. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" %} {% data variables.product.UI_advanced_security %}**. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis", click {% octicon "kebab-horizontal" aria-label="Menu" %}. If there is a **{% octicon "workflow" aria-hidden="true" %} Switch to advanced** option, you are currently using default setup.
+To check if default setup is enabled, navigate to the main page of the repository, then click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} {% data variables.product.UI_advanced_security %}**. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis", click {% octicon "kebab-horizontal" aria-label="Menu" %}. If there is a **{% octicon "workflow" aria-hidden="true" aria-label="workflow" %} Switch to advanced** option, you are currently using default setup.
-If you want to return to using advanced setup and get {% data variables.product.prodname_code_scanning %} results from your custom workflow file, click **{% octicon "stop" aria-hidden="true" %} Disable {% data variables.product.prodname_codeql %}** to disable default setup. Then you should re-enable your pre-existing workflows to start triggering and uploading results from advanced setup. For more information, see [AUTOTITLE](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow) and [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning).
+If you want to return to using advanced setup and get {% data variables.product.prodname_code_scanning %} results from your custom workflow file, click **{% octicon "stop" aria-hidden="true" aria-label="stop" %} Disable {% data variables.product.prodname_codeql %}** to disable default setup. Then you should re-enable your pre-existing workflows to start triggering and uploading results from advanced setup. For more information, see [AUTOTITLE](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow) and [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning).
{% data reusables.code-scanning.troubleshooting-multiple-configurations %}
diff --git a/content/code-security/code-scanning/troubleshooting-sarif-uploads/default-setup-enabled.md b/content/code-security/code-scanning/troubleshooting-sarif-uploads/default-setup-enabled.md
index 564785f01355..4af686973052 100644
--- a/content/code-security/code-scanning/troubleshooting-sarif-uploads/default-setup-enabled.md
+++ b/content/code-security/code-scanning/troubleshooting-sarif-uploads/default-setup-enabled.md
@@ -33,7 +33,7 @@ You will only see this error for SARIF files that contain results created using
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
1. In the "{% data variables.product.UI_code_security_scanning %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis," click {% octicon "kebab-horizontal" aria-label="Menu" %}.
-1. If there is a **{% octicon "workflow" aria-hidden="true" %} Switch to advanced** option, default setup is enabled for the repository.
+1. If there is a **{% octicon "workflow" aria-hidden="true" aria-label="workflow" %} Switch to advanced** option, default setup is enabled for the repository.
## Fixing the problem
@@ -46,5 +46,5 @@ Before you can fix the problem, you need to decide whether {% data variables.pro
### Disabling default setup to unblock SARIF upload
-1. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis," from the {% octicon "kebab-horizontal" aria-label="Menu" %} menu select **{% octicon "stop" aria-hidden="true" %} Disable {% data variables.product.prodname_codeql %}**.
+1. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis," from the {% octicon "kebab-horizontal" aria-label="Menu" %} menu select **{% octicon "stop" aria-hidden="true" aria-label="stop" %} Disable {% data variables.product.prodname_codeql %}**.
{% data reusables.code-scanning.sarif-upload-retry %}
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 7fb8b4f86ffc..d095f00e3252 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
@@ -26,7 +26,7 @@ redirect_from:
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-security %}
-1. To filter to see all closed alerts, click **{% octicon "check" aria-hidden="true" %} Closed**. Alternatively, use the `is:closed` filter query in the search bar.
+1. To filter to see all closed alerts, click **{% octicon "check" aria-hidden="true" aria-label="check" %} Closed**. Alternatively, use the `is:closed` filter query in the search bar.
diff --git a/content/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md b/content/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md
index cac16098fece..80224e1acf1f 100644
--- a/content/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md
+++ b/content/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md
@@ -119,7 +119,7 @@ To re-run a {% data variables.product.prodname_dependabot_version_updates %} or
### Re-running a {% data variables.product.prodname_dependabot_security_updates %} job
{% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click **{% octicon "shield-lock" aria-hidden="true" %} Security**.
+1. Under your repository name, click **{% octicon "shield-lock" aria-hidden="true" aria-label="shield-lock" %} Security**.
1. In the left sidebar, under "Vulnerability alerts", click **{% data variables.product.prodname_dependabot %}**.
1. Under "{% data variables.product.prodname_dependabot %}", click the alert you want to view.
1. In the section displaying the error details for the alert, click **Try again** to re-run the {% data variables.product.prodname_dependabot_security_updates %} job.
diff --git a/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md b/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
index f77c37c2e9cb..499468c2269b 100644
--- a/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
+++ b/content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
@@ -77,8 +77,8 @@ Use to define exactly which dependencies to maintain for a package ecosystem. Of
{% data variables.product.prodname_dependabot %} default behavior:
-* {% octicon "versions" aria-hidden="true" %} All dependencies explicitly defined in a manifest are kept up to date by version updates.
-* {% octicon "shield-check" aria-hidden="true" %} All dependencies defined in lock files with vulnerable dependencies are updated by security updates.
+* {% octicon "versions" aria-hidden="true" aria-label="versions" %} All dependencies explicitly defined in a manifest are kept up to date by version updates.
+* {% octicon "shield-check" aria-hidden="true" aria-label="shield-check" %} All dependencies defined in lock files with vulnerable dependencies are updated by security updates.
When `allow` is specified {% data variables.product.prodname_dependabot %} uses the following process:
@@ -121,8 +121,8 @@ Specify individual assignees for all pull requests raised for a package ecosyste
When `assignees` is defined:
-* {% octicon "versions" aria-hidden="true" %} All pull requests for version updates are created with the chosen assignees.
-* {% octicon "shield-check" aria-hidden="true" %} All pull requests for security updates are created with the chosen assignees, unless `target-branch` defines updates to a non-default branch.
+* {% octicon "versions" aria-hidden="true" aria-label="versions" %} All pull requests for version updates are created with the chosen assignees.
+* {% octicon "shield-check" aria-hidden="true" aria-label="shield-check" %} All pull requests for security updates are created with the chosen assignees, unless `target-branch` defines updates to a non-default branch.
Assignees must have write access to the repository. For organization-owned repositories, organization members with read access are also valid assignees.
@@ -136,8 +136,8 @@ Define the format for commit messages. Since the titles of pull requests are wri
When `commit-message` is defined:
-* {% octicon "versions" aria-hidden="true" %} All commit messages follow the defined pattern.
-* {% octicon "shield-check" aria-hidden="true" %} All commit messages follow the defined pattern, unless `target-branch` defines updates to a non-default branch.
+* {% octicon "versions" aria-hidden="true" aria-label="versions" %} All commit messages follow the defined pattern.
+* {% octicon "shield-check" aria-hidden="true" aria-label="shield-check" %} All commit messages follow the defined pattern, unless `target-branch` defines updates to a non-default branch.
| Parameters | Purpose |
|------------|---------|
@@ -245,8 +245,8 @@ Use with the [`allow`](#allow--) option to define exactly which dependencies to
{% data variables.product.prodname_dependabot %} default behavior:
-* {% octicon "versions" aria-hidden="true" %} All dependencies explicitly defined in a manifest are kept up to date by version updates.
-* {% octicon "shield-check" aria-hidden="true" %} All dependencies defined in lock files with vulnerable dependencies are updated by security updates.
+* {% octicon "versions" aria-hidden="true" aria-label="versions" %} All dependencies explicitly defined in a manifest are kept up to date by version updates.
+* {% octicon "shield-check" aria-hidden="true" aria-label="shield-check" %} All dependencies defined in lock files with vulnerable dependencies are updated by security updates.
When `ignore` is used {% data variables.product.prodname_dependabot %} uses the following process:
@@ -466,8 +466,8 @@ Specify individual reviewers, or teams of reviewers, for all pull requests raise
When `reviewers` is defined:
-* {% octicon "versions" aria-hidden="true" %} All pull requests for version updates are created with the chosen reviewers.
-* {% octicon "shield-check" aria-hidden="true" %} All pull requests for security updates are created with the chosen reviewers, unless `target-branch` defines updates to a non-default branch.
+* {% octicon "versions" aria-hidden="true" aria-label="versions" %} All pull requests for version updates are created with the chosen reviewers.
+* {% octicon "shield-check" aria-hidden="true" aria-label="shield-check" %} All pull requests for security updates are created with the chosen reviewers, unless `target-branch` defines updates to a non-default branch.
Reviewers must have at least read access to the repository.
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 37500ae21949..554411483842 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
@@ -43,7 +43,7 @@ For an example of a real `SECURITY.md` file, see [https://github.com/electron/el
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-security %}
-1. In the left sidebar, under "Reporting", click **{% octicon "law" aria-hidden="true" %} Policy**.
+1. In the left sidebar, under "Reporting", click **{% octicon "law" aria-hidden="true" aria-label="law" %} Policy**.
1. Click **Start setup**.
1. In the new `SECURITY.md` file, add information about supported versions of your project and how to report a vulnerability.
{% data reusables.files.write_commit_message %}
diff --git a/content/code-security/getting-started/dependabot-quickstart-guide.md b/content/code-security/getting-started/dependabot-quickstart-guide.md
index 943e4cf145d5..492a4ede1bd9 100644
--- a/content/code-security/getting-started/dependabot-quickstart-guide.md
+++ b/content/code-security/getting-started/dependabot-quickstart-guide.md
@@ -33,7 +33,7 @@ For the purpose of this guide, we're going to use a demo repository to illustrat
You need to start by forking the demo repository.
1. Navigate to [https://github.com/dependabot/demo](https://github.com/dependabot/demo).
-1. At the top of the page, on the right, click **{% octicon "repo-forked" aria-hidden="true" %} Fork**.
+1. At the top of the page, on the right, click **{% octicon "repo-forked" aria-hidden="true" aria-label="repo-forked" %} Fork**.
1. Select an owner (you can select your {% data variables.product.prodname_dotcom %} personal account) and type a repository name. For more information about forking repositories, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo#forking-a-repository).
1. Click **Create fork**.
diff --git a/content/code-security/getting-started/quickstart-for-securing-your-organization.md b/content/code-security/getting-started/quickstart-for-securing-your-organization.md
index f051abf6673b..875f0ccd503a 100644
--- a/content/code-security/getting-started/quickstart-for-securing-your-organization.md
+++ b/content/code-security/getting-started/quickstart-for-securing-your-organization.md
@@ -67,7 +67,7 @@ When you're ready to proceed, follow these steps to enable a feature for all rep
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" %} Code security and analysis**.
+1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} Code security and analysis**.
1. Locate the feature that you want to enable and use any associated check boxes to fine-tune the options.
1. When you are ready to enable the feature for all repositories in your organization where the feature is supported, next to the name of the feature, click **Enable all**.
@@ -84,7 +84,7 @@ You can use the "Security coverage" view to identify repositories that require a
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
-1. In the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage**.
+1. In the sidebar, click **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Coverage**.
On this view, you can use checkboxes to select specific repositories, or you can use the search bar to find the repositories where you want to enable a feature. For example, you can use filters to identify repositories where a certain team has write or admin access, or exclude repositories that don't require the same level of protection, such as test repositories or repositories for internal documentation. Then you can enable features for all selected repositories at once. For more information, see [AUTOTITLE](/code-security/security-overview/enabling-security-features-for-multiple-repositories).
@@ -99,7 +99,7 @@ You can choose to enable a security feature automatically in all new repositorie
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" %} Code security and analysis**.
+1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} Code security and analysis**.
1. Below the name of the feature, select the option for automatically enabling the feature in applicable future repositories.
diff --git a/content/code-security/getting-started/quickstart-for-securing-your-repository.md b/content/code-security/getting-started/quickstart-for-securing-your-repository.md
index 9490e969af39..6ce362b87c9d 100644
--- a/content/code-security/getting-started/quickstart-for-securing-your-repository.md
+++ b/content/code-security/getting-started/quickstart-for-securing-your-repository.md
@@ -32,7 +32,7 @@ Your security needs are unique to your repository, so you may not need to enable
The first step to securing a repository is to establish who can see and modify your code. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features).
-From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**, then scroll down to the "Danger Zone."
+From the main page of your repository, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, then scroll down to the "Danger Zone."
* To change who can view your repository, click **Change visibility**. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility).
* To change who can access your repository and adjust permissions, click **Manage access**. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository).
@@ -42,7 +42,7 @@ From the main page of your repository, click **{% octicon "gear" aria-hidden="tr
{% ifversion fpt or ghec %}
{% data reusables.dependency-graph.feature-availability %} The dependency graph interprets manifest and lock files in a repository to identify dependencies.
-1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. Click **{% data variables.product.UI_advanced_security %}**.
1. Next to Dependency graph, click **Enable** or **Disable**.
{% endif %}
@@ -79,7 +79,7 @@ Dependency review is a {% data variables.product.prodname_GH_code_security %} fe
To enable dependency review for a repository, ensure that the dependency graph is enabled and enable {% data variables.product.prodname_GH_code_security %}.
-1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. Click **{% data variables.product.UI_advanced_security %}**.{% ifversion fpt or ghec %}
1. To the right of {% data variables.product.prodname_code_security %}, click **Enable**.
1. Under {% data variables.product.prodname_code_security %}, check that dependency graph is enabled for the repository. {% elsif ghes %}
@@ -89,7 +89,7 @@ To enable dependency review for a repository, ensure that the dependency graph i
For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected.
-1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. Click **{% data variables.product.UI_advanced_security %}**.
1. Next to {% data variables.product.prodname_dependabot_security_updates %}, click **Enable**.
@@ -100,7 +100,7 @@ For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-secur
You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates).
{% ifversion dependabot-settings-update-37 %}
-1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. Click **{% data variables.product.UI_advanced_security %}**.
1. Next to {% data variables.product.prodname_dependabot_version_updates %}, click **Enable** to create a basic `dependabot.yml` configuration file.
1. Specify the dependencies to update and any associated configuration options, then commit the file to the repository. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates).
@@ -120,11 +120,11 @@ To enable {% data variables.product.prodname_dependabot_version_updates %}, you
You can configure {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.code-scanning.codeql_workflow %} or third-party tool. Depending on the programming languages in your repository, you can configure {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %} using default setup, in which {% data variables.product.github %} automatically determines the languages to scan, query suites to run, and events that will trigger a new scan. For more information, see [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning).
-1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
-1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" %} {% data variables.product.UI_advanced_security %}**.{% ifversion ghas-products %}
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" aria-label="shield-lock" %} {% data variables.product.UI_advanced_security %}**.{% ifversion ghas-products %}
1. If "{% data variables.product.prodname_code_security %}" or "{% data variables.product.prodname_GHAS %}" is not already enabled, click **Enable**.
-1. To the right of "CodeQL analysis", select **Set up** {% octicon "triangle-down" aria-hidden="true" %}, then click **Default**.{% else %}
-1. In the "{% data variables.product.prodname_code_scanning_caps %}" section, select **Set up** {% octicon "triangle-down" aria-hidden="true" %}, then click **Default**.{% endif %}
+1. To the right of "CodeQL analysis", select **Set up** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click **Default**.{% else %}
+1. In the "{% data variables.product.prodname_code_scanning_caps %}" section, select **Set up** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click **Default**.{% endif %}
1. In the pop-up window that appears, review the default configuration settings for your repository, then click **Enable {% data variables.product.prodname_codeql %}**.{% ifversion code-scanning-autofix %}
1. Choose whether you want to enable addition features, such as {% data variables.product.prodname_copilot_autofix_short %}.{% endif %}
@@ -139,7 +139,7 @@ As an alternative to default setup, you can use advanced setup, which generates
{% ifversion ghas-products %}{% data variables.product.prodname_GH_secret_protection %} includes {% data variables.product.prodname_secret_scanning %} and push protection, as well as other features that help you detect and prevent secret leaks in your repository.{% endif %}
-1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. From the main page of your repository, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. Click **{% data variables.product.UI_advanced_security %}**.
1. If "{% data variables.product.prodname_secret_protection %}" or "{% data variables.product.prodname_GHAS %}" is not already enabled, click **Enable**.
1. If the option "{% data variables.product.prodname_secret_scanning_caps %}" is shown, click **Enable**.{% ifversion ghas-products %}
@@ -149,8 +149,8 @@ As an alternative to default setup, you can use advanced setup, which generates
If you are a repository maintainer, it's good practice to specify a security policy for your repository by creating a file named `SECURITY.md` in the repository. This file instructs users about how to best contact you and collaborate with you when they want to report security vulnerabilities in your repository. You can view the security policy of a repository from the repository’s **Security** tab.
-1. From the main page of your repository, click **{% octicon "shield" aria-hidden="true" %} Security**.
-1. In the left sidebar, under "Reporting", click **{% octicon "law" aria-hidden="true" %} Policy**.
+1. From the main page of your repository, click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security**.
+1. In the left sidebar, under "Reporting", click **{% octicon "law" aria-hidden="true" aria-label="law" %} Policy**.
1. Click **Start setup**.
1. Add information about supported versions of your project and how to report vulnerabilities.
diff --git a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/evaluating-alerts.md b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/evaluating-alerts.md
index 69267e364804..3c7b92718461 100644
--- a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/evaluating-alerts.md
+++ b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/evaluating-alerts.md
@@ -57,7 +57,7 @@ With a {% data variables.product.prodname_copilot_enterprise %} license, you can
## Performing an on-demand validity check
-Once you have enabled validity checks for partner patterns for your repository, you can perform an "on-demand" validity check for any supported secret by clicking **{% octicon "sync" aria-hidden="true" %} Verify secret** in the alert view. {% data variables.product.company_short %} will send the pattern to the relevant partner and display the validation status of the secret in the alert view.
+Once you have enabled validity checks for partner patterns for your repository, you can perform an "on-demand" validity check for any supported secret by clicking **{% octicon "sync" aria-hidden="true" aria-label="sync" %} Verify secret** in the alert view. {% data variables.product.company_short %} will send the pattern to the relevant partner and display the validation status of the secret in the alert view.
diff --git a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/monitoring-alerts.md b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/monitoring-alerts.md
index 9fc54bb2ec62..57a9d2748d01 100644
--- a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/monitoring-alerts.md
+++ b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/monitoring-alerts.md
@@ -25,7 +25,7 @@ In addition to displaying an alert in the **Security** tab of the repository, {%
{% data reusables.secret-scanning.secret-scanning-configure-notifications %}
{% data reusables.repositories.navigate-to-repo %}
-1. To start watching the repository, select **{% octicon "eye" aria-hidden="true" %} Watch**.
+1. To start watching the repository, select **{% octicon "eye" aria-hidden="true" aria-label="eye" %} Watch**.
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 62258d63de30..a611622acb49 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
@@ -35,7 +35,7 @@ You can specify custom patterns for {% data variables.product.prodname_secret_sc
### Regular expression syntax for manually defining custom patterns {% endif %}
-The **More options {% octicon "chevron-down" aria-hidden="true" %}** section in the UI helps you write regular expressions manually.
+The **More options {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %}** section in the UI helps you write regular expressions manually.
* **Secret format:** an expression that describes the format of the secret itself.
* **Before secret:** an expression that describes the characters that come before the secret. By default, this is set to `\A|[^0-9A-Za-z]` which means that the secret must be at the start of a line or be preceded by a non-alphanumeric character.
diff --git a/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-a-custom-security-configuration.md b/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-a-custom-security-configuration.md
index c0def9485fcc..7b0a501c9765 100644
--- a/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-a-custom-security-configuration.md
+++ b/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-a-custom-security-configuration.md
@@ -25,7 +25,7 @@ After you create a {% data variables.product.prodname_custom_security_configurat
{% data reusables.security-configurations.view-configurations-page %}
1. Optionally, in the "Apply configurations" section, filter for specific repositories you would like to apply your {% data variables.product.prodname_custom_security_configuration %} to. To learn how to filter the repository table, see [AUTOTITLE](/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table).
{% data reusables.security-configurations.select-repos %}
-1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **YOUR-CONFIGURATION-NAME**.
+1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **YOUR-CONFIGURATION-NAME**.
{% data reusables.security-configurations.default-configuration-exception-repo-transfers %}
diff --git a/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-the-github-recommended-security-configuration-in-your-organization.md b/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-the-github-recommended-security-configuration-in-your-organization.md
index a2ba1600d413..aa43d960fc1f 100644
--- a/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-the-github-recommended-security-configuration-in-your-organization.md
+++ b/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/applying-the-github-recommended-security-configuration-in-your-organization.md
@@ -24,7 +24,7 @@ The {% data variables.product.prodname_github_security_configuration %} is a col
{% data reusables.profile.access_org %}
{% data reusables.organizations.org_settings %}
{% data reusables.security-configurations.view-configurations-page %}
-1. In the "{% data variables.product.company_short %} recommended" row of the configurations table for your organization, select the **Apply to** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **All repositories** or **All repositories without configurations**.
+1. In the "{% data variables.product.company_short %} recommended" row of the configurations table for your organization, select the **Apply to** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **All repositories** or **All repositories without configurations**.
{% data reusables.security-configurations.default-configuration-exception-repo-transfers %}
@@ -37,7 +37,7 @@ The {% data variables.product.prodname_github_security_configuration %} is a col
{% data reusables.security-configurations.view-configurations-page %}
1. Optionally, in the "Apply configurations" section, filter the view to find the repositories you would like to apply the {% data variables.product.prodname_github_security_configuration %} to. To learn how to filter the repository table, see [AUTOTITLE](/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table).
{% data reusables.security-configurations.select-repos %}
-1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **{% data variables.product.company_short %} recommended**.
+1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **{% data variables.product.company_short %} recommended**.
{% data reusables.security-configurations.default-configuration-exception-repo-transfers %}
diff --git a/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/creating-a-custom-security-configuration.md b/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/creating-a-custom-security-configuration.md
index b377b6dbca64..4b6c36d4c9a3 100644
--- a/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/creating-a-custom-security-configuration.md
+++ b/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/creating-a-custom-security-configuration.md
@@ -72,7 +72,7 @@ You can also choose whether or not you want to include {% data variables.product
* **Security updates**. To learn about security updates, see [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates).{% ifversion fpt or ghec %}
1. For "Private vulnerability reporting", choose whether you want to enable, disable, or keep the existing settings. To learn about private vulnerability reporting, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository).{% endif %}
1. Optionally, in the "Policy" section, you can use additional options to control how the configuration is applied:
- * **Use as default for newly created repositories**. Select the **None** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Public**, **Private and internal**, or **All repositories**.
+ * **Use as default for newly created repositories**. Select the **None** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Public**, **Private and internal**, or **All repositories**.
{% data reusables.security-configurations.default-configuration-exception-repo-transfers %}
* **Enforce configuration**. Block repository owners from changing features that are enabled or disabled by the configuration (features that are not set aren't enforced). Select **Enforce** from the dropdown menu.
@@ -111,7 +111,7 @@ You can also choose whether or not you want to include {% data variables.product
* **Security updates**. To learn about security updates, see [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates).{% ifversion fpt or ghec %}
1. For "Private vulnerability reporting", choose whether you want to enable, disable, or keep the existing settings. To learn about private vulnerability reporting, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository).{% endif %}
1. Optionally, in the "Policy" section, you can use additional options to control how the configuration is applied:
- * **Use as default for newly created repositories**. Select the **None** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Public**, **Private and internal**, or **All repositories**.
+ * **Use as default for newly created repositories**. Select the **None** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Public**, **Private and internal**, or **All repositories**.
{% data reusables.security-configurations.default-configuration-exception-repo-transfers %}
* **Enforce configuration**. Block repository owners from changing features that are enabled or disabled by the configuration (features that are not set aren't enforced). Select **Enforce** from the dropdown menu.
@@ -145,7 +145,7 @@ You can also choose whether or not you want to include {% data variables.product
{% ifversion push-protection-delegated-bypass-configurations %}
1. Optionally, under "Push protection", choose whether you want to assign bypass privileges to selected actors in your organization. By assigning bypass privileges, selected organization members can bypass push protection, and there is a review and approval process for all other contributors. For further guidance on how to configure this setting, see [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/enabling-delegated-bypass-for-push-protection#configuring-delegated-bypass-for-an-organization).
{% endif %}
-1. Optionally, in the "Policy" section, you can choose to automatically apply the {% data variables.product.prodname_security_configuration %} to newly created repositories depending on their visibility. Select the **None** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Public**, or **Private and internal**, or **All repositories**.
+1. Optionally, in the "Policy" section, you can choose to automatically apply the {% data variables.product.prodname_security_configuration %} to newly created repositories depending on their visibility. Select the **None** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Public**, or **Private and internal**, or **All repositories**.
{% data reusables.security-configurations.default-configuration-exception-repo-transfers %}
1. Optionally, in the "Policy" section, you can enforce the configuration and block repository owners from changing features that are enabled or disabled by the configuration (features that are not set aren't enforced). Next to "Enforce configuration", select **Enforce** from the dropdown menu.
diff --git a/content/code-security/securing-your-organization/fixing-security-alerts-at-scale/creating-managing-security-campaigns.md b/content/code-security/securing-your-organization/fixing-security-alerts-at-scale/creating-managing-security-campaigns.md
index 7c996602fbcf..c158c04519ab 100644
--- a/content/code-security/securing-your-organization/fixing-security-alerts-at-scale/creating-managing-security-campaigns.md
+++ b/content/code-security/securing-your-organization/fixing-security-alerts-at-scale/creating-managing-security-campaigns.md
@@ -32,13 +32,13 @@ You choose the alerts that you want to include in the campaign by using either:
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
{% data reusables.code-scanning.campaigns-click %}
-1. Click **Create campaign {% octicon "triangle-down" aria-hidden="true" %}**, then select one of the following options:
+1. Click **Create campaign {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}**, then select one of the following options:
* Click **From template**, then select a pre-defined campaign template from the list.
* Click **From code scanning filters**, then add filters to define a subset of alerts for your campaign. See [Examples of useful filters](#examples-of-useful-filters).
1. Review the set of alerts to be included in the campaign, and adjust the filters as necessary. Make sure you have chosen 1000 alerts or fewer.
1. When you are satisfied with the scope of the campaign, click **Save as**, then choose whether you want to create a draft campaign, or move straight ahead to finalizing the details of the campaign before publishing it:
- * If you plan to review the scope and details of the campaign prior to launch, or seek feedback on the implementation of the campaign, click **{% octicon "issue-draft" aria-hidden="true" %} Draft campaign**.
- * If you intend to publish the campaign, and don't need a review phase, click **{% octicon "goal" aria-hidden="true" %} Publish campaign**.
+ * If you plan to review the scope and details of the campaign prior to launch, or seek feedback on the implementation of the campaign, click **{% octicon "issue-draft" aria-hidden="true" aria-label="issue-draft" %} Draft campaign**.
+ * If you intend to publish the campaign, and don't need a review phase, click **{% octicon "goal" aria-hidden="true" aria-label="goal" %} Publish campaign**.
1. Optionally, if you have chosen to create a draft campaign, edit, save, and review the details of the campaign:
* Edit the "Campaign name" and "Short description" to match your campaign needs and to link to any resources that support the campaign.
* Define a "Campaign due date" and select one or more "Campaign managers" as the primary contacts for the campaign. Campaign managers must be users or teams that are owners or security managers in the organization.
@@ -110,7 +110,7 @@ You can edit the name, description, due date, and manager for a campaign.
{% data reusables.organizations.security-overview %}
{% data reusables.code-scanning.campaigns-click %}
1. From the list of campaigns, click the name of the campaign to display the campaign tracking view.
-1. In the campaign title row, click {% octicon "kebab-horizontal" aria-label="Campaign options" %} and select **{% octicon "pencil" aria-hidden="true" %} Edit campaign**.
+1. In the campaign title row, click {% octicon "kebab-horizontal" aria-label="Campaign options" %} and select **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit campaign**.
1. In the "Edit campaign" dialog make your changes and then click **Save changes**.
The changes are made immediately.
@@ -126,7 +126,7 @@ If you don't need to retain the campaign or its data, you can delete it.
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
{% data reusables.code-scanning.campaigns-click %}
-1. To the right of the campaign you want to close, click {% octicon "kebab-horizontal" aria-label="Campaign options" %}, then select **{% octicon "archive" aria-hidden="true" %} Close campaign**.
+1. To the right of the campaign you want to close, click {% octicon "kebab-horizontal" aria-label="Campaign options" %}, then select **{% octicon "archive" aria-hidden="true" aria-label="archive" %} Close campaign**.
### Reopen a closed campaign
@@ -134,14 +134,14 @@ If you don't need to retain the campaign or its data, you can delete it.
{% data reusables.organizations.security-overview %}
{% data reusables.code-scanning.campaigns-click %}
1. Above the list of campaigns, click **Closed** to view the list of closed campaigns.
-1. To the right of the campaign you want to reopen, click {% octicon "kebab-horizontal" aria-label="Campaign options" %}, then select **{% octicon "play" aria-hidden="true" %} Reopen campaign**.
+1. To the right of the campaign you want to reopen, click {% octicon "kebab-horizontal" aria-label="Campaign options" %}, then select **{% octicon "play" aria-hidden="true" aria-label="play" %} Reopen campaign**.
### Delete a campaign
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
{% data reusables.code-scanning.campaigns-click %}
-1. To the right of the campaign you want to delete, click {% octicon "kebab-horizontal" aria-label="Campaign options" %}, then select **{% octicon "trash" aria-hidden="true" %} Delete campaign**.
+1. To the right of the campaign you want to delete, click {% octicon "kebab-horizontal" aria-label="Campaign options" %}, then select **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete campaign**.
## Next steps
diff --git a/content/code-security/securing-your-organization/fixing-security-alerts-at-scale/tracking-security-campaigns.md b/content/code-security/securing-your-organization/fixing-security-alerts-at-scale/tracking-security-campaigns.md
index 75c51d6550f7..53660c174e81 100644
--- a/content/code-security/securing-your-organization/fixing-security-alerts-at-scale/tracking-security-campaigns.md
+++ b/content/code-security/securing-your-organization/fixing-security-alerts-at-scale/tracking-security-campaigns.md
@@ -18,7 +18,7 @@ topics:
The tracking view provides an overview of data for all open and closed campaigns. It helps you understand the impact of the campaigns, track progress through campaigns and measure success towards achieving your organization's goals.
-To display the campaign tracking view, navigate to the **Security** tab for the organization, then in the left sidebar click **{% octicon "goal" aria-hidden="true" %} Campaigns**.
+To display the campaign tracking view, navigate to the **Security** tab for the organization, then in the left sidebar click **{% octicon "goal" aria-hidden="true" aria-label="goal" %} Campaigns**.
@@ -38,7 +38,7 @@ For both open and closed campaigns, the view breaks down the total alert count i
You can similarly track how a single campaign is progressing by viewing the campaign's own tracking page.
-To display the tracking page, navigate to the **Security** tab for the organization, click **{% octicon "goal" aria-hidden="true" %} Campaigns** in the left sidebar, and then select the campaign you want to view from the list of campaigns.
+To display the tracking page, navigate to the **Security** tab for the organization, click **{% octicon "goal" aria-hidden="true" aria-label="goal" %} Campaigns** in the left sidebar, and then select the campaign you want to view from the list of campaigns.
diff --git a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/detaching-repositories-from-their-security-configurations.md b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/detaching-repositories-from-their-security-configurations.md
index e6a324cea5cf..f536a27c732c 100644
--- a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/detaching-repositories-from-their-security-configurations.md
+++ b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/detaching-repositories-from-their-security-configurations.md
@@ -25,5 +25,5 @@ Alternatively, if you want to apply a {% data variables.product.prodname_securit
{% data reusables.security-configurations.view-configurations-page %}
1. Optionally, in the "Apply configurations" section, filter for specific repositories you would like to detach from their configurations. To learn more, see [AUTOTITLE](/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table).
{% data reusables.security-configurations.select-repos %}
-1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **No configuration**.
+1. Select the **Apply configuration** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **No configuration**.
1. To finish detaching your repositories from their linked {% data variables.product.prodname_security_configurations %}, in the "No configuration?" window, click **No configuration**.
diff --git a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table.md b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table.md
index 895984ee2191..395411669540 100644
--- a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table.md
+++ b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/filtering-repositories-in-your-organization-using-the-repository-table.md
@@ -30,7 +30,7 @@ By default, when managing {% data variables.product.prodname_security_configurat
{% data reusables.profile.access_org %}
{% data reusables.organizations.org_settings %}
{% data reusables.security-configurations.view-configurations-page %}
-1. To open the advanced filter dialog, in the "Apply configurations" section, click **{% octicon "filter" aria-hidden="true" %} Filter**.
-1. In the "Advanced filters" window, select the **{% octicon "plus" aria-hidden="true" %} Add a filter** dropdown menu, then click a filter.
+1. To open the advanced filter dialog, in the "Apply configurations" section, click **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter**.
+1. In the "Advanced filters" window, select the **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a filter** dropdown menu, then click a filter.
1. To search for repositories matching the selected filter, fill out the available fields for that filter, then click **Apply**. You can repeat this process to add as many filters as you would like to your search.
-1. Optionally, to remove a filter from your search, click **{% octicon "filter" aria-hidden="true" %} Filter**. In the row of the filter you want to remove, click {% octicon "x" aria-label="Delete FILTER-NUMBER: FILTER-PROPERTIES" %}, then click **Apply**.
+1. Optionally, to remove a filter from your search, click **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter**. In the row of the filter you want to remove, click {% octicon "x" aria-label="Delete FILTER-NUMBER: FILTER-PROPERTIES" %}, then click **Apply**.
diff --git a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/finding-repositories-with-attachment-failures.md b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/finding-repositories-with-attachment-failures.md
index fdacbd728552..ec8347fdfc29 100644
--- a/content/code-security/securing-your-organization/managing-the-security-of-your-organization/finding-repositories-with-attachment-failures.md
+++ b/content/code-security/securing-your-organization/managing-the-security-of-your-organization/finding-repositories-with-attachment-failures.md
@@ -29,7 +29,7 @@ Click the link in the banner display, or alternatively, filter the list of repos
{% data reusables.organizations.org_settings %}
{% data reusables.security-configurations.view-configurations-page %}
1. In the "Apply configurations" section, filter by `config-status:failed`.
-1. From the results list, for the repository you're interested in, click **{% octicon "alert" aria-hidden="true" %} Failed REASON**.
+1. From the results list, for the repository you're interested in, click **{% octicon "alert" aria-hidden="true" aria-label="alert" %} Failed REASON**.
1. In the dialog box, review the information and follow the remediation guidance.
## Further reading
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 61c2bdcc5be3..7560ffd3b5a6 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
@@ -40,7 +40,7 @@ To best secure your organization, you should encourage contributors to review an
* {% data variables.secret-scanning.user_alerts_caps %}, which appear on {% data variables.product.github %} and can be resolved
{% endif %}
-You can view {% data variables.product.prodname_secret_scanning %} alerts for an organization by navigating to the main page of that organization, clicking the **{% octicon "shield" aria-hidden="true" %} Security** tab, then clicking **{% octicon "key" aria-hidden="true" %} {% data variables.product.prodname_secret_scanning_caps %}** in the "Metrics" or "Alerts" section.
+You can view {% data variables.product.prodname_secret_scanning %} alerts for an organization by navigating to the main page of that organization, clicking the **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security** tab, then clicking **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.prodname_secret_scanning_caps %}** in the "Metrics" or "Alerts" section.
* **Metrics**. To see detailed information on push protection events, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection).
* **Alerts**. To see detailed information on **Default** and **Generic** alerts for exposed secrets in the organization.
@@ -53,7 +53,7 @@ To learn how to evaluate {% data variables.product.prodname_secret_scanning %} a
{% data reusables.code-scanning.about-code-scanning %} These problems are raised as {% data variables.product.prodname_code_scanning %} alerts, which contain detailed information on the vulnerability or error detected.
-You can view the {% data variables.product.prodname_code_scanning %} alerts for an organization by navigating to the main page of that organization, clicking the **{% octicon "shield" aria-hidden="true" %} Security** tab, then clicking:
+You can view the {% data variables.product.prodname_code_scanning %} alerts for an organization by navigating to the main page of that organization, clicking the **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security** tab, then clicking:
* **{% data variables.product.prodname_codeql %} pull request alerts**. To see information on {% data variables.product.prodname_code_scanning %} alerts found and remediated in pull requests.
* **{% data variables.product.prodname_code_scanning_caps %}**. To see detailed information on alerts for potentially vulnerable code in the organization, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).
@@ -64,7 +64,7 @@ To learn how to interpret and resolve {% data variables.product.prodname_code_sc
## Interpreting {% data variables.product.prodname_dependabot_alerts %}
-{% data variables.product.prodname_dependabot_alerts %} inform you about vulnerabilities in the dependencies that you use in repositories in your organization. You can view {% data variables.product.prodname_dependabot_alerts %} for an organization by navigating to the main page of that organization, clicking the **{% octicon "shield" aria-hidden="true" %} Security** tab, then clicking **{% octicon "dependabot" aria-hidden="true" %} {% data variables.product.prodname_dependabot %}**.
+{% data variables.product.prodname_dependabot_alerts %} inform you about vulnerabilities in the dependencies that you use in repositories in your organization. You can view {% data variables.product.prodname_dependabot_alerts %} for an organization by navigating to the main page of that organization, clicking the **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security** tab, then clicking **{% octicon "dependabot" aria-hidden="true" aria-label="dependabot" %} {% data variables.product.prodname_dependabot %}**.
For an introduction to {% data variables.product.prodname_dependabot_alerts %}, see [AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
diff --git a/content/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md b/content/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md
index 586ccbb236fc..1dd579e59199 100644
--- a/content/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md
+++ b/content/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md
@@ -47,7 +47,7 @@ Notifications depend on the user's notification preferences. You will receive an
* In your notification settings, under "Subscriptions", then under "Watching", you have selected to receive notifications by email.
{% data reusables.repositories.navigate-to-repo %}
-1. To start watching the repository, select **{% octicon "eye" aria-hidden="true" %} Watch**.
+1. To start watching the repository, select **{% octicon "eye" aria-hidden="true" aria-label="eye" %} Watch**.
diff --git a/content/code-security/security-overview/assessing-adoption-code-security.md b/content/code-security/security-overview/assessing-adoption-code-security.md
index ce5b476face0..0ac45b9c97b8 100644
--- a/content/code-security/security-overview/assessing-adoption-code-security.md
+++ b/content/code-security/security-overview/assessing-adoption-code-security.md
@@ -44,11 +44,11 @@ You can view data to assess the enablement of features for secure coding across
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
-1. To display the "Security coverage" view, in the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage**.
+1. To display the "Security coverage" view, in the sidebar, click **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Coverage**.
{% data reusables.code-scanning.using-security-overview-coverage %}
{% ifversion pre-security-configurations %}
-1. Optionally, click **{% octicon "gear" aria-hidden="true" %} Security settings** to enable security features for a repository and click **Save security settings** to confirm the changes. If a feature is not shown, it has more complex configuration requirements and you need to use the repository settings dialog. For more information, see [AUTOTITLE](/code-security/getting-started/securing-your-repository).
+1. Optionally, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Security settings** to enable security features for a repository and click **Save security settings** to confirm the changes. If a feature is not shown, it has more complex configuration requirements and you need to use the repository settings dialog. For more information, see [AUTOTITLE](/code-security/getting-started/securing-your-repository).
1. Optionally, select some or all of the repositories that match your current search and click **Security settings** in the table header to display a side panel where you can enable security features for the selected repositories. When you've finished, click **Apply changes** to confirm the changes. For more information, see [AUTOTITLE](/code-security/security-overview/enabling-security-features-for-multiple-repositories).
{% data reusables.security-overview.settings-limitations %}
@@ -86,7 +86,7 @@ You can view data to assess the enablement status and enablement status trends o
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
-1. In the sidebar, under "Metrics", click **{% octicon "meter" aria-hidden="true" %} Enablement trends**.
+1. In the sidebar, under "Metrics", click **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Enablement trends**.
1. Click on one of the tabs for "{% data variables.product.prodname_dependabot %}", "{% data variables.product.prodname_code_scanning_caps %}", or "{% data variables.product.prodname_secret_scanning_caps %}" to view enablement trends and the percentage of repositories in your organization with that feature enabled. This data is displayed as a graph and a detailed table.
1. Optionally, use the options at the top of the "Enablement trends" view page to filter the group of repositories you want to see enablement trends for.
* Use the date picker to set the time range that you want to view enablement trends for.
diff --git a/content/code-security/security-overview/assessing-code-security-risk.md b/content/code-security/security-overview/assessing-code-security-risk.md
index 91f360a8d89b..e2805636faed 100644
--- a/content/code-security/security-overview/assessing-code-security-risk.md
+++ b/content/code-security/security-overview/assessing-code-security-risk.md
@@ -52,7 +52,7 @@ For information about the **Overview**, see [AUTOTITLE](/code-security/security-
{% data reusables.security-overview.unaffected-repositories %}
{% data reusables.organizations.security-overview-feature-specific-page %} {% ifversion security-overview-export-data %}
-1. Optionally, use the **{% octicon "download" aria-hidden="true" %} Export CSV** button to download a CSV file of the data currently displayed on the page for security research and in-depth data analysis. For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %}
+1. Optionally, use the **{% octicon "download" aria-hidden="true" aria-label="download" %} Export CSV** button to download a CSV file of the data currently displayed on the page for security research and in-depth data analysis. For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %}
{% data reusables.security-overview.alert-differences %}
@@ -64,14 +64,14 @@ You can view data for security alerts across organizations in an enterprise.
{% ifversion ghes %}{% data reusables.enterprise-accounts.access-enterprise-ghes %}{% else %}{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}{% endif %}
{% data reusables.code-scanning.click-code-security-enterprise %}
-1. To display the "Security risk" view, in the sidebar, click **{% octicon "shield" aria-hidden="true" %} Risk**.
+1. To display the "Security risk" view, in the sidebar, click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Risk**.
{% data reusables.code-scanning.using-security-overview-risk %}
{% data reusables.security-overview.unaffected-repositories %}
{% data reusables.organizations.security-overview-feature-specific-page %}{% ifversion security-overview-export-data %}
-1. Optionally, use the {% octicon "download" aria-hidden="true" %} **Export CSV** button to download a CSV file of the data currently displayed on the page for security research and in-depth data analysis. For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %}
+1. Optionally, use the {% octicon "download" aria-hidden="true" aria-label="download" %} **Export CSV** button to download a CSV file of the data currently displayed on the page for security research and in-depth data analysis. For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %}
{% data reusables.security-overview.alert-differences %}
diff --git a/content/code-security/security-overview/enabling-security-features-for-multiple-repositories.md b/content/code-security/security-overview/enabling-security-features-for-multiple-repositories.md
index e3a047772752..64fb270fcce4 100644
--- a/content/code-security/security-overview/enabling-security-features-for-multiple-repositories.md
+++ b/content/code-security/security-overview/enabling-security-features-for-multiple-repositories.md
@@ -56,6 +56,6 @@ The security features that you can enable and disable in this view are:
* {% data variables.secret-scanning.alerts_caps %}
* {% data variables.product.prodname_secret_scanning_caps %} as a push protection
-If you're blocked from enabling a security feature due to an enterprise policy, you will still be able to see the affected repository in the "Security Coverage" view and access the side panel from the **{% octicon "gear" aria-hidden="true" %} Security settings** button. However, you will see a message in the side panel indicating that the functionality is not available. For more information about enterprise policies, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise).
+If you're blocked from enabling a security feature due to an enterprise policy, you will still be able to see the affected repository in the "Security Coverage" view and access the side panel from the **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Security settings** button. However, you will see a message in the side panel indicating that the functionality is not available. For more information about enterprise policies, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise).
Organization owners and security managers can use security overview to enable or disable security features for all repositories belonging to their organization. There are no enterprise policies that restrict organization owners or security managers from enabling or disabling any security features. For more information about enterprise policies, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies).
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 1255a25e6fac..3f38f6ab060d 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
@@ -34,8 +34,8 @@ The CSV file you download will contain data corresponding to the filters you hav
{% data reusables.profile.access_org %}
1. In the "Organizations" section, select the organization for which you would like to download security overview data.
{% data reusables.organizations.security-overview %}
-1. In the "Security" sidebar, choose the page that you want to export data from by clicking on **{% octicon "graph" aria-hidden="true" %}Overview**, **{% octicon "meter" aria-hidden="true" %} Coverage**, **{% octicon "shield" aria-hidden="true" %} Risk** or **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_codeql %} pull request alerts**.
-1. Next to the search bar, click **{% octicon "download" aria-hidden="true" %} Export CSV**.
+1. In the "Security" sidebar, choose the page that you want to export data from by clicking on **{% octicon "graph" aria-hidden="true" aria-label="graph" %}Overview**, **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Coverage**, **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Risk** or **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull request alerts**.
+1. Next to the search bar, click **{% octicon "download" aria-hidden="true" aria-label="download" %} Export CSV**.
It may take a moment for {% data variables.product.github %} to generate the CSV file of your data. Once the CSV file generates, the file will automatically start downloading, and a banner will appear confirming your report is ready. If you are downloading the CSV from the overview page, you will also receive an email when your report is ready, containing a link to download the CSV.
@@ -47,6 +47,6 @@ The CSV file you download will contain data corresponding to the filters you hav
{% ifversion ghes %}{% data reusables.enterprise-accounts.access-enterprise-ghes %}{% else %}{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}{% endif %}
{% data reusables.code-scanning.click-code-security-enterprise %}
1. Choose the page that you want to export data from by clicking on **Overview**, **Risk**, or **Coverage**.
-1. Next to the search bar, click {% octicon "download" aria-hidden="true" %} **Export CSV**.
+1. Next to the search bar, click {% octicon "download" aria-hidden="true" aria-label="download" %} **Export CSV**.
It may take a moment for {% data variables.product.github %} to generate the CSV file of your data. Once the CSV file generates, the file will automatically start downloading, and a banner will appear confirming your report is ready. If you are downloading the CSV from the overview page, you will also receive an email when your report is ready, containing a link to download the CSV.
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 e50d71961b6e..9d06af15e9f0 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
@@ -43,7 +43,7 @@ All security views have features to help you define filters. These provide an ea
* **Interactive search text box.** When you click in the search box and press the keyboard "Space" key, a pop-up text box shows the filter options available in that view. You can use the mouse or keyboard arrow keys to select the options you want in the text box before pressing the keyboard "Return" key to add the filter. Supported for all views.
* **Dropdown selectors and toggles.** Shown at the end of the "Search text box" or in the header of the data table. As you choose the data to view, the filters shown in the search text box are updated accordingly. Supported on the alert views.
-* **Advanced filters dialog.** When you click the **{% octicon "filter" aria-hidden="true" %} Filter** button, you can use dropdown lists to select the "Qualifier", "Operator", and "Values" for each filter. Supported on the "Overview" and metric views.
+* **Advanced filters dialog.** When you click the **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter** button, you can use dropdown lists to select the "Qualifier", "Operator", and "Values" for each filter. Supported on the "Overview" and metric views.
## Repository name, visibility, and status filters
diff --git a/content/code-security/security-overview/reviewing-requests-to-bypass-push-protection.md b/content/code-security/security-overview/reviewing-requests-to-bypass-push-protection.md
index 0065522ec807..cb50e1d97775 100644
--- a/content/code-security/security-overview/reviewing-requests-to-bypass-push-protection.md
+++ b/content/code-security/security-overview/reviewing-requests-to-bypass-push-protection.md
@@ -28,7 +28,7 @@ For more information, see [AUTOTITLE](/code-security/secret-scanning/using-advan
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
-1. In the sidebar, under "Requests", click **{% octicon "key" aria-hidden="true" %} Push protection bypass**.
+1. In the sidebar, under "Requests", click **{% octicon "key" aria-hidden="true" aria-label="key" %} Push protection bypass**.
1. Select the **All statuses** dropdown menu, then click **Open** to view requests that are awaiting review, or that have been approved but for which the commits haven't been pushed to the repository yet.
1. Click the request that you want to review.
1. Review the details of the request.
diff --git a/content/code-security/security-overview/viewing-metrics-for-pull-request-alerts.md b/content/code-security/security-overview/viewing-metrics-for-pull-request-alerts.md
index 4aace0de1459..8855ab467dba 100644
--- a/content/code-security/security-overview/viewing-metrics-for-pull-request-alerts.md
+++ b/content/code-security/security-overview/viewing-metrics-for-pull-request-alerts.md
@@ -49,15 +49,15 @@ You can apply filters to the data. The metrics are based on activity from the de
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
-1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_codeql %} pull request alerts**.
+1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull request alerts**.
1. Optionally, use the date picker to set the time range. The date picker will show data based on the pull request alerts' creation dates.
1. Optionally, apply filters in the search box at the top of the page.
1. Alternatively, you can open the advanced filter dialog:
- * At the top of the page, next to the search box, click **{% octicon "filter" aria-hidden="true" %} Filter**.
- * Click **{% octicon "plus" aria-hidden="true" %} Add a filter**, then select a filter from the dropdown menu.
+ * At the top of the page, next to the search box, click **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter**.
+ * Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a filter**, then select a filter from the dropdown menu.
* To search for repositories matching the selected filter, fill out the available fields for that filter, then click **Apply**. You can repeat this process to add as many filters as you would like to your search.
- * Optionally, to remove a filter from your search, click **{% octicon "filter" aria-hidden="true" %} Filter**. In the row of the filter you want to remove, click {% octicon "x" aria-label="Delete FILTER-NUMBER: FILTER-PROPERTIES" %}, then click **Apply**.{% ifversion security-overview-export-data %}
-1. You can use the **{% octicon "download" aria-hidden="true" %} Export CSV** button to download a CSV file of the data currently displayed on the page for security research and in-depth data analysis. For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %}
+ * Optionally, to remove a filter from your search, click **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter**. In the row of the filter you want to remove, click {% octicon "x" aria-label="Delete FILTER-NUMBER: FILTER-PROPERTIES" %}, then click **Apply**.{% ifversion security-overview-export-data %}
+1. You can use the **{% octicon "download" aria-hidden="true" aria-label="download" %} Export CSV** button to download a CSV file of the data currently displayed on the page for security research and in-depth data analysis. For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %}
## Viewing {% data variables.product.prodname_codeql %} pull request alerts metrics for your enterprise
@@ -65,6 +65,6 @@ You can also view metrics for {% data variables.product.prodname_codeql %} alert
{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
{% data reusables.code-scanning.click-code-security-enterprise %}
-1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_codeql %} pull request alerts**.
+1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_codeql %} pull request alerts**.
{% data reusables.security-overview.enterprise-filters-tip %}
diff --git a/content/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection.md b/content/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection.md
index fc83bcf18517..1cc74d226429 100644
--- a/content/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection.md
+++ b/content/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection.md
@@ -48,7 +48,7 @@ The metrics are based on activity from the default period or your selected perio
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
-1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_secret_scanning_caps %}**.
+1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} {% data variables.product.prodname_secret_scanning_caps %}**.
1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your organization.
{% data reusables.security-overview.filter-secret-scanning-metrics %}
diff --git a/content/code-security/security-overview/viewing-security-insights.md b/content/code-security/security-overview/viewing-security-insights.md
index 73684486517d..fce6d06d2f0e 100644
--- a/content/code-security/security-overview/viewing-security-insights.md
+++ b/content/code-security/security-overview/viewing-security-insights.md
@@ -77,7 +77,7 @@ Keep in mind that the overview page tracks changes over time for security alert
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
-1. The overview page is the primary view that you will see after clicking on the "Security" tab. To get to the dashboard from another security overview page, in the sidebar, click **{% octicon "graph" aria-hidden="true" %} Overview**.{% ifversion security-overview-3-tab-dashboard %}
+1. The overview page is the primary view that you will see after clicking on the "Security" tab. To get to the dashboard from another security overview page, in the sidebar, click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} Overview**.{% ifversion security-overview-3-tab-dashboard %}
1. By default, the **Detection** tab is displayed. If you want to switch to another tab to see other metrics, click **Remediation** or **Prevention**.{% endif %}
{% data reusables.security-overview.filter-and-toggle %}
diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization.md
index 19394622802e..638c9b14a11c 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization.md
@@ -35,7 +35,7 @@ You need to add the {% data variables.dependency-review.action_name %} to one of
{% data reusables.organizations.access-ruleset-settings %}
1. Click the **New ruleset** dropdown menu, and select **New branch ruleset**.
1. To help identify your ruleset and clarify its purpose, give the ruleset a name in **Ruleset Name**.
-1. Set **Enforcement status** to **{% octicon "play" aria-hidden="true" %} Active**.
+1. Set **Enforcement status** to **{% octicon "play" aria-hidden="true" aria-label="play" %} Active**.
1. Optionally, you can target specific repositories in your organization. For more information, see [Choosing which repositories to target in your organization](/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization#choosing-which-repositories-to-target-in-your-organization).
1. In the "Rules" section, select the "Require workflows to pass before merging" option.
1. In "Workflow configurations", click **Add workflow**.
diff --git a/content/code-security/trialing-github-advanced-security/explore-trial-code-scanning.md b/content/code-security/trialing-github-advanced-security/explore-trial-code-scanning.md
index 1de77bcb4e5d..7f6a5de7e1d3 100644
--- a/content/code-security/trialing-github-advanced-security/explore-trial-code-scanning.md
+++ b/content/code-security/trialing-github-advanced-security/explore-trial-code-scanning.md
@@ -36,7 +36,7 @@ By default, only the repository administrator and the organization owner can vie
The default setup for {% data variables.product.prodname_code_scanning %} runs a set of high confidence queries. These are chosen to ensure that, when you roll out {% data variables.product.prodname_code_scanning %} across your whole codebase, developers see a limited set of high quality results, with few false positive results.
-You can see a summary of any results found in the organizations in your trial enterprise in the **{% octicon "shield" aria-hidden="true" %} Security** tab for the enterprise. There are also separate views for each type of security alert. See [AUTOTITLE](/code-security/security-overview/viewing-security-insights).
+You can see a summary of any results found in the organizations in your trial enterprise in the **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security** tab for the enterprise. There are also separate views for each type of security alert. See [AUTOTITLE](/code-security/security-overview/viewing-security-insights).
If you don't see the results you expect for {% data variables.product.prodname_code_scanning %}, you can update default setup to run an extended query suite for repositories where you expected to find more results. This is controlled at the repository level, see [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup).
diff --git a/content/code-security/trialing-github-advanced-security/explore-trial-secret-scanning.md b/content/code-security/trialing-github-advanced-security/explore-trial-secret-scanning.md
index 408619e554f2..c645d106c533 100644
--- a/content/code-security/trialing-github-advanced-security/explore-trial-secret-scanning.md
+++ b/content/code-security/trialing-github-advanced-security/explore-trial-secret-scanning.md
@@ -22,7 +22,7 @@ This guide assumes that you have planned and started a trial of {% data variable
* Control and audit the bypass process for push protection and {% data variables.secret-scanning.alerts %}.
* Enable validity checks for exposed tokens.
-If you have already scanned the code in your organization for leaked secrets using the free secret risk assessment, you will also want to explore that data more completely using the additional views on the **{% octicon "shield" aria-hidden="true" %} Security** tab for the organization.
+If you have already scanned the code in your organization for leaked secrets using the free secret risk assessment, you will also want to explore that data more completely using the additional views on the **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security** tab for the organization.
For full details of the features available, see [{% data variables.product.prodname_GH_secret_protection %}](/get-started/learning-about-github/about-github-advanced-security#github-secret-protection).
@@ -34,7 +34,7 @@ Most enterprises choose to enable {% data variables.product.prodname_secret_prot
By default, only the repository administrator and the organization owner can view all {% data variables.product.prodname_secret_scanning %} alerts in their area. You should assign the predefined security manager role to all organization teams and users who you want to access the alerts found during the trial. You may also want to give the enterprise account owner this role for each organization in the trial. For more information, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
-You can see a summary of any results found in the organizations in your trial enterprise in the **{% octicon "shield" aria-hidden="true" %} Security** tab for the enterprise. There are also separate views for each type of security alert. See [AUTOTITLE](/code-security/security-overview/viewing-security-insights).
+You can see a summary of any results found in the organizations in your trial enterprise in the **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security** tab for the enterprise. There are also separate views for each type of security alert. See [AUTOTITLE](/code-security/security-overview/viewing-security-insights).
## Identify additional access tokens
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 def3b423500f..ed11fec5eb01 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
@@ -74,7 +74,7 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
-1. Click the **{% octicon "code" aria-hidden="true" %} Code** button, then click the **Codespaces** tab.
+1. Click the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** button, then click the **Codespaces** tab.
A message is displayed at the bottom of the dialog telling you who will pay for the 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 7af6904b09c6..a241c6973483 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
@@ -66,7 +66,7 @@ You can create a codespace from any template repository, then publish your work
{% data reusables.codespaces.use-this-template %}
> [!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).
+ > 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" aria-label="code" %} 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/deleting-a-codespace.md b/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md
index cea4c73ef1cd..f806d28fac37 100644
--- a/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md
+++ b/content/codespaces/developing-in-a-codespace/deleting-a-codespace.md
@@ -41,7 +41,7 @@ There are costs associated with storing codespaces. You should therefore delete
{% webui %}
{% data reusables.codespaces.your-codespaces-procedure-step %}
-1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="Codespace configuration" %}, then click **{% octicon "trash" aria-hidden="true" %} Delete**.
+1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="Codespace configuration" %}, then click **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete**.
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 75593637b5e0..c379774d1c3d 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
@@ -36,7 +36,7 @@ You can view all your codespaces on the "Your codespaces" page at [github.com/co
You can quickly resume a codespace when you're viewing a repository on {% data variables.product.github %}.
-1. With the **{% octicon "code" aria-hidden="true" %} Code** tab of your repository displayed on {% data variables.product.github %}, press , (the comma key).
+1. With the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** tab of your repository displayed on {% data variables.product.github %}, press , (the comma key).
The "Resume codespace" page is displayed. This allows you to resume your most recently used codespace for the currently selected branch of the repository or, if you were viewing a pull request, for the topic branch of the pull request.
diff --git a/content/codespaces/developing-in-a-codespace/using-github-codespaces-for-pull-requests.md b/content/codespaces/developing-in-a-codespace/using-github-codespaces-for-pull-requests.md
index 12214256fb98..de8b817543d0 100644
--- a/content/codespaces/developing-in-a-codespace/using-github-codespaces-for-pull-requests.md
+++ b/content/codespaces/developing-in-a-codespace/using-github-codespaces-for-pull-requests.md
@@ -30,7 +30,7 @@ Using a codespace to work on a pull request gives you all the benefits of {% dat
{% data reusables.repositories.sidebar-pr %}
1. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}.
-1. On the right-hand side of your screen, click **{% octicon "code" aria-hidden="true" %} Code**.
+1. On the right-hand side of your screen, click **{% octicon "code" aria-hidden="true" aria-label="code" %} Code**.
1. In the {% data variables.product.prodname_codespaces %} tab, click {% octicon "plus" aria-label="Create a codespace on BRANCH" %}.
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 ec6a50c03575..3ae0118e5a11 100644
--- a/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
+++ b/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
@@ -20,7 +20,7 @@ If it currently takes more than 2 minutes to create a codespace for a repository
By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds.
-When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-hidden="true" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-hidden="true" %} Prebuild in progress" label. For more information, see [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
+When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-hidden="true" aria-label="zap" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-hidden="true" aria-label="history" %} Prebuild in progress" label. For more information, see [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
diff --git a/content/codespaces/quickstart.md b/content/codespaces/quickstart.md
index ef930ed304a4..15cc25f21967 100644
--- a/content/codespaces/quickstart.md
+++ b/content/codespaces/quickstart.md
@@ -59,7 +59,7 @@ Once your codespace is created, the template repository will be automatically cl
1. Go back to the running application tab in your browser and refresh to see your changes.
- {% octicon "light-bulb" aria-hidden="true" %} If you've closed the browser tab, click the Ports tab in {% data variables.product.prodname_vscode_shortname %}, hover over the **Local Address** value for the running port, and click the **Open in Browser** icon.
+ {% octicon "light-bulb" aria-hidden="true" aria-label="light-bulb" %} If you've closed the browser tab, click the Ports tab in {% data variables.product.prodname_vscode_shortname %}, hover over the **Local Address** value for the running port, and click the **Open in Browser** icon.
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 cd3f8a4f71f3..41798fa4d711 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
@@ -176,7 +176,7 @@ If none of the predefined configurations meets your needs, you can create a cust
### Adding a `devcontainer.json` file
If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.github %}.
-1. Navigate to your repository and click the **{% octicon "code" aria-hidden="true" %} Code** dropdown.
+1. Navigate to your repository and click the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** dropdown.
1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**.
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 1dc3d3fc5fbb..bd119afcb57b 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
@@ -16,7 +16,7 @@ topics:
If a project needs user-specific secrets to be set up, you can prompt people to do this when they create a codespace. You do this by adding a setting to a dev container configuration file for the repository.
-After you specify recommended secrets, if people have not already created those secrets in their personal settings for {% data variables.product.prodname_codespaces %}, they will be prompted to do so when they use the advanced options method of creating a codespace. This is done on {% data variables.product.github %} by clicking the **{% octicon "code" aria-hidden="true" %} Code** button, then clicking the **Codespaces** tab, then selecting {% octicon "kebab-horizontal" aria-label="Codespace repository configuration" %} and clicking **New with options**.
+After you specify recommended secrets, if people have not already created those secrets in their personal settings for {% data variables.product.prodname_codespaces %}, they will be prompted to do so when they use the advanced options method of creating a codespace. This is done on {% data variables.product.github %} by clicking the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** button, then clicking the **Codespaces** tab, then selecting {% octicon "kebab-horizontal" aria-label="Codespace repository configuration" %} and clicking **New with options**.
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 bb9f241a1278..f3df6cf79e34 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
@@ -45,7 +45,7 @@ You can use the "Share a deep link" option to configure more options for the cod
-1. Click the **{% octicon "code" aria-hidden="true" %} Code** button, then click the **Codespaces** tab.
+1. Click the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** button, then click the **Codespaces** tab.
1. To open the "Share codespace configuration" window, at the top right of the **Codespaces** tab, select {% octicon "kebab-horizontal" aria-label="Codespace repository configuration" %}, then click **Share a deep link**.
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 674db18a9a1f..116f58887e16 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
@@ -70,11 +70,11 @@ You may have a codespace that you want to keep for longer than the retention per
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).
{% data reusables.codespaces.your-codespaces-procedure-step %}
-1. To the right of the codespace you want to exempt from automatic deletion, click {% octicon "kebab-horizontal" aria-label="Codespace configuration" %}, then click **{% octicon "bookmark" aria-hidden="true" %} Keep codespace**.
+1. To the right of the codespace you want to exempt from automatic deletion, click {% octicon "kebab-horizontal" aria-label="Codespace configuration" %}, then click **{% octicon "bookmark" aria-hidden="true" aria-label="bookmark" %} Keep codespace**.
-Codespaces that you have exempted from automatic deletion are indicated in your list of codespaces with the bookmark icon ({% octicon "bookmark-fill" aria-hidden="true" %}).
+Codespaces that you have exempted from automatic deletion are indicated in your list of codespaces with the bookmark icon ({% octicon "bookmark-fill" aria-hidden="true" aria-label="bookmark-fill" %}).
diff --git a/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
index 9118e316a899..679532d62568 100644
--- a/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
+++ b/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
@@ -27,9 +27,9 @@ You can export your changes in one of several ways, depending on how you created
The following steps describe how to export your changes to a branch or fork. For information on exporting an unpublished codespace to a new repository, see [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template#publishing-from-githubcom).
-{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-hidden="true" %} Code** menu.
+{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** menu.
1. Click the ellipsis (**...**) to the right of the codespace you want to export from.
-1. Select **{% octicon "git-branch" aria-hidden="true" %} Export changes to a branch** or **{% octicon "git-branch" aria-hidden="true" %} Export changes to a fork**.
+1. Select **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Export changes to a branch** or **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Export changes to a fork**.
diff --git a/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index 3da6a6b3e480..497b885583b2 100644
--- a/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -14,7 +14,7 @@ For more information about {% data variables.product.prodname_github_codespaces
## Checking whether a codespace was created from a prebuild?
-When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-hidden="true" %} Prebuild ready" is shown next to it.
+When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-hidden="true" aria-label="zap" %} Prebuild ready" is shown next to it.
@@ -46,18 +46,18 @@ You can check how much storage space has been consumed by prebuilds in your curr
## The "Prebuild Ready" label is sometimes missing
-You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-hidden="true" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
+You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-hidden="true" aria-label="zap" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
-By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-hidden="true" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see [AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds).
+By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-hidden="true" aria-label="zap" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see [AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds).
If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
-Here are things to check if the "{% octicon "zap" aria-hidden="true" %} Prebuild Ready" label is not displayed for a particular branch:
+Here are things to check if the "{% octicon "zap" aria-hidden="true" aria-label="zap" %} Prebuild Ready" label is not displayed for a particular branch:
* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this.
* Confirm that the prebuild configuration includes your region.
* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
-* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-hidden="true" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
+* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
## Some resources cannot be accessed in codespaces created using a prebuild
diff --git a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
index 00b149f0d7bb..0aea4a282091 100644
--- a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
+++ b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
@@ -34,7 +34,7 @@ Wikis can display PNG, JPEG, and GIF images.
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-wiki %}
1. Using the wiki sidebar, navigate to the page you want to change, and then click **Edit**.
-1. In the wiki toolbar, click {% octicon "image" aria-hidden="true" %}.
+1. In the wiki toolbar, click {% octicon "image" aria-hidden="true" aria-label="image" %}.
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 98f491bdc07d..c773c8712de4 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
@@ -76,7 +76,7 @@ If reported content is enabled for a public repository, you can also report cont
## Reporting contact link abuse in the template chooser
1. Navigate to the repository that contains the contact link you'd like to report.
-1. Under the repository name, click **{% octicon "issue-opened" aria-hidden="true" %} Issues**.
+1. Under the repository name, click **{% octicon "issue-opened" aria-hidden="true" aria-label="issue-opened" %} Issues**.
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**.
diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md
index dd01dc33ee38..455f9658957d 100644
--- a/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md
+++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md
@@ -28,5 +28,5 @@ You can also block users. For more information, see [AUTOTITLE](/communities/mai
## Limiting interactions for your personal account
{% data reusables.user-settings.access_settings %}
-1. In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation** then click **Interaction limits**.
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" aria-label="report" %} Moderation** then click **Interaction limits**.
{% data reusables.community.set-interaction-limit %}
diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index 86590935908e..e9c537d9019c 100644
--- a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -32,7 +32,7 @@ Organization owners and moderators can also block users for a specific amount of
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. _For organization owners:_ In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation**, then click **Interaction limits**.
+1. _For organization owners:_ In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" aria-label="report" %} Moderation**, then click **Interaction limits**.
_For organization moderators:_ In the sidebar, click **Interaction limits**.
diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index de2f641f44ee..d030c1dfb9c6 100644
--- a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -28,7 +28,7 @@ You can also enable activity limitations on all repositories owned by your perso
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" %} Moderation options**, then click **Interaction limits**.
+1. In the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Moderation options**, then click **Interaction limits**.
{% data reusables.community.set-interaction-limit %}
## 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 3bf4201815ec..c811b954f4ed 100644
--- a/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
+++ b/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -40,7 +40,7 @@ If a comment is off-topic, outdated, or resolved, you may want to hide a comment
{% ifversion fpt or ghec %}Organization moderators, and anyone{% else %}Anyone{% endif %} with write access to a repository, can unhide comments on issues, pull requests, and commits.
1. Navigate to the comment you'd like to unhide.
-1. On the right side of the comment, click **{% octicon "fold" aria-hidden="true" %} Show comment**.
+1. On the right side of the comment, click **{% octicon "fold" aria-hidden="true" aria-label="fold" %} Show comment**.
1. On the right side of the expanded comment, select the {% octicon "kebab-horizontal" aria-label="Show options" %} dropdown menu, then click **Unhide**.
diff --git a/content/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace.md b/content/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace.md
index 6c18b4247b03..e162ca75d180 100644
--- a/content/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace.md
+++ b/content/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace.md
@@ -21,7 +21,7 @@ The following steps assume you have {% data variables.product.prodname_github_co
1. Navigate to the open source repository for {% data variables.product.prodname_docs %}, [`github/docs`](https://github.com/github/docs).
1. If you're an open source contributor, create a fork of the repository, then follow the rest of the steps in this procedure from your fork. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
1. Create a branch to work on. 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).
-1. On the main page of the repository, click **{% octicon "code" aria-hidden="true" %} Code**, then click **Create codespace on BRANCH-NAME**.
+1. On the main page of the repository, click **{% octicon "code" aria-hidden="true" aria-label="code" %} Code**, then click **Create codespace on BRANCH-NAME**.
The "Setting up your codespace" page is displayed. After a short time the browser-based version of {% data variables.product.prodname_vscode %} is displayed.
1. Use the Explorer to navigate to the markdown file you want to edit. If the file is an article, it will be located in the `content` directory. If the file is reusable content, it will be located in the `data` directory.
diff --git a/content/copilot/building-copilot-extensions/managing-the-availability-of-your-copilot-extension.md b/content/copilot/building-copilot-extensions/managing-the-availability-of-your-copilot-extension.md
index 12f00b95384c..d4556674f034 100644
--- a/content/copilot/building-copilot-extensions/managing-the-availability-of-your-copilot-extension.md
+++ b/content/copilot/building-copilot-extensions/managing-the-availability-of-your-copilot-extension.md
@@ -20,7 +20,7 @@ If you make your app public, you can choose to publish it on the {% data variabl
{% data reusables.profile.access_org %}
{% data reusables.organizations.org-list %}
-1. At the bottom of the sidebar, select **{% octicon "code" aria-hidden="true" %} Developer settings**, then click **{% data variables.product.prodname_github_apps %}**.
+1. At the bottom of the sidebar, select **{% octicon "code" aria-hidden="true" aria-label="code" %} Developer settings**, then click **{% data variables.product.prodname_github_apps %}**.
1. In the "{% data variables.product.prodname_github_apps %}" section, next to the name of your {% data variables.product.prodname_copilot_extension_short %}, click **Edit**.
1. In the sidebar, click **Advanced**. At the bottom of the "Danger Zone" section, you will see one of two options:
* **Make public:** If you see the **Make public** option, your {% data variables.product.prodname_github_app %} is currently private, and can only be installed by the organization or user that created the app. You can click **Make public** to allow any other account with the link to your app's installation page to install your {% data variables.product.prodname_copilot_short %} extension. Leave the settings unchanged to keep your app private.
@@ -44,7 +44,7 @@ App managers cannot create, edit, or publish extensions on the {% data variables
{% data reusables.profile.access_org %}
{% data reusables.organizations.org-list %}
-1. At the bottom of the sidebar, select **{% octicon "code" aria-hidden="true" %} Developer settings**, then click **{% data variables.product.prodname_github_apps %}**.
+1. At the bottom of the sidebar, select **{% octicon "code" aria-hidden="true" aria-label="code" %} Developer settings**, then click **{% data variables.product.prodname_github_apps %}**.
1. Select the app you'd like to publish to the {% data variables.product.prodname_marketplace %}.
1. On the app settings landing page, scroll down to the Marketplace section, then click **List in Marketplace**. The Marketplace section is only visible if your app is public.
1. In the "Listing name" text box, type a name for your listing. This name is displayed on the {% data variables.product.prodname_marketplace %} page and in search results, and can be changed later. {% data variables.product.github %} recommends using any of the following naming conventions:
diff --git a/content/copilot/building-copilot-extensions/quickstart-for-github-copilot-extensions-using-agents.md b/content/copilot/building-copilot-extensions/quickstart-for-github-copilot-extensions-using-agents.md
index 4fc9d06f7817..34e5088b1dd5 100644
--- a/content/copilot/building-copilot-extensions/quickstart-for-github-copilot-extensions-using-agents.md
+++ b/content/copilot/building-copilot-extensions/quickstart-for-github-copilot-extensions-using-agents.md
@@ -59,8 +59,8 @@ For more detailed instructions, see [AUTOTITLE](/copilot/building-copilot-extens
Rather than deploying the Blackbeard agent as a web app, you can host your agent in a codespace for a significantly faster build process.
-1. Navigate to the [`copilot-extensions/blackbeard-extension`](https://github.com/copilot-extensions/blackbeard-extension) repository. Select the **{% octicon "code" aria-hidden="true" %} Code** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Create codespace on main**.
-1. To find your new codespace, select the **{% octicon "code" aria-hidden="true" %} Code** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu. Next to your new codespace, select {% octicon "kebab-horizontal" aria-label="Show more actions for codespace" %}, then click **{% octicon "globe" aria-hidden="true" %} Open in Browser**.
+1. Navigate to the [`copilot-extensions/blackbeard-extension`](https://github.com/copilot-extensions/blackbeard-extension) repository. Select the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Create codespace on main**.
+1. To find your new codespace, select the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu. Next to your new codespace, select {% octicon "kebab-horizontal" aria-label="Show more actions for codespace" %}, then click **{% octicon "globe" aria-hidden="true" aria-label="globe" %} Open in Browser**.
1. In the integrated Terminal, run `npm start` to start the Blackbeard agent on port 3000.
1. In the "Ports" tab of the {% data variables.product.prodname_vscode_shortname %} panel, click **Forward a port**, then add port 3000.
1. Right-click the port and set the visibility to "Public," then copy the local address.
diff --git a/content/copilot/customizing-copilot/adding-organization-custom-instructions-for-github-copilot.md b/content/copilot/customizing-copilot/adding-organization-custom-instructions-for-github-copilot.md
index af499cf8eeab..9abd96d01767 100644
--- a/content/copilot/customizing-copilot/adding-organization-custom-instructions-for-github-copilot.md
+++ b/content/copilot/customizing-copilot/adding-organization-custom-instructions-for-github-copilot.md
@@ -30,7 +30,7 @@ You can add organization custom instructions via your organization settings.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then click **Custom instructions**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then click **Custom instructions**.
1. Under "Preferences and instructions", add natural language instructions to the text box.
You can write your instructions in any format you prefer. For example, you can write them as a single block of text, each on a new line, or separated by blank lines.
diff --git a/content/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot.md b/content/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot.md
index 7e1605c56773..f5b9368eff0f 100644
--- a/content/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot.md
+++ b/content/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot.md
@@ -273,7 +273,7 @@ To enable prompt files, configure the workspace settings.
### Using prompt files
-1. At the bottom of the {% data variables.product.prodname_copilot_chat_short %} view, click the **Attach context** icon ({% octicon "paperclip" aria-hidden="true" %}).
+1. At the bottom of the {% data variables.product.prodname_copilot_chat_short %} view, click the **Attach context** icon ({% octicon "paperclip" aria-hidden="true" aria-label="paperclip" %}).
1. In the dropdown menu, click **Prompt...** and choose the prompt file you want to use.
1. Optionally, attach additional files, including prompt files, to provide more context.
1. Optionally, type additional information in the chat prompt box.
diff --git a/content/copilot/customizing-copilot/creating-a-custom-model-for-github-copilot.md b/content/copilot/customizing-copilot/creating-a-custom-model-for-github-copilot.md
index bc212d8529d6..853d99b762ea 100644
--- a/content/copilot/customizing-copilot/creating-a-custom-model-for-github-copilot.md
+++ b/content/copilot/customizing-copilot/creating-a-custom-model-for-github-copilot.md
@@ -82,7 +82,7 @@ You can use your organization settings to create a custom large language model.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then click **Custom model**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then click **Custom model**.
1. On the "Custom models" page, click **Train a new custom model**.
1. Under "Select repositories," choose either **Selected repositories** or **All repositories**.
diff --git a/content/copilot/customizing-copilot/extending-copilot-chat-with-mcp.md b/content/copilot/customizing-copilot/extending-copilot-chat-with-mcp.md
index d2bdd4f91d71..a8c56dd2a700 100644
--- a/content/copilot/customizing-copilot/extending-copilot-chat-with-mcp.md
+++ b/content/copilot/customizing-copilot/extending-copilot-chat-with-mcp.md
@@ -70,7 +70,7 @@ You can use the same steps to configure MCP servers in your personal {% data var
-1. Open {% data variables.product.prodname_copilot_chat_short %} by clicking the {% octicon "copilot" aria-hidden="true" %} icon in the title bar of {% data variables.product.prodname_vscode %}.
+1. Open {% data variables.product.prodname_copilot_chat_short %} by clicking the {% octicon "copilot" aria-hidden="true" aria-label="copilot" %} icon in the title bar of {% data variables.product.prodname_vscode %}.
1. In the {% data variables.product.prodname_copilot_chat_short %} box, select **Agent** from the popup menu.
@@ -85,7 +85,7 @@ For more information on configuring MCP servers in {% data variables.product.pro
Once you have configured your MCP servers, you can use them in {% data variables.product.prodname_copilot_chat_short %} to access a wide range of tools and services. In the example below, we will use the Fetch MCP server to fetch details about a web page.
-1. Open {% data variables.product.prodname_copilot_chat_short %} by clicking the {% octicon "copilot" aria-hidden="true" %} icon in the title bar of {% data variables.product.prodname_vscode %}.
+1. Open {% data variables.product.prodname_copilot_chat_short %} by clicking the {% octicon "copilot" aria-hidden="true" aria-label="copilot" %} icon in the title bar of {% data variables.product.prodname_vscode %}.
1. In the {% data variables.product.prodname_copilot_chat_short %} box, select **Agent** from the popup menu.
1. In the file with the MCP configuration, check that the MCP server is running. If it is not running, click the "Start" button to start the MCP server.
@@ -131,7 +131,7 @@ For information on other currently available MCP servers, see [the MCP servers r
## Configuring MCP servers in JetBrains IDEs
-1. In the lower right corner, click **{% octicon "copilot" aria-hidden="true" %}**.
+1. In the lower right corner, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}**.
1. From the menu, select "Edit settings".
1. Under the MCP section, click "Edit in `mcp.json`".
1. Define your MCP servers. You can use the following configuration as an example:
@@ -182,7 +182,7 @@ For information on other currently available MCP servers, see [the MCP servers r
## Configuring MCP servers in Eclipse
-1. To open the {% data variables.product.prodname_copilot_chat_short %} panel, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) in the status bar at the bottom of Eclipse.
+1. To open the {% data variables.product.prodname_copilot_chat_short %} panel, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) in the status bar at the bottom of Eclipse.
1. From the menu, select "Edit preferences".
1. In the left pane, expand {% data variables.product.prodname_copilot_chat_short %} and click **MCP**.
1. Define your MCP servers. You can use the following configuration as an example:
diff --git a/content/copilot/customizing-copilot/extending-the-capabilities-of-github-copilot-in-your-organization.md b/content/copilot/customizing-copilot/extending-the-capabilities-of-github-copilot-in-your-organization.md
index d10264acca50..544438aabd0e 100644
--- a/content/copilot/customizing-copilot/extending-the-capabilities-of-github-copilot-in-your-organization.md
+++ b/content/copilot/customizing-copilot/extending-the-capabilities-of-github-copilot-in-your-organization.md
@@ -33,7 +33,7 @@ Before you install any {% data variables.product.prodname_copilot_extensions_sho
## Installing {% data variables.product.prodname_copilot_extensions %} for your organization
1. Open [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=apps&copilot_app=true).
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**.
1. In the list of {% data variables.product.prodname_copilot_extensions_short %}, locate an app you'd like to install.
1. To install the {% data variables.product.prodname_copilot_extension_short %} on an organization with a {% data variables.product.prodname_copilot_business_short %} or {% data variables.product.prodname_copilot_enterprise_short %} plan, see [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-from-github-marketplace-for-your-organizations).
{% data reusables.copilot.copilot-extensions.extension-specific-onboarding-steps %}
diff --git a/content/copilot/customizing-copilot/managing-copilot-knowledge-bases.md b/content/copilot/customizing-copilot/managing-copilot-knowledge-bases.md
index 6fc662781ca7..81702d2ce915 100644
--- a/content/copilot/customizing-copilot/managing-copilot-knowledge-bases.md
+++ b/content/copilot/customizing-copilot/managing-copilot-knowledge-bases.md
@@ -37,7 +37,7 @@ Knowledge bases you create will be accessible by all organization members with a
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then click **Knowledge bases**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then click **Knowledge bases**.
1. To the right of "Knowledge bases", click **New knowledge base**.
1. In the "Name" field, enter a unique name for the knowledge base. Optionally, in the "Description" field, you can add a description for the knowledge base.
@@ -68,7 +68,7 @@ Organization owners can update a knowledge base created in their organization.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then click **Knowledge bases**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then click **Knowledge bases**.
1. To the right of the knowledge base you want to edit, click {% octicon "pencil" aria-label="The pencil symbol" %}.
1. Make your desired changes to your knowledge base.
1. Click **Update knowledge base**.
@@ -80,6 +80,6 @@ Organization owners can delete a knowledge base created in their organization.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then click **Knowledge bases**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then click **Knowledge bases**.
1. To the right of the knowledge base you want to delete, click {% octicon "trash" aria-label="The trash symbol" %}.
1. In the "Confirm deletion" dialog box, review the information and click **Delete**.
diff --git a/content/copilot/managing-copilot/configure-personal-settings/configuring-github-copilot-in-your-environment.md b/content/copilot/managing-copilot/configure-personal-settings/configuring-github-copilot-in-your-environment.md
index 6c8b6544b232..f35069af7830 100644
--- a/content/copilot/managing-copilot/configure-personal-settings/configuring-github-copilot-in-your-environment.md
+++ b/content/copilot/managing-copilot/configure-personal-settings/configuring-github-copilot-in-your-environment.md
@@ -463,7 +463,7 @@ You can use the default keyboard shortcuts for inline suggestions in Eclipse whe
If you don't want to use the default keyboard shortcuts for {% data variables.product.prodname_copilot %}, you can rebind the shortcuts in the Key Bindings editor and use your preferred keyboard shortcuts.
-1. In the IDE, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** to open the menu.
+1. In the IDE, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** to open the menu.
1. Click **Edit Keyboard Shortcuts...** to rebind the shortcuts.
## Settings and configurations
diff --git a/content/copilot/managing-copilot/configure-personal-settings/installing-the-github-copilot-extension-in-your-environment.md b/content/copilot/managing-copilot/configure-personal-settings/installing-the-github-copilot-extension-in-your-environment.md
index c18941937644..3b13053ce96d 100644
--- a/content/copilot/managing-copilot/configure-personal-settings/installing-the-github-copilot-extension-in-your-environment.md
+++ b/content/copilot/managing-copilot/configure-personal-settings/installing-the-github-copilot-extension-in-your-environment.md
@@ -241,7 +241,7 @@ To use the {% data variables.product.prodname_copilot %} extension, you must hav
1. After the extension is installed, restart Eclipse to apply the changes.
-1. In the bottom right corner of the Eclipse workbench, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, then click **Sign In to {% data variables.product.prodname_dotcom %}**.
+1. In the bottom right corner of the Eclipse workbench, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, then click **Sign In to {% data variables.product.prodname_dotcom %}**.
1. In the "Sign In to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy Code and Open**.
diff --git a/content/copilot/managing-copilot/configure-personal-settings/using-github-copilot-with-an-account-on-ghecom.md b/content/copilot/managing-copilot/configure-personal-settings/using-github-copilot-with-an-account-on-ghecom.md
index 0119a931f226..cc67c0b0f177 100644
--- a/content/copilot/managing-copilot/configure-personal-settings/using-github-copilot-with-an-account-on-ghecom.md
+++ b/content/copilot/managing-copilot/configure-personal-settings/using-github-copilot-with-an-account-on-ghecom.md
@@ -100,10 +100,10 @@ For the "{% data variables.product.prodname_enterprise %} URL" field, enter the
## Authenticating from Eclipse
-1. In the IDE, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** to open the menu.
+1. In the IDE, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** to open the menu.
1. Click **Edit Preferences...**.
1. In the **{% data variables.product.prodname_enterprise %} Authentication Endpoint** field, enter the URL where you access {% data variables.product.github %}. For example: `https://{% data variables.enterprise.data_residency_example_domain %}`.
1. Click **Apply**.
-1. Open the **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** menu again then click **Sign In to {% data variables.product.prodname_dotcom %}**.
+1. Open the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** menu again then click **Sign In to {% data variables.product.prodname_dotcom %}**.
{% endeclipse %}
diff --git a/content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/excluding-content-from-github-copilot.md b/content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/excluding-content-from-github-copilot.md
index 3c983b12a8e9..a167dad2f71a 100644
--- a/content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/excluding-content-from-github-copilot.md
+++ b/content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/excluding-content-from-github-copilot.md
@@ -73,7 +73,7 @@ You can use your repository settings to specify content in your repository that
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Code & automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**.
+1. In the "Code & automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**.
If your repository inherits any exclusions from {% ifversion fpt %}its parent organization{% else %} organizations in the same enterprise{% endif %}, you'll see {% ifversion ghec %}one or more{% else %} a{% endif %} gray box{% ifversion ghec %}es{% endif %} at the top of the page containing details of these exclusions. You cannot edit these settings.
@@ -109,7 +109,7 @@ You can use your organization settings to specify files that {% data variables.p
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then click **Content exclusion**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then click **Content exclusion**.
1. In the box following "Repositories and paths to exclude," enter the details of files from which {% data variables.product.prodname_copilot_short %} should be excluded.
To exclude files located anywhere (within a Git repository or elsewhere), enter `"*":` followed by the path to the file, or files, you want to exclude. If you want to specify multiple file path patterns, list each pattern on a separate line.
diff --git a/content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/reviewing-changes-to-content-exclusions-for-github-copilot.md b/content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/reviewing-changes-to-content-exclusions-for-github-copilot.md
index cce480d5f5d4..7260698f96ca 100644
--- a/content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/reviewing-changes-to-content-exclusions-for-github-copilot.md
+++ b/content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/reviewing-changes-to-content-exclusions-for-github-copilot.md
@@ -22,7 +22,7 @@ Organization and repository settings include the ability to exclude content from
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Code & automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**.
+1. In the "Code & automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**.
{% data reusables.copilot.view-last-change-content-exclusions %}
1. Click the time of the last change.
@@ -36,7 +36,7 @@ Organization and repository settings include the ability to exclude content from
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then click **Content exclusion**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then click **Content exclusion**.
{% data reusables.copilot.view-last-change-content-exclusions %}
1. Click the time of the last change.
diff --git a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-free-access-to-copilot-pro-as-a-student-teacher-or-maintainer.md b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-free-access-to-copilot-pro-as-a-student-teacher-or-maintainer.md
index f34d3d297383..bce7ef006b8e 100644
--- a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-free-access-to-copilot-pro-as-a-student-teacher-or-maintainer.md
+++ b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-free-access-to-copilot-pro-as-a-student-teacher-or-maintainer.md
@@ -32,6 +32,6 @@ If you do not meet the previous criteria, you can either:
## Accessing {% data variables.product.prodname_copilot_pro_short %} for free
-1. In the upper-right corner of any page, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" %} Your {% data variables.product.prodname_copilot_short %}**.
+1. In the upper-right corner of any page, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Your {% data variables.product.prodname_copilot_short %}**.
1. If you qualify for free access to {% data variables.product.prodname_copilot_short %}, you will see a page titled "{% data variables.product.prodname_copilot_pro %}" informing you that you are eligible. Click **Get access to {% data variables.product.prodname_copilot %}**.
1. On the page that appears, configure the {% data variables.product.prodname_copilot_short %} use policies to meet your needs, then click **Save and complete**.
diff --git a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-started-with-a-copilot-plan.md b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-started-with-a-copilot-plan.md
index d5f7c859928d..91d79d62c427 100644
--- a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-started-with-a-copilot-plan.md
+++ b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/getting-started-with-copilot-on-your-personal-account/getting-started-with-a-copilot-plan.md
@@ -41,7 +41,7 @@ There are a few ways to start using {% data variables.product.prodname_copilot_f
In {% data variables.product.prodname_vs %} and {% data variables.product.prodname_vscode_shortname %} you can access {% data variables.product.prodname_copilot_free_short %} directly from the editor.
-1. In the top right of {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode_shortname %}, click **{% octicon "copilot" aria-hidden="true" %}**.
+1. In the top right of {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode_shortname %}, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}**.
1. In the sidebar, click **Sign up for {% data variables.product.prodname_copilot_free_short %}**.
1. If you have a {% data variables.product.github %} account, you will be prompted to sign in. If you don't have a {% data variables.product.github %} account, you will be prompted to create one.
diff --git a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/disabling-github-copilot-free.md b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/disabling-github-copilot-free.md
index 45b1032a1159..31bdb576b4a3 100644
--- a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/disabling-github-copilot-free.md
+++ b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/disabling-github-copilot-free.md
@@ -17,7 +17,7 @@ redirect_from:
You can disable {% data variables.product.prodname_copilot_free_short %} in your {% data variables.product.github %} account settings. This will disable all features of {% data variables.product.prodname_copilot_short %} on {% data variables.product.github %}.
-1. In the upper-right corner of any page, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" %} Your {% data variables.product.prodname_copilot_short %}**.
+1. In the upper-right corner of any page, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Your {% data variables.product.prodname_copilot_short %}**.
1. Under "Visibility," to the right of "Show {% data variables.product.prodname_copilot_short %}, select **Disabled** from the dropdown.
## Disabling {% data variables.product.prodname_copilot_free_short %} in your IDE
diff --git a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/extending-the-capabilities-of-github-copilot-in-your-personal-account.md b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/extending-the-capabilities-of-github-copilot-in-your-personal-account.md
index 24d3eed8abcd..5817ea4186ab 100644
--- a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/extending-the-capabilities-of-github-copilot-in-your-personal-account.md
+++ b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/extending-the-capabilities-of-github-copilot-in-your-personal-account.md
@@ -26,7 +26,7 @@ You can also create your own custom {% data variables.product.prodname_copilot_e
## Installing {% data variables.product.prodname_copilot_extensions %} for your personal account
1. Open [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=apps&copilot_app=true).
-1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**.
+1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**.
1. In the list of {% data variables.product.prodname_copilot_extensions_short %}, locate an app you'd like to install.
1. To install the {% data variables.product.prodname_copilot_extension_short %} on your personal account, see [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-from-github-marketplace-for-your-personal-account#installing-a-github-app-in-your-personal-account).
{% data reusables.copilot.copilot-extensions.extension-specific-onboarding-steps %}
diff --git a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber.md b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber.md
index 3d0a89477170..7934066878dc 100644
--- a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber.md
+++ b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber.md
@@ -41,7 +41,7 @@ If you choose to allow suggestions matching public code, when {% data variables.
To use {% data variables.copilot.copilot_coding_agent %} in repositories owned by your own personal account, you must enable it for those repositories in your account settings.
{% data reusables.user-settings.copilot-settings %}
-1. In the sidebar, under **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, click **Coding agent**.
+1. In the sidebar, under **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, click **Coding agent**.
1. On the {% data variables.copilot.copilot_coding_agent %} page, under "Policies," click the dropdown button for "Repository access," then choose either **No repositories**, **All repositories**, or **Only selected repositories**.
1. If you choose **Only selected repositories**, click **Select repositories** and choose the repositories where you want to enable {% data variables.copilot.copilot_coding_agent %}.
diff --git a/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-access-to-copilot-in-your-enterprise/viewing-copilot-license-usage-in-your-enterprise.md b/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-access-to-copilot-in-your-enterprise/viewing-copilot-license-usage-in-your-enterprise.md
index 02aa6f8c6aa3..307c966a590f 100644
--- a/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-access-to-copilot-in-your-enterprise/viewing-copilot-license-usage-in-your-enterprise.md
+++ b/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-access-to-copilot-in-your-enterprise/viewing-copilot-license-usage-in-your-enterprise.md
@@ -54,7 +54,7 @@ If you have a {% data variables.product.prodname_copilot_business_short %} or {%
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
1. Under "{% data variables.product.prodname_copilot_short %}", view the breakdown of your {% data variables.product.prodname_copilot %} usage and upcoming changes in your organization.
diff --git a/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-plan-for-your-enterprise/subscribing-to-copilot-for-your-enterprise.md b/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-plan-for-your-enterprise/subscribing-to-copilot-for-your-enterprise.md
index 6995d6ff0db3..ee1893bd3148 100644
--- a/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-plan-for-your-enterprise/subscribing-to-copilot-for-your-enterprise.md
+++ b/content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-plan-for-your-enterprise/subscribing-to-copilot-for-your-enterprise.md
@@ -21,7 +21,7 @@ redirect_from:
1. Ensure you are signed in as an enterprise admin on {% data variables.product.github %}.
1. Navigate to the [{% data variables.product.prodname_copilot %} sign up page](https://github.com/github-copilot/purchase).
-1. Ensure you are signed in to the right enterprise account. If you are not, click **{% octicon "arrow-switch" aria-hidden="true" %} Switch** and select the enterprise for which you want to purchase {% data variables.product.prodname_copilot %}. You can also append `?enterprise=YOUR-ENTERPRISE` to the URL to pre-select the enterprise.
+1. Ensure you are signed in to the right enterprise account. If you are not, click **{% octicon "arrow-switch" aria-hidden="true" aria-label="arrow-switch" %} Switch** and select the enterprise for which you want to purchase {% data variables.product.prodname_copilot %}. You can also append `?enterprise=YOUR-ENTERPRISE` to the URL to pre-select the enterprise.
1. Follow the steps to sign up and enable {% data variables.product.prodname_copilot_short %} for organizations in your enterprise. If you purchased {% data variables.product.prodname_copilot_enterprise_short %}, you will be able to assign either {% data variables.product.prodname_copilot_enterprise_short %} or {% data variables.product.prodname_copilot_business_short %} to each individual organization in the enterprise.
## Next steps
diff --git a/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/managing-requests-for-copilot-business-in-your-organization.md b/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/managing-requests-for-copilot-business-in-your-organization.md
index 1e70d7f7e052..dc6beb0d20a5 100644
--- a/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/managing-requests-for-copilot-business-in-your-organization.md
+++ b/content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/managing-requests-for-copilot-business-in-your-organization.md
@@ -19,7 +19,7 @@ If your organization is owned by an enterprise, before you can approve a request
{% data reusables.profile.access_org %}
{% data reusables.organizations.org-list %}
-1. In the "Access" section of the sidebar, click **{% octicon "bell" aria-hidden="true" %} Requests from members**.
+1. In the "Access" section of the sidebar, click **{% octicon "bell" aria-hidden="true" aria-label="bell" %} Requests from members**.
1. To accept the request and grant the member access to {% data variables.product.prodname_copilot_for_business %}, click **Buy {% data variables.product.prodname_copilot_business_short %}**.
All requests for {% data variables.product.prodname_copilot_business_short %} are grouped together under "{% data variables.product.prodname_copilot_business_short %}."
diff --git a/content/copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements.md b/content/copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements.md
index 83e24d45a291..79a1ee706ac3 100644
--- a/content/copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements.md
+++ b/content/copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements.md
@@ -19,7 +19,7 @@ You can track your monthly usage of premium requests to help you get the most va
## Viewing premium request usage
{% data reusables.user-settings.access_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
1. Under "Usage by product", on the "Copilot" tab, you can see the total cost of the additional premium requests you've used this month. Click **View details** to view a breakdown of the amount of additional premium requests you've used.
1. Optionally, to download a CSV usage report, in the sidebar under "Billing & Licensing," select **Usage**. Then click the down arrow next to "Get usage report" to download your monthly **{% data variables.product.prodname_copilot_short %} premium usage report**. Please allow up to 20 minutes to receive the email with the report.
diff --git a/content/copilot/quickstart.md b/content/copilot/quickstart.md
index 395cf9210500..c2213a4c8b6e 100644
--- a/content/copilot/quickstart.md
+++ b/content/copilot/quickstart.md
@@ -44,7 +44,7 @@ To use {% data variables.product.prodname_copilot_short %} on the {% data variab
## Asking your first question
1. On {% data variables.product.github %}, navigate to a repository and open a file.
-1. Click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) at the top right of the file view.
+1. Click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) at the top right of the file view.
diff --git a/content/copilot/rolling-out-github-copilot-at-scale/assigning-licenses/managing-your-companys-spending-on-github-copilot.md b/content/copilot/rolling-out-github-copilot-at-scale/assigning-licenses/managing-your-companys-spending-on-github-copilot.md
index 3bac1ec4c6e3..83e417104443 100644
--- a/content/copilot/rolling-out-github-copilot-at-scale/assigning-licenses/managing-your-companys-spending-on-github-copilot.md
+++ b/content/copilot/rolling-out-github-copilot-at-scale/assigning-licenses/managing-your-companys-spending-on-github-copilot.md
@@ -14,7 +14,7 @@ redirect_from:
When you're adopting {% data variables.product.prodname_copilot %} in an enterprise, you will want to set budgets and track spending to ensure your rollout is sustainable. {% data variables.product.github %} offers billing tools to help you visualize your spending patterns, receive alerts when you reach budget thresholds, and optimize your license usage.
->[!NOTE] Some of the tools recommended in this article are part of {% data variables.product.github %}'s new billing platform, which isn't available to all customers. If your enterprise has access, you will see a **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing** option in your enterprise account's settings.
+>[!NOTE] Some of the tools recommended in this article are part of {% data variables.product.github %}'s new billing platform, which isn't available to all customers. If your enterprise has access, you will see a **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing** option in your enterprise account's settings.
## Understand who can grant licenses
@@ -50,7 +50,7 @@ The default budget that is created applies to your whole enterprise. To set a ne
{% elsif ghec %}
-1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
{% endif %}
1. Click **Budgets and alerts**.
@@ -72,7 +72,7 @@ You can view a CSV report that shows the cumulative number of premium requests p
You can download the report for an enterprise account, or for an organization that is not part of an enterprise.
-1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
1. In the left sidebar, click **Usage**.
1. To download the usage report, select **Get usage report** in the upper-right corner of the page, and click **{% data variables.product.prodname_copilot_short %} premium requests usage report**.
@@ -84,7 +84,7 @@ For example, if you were running a pilot program for {% data variables.product.p
### Create a cost center
-1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
1. In the left sidebar, click **Cost centers**, then click **New cost center**.
1. Create the cost center. You don't need to add any repositories or organizations, because you will add users to the cost center directly in the next step.
@@ -98,7 +98,7 @@ With {% data variables.product.github %}'s new billing platform, you can set a m
{% ifversion ghec %}You can create the budget for the whole enterprise or for a cost center.{% endif %}
-1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
1. In the left sidebar, click **Budgets and alerts**.
1. Click **New budget**.
1. Select **{% data variables.product.prodname_copilot_short %}** for the product, or **{% data variables.product.prodname_copilot_short %} Premium Request** for the SKU, then configure the settings as required. You can choose who receives alerts when budget thresholds are reached.
@@ -108,7 +108,7 @@ With {% data variables.product.github %}'s new billing platform, you can set a m
With {% data variables.product.github %}'s new billing platform, you can understand your spending trends by viewing a graph for {% data variables.product.prodname_copilot_short %} usage over a certain timeframe. For more detailed insights, you can filter the results by cost center and group usage by the type of {% data variables.product.prodname_copilot_short %} plan.
-1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
1. In the left sidebar, click **Usage**.
1. In the "Metered usage" section, in the search field, enter `product:copilot`. To filter by cost center, add a query like `cost_center:ce-pilot-group`.
1. To understand spending differences between {% data variables.product.prodname_copilot_business_short %} and {% data variables.product.prodname_copilot_enterprise_short %} plans, select the **Group: None** dropdown menu and click **Group: SKU**.
diff --git a/content/copilot/rolling-out-github-copilot-at-scale/enabling-developers/integrating-agentic-ai.md b/content/copilot/rolling-out-github-copilot-at-scale/enabling-developers/integrating-agentic-ai.md
index 833f9d2e580d..0a113da7bbaa 100644
--- a/content/copilot/rolling-out-github-copilot-at-scale/enabling-developers/integrating-agentic-ai.md
+++ b/content/copilot/rolling-out-github-copilot-at-scale/enabling-developers/integrating-agentic-ai.md
@@ -114,7 +114,7 @@ To hit a tight deadline, you're aiming to speed up each stage of the process, fo
## Get started with agentic AI
-Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 %}
+Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 aria-label="link-external" %}
To get started with the features mentioned in this article, use the links in the following table.
diff --git a/content/copilot/rolling-out-github-copilot-at-scale/enabling-developers/using-copilot-coding-agent-in-org.md b/content/copilot/rolling-out-github-copilot-at-scale/enabling-developers/using-copilot-coding-agent-in-org.md
index f97a3fdc593c..9f4ae22d6d4e 100644
--- a/content/copilot/rolling-out-github-copilot-at-scale/enabling-developers/using-copilot-coding-agent-in-org.md
+++ b/content/copilot/rolling-out-github-copilot-at-scale/enabling-developers/using-copilot-coding-agent-in-org.md
@@ -83,7 +83,7 @@ All AI models are trained to meet a request, even if they don't have all the inf
## Piloting {% data variables.copilot.copilot_coding_agent %}
-Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 %}
+Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 aria-label="link-external" %}
> [!TIP] During the {% data variables.release-phases.public_preview %}, you need {% data variables.product.prodname_copilot_pro_plus %} or {% data variables.product.prodname_copilot_enterprise %} to use {% data variables.copilot.copilot_coding_agent %}.
diff --git a/content/copilot/rolling-out-github-copilot-at-scale/planning-your-rollout/choosing-your-enterprises-plan-for-github-copilot.md b/content/copilot/rolling-out-github-copilot-at-scale/planning-your-rollout/choosing-your-enterprises-plan-for-github-copilot.md
index 066055fb8deb..17b4eed2726c 100644
--- a/content/copilot/rolling-out-github-copilot-at-scale/planning-your-rollout/choosing-your-enterprises-plan-for-github-copilot.md
+++ b/content/copilot/rolling-out-github-copilot-at-scale/planning-your-rollout/choosing-your-enterprises-plan-for-github-copilot.md
@@ -21,7 +21,7 @@ When you adopt {% data variables.product.prodname_copilot %} in a company, you w
This article helps you to decide whether to adopt {% data variables.product.prodname_copilot_business_short %} or {% data variables.product.prodname_copilot_enterprise_short %}.
-Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 %}
+Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 aria-label="link-external" %}
## About the plans
diff --git a/content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md b/content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md
index 2dc966b348a8..baca5181830d 100644
--- a/content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md
+++ b/content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md
@@ -18,10 +18,10 @@ redirect_from:
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
-1. Click the **{% octicon "check-circle" aria-hidden="true" %} Getting Started** tab.
+1. Click the **{% octicon "check-circle" aria-hidden="true" aria-label="check-circle" %} Getting Started** tab.
1. Under "Next steps", click **Verify your payment method**. This will enable {% data variables.product.prodname_copilot %} in your enterprise.
-After you've completed these steps, you will be able to confirm that {% data variables.product.prodname_copilot %} is enabled in your enterprise's **{% octicon "law" aria-hidden="true" %} Policies** tab.
+After you've completed these steps, you will be able to confirm that {% data variables.product.prodname_copilot %} is enabled in your enterprise's **{% octicon "law" aria-hidden="true" aria-label="law" %} Policies** tab.
## 2. Set policies
diff --git a/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat.md b/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat.md
index 65d4f256cbd7..79bdef793156 100644
--- a/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat.md
+++ b/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-chat.md
@@ -56,11 +56,11 @@ These instructions are for {% data variables.product.prodname_copilot_short %} o
> [!NOTE] If you use {% data variables.product.prodname_copilot_extensions_short %}, they may override the model you select.
-1. In the top right of any page on {% data variables.product.github %}, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %} beside the **{% octicon "copilot" aria-hidden="true" %}** icon and click **Immersive** in the dropdown menu.
+1. In the top right of any page on {% data variables.product.github %}, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %} beside the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon and click **Immersive** in the dropdown menu.
-1. At the top of the immersive view, select the **CURRENT-MODEL** {% octicon "chevron-down" aria-hidden="true" %} dropdown menu, then click the AI model of your choice.
+1. At the top of the immersive view, select the **CURRENT-MODEL** {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} dropdown menu, then click the AI model of your choice.
1. Optionally, after submitting a prompt, you can regenerate the same prompt using a different model by clicking the retry icon ({% octicon "sync" aria-label="The re-run icon" %}) below the response. The new response will use your selected model and maintain the full context of the conversation.
@@ -101,7 +101,7 @@ These instructions are for {% data variables.product.prodname_vscode_shortname %
{% data reusables.copilot.chat-model-limitations-ide %}
{% data reusables.copilot.open-chat-vs-code %}
-1. In the bottom right of the chat view, select the **CURRENT-MODEL** {% octicon "chevron-down" aria-hidden="true" %} dropdown menu, then click the AI model of your choice.
+1. In the bottom right of the chat view, select the **CURRENT-MODEL** {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} dropdown menu, then click the AI model of your choice.
{% endvscode %}
@@ -132,7 +132,7 @@ To use multi-model {% data variables.product.prodname_copilot_chat_short %}, you
{% data reusables.copilot.chat-model-limitations-ide %}
1. In the {% data variables.product.prodname_vs %} menu bar, click **View**, then click **{% data variables.product.prodname_copilot_chat %}**.
-1. In the bottom right of the chat view, select the **CURRENT-MODEL** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click the AI model of your choice.
+1. In the bottom right of the chat view, select the **CURRENT-MODEL** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click the AI model of your choice.
{% endvisualstudio %}
@@ -169,9 +169,9 @@ These instructions are for the JetBrains IDEs. For instructions on different cli
{% data reusables.copilot.chat-model-limitations-ide %}
-1. Click the **{% octicon "copilot" aria-hidden="true" %}** icon in the status bar.
+1. Click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon in the status bar.
1. In the popup menu, click **Open {% data variables.product.prodname_copilot_chat %}**.
-1. In the bottom right of the chat view, select an AI model of your choice from the {% octicon "chevron-down" aria-hidden="true" %} dropdown menu.
+1. In the bottom right of the chat view, select an AI model of your choice from the {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} dropdown menu.
{% endjetbrains %}
@@ -204,7 +204,7 @@ These instructions are for the Eclipse IDE. For instructions on different client
{% data reusables.copilot.chat-model-limitations-ide %}
-1. Click the **{% octicon "copilot" aria-hidden="true" %}** icon in the status bar.
+1. Click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon in the status bar.
1. In the popup menu, click **Open Chat**.
1. In the bottom right of the chat panel, click the currently selected AI model, then select an alternative model from the popup menu.
@@ -245,8 +245,8 @@ To use multi-model {% data variables.product.prodname_copilot_chat_short %}, you
{% data reusables.copilot.chat-model-limitations-ide %}
-1. To open the chat view, click **Editor** in the menu bar, then click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then **Open Chat**. {% data variables.product.prodname_copilot_chat_short %} opens in a new window.
-1. In the bottom right of the chat view, select the **CURRENT-MODEL** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click the AI model of your choice.
+1. To open the chat view, click **Editor** in the menu bar, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then **Open Chat**. {% data variables.product.prodname_copilot_chat_short %} opens in a new window.
+1. In the bottom right of the chat view, select the **CURRENT-MODEL** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click the AI model of your choice.
{% endxcode %}
diff --git a/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-code-completion.md b/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-code-completion.md
index f20e82f1676a..2a6d11a0a270 100644
--- a/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-code-completion.md
+++ b/content/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-code-completion.md
@@ -90,7 +90,7 @@ The following instructions are for {% data variables.product.prodname_vscode_sho
1. Type `change completions model` and select the "{% data variables.product.prodname_copilot %}: Change Completions Model" command.
1. In the dropdown menu, select the model you want to use.
-Alternatively, if Command Center is enabled, you can click {% octicon "chevron-down" aria-label="The downward-pointing arrowhead" %} beside the **{% octicon "copilot" aria-hidden="true" %}** icon at the top of the {% data variables.product.prodname_vscode_shortname %} window, then click **Configure Code Completions** in the dropdown menu. Then choose **Change Completions Model** in the dropdown menu and select the model you want to use.
+Alternatively, if Command Center is enabled, you can click {% octicon "chevron-down" aria-label="The downward-pointing arrowhead" %} beside the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon at the top of the {% data variables.product.prodname_vscode_shortname %} window, then click **Configure Code Completions** in the dropdown menu. Then choose **Change Completions Model** in the dropdown menu and select the model you want to use.
## Checking which model is being used
@@ -107,7 +107,7 @@ Alternatively, if Command Center is enabled, you can click {% octicon "chevron-d
The following instructions are for {% data variables.product.prodname_vs %}. If you are using {% data variables.product.prodname_vscode_shortname %}, or a JetBrains IDE, click the appropriate tab at the start of this article.
-1. Click the **{% octicon "copilot" aria-hidden="true" %}** icon in the top right corner.
+1. Click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon in the top right corner.
1. Click **Settings**, then click **Options**.
1. Under **{% data variables.product.prodname_copilot_short %} Completions**, use the dropdown menu to select the model you want to use.
@@ -119,7 +119,7 @@ The following instructions are for {% data variables.product.prodname_vs %}. If
The following instructions are for JetBrains IDEs. If you are using {% data variables.product.prodname_vs %}, or {% data variables.product.prodname_vscode_shortname %}, click the appropriate tab at the start of this article.
-1. Click the **{% octicon "copilot" aria-hidden="true" %}** icon in the status bar.
+1. Click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon in the status bar.
1. In the popup menu, click **Edit Model for Completion**.
1. In the settings dialog box for "Languages & Frameworks > {% data variables.product.prodname_copilot %}," click the dropdown menu for **Model for completions** and select the model you want to use.
1. Click **OK**.
diff --git a/content/copilot/using-github-copilot/code-review/configuring-coding-guidelines.md b/content/copilot/using-github-copilot/code-review/configuring-coding-guidelines.md
index 93b1c34b1389..63e3b9fb0cf5 100644
--- a/content/copilot/using-github-copilot/code-review/configuring-coding-guidelines.md
+++ b/content/copilot/using-github-copilot/code-review/configuring-coding-guidelines.md
@@ -43,7 +43,7 @@ Coding guidelines are configured at the repository level. You can create and ena
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Code & automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, then **Code review**.
+1. In the "Code & automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, then **Code review**.
1. Click **Create guideline**.
1. Under "Name," give the coding guideline a name.
1. Under "Description," provide a description of the coding guideline up to 600 characters long. This will be used by {% data variables.product.prodname_copilot_short %} to understand your coding style and to decide when to leave a comment.
@@ -59,9 +59,9 @@ Coding guidelines are configured at the repository level. You can create and ena
1. Test your coding guideline to make sure it works as expected.
1. Click **Add sample**.
- 1. Add your own sample, or press **{% octicon "copilot" aria-hidden="true" %} Generate code sample** to automatically generate a code sample based on your title and description.
+ 1. Add your own sample, or press **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Generate code sample** to automatically generate a code sample based on your title and description.
1. Click **Save** to save the code sample.
- 1. Test the coding guideline against your sample by pressing **{% octicon "play" aria-hidden="true" %} Run**.
+ 1. Test the coding guideline against your sample by pressing **{% octicon "play" aria-hidden="true" aria-label="play" %} Run**.
1. Save your coding guideline, and turn it on, by clicking **Save guideline**.
diff --git a/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-github-mobile.md b/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-github-mobile.md
index c7b4fe6c26c5..218cf845cc4b 100644
--- a/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-github-mobile.md
+++ b/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-github-mobile.md
@@ -50,7 +50,7 @@ If you are part of an organization{% ifversion ghec %} or enterprise{% endif %}
You can ask a general question about software development{% ifversion ghec %} that is not focused on a particular context, such as a repository{% endif %}.
{% data reusables.copilot.chat-mobile-start-chat %}
-1. If the page displays a previous conversation you had with {% data variables.product.prodname_copilot_short %}, tap {% octicon "kebab-horizontal" %} in the top right corner of the screen, and then tap **New conversation {% octicon "plus" aria-hidden="true" %}**.
+1. If the page displays a previous conversation you had with {% data variables.product.prodname_copilot_short %}, tap {% octicon "kebab-horizontal" aria-label="kebab-horizontal" %} in the top right corner of the screen, and then tap **New conversation {% octicon "plus" aria-hidden="true" aria-label="plus" %}**.
1. At the bottom of the page, in the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
Some examples of general questions you could ask are:
@@ -70,7 +70,7 @@ You can ask a general question about software development{% ifversion ghec %} th
You can ask questions about a specific repository, to get help with understanding the code, or to get help with a specific task you're working on.
-1. In {% data variables.product.prodname_mobile %}, navigate to a repository, and tap the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, navigate to a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
1. At the bottom of the page, use the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
For example, if you chose the repository you are working in as the context, you could ask:
@@ -94,8 +94,8 @@ You can chat with {% data variables.product.prodname_copilot_short %} about a fi
1. In {% data variables.product.prodname_mobile %}, navigate to a repository and open a file.
1. Do one of the following:
- * To ask a question about the entire file, tap the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) in the bottom right corner of the file view.
- * To ask a question about specific lines within the file, select and copy the lines you want to ask about. Then tap the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) and paste the copied lines in the {% data variables.product.prodname_copilot_chat_short %} input field.
+ * To ask a question about the entire file, tap the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) in the bottom right corner of the file view.
+ * To ask a question about specific lines within the file, select and copy the lines you want to ask about. Then tap the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) and paste the copied lines in the {% data variables.product.prodname_copilot_chat_short %} input field.
1. Type a question in the "Ask {% data variables.product.prodname_copilot_short %}" box at the bottom of the chat panel and send the message.
@@ -121,7 +121,7 @@ You can chat with {% data variables.product.prodname_copilot_short %} about a fi
You can ask questions about a specific pull request in a repository.
-1. In {% data variables.product.prodname_mobile %}, navigate to a pull request in a repository, and tap the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, navigate to a pull request in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
1. At the bottom of the page, use the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
For example, you could ask:
@@ -139,7 +139,7 @@ You can ask questions about a specific pull request in a repository.
You can ask questions about a specific issue in a repository.
-1. In {% data variables.product.prodname_mobile %}, navigate to an issue in a repository, and tap the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, navigate to an issue in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
1. At the bottom of the page, use the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
For example, you could ask:
@@ -157,7 +157,7 @@ You can ask questions about a specific issue in a repository.
You can ask questions about a specific discussion in a repository.
-1. In {% data variables.product.prodname_mobile %}, navigate to a discussion in a repository, and tap the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, navigate to a discussion in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
1. At the bottom of the page, use the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
For example, you could ask:
diff --git a/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-github.md b/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-github.md
index 2dd18d65b538..6ab8e7b42cd3 100644
--- a/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-github.md
+++ b/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-github.md
@@ -69,7 +69,7 @@ You can open {% data variables.product.prodname_copilot_chat_short %} from any p
Depending on the question you ask, and your enterprise and organization settings, {% data variables.product.prodname_copilot_short %} may respond using information based on the results of a Bing search. By using Bing search, {% data variables.product.prodname_copilot_short %} can answer a broad range of tech-related questions with up-to-date details based on information currently available on the internet. For information on how to enable or disable Bing search integration, see [AUTOTITLE](/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-copilot-policies-as-an-individual-subscriber#enabling-or-disabling-web-search-for-github-copilot-chat) and [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise).
-1. At the top right of any page on {% data variables.product.github %}, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %} beside the **{% octicon "copilot" aria-hidden="true" %}** icon and click **Immersive** in the dropdown menu.
+1. At the top right of any page on {% data variables.product.github %}, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %} beside the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon and click **Immersive** in the dropdown menu.
@@ -203,7 +203,7 @@ Organization owners (with a {% data variables.product.prodname_copilot_enterpris
When you enter a query, {% data variables.product.prodname_copilot_short %} searches for relevant documentation snippets, synthesizes a summary of the relevant snippets to answer your question, and provides links to the source documentation for additional context.
-1. At the top right of any page on {% data variables.product.github %}, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %} beside the **{% octicon "copilot" aria-hidden="true" %}** icon and click **Immersive** in the dropdown menu.
+1. At the top right of any page on {% data variables.product.github %}, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %} beside the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon and click **Immersive** in the dropdown menu.
@@ -227,14 +227,14 @@ You can chat with {% data variables.product.prodname_copilot_short %} about a fi
1. On {% data variables.product.github %}, navigate to a repository and open a file.
1. Do one of the following:
- * To ask a question about the entire file, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) at the top right of the file view.
+ * To ask a question about the entire file, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) at the top right of the file view.
* To ask a question about specific lines within the file:
1. Select the lines by clicking the line number for the first line you want to select, holding down Shift and clicking the line number for the last line you want to select.
- 1. To ask your own question about the selected lines, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) to the right of your selection.
+ 1. To ask your own question about the selected lines, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) to the right of your selection.
This displays the {% data variables.product.prodname_copilot_chat %} panel with the selected lines indicated as the context of your question.
1. To ask a predefined question, click the downward-pointing button beside the {% data variables.product.prodname_copilot_short %} icon, then choose one of the options.
@@ -250,7 +250,7 @@ You can chat with {% data variables.product.prodname_copilot_short %} about a fi
{% data variables.product.prodname_copilot_short %} allows you to use natural language questions to ask about security alerts in repositories in your organization when these alerts are generated by {% data variables.product.prodname_GHAS %} features ({% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_secret_scanning %}, and {% data variables.product.prodname_dependabot_alerts %}).
-1. At the top right of any page on {% data variables.product.github %}, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %} beside the **{% octicon "copilot" aria-hidden="true" %}** icon and click **Immersive** in the dropdown menu.
+1. At the top right of any page on {% data variables.product.github %}, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %} beside the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon and click **Immersive** in the dropdown menu.
@@ -292,7 +292,7 @@ You can ask {% data variables.product.prodname_copilot_short %} different questi
1. Click the **Files changed** tab.
1. Click the line number for the first line you want to select, then hold down Shift and click the line number for the last line you want to select.
1. Ask {% data variables.product.prodname_copilot_short %} a question, or choose from a list of predefined questions.
- * _To ask your own question about the selected lines_, to the right of your selection, click the {% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %} icon.
+ * _To ask your own question about the selected lines_, to the right of your selection, click the {% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %} icon.
This displays the {% data variables.product.prodname_copilot_chat %} panel with the selected lines indicated as the context of your question.
### Ask why a workflow has failed
@@ -413,9 +413,9 @@ You can share {% data variables.product.prodname_copilot_chat_short %} conversat
Once you share a conversation, the conversation and future messages will be visible to anyone with the link.
-1. In the top right of any page on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon next to the search bar.
-1. To view a conversation in immersive mode, click **{% octicon "screen-full" aria-hidden="true" %} Immersive**.
-1. Once you submit your first prompt, a share button will appear in the upper right corner. Click **{% octicon "lock" aria-hidden="true" %} Share** to open the share dialog.
+1. In the top right of any page on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon next to the search bar.
+1. To view a conversation in immersive mode, click **{% octicon "screen-full" aria-hidden="true" aria-label="screen-full" %} Immersive**.
+1. Once you submit your first prompt, a share button will appear in the upper right corner. Click **{% octicon "lock" aria-hidden="true" aria-label="lock" %} Share** to open the share dialog.
@@ -428,7 +428,7 @@ Once you share a conversation, the conversation and future messages will be visi
To give feedback about a particular {% data variables.product.prodname_copilot_chat_short %} response, click either the thumbs up or thumbs down icon at the bottom of each chat response.
-To give feedback about {% data variables.product.prodname_copilot_chat_short %} in general, click the ellipsis (**...**) at the top right of the chat panel, then click **{% octicon "comment-discussion" aria-hidden="true" %} Give feedback**.
+To give feedback about {% data variables.product.prodname_copilot_chat_short %} in general, click the ellipsis (**...**) at the top right of the chat panel, then click **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Give feedback**.
## Further reading
diff --git a/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-your-ide.md b/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-your-ide.md
index 730de1ee54ff..00cd11604c17 100644
--- a/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-your-ide.md
+++ b/content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-your-ide.md
@@ -28,7 +28,7 @@ shortTitle: Chat in IDE
You can ask {% data variables.product.prodname_copilot_chat_short %} to give you code suggestions, explain code, generate unit tests, and suggest code fixes.
-1. To open the chat view, click the **{% octicon "copilot" aria-hidden="true" %}** icon in the title bar of {% data variables.product.prodname_vscode %}. If the **{% octicon "copilot" aria-hidden="true" %}** icon is not displayed, right-click the title bar and make sure that **Command Center** is selected.
+1. To open the chat view, click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon in the title bar of {% data variables.product.prodname_vscode %}. If the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon is not displayed, right-click the title bar and make sure that **Command Center** is selected.
@@ -407,7 +407,7 @@ By default, {% data variables.product.prodname_copilot_chat_short %} will refere
* **Built-in requests**. In addition to submitting prompts through the chat window, you can submit built-in requests by right clicking in a file, selecting **{% data variables.product.prodname_copilot %}**, then selecting one of the options.
* **Inline**. You can submit a chat prompt inline, and scope it to a highlighted code block or your current file.
- * To start an inline chat, right click on a code block or anywhere in your current file, hover over **{% data variables.product.prodname_copilot %}**, then select **{% octicon "plus" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}: Inline Chat**, or enter Ctrl+Shift+I.
+ * To start an inline chat, right click on a code block or anywhere in your current file, hover over **{% data variables.product.prodname_copilot %}**, then select **{% octicon "plus" aria-hidden="true" aria-label="plus" %} {% data variables.product.prodname_copilot_short %}: Inline Chat**, or enter Ctrl+Shift+I.
## {% data variables.product.prodname_copilot_edits_short %}
@@ -422,7 +422,7 @@ Use {% data variables.product.prodname_copilot_edits_short %} to make changes ac
#### Using edit mode
-1. To start an edit session, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** in the menu bar, then select **Open {% data variables.product.prodname_copilot_chat %}**.
+1. To start an edit session, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** in the menu bar, then select **Open {% data variables.product.prodname_copilot_chat %}**.
1. At the top of the chat panel, click **{% data variables.product.prodname_copilot_edits_short %}**.
1. Add relevant files to the _working set_ to indicate to {% data variables.product.prodname_copilot %} which files you want to work on. You can add all open files by clicking **Add all open files** or individually search for single files.
1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_edits_short %} determines which files in your _working set_ to change and adds a short description of the change.
@@ -434,7 +434,7 @@ Use {% data variables.product.prodname_copilot_edits_short %} to make changes ac
#### Using agent mode
-1. To start an edit session using agent mode, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** in the menu bar, then select **Open {% data variables.product.prodname_copilot_chat %}**.
+1. To start an edit session using agent mode, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** in the menu bar, then select **Open {% data variables.product.prodname_copilot_chat %}**.
1. At the top of the chat panel, click the **Agent** tab.
1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_short %} streams the edits in the editor, updates the working set, and if necessary, suggests terminal commands to run.
1. Review the changes. If {% data variables.product.prodname_copilot_short %} suggested terminal commands, confirm whether or not {% data variables.product.prodname_copilot_short %} can run them. In response, {% data variables.product.prodname_copilot_short %} iterates and performs additional actions to complete the task in your original prompt.
@@ -477,7 +477,7 @@ To use {% data variables.product.prodname_copilot %} for Xcode, you must install
You can ask {% data variables.product.prodname_copilot_chat_short %} to give you code suggestions, explain code, generate unit tests, and suggest code fixes.
-1. To open the chat view, click **Editor** in the menu bar, then click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** then **Open Chat**. {% data variables.product.prodname_copilot_chat_short %} opens in a new window.
+1. To open the chat view, click **Editor** in the menu bar, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** then **Open Chat**. {% data variables.product.prodname_copilot_chat_short %} opens in a new window.
1. Enter a prompt in the prompt box. For example prompts, see [AUTOTITLE](/copilot/using-github-copilot/guides-on-using-github-copilot/getting-started-with-prompts-for-copilot-chat).
@@ -505,7 +505,7 @@ To see all available slash commands, type `/` in the chat prompt box. For more i
### Using agent mode
-1. To open the chat view, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}** in the menu bar, then click **Open Chat**.
+1. To open the chat view, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** in the menu bar, then click **Open Chat**.
1. At the bottom of the chat panel, select **Agent** from the mode dropdown.
1. Optionally, add relevant files to the _working set_ view to indicate to {% data variables.product.prodname_copilot_short %} which files you want to work on.
1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_short %} streams the edits in the editor, updates the working set, and if necessary, suggests terminal commands to run.
@@ -551,7 +551,7 @@ To indicate whether a response was helpful, use {% octicon "thumbsup" aria-label
You can ask {% data variables.product.prodname_copilot_chat_short %} to give you code suggestions, explain code, generate unit tests, and suggest code fixes.
-1. To open the {% data variables.product.prodname_copilot_chat_short %} panel, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) in the status bar at the bottom of Eclipse, then click **Open Chat**.
+1. To open the {% data variables.product.prodname_copilot_chat_short %} panel, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) in the status bar at the bottom of Eclipse, then click **Open Chat**.
1. Enter a prompt in the prompt box, then press Enter.
@@ -579,7 +579,7 @@ To see all available slash commands, type `/` in the chat prompt box.
### Using agent mode
-1. To open the {% data variables.product.prodname_copilot_chat_short %} panel, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) in the status bar at the bottom of Eclipse, then click **Open Chat**.
+1. To open the {% data variables.product.prodname_copilot_chat_short %} panel, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) in the status bar at the bottom of Eclipse, then click **Open Chat**.
1. At the bottom of the chat panel, select **Agent** from the mode dropdown.
1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_short %} streams the edits in the editor, updates the working set, and if necessary, suggests terminal commands to run.
1. Review the changes. If {% data variables.product.prodname_copilot_short %} suggested terminal commands, confirm whether or not {% data variables.product.prodname_copilot_short %} can run them. In response, {% data variables.product.prodname_copilot_short %} iterates and performs additional actions to complete the task in your original prompt.
diff --git a/content/copilot/using-github-copilot/getting-code-suggestions-in-your-ide-with-github-copilot.md b/content/copilot/using-github-copilot/getting-code-suggestions-in-your-ide-with-github-copilot.md
index 11250b9a0998..ef37962e6e1c 100644
--- a/content/copilot/using-github-copilot/getting-code-suggestions-in-your-ide-with-github-copilot.md
+++ b/content/copilot/using-github-copilot/getting-code-suggestions-in-your-ide-with-github-copilot.md
@@ -20,11 +20,11 @@ topics:
diff --git a/content/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/troubleshooting-copilot-coding-agent.md b/content/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/troubleshooting-copilot-coding-agent.md
index a92d594214d9..9fb1e5e3fd63 100644
--- a/content/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/troubleshooting-copilot-coding-agent.md
+++ b/content/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/troubleshooting-copilot-coding-agent.md
@@ -19,7 +19,7 @@ redirect_from:
You can only assign issues to {% data variables.product.prodname_copilot_short %} if you have access to {% data variables.product.prodname_copilot_short %} through either the **{% data variables.product.prodname_copilot_pro_plus %}** plan or the **{% data variables.product.prodname_copilot_enterprise %}** plan.
If you do not already have a subscription for one of these plans, click this button for more information:
-Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 %}
+Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 aria-label="link-external" %}
If you _do_ have either {% data variables.product.prodname_copilot_pro_plus %} or {% data variables.product.prodname_copilot_enterprise %}, check that {% data variables.copilot.copilot_coding_agent %} {% ifversion ghec %}is enabled and{% endif %} has been made available for the repository:
diff --git a/content/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/using-copilot-to-work-on-an-issue.md b/content/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/using-copilot-to-work-on-an-issue.md
index 216bbc850293..b5c1448336ad 100644
--- a/content/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/using-copilot-to-work-on-an-issue.md
+++ b/content/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/using-copilot-to-work-on-an-issue.md
@@ -51,7 +51,7 @@ You can assign an issue to {% data variables.product.prodname_copilot_short %} o
You can also assign issues to {% data variables.product.prodname_copilot_short %} from other places on {% data variables.product.prodname_dotcom_the_website %}:
-* From the list of issues on a repository's **{% octicon "issue-opened" aria-hidden="true" %} Issues** page.
+* From the list of issues on a repository's **{% octicon "issue-opened" aria-hidden="true" aria-label="issue-opened" %} Issues** page.
* When viewing an issue in {% data variables.product.github %} {% data variables.projects.projects_v2_caps %}.
### Assigning an issue to {% data variables.product.prodname_copilot_short %} via the {% data variables.product.github %} API
diff --git a/content/copilot/using-github-copilot/using-copilot-text-completion.md b/content/copilot/using-github-copilot/using-copilot-text-completion.md
index 21f2c3e77907..6d9a4b67785f 100644
--- a/content/copilot/using-github-copilot/using-copilot-text-completion.md
+++ b/content/copilot/using-github-copilot/using-copilot-text-completion.md
@@ -35,4 +35,4 @@ You can use {% data variables.product.prodname_copilot_autocomplete_pr %} in the
You can disable or enable {% data variables.product.prodname_copilot_autocomplete_pr %} for your pull request descriptions. Your preference will be saved for future pull requests.
1. On {% data variables.product.github %}, create a pull request.
-1. At the top of the description field, select {% octicon "copilot" aria-hidden="true" %} then hover over **Autocomplete ({% data variables.release-phases.public_preview_caps %})**, and click **Disabled** or **Enabled**.
+1. At the top of the description field, select {% octicon "copilot" aria-hidden="true" aria-label="copilot" %} then hover over **Autocomplete ({% data variables.release-phases.public_preview_caps %})**, and click **Disabled** or **Enabled**.
diff --git a/content/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request.md b/content/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request.md
index 470a6e341d69..191596025b12 100644
--- a/content/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request.md
+++ b/content/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request.md
@@ -49,7 +49,7 @@ Without access to {% data variables.product.prodname_copilot_workspace %} you ca
To work on a pull request in {% data variables.product.prodname_copilot_workspace %}:
-1. Click the **{% octicon "copilot" aria-hidden="true" %} Open in {% data variables.product.prodname_copilot_workspace_short %}** button on the right side of the main page of a pull request.
+1. Click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Open in {% data variables.product.prodname_copilot_workspace_short %}** button on the right side of the main page of a pull request.
{% data variables.product.prodname_copilot_workspace %} opens, displaying an overview of the pull request.
@@ -146,9 +146,9 @@ You can type commands directly into the terminal, or you can use quick commands
You can configure **Build**, **Run**, and **Test** commands that you can use when you work on a specific project in {% data variables.product.prodname_copilot_workspace %}. If commands have already been configured for the repository, you can replace them with alternative commands for your own personal use.
-1. At the top of the {% data variables.product.prodname_copilot_workspace_short %} window, click **{% octicon "gear" aria-hidden="true" %} Configure**.
+1. At the top of the {% data variables.product.prodname_copilot_workspace_short %} window, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Configure**.
- If **Build**, **Run**, and **Test** quick commands have already been defined, the **{% octicon "play" aria-hidden="true" %} Build** button is displayed instead of **{% octicon "gear" aria-hidden="true" %} Configure**. Click the dropdown arrow beside the **{% octicon "play" aria-hidden="true" %} Build** button and then click **{% octicon "gear" aria-hidden="true" %} Configure** from the dropdown menu.
+ If **Build**, **Run**, and **Test** quick commands have already been defined, the **{% octicon "play" aria-hidden="true" aria-label="play" %} Build** button is displayed instead of **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Configure**. Click the dropdown arrow beside the **{% octicon "play" aria-hidden="true" aria-label="play" %} Build** button and then click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Configure** from the dropdown menu.
@@ -200,7 +200,7 @@ You can change how files are displayed in {% data variables.product.prodname_cop
### Changing the diff view
-1. Click the compare picker icon ({% octicon "git-compare" aria-hidden="true" %}), at the top right of the {% data variables.product.prodname_copilot_workspace_short %} editor panel.
+1. Click the compare picker icon ({% octicon "git-compare" aria-hidden="true" aria-label="git-compare" %}), at the top right of the {% data variables.product.prodname_copilot_workspace_short %} editor panel.
1. Choose a view option:
* **Unified** - Shows changes in a single view, with added lines highlighted in green and removed lines highlighted in red.
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 065aee374ca5..7824fe64fb6b 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
@@ -12,7 +12,7 @@ versions:
ghes: '*'
---
-Download {% data variables.product.prodname_desktop %} {% octicon "link-external" height:16 %}
+Download {% data variables.product.prodname_desktop %} {% octicon "link-external" height:16 aria-label="link-external" %}
## About {% data variables.product.prodname_desktop %} installation
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 78468ba220bb..b29ba610d0ba 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
@@ -22,7 +22,7 @@ Repository administrators can enable rulesets for a branch to enforce specific c
## Choosing a branch and making changes
-1. [Create a new branch](/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking **{% octicon "git-branch" aria-hidden="true" %} Current Branch** on the toolbar and selecting the branch from the list.
+1. [Create a new branch](/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch** on the toolbar and selecting the branch from the list.
{% data reusables.desktop.make-changes %}
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 a7ff97d321e6..43c189a789f3 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
@@ -58,7 +58,7 @@ Repository administrators can also enable rulesets. Rulesets can be used to requ
If you create a branch in {% data variables.product.prodname_desktop %}, you'll need to publish the branch to make it available for collaboration on {% data variables.product.github %}.
-1. In the repository bar, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch**, then click the branch that you want to publish.
+1. In the repository bar, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch**, then click the branch that you want to publish.
1. Click **Publish branch**.
@@ -70,7 +70,7 @@ You can view and make commits to any of your repository's branches. If you have
> [!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.
+1. In the repository bar, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch**, then click the branch that you want to switch to.
1. If you have saved, uncommitted changes, in the "Switch Branch" window, select **Leave my changes on CURRENT-BRANCH** or **Bring my changes to NEW-BRANCH**, then click **Switch Branch**.
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 fd7cd056d1a2..967aeb542f0f 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
@@ -24,7 +24,7 @@ Checking out a commit puts your repository in a "detached HEAD" state. In Git te
{% data reusables.desktop.history-tab %}
1. Right-click on the commit you would like to checkout and select **Checkout commit**.
-1. The **{% octicon "git-branch" aria-hidden="true" %} Current Branch** item in the repository bar will now show "Detached HEAD", along with the SHA of the commit that was checked out.
+1. The **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch** item in the repository bar will now show "Detached HEAD", along with the SHA of the commit that was checked out.
1. To exit the "detached HEAD" state you will need to switch branches. For more information, see [AUTOTITLE](/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop#switching-between-branches).
diff --git a/content/desktop/managing-commits/cherry-picking-a-commit-in-github-desktop.md b/content/desktop/managing-commits/cherry-picking-a-commit-in-github-desktop.md
index 41a9b7447765..091afc6ea38e 100644
--- a/content/desktop/managing-commits/cherry-picking-a-commit-in-github-desktop.md
+++ b/content/desktop/managing-commits/cherry-picking-a-commit-in-github-desktop.md
@@ -39,7 +39,7 @@ You can also use cherry-picking when collaborating with a team. Some projects in
{% endwindows %}
-1. Right-click the selected commit and click **Cherry pick commit**, then select the branch that you want to copy the commit to. You can also drag the commit that you want to cherry-pick from the "History" tab to the **{% octicon "git-branch" aria-hidden="true" %} Current Branch** dropdown menu, then drop the commit on the branch that you want to copy the commit to.
+1. Right-click the selected commit and click **Cherry pick commit**, then select the branch that you want to copy the commit to. You can also drag the commit that you want to cherry-pick from the "History" tab to the **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch** dropdown menu, then drop the commit on the branch that you want to copy the commit to.
diff --git a/content/desktop/overview/about-github-desktop.md b/content/desktop/overview/about-github-desktop.md
index 80813bbc8a57..401ecc01cfa5 100644
--- a/content/desktop/overview/about-github-desktop.md
+++ b/content/desktop/overview/about-github-desktop.md
@@ -13,7 +13,7 @@ redirect_from:
- /get-started/using-github/github-desktop
---
-Download {% data variables.product.prodname_desktop %} {% octicon "link-external" height:16 %}
+Download {% data variables.product.prodname_desktop %} {% octicon "link-external" height:16 aria-label="link-external" %}
## About {% data variables.product.prodname_desktop %}
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 dbd36534a811..e1e237480612 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
@@ -25,7 +25,7 @@ Some workflows require or benefit from rebasing instead of merging. By rebasing
## Pulling to your local branch from the remote
-1. In {% data variables.product.prodname_desktop %}, use the **{% octicon "git-branch" aria-hidden="true" %} Current Branch** drop-down, and select the local branch you want to update.
+1. In {% data variables.product.prodname_desktop %}, use the **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch** drop-down, and select the local branch you want to update.
1. To check for commits on the remote branch, click **Fetch origin**
diff --git a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
index 3aef6ce99b3d..1283d747b5f0 100644
--- a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
+++ b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
@@ -41,7 +41,7 @@ You cannot comment on a pull request from {% data variables.product.prodname_des
{% data reusables.repositories.sidebar-pr %}
1. In the list of pull requests, click the pull request that you would like to open in {% data variables.product.prodname_desktop %}.
-1. To the right of the title of the pull request, click **{% octicon "code" aria-hidden="true" %} Code**, then, on the **Local** tab, click **Checkout with GitHub Desktop**.
+1. To the right of the title of the pull request, click **{% octicon "code" aria-hidden="true" aria-label="code" %} Code**, then, on the **Local** tab, click **Checkout with GitHub Desktop**.
diff --git a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md
index 52163a53cf8b..c9bc4696cde9 100644
--- a/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md
+++ b/content/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md
@@ -23,7 +23,7 @@ redirect_from:
1. Click on the pull request number, to the right of the pull request branch name.
-1. To re-run failed checks, click **{% octicon "sync" aria-hidden="true" %} Re-run** and select **Re-run Failed Checks**.
+1. To re-run failed checks, click **{% octicon "sync" aria-hidden="true" aria-label="sync" %} Re-run** and select **Re-run Failed Checks**.
1. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check.
diff --git a/content/discussions/guides/finding-your-discussions.md b/content/discussions/guides/finding-your-discussions.md
index 25d04fd0afe2..7c64777a9c75 100644
--- a/content/discussions/guides/finding-your-discussions.md
+++ b/content/discussions/guides/finding-your-discussions.md
@@ -12,7 +12,7 @@ redirect_from:
## Finding discussions
-1. In the top-left corner of {% data variables.product.prodname_dotcom %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "comment-discussion" aria-hidden="true" %} Discussions**.
+1. In the top-left corner of {% data variables.product.prodname_dotcom %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Discussions**.
diff --git a/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index cb0bc567f7eb..714321eb8065 100644
--- a/content/discussions/managing-discussions-for-your-community/managing-discussions.md
+++ b/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -61,7 +61,7 @@ You can pin up to four important discussions above the list of discussions for t
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" %} Pin discussion**.
+1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" aria-label="pin" %} Pin discussion**.
@@ -75,7 +75,7 @@ You can pin up to four important discussions above the list of discussions in a
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" %} Pin discussion to CATEGORY**.
+1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" aria-label="pin" %} Pin discussion to CATEGORY**.
@@ -88,7 +88,7 @@ Editing a pinned discussion will not change the discussion's category. For more
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click **{% octicon "pencil" aria-hidden="true" %} Edit pinned discussion**.
+1. In the right sidebar, click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit pinned discussion**.
1. Customize the look of the pinned discussion.
@@ -105,7 +105,7 @@ You can unpin a globally pinned discussion. This will not delete the discussion,
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" %} Unpin discussion**.
+1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" aria-label="pin" %} Unpin discussion**.
@@ -118,7 +118,7 @@ You can unpin a discussion pinned to a specific category. This will not delete t
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" %} Unpin discussion from this category**.
+1. In the right sidebar, click **{% octicon "pin" aria-hidden="true" aria-label="pin" %} Unpin discussion from this category**.
@@ -131,7 +131,7 @@ To transfer a discussion, you must have permissions to create discussions in the
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "arrow-right" aria-hidden="true" %}**Transfer this discussion**.
+1. In the right sidebar, click {% octicon "arrow-right" aria-hidden="true" aria-label="arrow-right" %}**Transfer this discussion**.
@@ -143,7 +143,7 @@ To transfer a discussion, you must have permissions to create discussions in the
{% data reusables.discussions.navigate-to-repo-or-org %}
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click **{% octicon "trash" aria-hidden="true" %} Delete discussion**.
+1. In the right sidebar, click **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete discussion**.
diff --git a/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
index d0f8c24c40bc..c08e0f06c15a 100644
--- a/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
+++ b/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
@@ -30,13 +30,13 @@ You can star repositories listed in the {% data variables.product.prodname_commu
Repository listings in the {% data variables.product.prodname_community_exchange %} gallery can be sorted on the number of stars a repository has.
-To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click **{% octicon "star" aria-hidden="true" %} Star** button found right by its name.
+To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click **{% octicon "star" aria-hidden="true" aria-label="star" %} Star** button found right by its name.
## Reporting abuse
The {% data variables.product.prodname_community_exchange %} community moderates repository submissions. You can report abusive repositories, spammy, or disruptive content at any time.
-To report an abusive repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to report, click the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down right by its name, then click **{% octicon "report" aria-hidden="true" %} Report abuse**.
+To report an abusive repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to report, click the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down right by its name, then click **{% octicon "report" aria-hidden="true" aria-label="report" %} Report abuse**.
## Further reading
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 68cd5a1e1f9f..214a0dd8677c 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
@@ -72,7 +72,7 @@ If you use a template repository for an assignment, you can define a dev contain
When a student opens an assignment, the repository's README file includes their teacher's recommendation of the IDE they should use for the work.
-Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-hidden="true" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. See [AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
+Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. See [AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
diff --git a/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/viewing-your-assignments-deadline.md b/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/viewing-your-assignments-deadline.md
index ab558f1287a1..fb34eb9d120a 100644
--- a/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/viewing-your-assignments-deadline.md
+++ b/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/viewing-your-assignments-deadline.md
@@ -13,4 +13,4 @@ Your teacher can set an assignment deadline for assignments on {% data variables
## Viewing an assignment's deadline
1. Navigate to your assignment repository.
-1. On the main page of your repository, scroll down until you see the repository's README, then click **{% octicon "calendar" aria-hidden="true" %} Review the assignment due date**. Your assignment deadline is visible below the link to your assignment repository. The deadline shown updates automatically any time your teacher alters the assignment deadline.
+1. On the main page of your repository, scroll down until you see the repository's README, then click **{% octicon "calendar" aria-hidden="true" aria-label="calendar" %} Review the assignment due date**. Your assignment deadline is visible below the link to your assignment repository. The deadline shown updates automatically any time your teacher alters the assignment deadline.
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 02d6395e12bc..9ef19858946e 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
@@ -14,7 +14,7 @@ After creating an assignment, you can edit many aspects of the assignment to bet
{% data reusables.classroom.sign-into-github-classroom %}
{% 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" %}.
+1. In the **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Assignments** tab, next to the assignment you would like to edit, click {% octicon "pencil" aria-label="The pencil icon" %}.
> [!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.
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 15916f0f192a..139db522a28b 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
@@ -19,11 +19,11 @@ If you set a cutoff date for an assignment in {% data variables.product.prodname
{% data reusables.classroom.sign-into-github-classroom %}
1. Navigate to your classroom.
1. Open the assignment for which you would like to grant an extension.
-1. In your classroom's roster, find the student or group you would like to grant an extension. In that student or group's row, select {% octicon "kebab-horizontal" aria-label="the dropdown menu" %}, then click **{% octicon "calendar" aria-hidden="true" %} Extend deadline**.
+1. In your classroom's roster, find the student or group you would like to grant an extension. In that student or group's row, select {% octicon "kebab-horizontal" aria-label="the dropdown menu" %}, then click **{% octicon "calendar" aria-hidden="true" aria-label="calendar" %} Extend deadline**.
1. In the modal that appears, select **Extend STUDENT OR GROUP'S assignment deadline**, then click **I understand, extend the deadline**. A "Deadline extended" label will appear next to that student or group's name in the classroom roster.
-1. Optionally, to revoke an extension, select {% octicon "kebab-horizontal" aria-label="the dropdown menu" %}, then click **{% octicon "calendar" aria-hidden="true" %} Revoke extension**.
+1. Optionally, to revoke an extension, select {% octicon "kebab-horizontal" aria-label="the dropdown menu" %}, then click **{% octicon "calendar" aria-hidden="true" aria-label="calendar" %} Revoke extension**.
In the modal that appears, select **Revoke STUDENT OR GROUP'S assignment extension**, then click **I understand, revoke the extension**. The "Deadline extended" label will be removed from the student or group's entry in the classroom roster.
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/monitor-students-progress-with-the-assignment-overview-page.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/monitor-students-progress-with-the-assignment-overview-page.md
index b466ae4c9ffd..d16ae6deeeda 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/monitor-students-progress-with-the-assignment-overview-page.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/monitor-students-progress-with-the-assignment-overview-page.md
@@ -45,7 +45,7 @@ You can search and sort the assignment overview page to find specific students o
1. To find a specific student or team on the assignment overview page, in the search bar, type the student's {% data variables.product.prodname_dotcom %} handle, the student's identifier, or the team's name, then press Enter or Return.
If the search term you enter matches multiple students or teams, each student or team will be shown in the search results. For example, if you have two students with the {% data variables.product.prodname_dotcom %} handles "@octocat" and "@monacat", and you search for "cat", both "@octocat" and "@monacat" will appear in the search results.
-1. To sort the students or teams displayed on an assignment overview page, select **Sort by:** {% octicon "triangle-down" aria-hidden="true" %}, then click **Alphabetical A-Z**, **Alphabetical Z-A**, **Newest**, or **Oldest**.
+1. To sort the students or teams displayed on an assignment overview page, select **Sort by:** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click **Alphabetical A-Z**, **Alphabetical Z-A**, **Newest**, or **Oldest**.
The **Newest** sort orders the results from the most recently updated assignment to the least recently updated assignment, while the **Oldest** sort does the opposite.
{% data reusables.classroom.clear-all-assignment-overview %}
@@ -54,11 +54,11 @@ You can search and sort the assignment overview page to find specific students o
Using a series of dropdown menus, you can apply multiple filters to the assignment overview page to search for students or teams based on specific criteria. You can even apply multiple filters from a single dropdown menu to include all students or teams that match the criteria.
-1. To filter for students with unlinked accounts, select the **Unlinked accounts** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Student identifiers** or **{% data variables.product.prodname_dotcom %} accounts**.
-1. To filter by which students have or haven't accepted the assignment, select the **Accepted** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Accepted** or **Unaccepted**.
-1. To filter by the submission status for each student's assignment repository, select the **Submitted** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Submitted**, **On-time**, **Late**, or **Not submitted**.
-1. To filter for students by passing or failing grades, select the **Passing** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Passing** or **Failing**.
-1. To unapply a filter, select the associated dropdown menu, then click the filter once more. A {% octicon "check" aria-hidden="true" %} is displayed alongside the name of an applied filter, while unapplied filters only display their names.
+1. To filter for students with unlinked accounts, select the **Unlinked accounts** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Student identifiers** or **{% data variables.product.prodname_dotcom %} accounts**.
+1. To filter by which students have or haven't accepted the assignment, select the **Accepted** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Accepted** or **Unaccepted**.
+1. To filter by the submission status for each student's assignment repository, select the **Submitted** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Submitted**, **On-time**, **Late**, or **Not submitted**.
+1. To filter for students by passing or failing grades, select the **Passing** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Passing** or **Failing**.
+1. To unapply a filter, select the associated dropdown menu, then click the filter once more. A {% octicon "check" aria-hidden="true" aria-label="check" %} is displayed alongside the name of an applied filter, while unapplied filters only display their names.
{% data reusables.classroom.clear-all-assignment-overview %}
## Downloading assignment details
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
index b287b81f31fb..cbd48600d915 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
@@ -18,7 +18,7 @@ The copied assignment includes assignment details such as the name, source repos
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
1. Navigate to the classroom that has the assignment that you want to reuse.
1. In the list of assignments, click the assignment you want to reuse.
-1. Select the **{% octicon "pencil" aria-hidden="true" %} Edit** dropdown menu in the top right of the page, then click **{% octicon "sync" aria-hidden="true" %} Reuse assignment**.
+1. Select the **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit** dropdown menu in the top right of the page, then click **{% octicon "sync" aria-hidden="true" aria-label="sync" %} Reuse assignment**.
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
index 9c38e42ecbe9..1e35a28e41c7 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
@@ -21,13 +21,13 @@ The Git & {% data variables.product.company_short %} starter assignment is a pre
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
1. Navigate to a classroom.
-1. In the **{% octicon "repo" aria-hidden="true" %} Assignments** tab, click **Use starter assignment**.
+1. In the **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Assignments** tab, click **Use starter assignment**.
### If there already are existing assignments in the classroom
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
1. Navigate to a classroom.
-1. In the **{% octicon "repo" aria-hidden="true" %} Assignments** tab, click the link in the blue banner.
+1. In the **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Assignments** tab, click the link in the blue banner.
## Setting up the basics for an assignment
diff --git a/content/enterprise-onboarding/getting-started-with-your-enterprise/ending-a-trial-of-github-enterprise.md b/content/enterprise-onboarding/getting-started-with-your-enterprise/ending-a-trial-of-github-enterprise.md
index c56b57a65f1a..1afacc4a6651 100644
--- a/content/enterprise-onboarding/getting-started-with-your-enterprise/ending-a-trial-of-github-enterprise.md
+++ b/content/enterprise-onboarding/getting-started-with-your-enterprise/ending-a-trial-of-github-enterprise.md
@@ -46,7 +46,7 @@ You can cancel a trial at any time. Once the trial has expired, you can delete t
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Profile**.
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Profile**.
1. At the bottom of the page, in the "Danger zone" section, click **Cancel trial** or **Delete trial**.
## Next steps
diff --git a/content/enterprise-onboarding/getting-started-with-your-enterprise/setting-up-a-trial-of-github-enterprise.md b/content/enterprise-onboarding/getting-started-with-your-enterprise/setting-up-a-trial-of-github-enterprise.md
index 9a949c1745d7..b69e7548e7de 100644
--- a/content/enterprise-onboarding/getting-started-with-your-enterprise/setting-up-a-trial-of-github-enterprise.md
+++ b/content/enterprise-onboarding/getting-started-with-your-enterprise/setting-up-a-trial-of-github-enterprise.md
@@ -49,7 +49,7 @@ You do not need to provide a payment method to start a trial. If you want to use
Go to the trial page and follow the instructions to sign up for the trial.
-Try {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 %}
+Try {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 aria-label="link-external" %}
When setting up your trial of GitHub Enterprise Cloud, you'll choose an enterprise type.
diff --git a/content/get-started/exploring-projects-on-github/using-github-copilot-to-explore-projects.md b/content/get-started/exploring-projects-on-github/using-github-copilot-to-explore-projects.md
index aeedeb8bd129..af8f46c03c0b 100644
--- a/content/get-started/exploring-projects-on-github/using-github-copilot-to-explore-projects.md
+++ b/content/get-started/exploring-projects-on-github/using-github-copilot-to-explore-projects.md
@@ -21,7 +21,7 @@ When you’re new to a project, it can be challenging to understand the purpose
1. On the {% data variables.product.prodname_dotcom %} website, go to the repository you want to chat about.
-1. Click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon at the top right of the page.
+1. Click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon at the top right of the page.
1. The heading at the top of the chat panel should read "Chatting about" followed by the name of the current repository.
If the wrong repository name is displayed, because you were previously chatting about another repository, click **All repositories** then choose the repository you want to chat about.
diff --git a/content/get-started/learning-to-code/finding-and-understanding-example-code.md b/content/get-started/learning-to-code/finding-and-understanding-example-code.md
index e55f7db77944..2ef11e8aced6 100644
--- a/content/get-started/learning-to-code/finding-and-understanding-example-code.md
+++ b/content/get-started/learning-to-code/finding-and-understanding-example-code.md
@@ -71,7 +71,7 @@ In the [`github/choosealicense.com`](https://github.com/github/choosealicense.co
If the README.md file doesn't give you all the answers, you can ask {% data variables.product.prodname_copilot_short %} to help you navigate the repository and locate functionality.
-To open {% data variables.product.prodname_copilot_chat_short %}, click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon next to the search bar and ask your question. For example:
+To open {% data variables.product.prodname_copilot_chat_short %}, click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon next to the search bar and ask your question. For example:
>What is the main landing page for this Jekyll website?
@@ -79,7 +79,7 @@ When you ask {% data variables.product.prodname_copilot_short %} questions about
### The repository's wiki
-Another possible source of information is the repository's **wiki**, a section of the repository specifically for hosting documentation. Every repository on {% data variables.product.github %} comes equipped with the ability to use a wiki, but not every repository uses it. To access the wiki, click the **{% octicon "book" aria-hidden="true" %} Wiki** tab in the repository.
+Another possible source of information is the repository's **wiki**, a section of the repository specifically for hosting documentation. Every repository on {% data variables.product.github %} comes equipped with the ability to use a wiki, but not every repository uses it. To access the wiki, click the **{% octicon "book" aria-hidden="true" aria-label="book" %} Wiki** tab in the repository.
### Releases
diff --git a/content/get-started/learning-to-code/getting-started-with-git.md b/content/get-started/learning-to-code/getting-started-with-git.md
index 2e78728ee291..deabb1e39b3e 100644
--- a/content/get-started/learning-to-code/getting-started-with-git.md
+++ b/content/get-started/learning-to-code/getting-started-with-git.md
@@ -63,7 +63,7 @@ When you create a new branch, you're creating a safe space to work on a new feat
Let's create a branch to work on changes in our repository:
-1. In {% data variables.product.prodname_desktop %}, select the {% octicon "git-branch" aria-hidden="true" %} **Current Branch** dropdown menu, then click **New Branch**.
+1. In {% data variables.product.prodname_desktop %}, select the {% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} **Current Branch** dropdown menu, then click **New Branch**.
1. Name your new branch `readme-updates`, then click **Create Branch**.
### Saving snapshots of your project
@@ -103,7 +103,7 @@ When you're happy with the changes you've made on a branch, you can publish your
Congratulations on merging your first pull request! Now that you've successfully brought your changes into the `main` branch, there are a few steps you should take to get ready for your next round of changes:
-1. In {% data variables.product.prodname_desktop %}, if you aren't on the `main` branch, select the {% octicon "git-branch" aria-hidden="true" %} **Current Branch** dropdown menu, then click **main**.
+1. In {% data variables.product.prodname_desktop %}, if you aren't on the `main` branch, select the {% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} **Current Branch** dropdown menu, then click **main**.
You should almost always switch back to the `main` branch before creating a new branch, since new branches are created as copies of the currently selected branch.
1. To check if any changes have been made to your remote `main` branch, click **Fetch origin**.
diff --git a/content/get-started/learning-to-code/reusing-other-peoples-code-in-your-projects.md b/content/get-started/learning-to-code/reusing-other-peoples-code-in-your-projects.md
index 5cf7e63fb1b2..a207086a5673 100644
--- a/content/get-started/learning-to-code/reusing-other-peoples-code-in-your-projects.md
+++ b/content/get-started/learning-to-code/reusing-other-peoples-code-in-your-projects.md
@@ -52,7 +52,7 @@ Explain this program.
Before you can reuse the code you've found, you need to understand its licensing. Licenses determine how you can use the code in a project, including your ability to copy, modify, and distribute that code.
-To identify the license for [new2code/python-factorial](https://github.com/new2code/python-factorial), locate the "About" section on the repository's main page. There, you'll see that the repository is licensed under the MIT license. To read the license, click {% octicon "law" aria-hidden="true" %} **MIT license**.
+To identify the license for [new2code/python-factorial](https://github.com/new2code/python-factorial), locate the "About" section on the repository's main page. There, you'll see that the repository is licensed under the MIT license. To read the license, click {% octicon "law" aria-hidden="true" aria-label="law" %} **MIT license**.
diff --git a/content/get-started/learning-to-code/setting-up-copilot-for-learning-to-code.md b/content/get-started/learning-to-code/setting-up-copilot-for-learning-to-code.md
index bcf9989d65b5..f94d901ab3f2 100644
--- a/content/get-started/learning-to-code/setting-up-copilot-for-learning-to-code.md
+++ b/content/get-started/learning-to-code/setting-up-copilot-for-learning-to-code.md
@@ -63,7 +63,7 @@ You're ready to start building real coding skills with {% data variables.product
Throughout your work on the project, engage in a long-running conversation with **{% data variables.product.prodname_copilot_chat_short %}**. Treat it as your **personal tutor**, asking questions as they arise and using it to navigate challenges or clarify concepts.
-Open {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode_shortname %} {% octicon "link-external" height:16 %}
+Open {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode_shortname %} {% octicon "link-external" height:16 aria-label="link-external" %}
{% data variables.product.prodname_copilot_chat_short %} is especially helpful for debugging your code. For step-by-step guidance, see [AUTOTITLE](/get-started/learning-to-code/learning-to-debug-with-github-copilot).
diff --git a/content/get-started/learning-to-code/storing-your-secrets-safely.md b/content/get-started/learning-to-code/storing-your-secrets-safely.md
index 08a43767fa0e..5fd2d3bf4916 100644
--- a/content/get-started/learning-to-code/storing-your-secrets-safely.md
+++ b/content/get-started/learning-to-code/storing-your-secrets-safely.md
@@ -136,7 +136,7 @@ Your secret is now safely encrypted and ready to use!
Now we can update the YAML workflow file to use the token and test it works.
-1. Navigate back to your repository. If you're in your repository's settings, you can click **{% octicon "code" aria-hidden="true" %} Code** under the repository name.
+1. Navigate back to your repository. If you're in your repository's settings, you can click **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** under the repository name.
1. Navigate to the YAML workflow file by clicking `.github/workflows` in the list of files.
1. Open the workflow file by clicking `comment.yml` in the list of files.
1. To start editing the workflow file, at the top-right, click {% octicon "pencil" aria-label="Edit this file" %}.
diff --git a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index f3af361315ec..57a06c522f52 100644
--- a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -33,7 +33,7 @@ An enterprise account allows you to centrally manage policy and settings for mul
To create your enterprise account, start a free 30-day trial of {% data variables.product.prodname_ghe_cloud %}. For more information, see [AUTOTITLE](/admin/overview/setting-up-a-trial-of-github-enterprise-cloud).
-Try {% data variables.product.prodname_ghe_cloud %} for free {% octicon "link-external" height:16 %}
+Try {% data variables.product.prodname_ghe_cloud %} for free {% octicon "link-external" height:16 aria-label="link-external" %}
### 4. Adding organizations to your enterprise account
diff --git a/content/get-started/onboarding/getting-started-with-the-github-enterprise-cloud-trial.md b/content/get-started/onboarding/getting-started-with-the-github-enterprise-cloud-trial.md
index 0d01f13d1767..433b937ebf0e 100644
--- a/content/get-started/onboarding/getting-started-with-the-github-enterprise-cloud-trial.md
+++ b/content/get-started/onboarding/getting-started-with-the-github-enterprise-cloud-trial.md
@@ -18,7 +18,7 @@ For full details of what is included in the trial, and what happens during, and
Go to the trial sign up page and follow the instructions on screen to sign up for the trial.
-Try {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 %}
+Try {% data variables.product.prodname_ghe_cloud %} {% octicon "link-external" height:16 aria-label="link-external" %}
## Part 2: Setting up {% data variables.product.prodname_ghe_cloud %}
diff --git a/content/get-started/start-your-journey/finding-inspiration-on-github.md b/content/get-started/start-your-journey/finding-inspiration-on-github.md
index 48b7c02c1bab..01d2c36473ec 100644
--- a/content/get-started/start-your-journey/finding-inspiration-on-github.md
+++ b/content/get-started/start-your-journey/finding-inspiration-on-github.md
@@ -36,7 +36,7 @@ Once you star repositories or follow people, you will see updates on their activ
1. Navigate to {% data variables.explore.explore_github %}.
1. Browse popular repositories and topics.
-1. Click **{% octicon "star" aria-hidden="true" %} Star** next to repositories and topics that interest you, so you can easily find them again later.
+1. Click **{% octicon "star" aria-hidden="true" aria-label="star" %} Star** next to repositories and topics that interest you, so you can easily find them again later.
1. Navigate to your {% data variables.explore.your_stars_page %} to see all your starred repositories and topics.
## Search for a topic or project on {% data variables.product.github %}
diff --git a/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/content/get-started/using-git/getting-changes-from-a-remote-repository.md
index 19c18406d750..ce54de94c301 100644
--- a/content/get-started/using-git/getting-changes-from-a-remote-repository.md
+++ b/content/get-started/using-git/getting-changes-from-a-remote-repository.md
@@ -26,7 +26,7 @@ $ git clone https://{% data variables.product.product_url %}/USERNAME/REPOSITORY
# Clones a repository to your computer
```
-You can choose from [several different URLs](/get-started/git-basics/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available on the main page of the repository when you click **{% octicon "code" aria-hidden="true" %} Code**.
+You can choose from [several different URLs](/get-started/git-basics/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available on the main page of the repository when you click **{% octicon "code" aria-hidden="true" aria-label="code" %} Code**.
diff --git a/content/get-started/using-github/communicating-on-github.md b/content/get-started/using-github/communicating-on-github.md
index 991b459cee9c..f6eeefc74e07 100644
--- a/content/get-started/using-github/communicating-on-github.md
+++ b/content/get-started/using-github/communicating-on-github.md
@@ -121,7 +121,7 @@ If you need more context or clarity on a specific issue or discussion, you can u
To ask a question about an issue or discussion:
-1. From anywhere on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon next to the search bar in the top right of the page.
+1. From anywhere on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon next to the search bar in the top right of the page.
diff --git a/content/get-started/using-github/github-mobile.md b/content/get-started/using-github/github-mobile.md
index a34e3de06c3b..37f780d77038 100644
--- a/content/get-started/using-github/github-mobile.md
+++ b/content/get-started/using-github/github-mobile.md
@@ -66,13 +66,13 @@ During the {% data variables.release-phases.public_preview %} for {% data variab
### Adding, switching, or signing out of accounts
-You can sign into mobile with any {% data variables.product.github %} account, on {% data variables.product.prodname_dotcom_the_website %}, on {% data variables.enterprise.data_residency_domain %}, or on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press **{% octicon "person" aria-hidden="true" %} Profile**, then tap **{% octicon "plus" aria-hidden="true" %} Add Enterprise Account**. Follow the prompts to sign in.
+You can sign into mobile with any {% data variables.product.github %} account, on {% data variables.product.prodname_dotcom_the_website %}, on {% data variables.enterprise.data_residency_domain %}, or on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press **{% octicon "person" aria-hidden="true" aria-label="person" %} Profile**, then tap **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add Enterprise Account**. Follow the prompts to sign in.
-After signing in with a second account, you can switch between the accounts you're currently logged into within the app. At the bottom of the app, long-press **{% octicon "person" aria-hidden="true" %} Profile**, then tap the account you want to switch to.
+After signing in with a second account, you can switch between the accounts you're currently logged into within the app. At the bottom of the app, long-press **{% octicon "person" aria-hidden="true" aria-label="person" %} Profile**, then tap the account you want to switch to.
-If you no longer need to access an account using {% data variables.product.prodname_mobile %}, you can sign out of that account. At the bottom of the app, long-press **{% octicon "person" aria-hidden="true" %} Profile**, swipe left on the account to sign out of, then tap **Sign out**.
+If you no longer need to access an account using {% data variables.product.prodname_mobile %}, you can sign out of that account. At the bottom of the app, long-press **{% octicon "person" aria-hidden="true" aria-label="person" %} Profile**, swipe left on the account to sign out of, then tap **Sign out**.
-Alternatively, once logged into one account, access the account switcher to log into other accounts or log out of an existing account by navigating to the **{% octicon "person" aria-hidden="true" %} Profile** tab, then tapping {% octicon "gear" aria-hidden="true" %}, and then tapping **Manage Accounts**.
+Alternatively, once logged into one account, access the account switcher to log into other accounts or log out of an existing account by navigating to the **{% octicon "person" aria-hidden="true" aria-label="person" %} Profile** tab, then tapping {% octicon "gear" aria-hidden="true" aria-label="gear" %}, and then tapping **Manage Accounts**.
## Supported languages for {% data variables.product.prodname_mobile %}
diff --git a/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/moderating-gist-comments.md b/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/moderating-gist-comments.md
index 1e2a3df5c860..7c265154fb97 100644
--- a/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/moderating-gist-comments.md
+++ b/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/moderating-gist-comments.md
@@ -11,8 +11,8 @@ versions:
You can hide existing comments and prevent new comments from being added to a gist by disabling comments for the gist. You can re-enable comments at any time. This will make existing comments visible.
1. Navigate to {% data variables.gists.gist_user %} and select the gist you want to moderate.
-1. In the top right corner, select **{% octicon "pencil" aria-hidden="true" %} Edit**.
-1. In the top right corner, select **{% octicon "comment" aria-hidden="true" %} Disable comments**.
+1. In the top right corner, select **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit**.
+1. In the top right corner, select **{% octicon "comment" aria-hidden="true" aria-label="comment" %} Disable comments**.
## Deleting comments
diff --git a/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/saving-gists-with-stars.md b/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/saving-gists-with-stars.md
index 2082495f29a6..6ab75c113eed 100644
--- a/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/saving-gists-with-stars.md
+++ b/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/saving-gists-with-stars.md
@@ -11,11 +11,11 @@ versions:
You can star a gist to add it to the "Starred" page. Starring makes it easy to find a gist again later.
1. Navigate to {% data variables.gists.discover_url %} and select the gist you want to star.
-1. To star the gist, click **{% octicon "star" aria-hidden="true" %} Star** in the top-right corner of the page.
+1. To star the gist, click **{% octicon "star" aria-hidden="true" aria-label="star" %} Star** in the top-right corner of the page.
-1. Optionally, to unstar a previously starred gist, click **{% octicon "star-fill" aria-hidden="true" %} Unstar**. This will remove the gist from your starred list.
+1. Optionally, to unstar a previously starred gist, click **{% octicon "star-fill" aria-hidden="true" aria-label="star-fill" %} Unstar**. This will remove the gist from your starred list.
## Viewing your starred gists
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 089617dd060a..b110fc0797ed 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
@@ -28,7 +28,7 @@ This type of permanent link will render as a code snippet only in the repository
{% data reusables.repositories.navigate-to-repo %}
1. Locate the code you'd like to link to:
* To link to code from a file, navigate to the file.
- * To link to code from a pull request, navigate to the pull request and click **{% octicon "diff" aria-hidden="true" %} Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**.
+ * To link to code from a pull request, navigate to the pull request and click **{% octicon "diff" aria-hidden="true" aria-label="diff" %} Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**.
{% data reusables.repositories.choose-line-or-range %}
1. To the left of the line or range of lines, click {% octicon "kebab-horizontal" aria-label="Code line X options" %}. In the drop-down menu, click **Copy permalink**.
diff --git a/content/github-models/use-github-models/optimizing-your-ai-powered-app-with-github-models.md b/content/github-models/use-github-models/optimizing-your-ai-powered-app-with-github-models.md
index cb0be906ebe5..6306f91dd388 100644
--- a/content/github-models/use-github-models/optimizing-your-ai-powered-app-with-github-models.md
+++ b/content/github-models/use-github-models/optimizing-your-ai-powered-app-with-github-models.md
@@ -33,7 +33,7 @@ You can access the **Comparisons** view directly from the **Models** tab in any
### 2. Creating a new prompt
1. On the main page of your new repository, click the **Models** tab.
-1. In the "Prompts" section, click **{% octicon "plus" aria-hidden="true" %} New Prompt**.
+1. In the "Prompts" section, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} New Prompt**.
1. In the upper-left corner, choose a model from the dropdown menu.
### 3. Writing a system prompt
@@ -68,7 +68,7 @@ When should I use rebase or merge?
### 6. Running the sample prompt
-1. In the upper-right corner, click **{% octicon "play" aria-hidden="true" %} Play**.
+1. In the upper-right corner, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Play**.
1. Make a change to the model or prompt, then run the prompt again to see what results you get.
## Testing different models against a prompt
@@ -76,29 +76,29 @@ When should I use rebase or merge?
Now, let's determine which model will work best for our application, using the **Comparisons** view. This view allows you to test different models on the same input, revealing differences in accuracy, creativity, tone, reasoning, and reliability. That will help us choose the model that best fits our needs in terms of quality, speed, cost, and consistency.
1. In the upper-left corner, click **Comparisons**.
-1. To compare different models, click **{% octicon "plus" aria-hidden="true" %} Add prompt** and select **{% octicon "repo-forked" aria-hidden="true" %} Copy original prompt** to duplicate your existing system and user prompts. Create at least two copies of the original prompt to evaluate three different models.
-1. Next to each prompt, click {% octicon "pencil" aria-hidden="Edit prompt" %}. From the **Model** dropdown, choose a different model for each prompt you created.
-1. Click **{% octicon "plus" aria-hidden="true" %} Add inputs** to create new rows for sample inputs.
+1. To compare different models, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add prompt** and select **{% octicon "repo-forked" aria-hidden="true" aria-label="repo-forked" %} Copy original prompt** to duplicate your existing system and user prompts. Create at least two copies of the original prompt to evaluate three different models.
+1. Next to each prompt, click {% octicon "pencil" aria-hidden="Edit prompt" aria-label="pencil" %}. From the **Model** dropdown, choose a different model for each prompt you created.
+1. Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add inputs** to create new rows for sample inputs.
- * Click **{% octicon "plus" aria-hidden="true" %} Add inputs**. Then, in the "Input" field, copy and paste the following text:
+ * Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add inputs**. Then, in the "Input" field, copy and paste the following text:
```text copy
How do I modify the most recent commit message in my current branch?
```
- * Click **{% octicon "plus" aria-hidden="true" %} Add inputs** again, then paste the following input:
+ * Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add inputs** again, then paste the following input:
```text copy
How do I move a specific commit from one branch to a different branch?
```
- * Click **{% octicon "plus" aria-hidden="true" %} Add inputs** one more time, and paste this input:
+ * Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add inputs** one more time, and paste this input:
```text copy
How do I find the author of a specific commit in a repository's history?
```
-1. To run the prompts, in the upper-right corner, click **{% octicon "play" aria-hidden="true" %} Run**.
+1. To run the prompts, in the upper-right corner, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Run**.
1. Try out different models against your prompt, making note of the **Latency** and the **Input** and **Output** token usage of the different models.
## Testing prompt variations with a specific model
@@ -114,15 +114,15 @@ Now, let's use {% data variables.product.prodname_github_models %} to test promp
### 1. Adding prompt variations
-For this example scenario, select the **same model for each column**, but provide a different prompt variation by editing the "User prompt" field of our existing prompts. Next to each prompt, click {% octicon "pencil" aria-hidden="Edit prompt" %}.
+For this example scenario, select the **same model for each column**, but provide a different prompt variation by editing the "User prompt" field of our existing prompts. Next to each prompt, click {% octicon "pencil" aria-hidden="Edit prompt" aria-label="pencil" %}.
-1. Click **{% octicon "pencil" aria-hidden="Edit prompt" %}** in "Prompt 2." Then, in the "User prompt" field, copy and paste the following text:
+1. Click **{% octicon "pencil" aria-hidden="Edit prompt" aria-label="pencil" %}** in "Prompt 2." Then, in the "User prompt" field, copy and paste the following text:
```text copy
I want to learn how to use Git from the command line, but explain it to me like I am five years old. {{input}}
```
-1. Click **{% octicon "pencil" aria-hidden="Edit prompt" %}** in "Prompt 3", then paste the following input:
+1. Click **{% octicon "pencil" aria-hidden="Edit prompt" aria-label="pencil" %}** in "Prompt 3", then paste the following input:
```text copy
I want to learn how to use Git from the command line. Give me instructions in the form of a haiku. {{input}}
@@ -130,7 +130,7 @@ For this example scenario, select the **same model for each column**, but provid
### 2. Running prompt variations
-1. To run the prompts, in the upper-right corner, click **{% octicon "play" aria-hidden="true" %} Run**.
+1. To run the prompts, in the upper-right corner, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Run**.
1. Try out different prompt variations, and compare the types of output the model gives you.
## Evaluating model output
@@ -151,14 +151,14 @@ Depending on the number of prompts and models you are evaluating, the model outp
For this example scenario, let's use the **String check** evaluator to check for a string in the output.
-1. In the lower-right corner of the **Prompts** field, click **{% octicon "plus" aria-hidden="true" %} Add evaluator** and select **{% octicon "note" aria-hidden="true" %} String check**.
+1. In the lower-right corner of the **Prompts** field, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add evaluator** and select **{% octicon "note" aria-hidden="true" aria-label="note" %} String check**.
1. In the **Name** field, enter "Amend check", then copy and paste the following input for the **Value** field:
```text copy
git commit --amend
```
-1. To run the prompts, in the upper-right corner, click **{% octicon "play" aria-hidden="true" %} Run**.
+1. To run the prompts, in the upper-right corner, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Run**.
1. The prompt output will now show a **Pass** or **Fail** label, letting you know which model contained the required string.
To learn more about the pre-built evaluators like similarity, groundedness, and relevance, see [AUTOTITLE](/github-models/use-github-models/evaluating-ai-models#evaluating-outputs).
diff --git a/content/github-models/use-github-models/prototyping-with-ai-models.md b/content/github-models/use-github-models/prototyping-with-ai-models.md
index 9101ca449990..0c2af14d5668 100644
--- a/content/github-models/use-github-models/prototyping-with-ai-models.md
+++ b/content/github-models/use-github-models/prototyping-with-ai-models.md
@@ -73,7 +73,7 @@ The steps to use each model are similar. In general, you will need to:
All models can be used with the Azure AI Inference SDK, and some models support additional SDKs. If you want to easily switch between models, you should select "Azure AI Inference SDK". If you selected "REST" as the language, you won't use an SDK. Instead, you will use the API endpoint directly. {% ifversion fpt %} See [{% data variables.product.prodname_github_models %} REST API](/rest/models?apiVersion=2022-11-28). {% endif %}
1. Either open a codespace, or set up your local environment:
- * To run in a codespace, click **{% octicon "codespaces" aria-hidden="true" %} Run codespace**, then click **Create new codespace**.
+ * To run in a codespace, click **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} Run codespace**, then click **Create new codespace**.
* To run locally:
* Create a {% data variables.product.company_short %} {% data variables.product.pat_generic %}. The token needs to have `models:read` permissions. See [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).
* Save your token as an environment variable.
@@ -89,16 +89,16 @@ You can save and share your progress in the playground with presets. Presets sav
* Your parameters
* Your chat history (optional)
-To create a preset for your current context, select **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" %} at the top right of the playground, then click **{% octicon "plus" aria-hidden="true" %} Create new preset**. You need to name your preset, and you can also choose to provide a preset description, include your chat history, and allow your preset to be shared.
+To create a preset for your current context, select **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} at the top right of the playground, then click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Create new preset**. You need to name your preset, and you can also choose to provide a preset description, include your chat history, and allow your preset to be shared.
There are two ways to load a preset:
-* Select the **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click the preset you want to load.
+* Select the **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click the preset you want to load.
* Open a shared preset URL
After you load a preset, you can edit, share, or delete the preset:
-* To edit the preset, change the parameters and prompt the model. Once you are satisfied with your changes, select the **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **{% octicon "pencil" aria-hidden="true" %} Edit preset** and save your updates.
-* To share the preset, select the **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **{% octicon "share" aria-hidden="true" %} Share preset** to get a shareable URL.
-* To delete the preset, select the **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **{% octicon "trash" aria-hidden="true" %} Delete preset** and confirm the deletion.
+* To edit the preset, change the parameters and prompt the model. Once you are satisfied with your changes, select the **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit preset** and save your updates.
+* To share the preset, select the **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **{% octicon "share" aria-hidden="true" aria-label="share" %} Share preset** to get a shareable URL.
+* To delete the preset, select the **Preset: PRESET-NAME** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete preset** and confirm the deletion.
## Using the prompt editor
@@ -108,7 +108,7 @@ The prompt editor in {% data variables.product.prodname_github_models %} is desi
* Fine-tune prompts for precision and relevance in your projects.
* Use a specialized space for single-turn scenarios to ensure consistent and optimized results.
-To access the prompt editor, click **{% octicon "stack" aria-hidden="true" %} Prompt editor** at the top right of the playground.
+To access the prompt editor, click **{% octicon "stack" aria-hidden="true" aria-label="stack" %} Prompt editor** at the top right of the playground.
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 dff417f967fa..7dbcf8398400 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
@@ -35,7 +35,7 @@ You can also configure workflow automations to keep your {% data variables.proje
{% data reusables.projects.classic-project-creation %}
{% data reusables.profile.access_profile %}
-1. On the top of your profile page, in the main navigation, click **{% octicon "project" aria-hidden="true" %} Projects**.
+1. On the top of your profile page, in the main navigation, click **{% octicon "project" aria-hidden="true" aria-label="project" %} Projects**.
@@ -88,7 +88,7 @@ You can also configure workflow automations to keep your {% data variables.proje
{% data reusables.projects.classic-project-creation %}
{% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click **{% octicon "project" aria-hidden="true" %} Projects**.
+1. Under your repository name, click **{% octicon "project" aria-hidden="true" aria-label="project" %} Projects**.
1. Click **Projects (classic)**.
{% data reusables.project-management.click-new-project %}
{% data reusables.project-management.create-project-name-description %}
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 e7376e60100f..6e43234c573f 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
@@ -32,7 +32,7 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %}
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests.
-1. In your {% data variables.projects.projects_v1_board %}, click **{% octicon "plus" aria-hidden="true" %} Add cards**.
+1. In your {% data variables.projects.projects_v1_board %}, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add cards**.
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).
@@ -47,14 +47,14 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} from the sidebar
-1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-hidden="true" %}**.
+1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-hidden="true" aria-label="gear" %}**.
1. Click the **Recent**, **Repository**, **User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to.
1. Type the name of the project in **Filter projects** field.
1. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request.
-1. Click **Awaiting triage**{% octicon "triangle-down" aria-hidden="true" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select.
+1. Click **Awaiting triage**{% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select.
## Further reading
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically.md
index 06aa1b6768fb..0035c527b2dc 100644
--- a/content/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically.md
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically.md
@@ -69,11 +69,11 @@ You can create additional duplicates of the auto-add workflow, up to a maximum d
Once you have duplicated a workflow, you can click **Edit** to start making changes to it. For more information, see [Configuring the auto-add workflow in your project](#configuring-the-auto-add-workflow-in-your-project).
{% data reusables.projects.access-workflows %}
-1. In the list of workflows, next to "Auto-add to project" click {% octicon "kebab-horizontal" %}.
+1. In the list of workflows, next to "Auto-add to project" click {% octicon "kebab-horizontal" aria-label="kebab-horizontal" %}.
-1. In the menu, click **{% octicon "duplicate" %} Duplicate workflow**.
+1. In the menu, click **{% octicon "duplicate" aria-label="duplicate" %} Duplicate workflow**.
1. To save your new workflow, when prompted, type the name you want to use for the new workflow.
{% endif %}
diff --git a/content/issues/planning-and-tracking-with-projects/creating-projects/copying-an-existing-project.md b/content/issues/planning-and-tracking-with-projects/creating-projects/copying-an-existing-project.md
index e822aa0f71a3..60b21e59fa55 100644
--- a/content/issues/planning-and-tracking-with-projects/creating-projects/copying-an-existing-project.md
+++ b/content/issues/planning-and-tracking-with-projects/creating-projects/copying-an-existing-project.md
@@ -27,7 +27,7 @@ When you copy a project, the new project will contain the same {% data reusables
-1. In the menu, click **{% octicon "copy" aria-hidden="true" %} Make a copy**.
+1. In the menu, click **{% octicon "copy" aria-hidden="true" aria-label="copy" %} Make a copy**.
1. Optionally, if you want all draft issues to be copied with the project, in the "Make a copy" dialog, select **Draft issues will be copied if selected**.
1. Under "Owner", select either the organization that will own the new project or your personal account.
1. Under "New project name", type the name of the new project.
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 46e05ea594dd..a9604481d354 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
@@ -37,7 +37,7 @@ You can migrate your {% data variables.projects.projects_v1_boards %} to the new
-1. On the top of your profile page, in the main navigation, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. On the top of your profile page, in the main navigation, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. Above the list of projects, click **Projects (classic)**.
{% data reusables.projects.migrate-project-steps %}
@@ -48,6 +48,6 @@ You can migrate your {% data variables.projects.projects_v1_boards %} to the new
> {% 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**.
+1. Under your repository name, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. In the left sidebar, click **Projects (classic)**.
{% data reusables.projects.migrate-project-steps %}
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 128d89002a46..d754075dac23 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
@@ -25,7 +25,7 @@ The current count of cards and the column's limit is displayed at the top of the
1. Click {% octicon "kebab-horizontal" aria-label="Column context menu" %} next to the name of the column you want to modify.
-1. In the menu, click **{% octicon "number" aria-hidden="true" %} Set column limit**.
+1. In the menu, click **{% octicon "number" aria-hidden="true" aria-label="number" %} Set column limit**.
1. Under "Column limit", type the card limit for this column.
1. Optionally, to remove the limit, clear the entry.
1. Click **Save**.
@@ -39,7 +39,7 @@ The current count of cards and the column's limit is displayed at the top of the
In the board layout, you choose any single select or iteration field for your columns. If you drag an item to a new column, the value of that column is applied to the dragged item. For example, if you use the "Status" field for your board columns and then drag an item with a status of `In progress` to the `Done` column, the status of the item will switch to `Done`.
{% data reusables.projects.open-view-menu %}
-1. Click **{% octicon "columns" aria-hidden="true" %} Column field**.
+1. Click **{% octicon "columns" aria-hidden="true" aria-label="columns" %} Column field**.
1. Click the field you want to use.
## Showing and hiding columns in board layout
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md
index b139f6c9e6e7..e494bdf65223 100644
--- a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md
+++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md
@@ -21,18 +21,18 @@ For more information about changing a view to use the roadmap layout, see [AUTOT
You can set the date or iteration fields that your roadmap will use to position items. When you set a view to a roadmap layout, {% data variables.product.company_short %} will attempt to use existing date and iteration fields you have already set up. For more information on creating new fields, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields) and [AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields).
-1. In the top right of your roadmap, click **{% octicon "calendar" aria-hidden="true" %} Date fields**.
+1. In the top right of your roadmap, click **{% octicon "calendar" aria-hidden="true" aria-label="calendar" %} Date fields**.
-1. Optionally, to create a new date or iteration field, click **{% octicon "plus" aria-hidden="true" %} New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
+1. Optionally, to create a new date or iteration field, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
1. Select a date or iteration field for "Start date" and "Target date."
## Setting vertical markers
You can configure vertical markers on a roadmap to show your iterations, the dates of items in your project, and the milestones associated with items in your project.
-1. In the top right of your roadmap, click **{% octicon "location" aria-hidden="true" %} Markers**.
+1. In the top right of your roadmap, click **{% octicon "location" aria-hidden="true" aria-label="location" %} Markers**.
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 af1fc8f433c7..87b3b277ffed 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
@@ -27,7 +27,7 @@ You can also hide individual fields using the field headers.
1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="Status column options" %}.
-1. Click **{% octicon "eye-closed" aria-hidden="true" %} Hide field**.
+1. Click **{% octicon "eye-closed" aria-hidden="true" aria-label="eye-closed" %} Hide field**.
## Grouping by field values
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
index 948830ead31a..7ae3c7fff25b 100644
--- a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
+++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
@@ -32,7 +32,7 @@ You can duplicate an existing view and use it as a base to make further changes.
1. Switch to the view you want to duplicate.
{% data reusables.projects.open-view-menu %}
-1. Click **{% octicon "versions" aria-hidden="true" %} Duplicate view**.
+1. Click **{% octicon "versions" aria-hidden="true" aria-label="versions" %} Duplicate view**.
## Saving changes to a view
@@ -54,7 +54,7 @@ You can rename your saved views. The name change is automatically saved.
1. Switch to the view you want to rename.
{% data reusables.projects.open-view-menu %}
-1. Click **{% octicon "pencil" aria-hidden="true" %} Rename view**.
+1. Click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Rename view**.
1. Type the new name for your view.
1. To save your changes, press Return.
@@ -62,4 +62,4 @@ You can rename your saved views. The name change is automatically saved.
1. Switch to the view you want to delete.
{% data reusables.projects.open-view-menu %}
-1. Click **{% octicon "trash" aria-hidden="true" %} Delete view**.
+1. Click **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete view**.
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/finding-your-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/finding-your-projects.md
index 5344258518b7..7fb6a9588291 100644
--- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/finding-your-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/finding-your-projects.md
@@ -16,7 +16,7 @@ topics:
You can browse all of your projects, regardless of where they are located. You can see the projects you have recently viewed and the projects you have created, and apply your own filters.
1. In the top left of any page, click {% octicon "three-bars" aria-label="Open global navigation menu" %} to open the global navigation menu.
-1. In the menu, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. In the menu, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
{% data reusables.projects.index-select %}
## Finding an organization's projects
@@ -25,7 +25,7 @@ You can view and filter all the projects owned by an organization that you have
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
-1. Under the organization name, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. Under the organization name, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
{% data reusables.projects.index-select %}
## Finding projects owned by your personal account
@@ -33,7 +33,7 @@ You can view and filter all the projects owned by an organization that you have
You can view and filter projects that you have created under your personal account.
{% data reusables.profile.access_profile %}
-1. On your profile, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. On your profile, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
{% data reusables.projects.index-select %}
## Finding projects linked to a repository
@@ -41,7 +41,7 @@ You can view and filter projects that you have created under your personal accou
Repositories can be linked to organization-level and user-level projects. You can browse and filter the projects that are linked to a specific repository. For more information on linking projects to a repository, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository).
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
-1. Click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. Click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
@@ -54,7 +54,7 @@ You can also link a project to specific teams in an organization and then browse
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
{% data reusables.organizations.specific_team %}
-1. Click **{% octicon "project" aria-hidden="true" %} Projects**.
+1. Click **{% octicon "project" aria-hidden="true" aria-label="project" %} Projects**.
diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
index 9aaf2397e201..b1047d882b29 100644
--- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
@@ -83,7 +83,7 @@ Specify a priority for all issues in your project.
Next, group all of the items in your project by priority to make it easier to focus on the high priority items.
{% data reusables.projects.open-view-menu %}
-1. Click **{% octicon "rows" aria-hidden="true" %} Group**.
+1. Click **{% octicon "rows" aria-hidden="true" aria-label="rows" %} Group**.
1. Click **Priority**.
Now, move issues between groups to change their priority.
@@ -123,7 +123,7 @@ When you changed the layout, your project displayed an indicator to show that th
To indicate the purpose of the view, give it a descriptive name.
{% data reusables.projects.open-view-menu %}
-1. Click **{% octicon "pencil" aria-hidden="true" %} Rename view**.
+1. Click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Rename view**.
1. Type the new name for your view.
1. To save changes, press Return.
@@ -145,7 +145,7 @@ Finally, add a built in workflow to set the status to **Todo** when an item is a
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
-1. In the menu, click **{% octicon "workflow" aria-hidden="true" %} Workflows**.
+1. In the menu, click **{% octicon "workflow" aria-hidden="true" aria-label="workflow" %} Workflows**.
1. Under **Default workflows**, click **Item added to project**.
1. Next to **When**, ensure that both `issues` and `pull requests` are selected.
1. Next to **Set**, select **Status:Todo**.
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 ec5cc82f3222..0d9785f9bdd2 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
@@ -53,7 +53,7 @@ If you know the issue or pull request number or if you know part of the title, y
You can add multiple issues and pull requests from your project and use filters, such as `label:bug`, to narrow down your search.
-1. In the bottom row of the project, click {% octicon "plus" aria-hidden="true" %}.
+1. In the bottom row of the project, click {% octicon "plus" aria-hidden="true" aria-label="plus" %}.
1. Click **Add item from repository**.
{% data reusables.projects.bulk-add %}
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 dafbd2203ad0..11b32675ccc2 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
@@ -31,7 +31,7 @@ You can archive an item to keep the context about the item in the project but re
-1. In the menu, click **{% octicon "archive" aria-hidden="true" %} Archived items**.
+1. In the menu, click **{% octicon "archive" aria-hidden="true" aria-label="archive" %} Archived items**.
1. Optionally, to filter the archived items displayed, type your filter into the text box above the list of items. For more information about the available filters, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects).
1. To the left of each item title, select the items you would like to restore.
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
index 7e3b5d7f3e97..fe203967de25 100644
--- a/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
@@ -17,7 +17,7 @@ You can list relevant projects in a repository. You can only list projects that
In order for repository members to see a project listed in a repository, they must have visibility for the project. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects) and [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects).
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
-1. Click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. Click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. Click **Link a project**.
1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository.
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 f88e8d74b28f..c2b50467e48d 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
@@ -24,7 +24,7 @@ Teams are granted read permissions on any project they are added to. This permis
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
{% data reusables.organizations.specific_team %}
-1. Click **{% octicon "project" aria-hidden="true" %} Projects**.
+1. Click **{% octicon "project" aria-hidden="true" aria-label="project" %} Projects**.
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/exporting-your-projects-data.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/exporting-your-projects-data.md
index de0fd322761f..5da5c059b7af 100644
--- a/content/issues/planning-and-tracking-with-projects/managing-your-project/exporting-your-projects-data.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/exporting-your-projects-data.md
@@ -16,7 +16,7 @@ allowTitleToDifferFromFilename: true
You can download a view as a _.tsv_ (tab-separated) file.
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
-1. Click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. Click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
{% data reusables.projects.open-view-menu %}
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md
index d261c9b6b152..5f6d6ece0b1e 100644
--- a/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md
+++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md
@@ -54,7 +54,7 @@ You can also add templates to teams and repositories, to make them accessible an
If you have write or admin permissions for a project in your organization, you can choose to copy the project as a template. This will make a duplicate of the current project—copying the {% data reusables.projects.what-gets-copied %} —and set that copied project as a template for your organization.
{% data reusables.projects.project-settings %}
-1. In the "Templates" section, click **{% octicon "duplicate" aria-hidden="true" %} Copy as template**.
+1. In the "Templates" section, click **{% octicon "duplicate" aria-hidden="true" aria-label="duplicate" %} Copy as template**.
## Configuring recommended templates
@@ -66,7 +66,7 @@ You can add up to six templates to your organization's recommended templates.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. Under "Recommended templates", click **Customize recommended templates**.
1. In the list of templates owned by your organization, select up to six templates that you want to recommend to your members.
@@ -80,7 +80,7 @@ You can change the display order of your recommended templates in the "Create pr
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. Under "Recommended templates", find the template you want to reposition, click on {% octicon "grabber" aria-label="Drag to reorder" %}, and drag the template to the new position.
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md
index 51fd581c1ad8..aa51e3d755e3 100644
--- a/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md
+++ b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md
@@ -36,7 +36,7 @@ If your project makes use of iteration fields, you can use the roadmap layout to
1. Click the name of the iteration field you want to adjust.
1. To add a new iteration of the same duration, click **Add iteration**.
-1. Optionally, to customize the duration of the new iteration and when it will start, click **{% octicon "triangle-down" aria-hidden="true" %} More options**, select a starting date and duration, and click **Add**.
+1. Optionally, to customize the duration of the new iteration and when it will start, click **{% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} More options**, select a starting date and duration, and click **Add**.
1. Click **Save changes**.
diff --git a/content/issues/tracking-your-work-with-issues/administering-issues/deleting-an-issue.md b/content/issues/tracking-your-work-with-issues/administering-issues/deleting-an-issue.md
index 7d06b8410a57..f7c8828a2f7c 100644
--- a/content/issues/tracking-your-work-with-issues/administering-issues/deleting-an-issue.md
+++ b/content/issues/tracking-your-work-with-issues/administering-issues/deleting-an-issue.md
@@ -23,7 +23,7 @@ The ability to delete issues depends on whether the repository is owned by a per
Collaborators do not receive a notification when issues are deleted. When visiting the URL of a deleted issue, collaborators will see a message stating that the web page can't be found (but they can use the API to determine that it was deleted). People with admin or owner permissions in the repository will additionally see the username of the person who deleted the issue and when it was deleted.
1. Navigate to the issue you want to delete.
-1. On the right side bar, under "Notifications", click **{% octicon "trash" aria-hidden="true" %} Delete issue**.
+1. On the right side bar, under "Notifications", click **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete issue**.
1. To confirm deletion, click **Delete this issue**.
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues.md b/content/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues.md
index 11a06a015953..12f4805d1659 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues.md
@@ -15,7 +15,7 @@ topics:
You can browse through all levels of sub-issues from the parent issue.
1. Navigate to the parent issue.
-1. To view the sub-issues under another sub-issue, click the expand toggle ({% octicon "triangle-right" aria-hidden="true" %}).
+1. To view the sub-issues under another sub-issue, click the expand toggle ({% octicon "triangle-right" aria-hidden="true" aria-label="triangle-right" %}).
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 7aacf7b739dd..a180bcceea5d 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
@@ -88,7 +88,7 @@ You can open a new issue from a specific line or lines of code in a file or pull
{% data reusables.repositories.navigate-to-repo %}
1. Locate the code you want to reference in an issue:
* To open an issue about code in a file, navigate to the file.
- * To open an issue about code in a pull request, navigate to the pull request and click **{% octicon "diff" aria-hidden="true" %} Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
+ * To open an issue about code in a pull request, navigate to the pull request and click **{% octicon "diff" aria-hidden="true" aria-label="diff" %} Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
{% data reusables.repositories.choose-line-or-range %}
1. To the left of the code range, click {% octicon "kebab-horizontal" aria-label="Code line X options" %}. In the dropdown menu, click **Reference in new issue**.
@@ -105,7 +105,7 @@ When you create an issue from a discussion, the contents of the discussion post
{% data reusables.discussions.discussions-tab %}
{% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click **{% octicon "issue-opened" aria-hidden="true" %} Create issue from discussion**.
+1. In the right sidebar, click **{% octicon "issue-opened" aria-hidden="true" aria-label="issue-opened" %} Create issue from discussion**.
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md b/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md
index 25bd5a6c6f21..8663163f61a9 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md
@@ -34,7 +34,7 @@ You can also make changes to the issue description. The edit history is availabl
-1. In the menu, click **{% octicon "pencil" aria-hidden="true" %} Edit**.
+1. In the menu, click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit**.
1. Type your changes to the issue description.
1. Click **Save**.
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md b/content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md
index d7c6e867536a..c9c75f18045c 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md
@@ -54,7 +54,7 @@ You can create up to 25 saved views.
1. At the top of any page, click {% octicon "issue-opened" aria-label="Issues" %} to see your issues.
1. On the left sidebar, under "Views", click the saved view you want to edit, duplicate or delete.
1. To the right of the name of the saved view, click **{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.**.
-1. Click **{% octicon "pencil" aria-hidden="true" %} Edit** to modify the view, **{% octicon "duplicate" aria-hidden="true" %} Duplicate** to create a copy of the view, or **{% octicon "trash" aria-hidden="true" %} Delete** to remove the view.
+1. Click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit** to modify the view, **{% octicon "duplicate" aria-hidden="true" aria-label="duplicate" %} Duplicate** to create a copy of the view, or **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete** to remove the view.
{% endif %}
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 6491741c8376..163e3fcbcb24 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
@@ -182,7 +182,7 @@ You can view the status of all attribution invitations for your organization.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.enterprise-migration-tool.import-export-tab %}
-1. Under "{% octicon "arrow-switch" aria-hidden="true" %} Import/Export", click **Attribution Invitations**.
+1. Under "{% octicon "arrow-switch" aria-hidden="true" aria-label="arrow-switch" %} Import/Export", click **Attribution Invitations**.
diff --git a/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
index 8986c103a20b..0e8a7a71ce0f 100644
--- a/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
+++ b/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
@@ -65,7 +65,7 @@ The content of a member-only `README.md` will be displayed in the member view of
You can pin repositories that you want to feature, such as those that are frequently used, to your organization's profile page. To choose which repositories to pin to your organization's profile, you must be an organization owner.
1. Navigate to your organization's profile page.
-1. In the right sidebar of the page, select the **{% octicon "eye" aria-hidden="true" %} View as** dropdown menu, then click **Public** or **Member**.
+1. In the right sidebar of the page, select the **{% octicon "eye" aria-hidden="true" aria-label="eye" %} View as** dropdown menu, then click **Public** or **Member**.
1. Navigate to the settings for pinned repositories.
diff --git a/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-dependencies-in-your-organization.md b/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-dependencies-in-your-organization.md
index c3acd66921e8..1f3f87f830e4 100644
--- a/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-dependencies-in-your-organization.md
+++ b/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-dependencies-in-your-organization.md
@@ -36,7 +36,7 @@ With dependency insights you can view vulnerabilities, licenses, and other impor
1. To filter by a vulnerability status, a license, or a combination of the two, click the results in the **Open security advisories** and **Licenses** graphs.
-1. To see which dependents in your organization are using each library, next to a vulnerability, click **{% octicon "package" aria-hidden-"true" %} X dependents**.
+1. To see which dependents in your organization are using each library, next to a vulnerability, click **{% octicon "package" aria-hidden-"true" aria-label="package" %} X dependents**.
## Further reading
diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
index a0b016dcc053..d53a8a69598e 100644
--- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
+++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -23,7 +23,7 @@ You can access {% data variables.product.company_short %}'s compliance reports i
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.compliance %}
-1. To the right of the report you want to access, click **{% octicon "download" aria-hidden="true" %} Download** or **{% octicon "link-external" aria-hidden="true" %} View**.
+1. To the right of the report you want to access, click **{% octicon "download" aria-hidden="true" aria-label="download" %} Download** or **{% octicon "link-external" aria-hidden="true" aria-label="link-external" %} View**.
{% data reusables.security.compliance-report-screenshot %}
diff --git a/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/managing-bots-and-service-accounts-with-two-factor-authentication.md b/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/managing-bots-and-service-accounts-with-two-factor-authentication.md
index 6673d08c4c4a..7d134957b0a3 100644
--- a/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/managing-bots-and-service-accounts-with-two-factor-authentication.md
+++ b/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/managing-bots-and-service-accounts-with-two-factor-authentication.md
@@ -31,7 +31,7 @@ You should ensure that 2FA is enabled for unattended or shared access accounts i
If you have already configured 2FA using TOTP and you need to locate the TOTP secret, use the following steps:
- 1. In the shared account's settings, click **{% octicon "shield-lock" aria-hidden="true" %} Password and authentication**.
+ 1. In the shared account's settings, click **{% octicon "shield-lock" aria-hidden="true" aria-label="shield-lock" %} Password and authentication**.
1. Under "Two-factor methods", to the right of "Authenticator app", click **Edit**.
1. In "Authenticator app", immediately below the QR code, click **setup key**.
diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index c280c25c0878..cab81f20b1f1 100644
--- a/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -44,7 +44,7 @@ If a team's access to a {% data variables.projects.projects_v1_board %} is inher
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
{% data reusables.organizations.specific_team %}
-1. Above the team's conversation, click **{% octicon "project" aria-hidden="true" %} Projects**.
+1. Above the team's conversation, click **{% octicon "project" aria-hidden="true" aria-label="project" %} Projects**.
1. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the permission level dropdown menu.
diff --git a/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
index 951b7a11c583..01f8c93e1190 100644
--- a/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
+++ b/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
@@ -27,7 +27,7 @@ This option may not be available to you if an enterprise owner restricts visibil
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. To allow members to adjust project visibility, select **Allow members to change project visibilities for this organization**.
1. Click **Save**.
diff --git a/content/organizations/managing-organization-settings/creating-an-announcement-banner-for-your-organization.md b/content/organizations/managing-organization-settings/creating-an-announcement-banner-for-your-organization.md
index 35b9b8554522..54778e55bda8 100644
--- a/content/organizations/managing-organization-settings/creating-an-announcement-banner-for-your-organization.md
+++ b/content/organizations/managing-organization-settings/creating-an-announcement-banner-for-your-organization.md
@@ -25,7 +25,7 @@ You can also set announcement banners at the enterprise level. For more informat
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Messages" section of the sidebar, click **{% octicon "megaphone" aria-hidden="true" %} Announcement**.
+1. In the "Messages" section of the sidebar, click **{% octicon "megaphone" aria-hidden="true" aria-label="megaphone" %} Announcement**.
1. Under "Announcement", in the text field, type the announcement you want displayed in a banner.
1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date.
diff --git a/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index e07ef88e31b7..f3e67e7dcfc0 100644
--- a/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -150,7 +150,7 @@ For each repository in your organization, you can see how much cache storage a r
{% data reusables.profile.access_profile %}
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "play" aria-hidden="true" %} Actions**, then click **Caches**.
+1. In the left sidebar, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Actions**, then click **Caches**.
1. Review the list of repositories for information about their {% data variables.product.prodname_actions %} caches. You can click on a repository name to see more detail about the repository's caches.
{% ifversion ghes %}
diff --git a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index b93752fb16c2..b3e1aea5d479 100644
--- a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -28,7 +28,7 @@ When {% data variables.projects.projects_v1_boards %} are disabled, you will no
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. Decide whether to disable {% data variables.projects.projects_v2_and_v1 %} in your organization. Then, under "Projects":
* To disable {% data variables.projects.projects_v2_and_v1 %}, deselect **Enable Projects for the organization**.
* To enable {% data variables.projects.projects_v2_and_v1 %} in the organization, select **Enable Projects for the organization**.
@@ -44,7 +44,7 @@ You can control whether organization members can create {% data variables.projec
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. Decide whether to allow members to create {% data variables.projects.projects_v1_boards %} in repositories in your organization. Then, under "Projects (classic) only":
* To enable {% data variables.projects.projects_v1_boards %} in repositories, select **Allow members to enable {% data variables.product.prodname_projects_v1_caps %} for all repositories**.
* To disable {% data variables.projects.projects_v1_boards %} in repositories, deselect **Allow members to enable {% data variables.product.prodname_projects_v1_caps %} for all repositories**.
diff --git a/content/organizations/managing-organization-settings/governing-how-people-use-repositories-in-your-organization.md b/content/organizations/managing-organization-settings/governing-how-people-use-repositories-in-your-organization.md
index 2f7b82294ee0..aa9e515070a9 100644
--- a/content/organizations/managing-organization-settings/governing-how-people-use-repositories-in-your-organization.md
+++ b/content/organizations/managing-organization-settings/governing-how-people-use-repositories-in-your-organization.md
@@ -34,7 +34,7 @@ As an alternative to custom properties, you can choose from a list of repositori
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. On the left side of the page, in the sidebar, click **{% octicon "law" aria-hidden="true" %} Policies**.
+1. On the left side of the page, in the sidebar, click **{% octicon "law" aria-hidden="true" aria-label="law" %} Policies**.
1. Under "Policies", click **Repository**.
1. Click **New policy**.
1. Configure your new policy, then click **Create**. For help, consult the following subsections.
diff --git a/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
index 496bf250b381..3f0959313e66 100644
--- a/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
+++ b/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
@@ -12,7 +12,7 @@ allowTitleToDifferFromFilename: true
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, select **{% octicon "code" aria-hidden="true" %} Developer settings**, then click **OAuth Apps**.
+1. In the left sidebar, select **{% octicon "code" aria-hidden="true" aria-label="code" %} Developer settings**, then click **OAuth Apps**.
1. Click **New OAuth App**.
1. Under **Application name**, type "Jira".
1. Under **Homepage URL**, type the full URL to your Jira instance.
diff --git a/content/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization.md b/content/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization.md
index d2f12998af70..f4c986005641 100644
--- a/content/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization.md
+++ b/content/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization.md
@@ -53,7 +53,7 @@ You{% ifversion custom-org-roles %}, and any users with the "Edit custom propert
{% data reusables.profile.org_settings %}
{% data reusables.organizations.access-custom-properties %}
1. Click the "Set values" tab.
-1. Select one or more repositories from the list and click **{% octicon "pencil" aria-hidden="true" %} Edit properties**.
+1. Select one or more repositories from the list and click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit properties**.
@@ -68,7 +68,7 @@ People with read permissions to a repository can view the values of custom prope
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Code and automation" section of the sidebar, click **{% octicon "tools" aria-hidden="true" %} Custom properties**.
+1. In the "Code and automation" section of the sidebar, click **{% octicon "tools" aria-hidden="true" aria-label="tools" %} Custom properties**.
{% ifversion ghec or fpt or ghes > 3.14 %}
@@ -78,7 +78,7 @@ You can search for repositories in your organization by custom properties values
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
-1. Under your organization name, click **{% octicon "repo" aria-hidden="true" %} Repositories**.
+1. Under your organization name, click **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Repositories**.
1. In the search bar, type `prop` to see a list of all custom properties in your organization, and select the property you'd like to search by.
{% endif %}
diff --git a/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md b/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
index a3403acc2ce9..45601443ecaf 100644
--- a/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
+++ b/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
@@ -22,8 +22,8 @@ You can also enable code review limits for individual repositories. If you enabl
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "report" aria-hidden="true" %} Moderation**.
-1. Under "{% octicon "report" aria-hidden="true" %} Moderation", click **Code review limits**.
+1. In the "Access" section of the sidebar, click **{% octicon "report" aria-hidden="true" aria-label="report" %} Moderation**.
+1. Under "{% octicon "report" aria-hidden="true" aria-label="report" %} Moderation", click **Code review limits**.
1. Review the information on screen.
1. Manage code review limits.
* To limit reviews to those with explicit access, click **Limit review on all repositories**.
diff --git a/content/organizations/managing-organization-settings/managing-rulesets-for-repositories-in-your-organization.md b/content/organizations/managing-organization-settings/managing-rulesets-for-repositories-in-your-organization.md
index bb2c1b284816..5e1e6e5224b1 100644
--- a/content/organizations/managing-organization-settings/managing-rulesets-for-repositories-in-your-organization.md
+++ b/content/organizations/managing-organization-settings/managing-rulesets-for-repositories-in-your-organization.md
@@ -71,7 +71,7 @@ You can view insights for rulesets to see how rulesets are affecting the reposit
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, in the "Code, planning, and automation" section, click **{% octicon "repo" aria-hidden="true" %} Repository**, then click **Rule insights**.
+1. In the left sidebar, in the "Code, planning, and automation" section, click **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Repository**, then click **Rule insights**.
diff --git a/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md b/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md
index b7d252e7ffda..308f4db24ee3 100644
--- a/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md
+++ b/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md
@@ -23,7 +23,7 @@ Organization owners can also use the REST API to review and manage {% data varia
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
1. Click the name of the token that you want to approve or deny.
1. Review the access and permissions that the token is requesting.
1. To grant the token access to the organization, click **Approve**. To deny the token access to the organization, click **Deny**.
@@ -33,7 +33,7 @@ Alternatively, you can approve or deny multiple tokens at once:
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
{% data reusables.user-settings.patv2-filters %}
1. Select each token that you want to approve or reject.
1. Select the **request selected...** dropdown menu and click **Approve...** or **Deny...**.
diff --git a/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md b/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md
index 3a1d445d68c3..8f1df9f5bb84 100644
--- a/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md
+++ b/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md
@@ -24,7 +24,7 @@ Organization owners can also use the REST API to review and revoke {% data varia
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
1. Click the name of the token that you want review or revoke.
1. Review the access and permissions that the token has.
1. To revoke access by the token to the organization, click **Revoke**.
@@ -33,7 +33,7 @@ Alternatively, you can revoke multiple tokens at once:
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
{% data reusables.user-settings.patv2-filters %}
1. Select each token that you want to revoke.
1. Select the **tokens selected...** dropdown menu and click **Revoke...**.
diff --git a/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md b/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md
index 399e819e2945..195901b6cdfc 100644
--- a/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md
+++ b/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md
@@ -20,7 +20,7 @@ Regardless of the chosen policy, {% data variables.product.pat_generic_caps_plur
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. {% ifversion tabbed-pat-settings-ui %}
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. {% ifversion tabbed-pat-settings-ui %}
1. Select either the **Fine-grained tokens** or **Tokens (classic)** tab to enforce this policy based on the token type. {% endif %}
1. Under **{% data variables.product.pat_v2_caps_plural %}** or **Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations**, select your access policy.
1. Click **Save**.
@@ -37,7 +37,7 @@ When you set a policy, tokens with non-compliant lifetimes will be blocked from
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, click **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**.
+1. In the left sidebar, click **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**.
1. Select either the **Fine-grained tokens** or **Tokens (classic)** tab to enforce this policy based on the token type.
1. Under **Set maximum lifetimes for {% data variables.product.pat_generic_plural %}**, set the maximum lifetime.
1. Click **Save**.
@@ -58,7 +58,7 @@ Organization owners can manage approval requirements for each {% data variables.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. {% ifversion tabbed-pat-settings-ui %}
+1. In the left sidebar, under **{% octicon "key" aria-hidden="true" aria-label="key" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. {% ifversion tabbed-pat-settings-ui %}
1. Select the **Fine-grained tokens** tab. {% endif %}
1. Under **Require approval of {% data variables.product.pat_v2_plural %}**, select the option that meets your needs:
1. Click **Save**.
diff --git a/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index 4c6b4bba4a80..8acd3d031012 100644
--- a/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -49,7 +49,7 @@ Any team members that have set their status to "Busy" will not be selected for r
{% data reusables.user-settings.access_org %}
{% data reusables.organizations.specific_team %}
{% data reusables.organizations.team_settings %}
-1. In the left sidebar, click **{% octicon "code-review" aria-hidden="true" %} Code review**.
+1. In the left sidebar, click **{% octicon "code-review" aria-hidden="true" aria-label="code-review" %} Code review**.
1. Select **Only notify requested team members.**
1. Click **Save changes**.
@@ -59,7 +59,7 @@ Any team members that have set their status to "Busy" will not be selected for r
{% data reusables.user-settings.access_org %}
{% data reusables.organizations.specific_team %}
{% data reusables.organizations.team_settings %}
-1. In the left sidebar, click **{% octicon "code-review" aria-hidden="true" %} Code review**.
+1. In the left sidebar, click **{% octicon "code-review" aria-hidden="true" aria-label="code-review" %} Code review**.
1. Select **Enable auto assignment**.
1. Under "How many team members should be assigned to review?", select the dropdown menu and choose a number of reviewers to be assigned to each pull request.
1. Under "Routing algorithm", use the dropdown menu and choose which algorithm you'd like to use. For more information, see [Routing algorithms](#routing-algorithms).
diff --git a/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md
index bacb415301d8..46f069849c91 100644
--- a/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md
+++ b/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md
@@ -24,7 +24,7 @@ If you're an organization owner or you have team maintainer permissions in both
{% data reusables.user-settings.access_org %}
{% data reusables.organizations.teams %}
1. In the list of teams, click the name of the team where you'd like to add the child team.
-1. At the top of the team page, click **{% octicon "people" aria-hidden="true" %} Teams**.
+1. At the top of the team page, click **{% octicon "people" aria-hidden="true" aria-label="people" %} Teams**.
diff --git a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
index db0af0b7be81..32bf21eb728a 100644
--- a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
+++ b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -98,7 +98,7 @@ If you disable automatic inheritance of access permissions, new packages scoped
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the sidebar, in the "Code, planning, and automation" section, click **{% octicon "package" aria-hidden="true" %} Packages**.
+1. In the sidebar, in the "Code, planning, and automation" section, click **{% octicon "package" aria-hidden="true" aria-label="package" %} Packages**.
1. Under "Default Package Settings", deselect **Inherit access from source repository**.
1. Click **Save**.
diff --git a/content/packages/learn-github-packages/viewing-packages.md b/content/packages/learn-github-packages/viewing-packages.md
index 6d973143c07b..ed7657d243d7 100644
--- a/content/packages/learn-github-packages/viewing-packages.md
+++ b/content/packages/learn-github-packages/viewing-packages.md
@@ -41,7 +41,7 @@ You can find and view a package located in the repositories of an organization y
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
-1. Under your organization name, click **{% octicon "package" aria-hidden="true" %} Packages**.
+1. Under your organization name, click **{% octicon "package" aria-hidden="true" aria-label="package" %} Packages**.
{% data reusables.package_registry.navigate-to-packages %}
## Viewing your packages
diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
index 74ae84e33322..7d05ede80ee4 100644
--- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
+++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@@ -32,7 +32,7 @@ You may be verifying a domain you own, which is currently in use by another user
> If you don’t see the options described below, make sure you’re in your **Profile settings**, not your repository settings. Domain verification happens at the profile level.
{% data reusables.user-settings.access_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" %} Pages**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" aria-label="browser" %} Pages**.
{% data reusables.pages.settings-verify-domain-setup %}
1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
@@ -51,7 +51,7 @@ Organization owners can verify custom domains for their organization.
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" %} Pages**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" aria-label="browser" %} Pages**.
{% data reusables.pages.settings-verify-domain-setup %}
1. Wait for your DNS configuration to change. This may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
diff --git a/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
index 3aa0c85a43db..f256fe9fa51d 100644
--- a/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
+++ b/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
@@ -38,7 +38,7 @@ To use a shorter and more memorable domain for your privately published site, yo
{% data reusables.repositories.sidebar-settings %}
{% data reusables.pages.sidebar-pages %}
1. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** dropdown menu, then select a visibility.
-1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" %} Visit site**.
+1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" aria-label="link-external" %} Visit site**.
diff --git a/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
index 1eb27c097828..837ce2b387b8 100644
--- a/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
+++ b/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
@@ -55,7 +55,7 @@ shortTitle: Create a GitHub Pages site
{% indented_data_reference reusables.pages.privately-publish-ghec-only spaces=3 %}
{%- endif %}
-1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" %} Visit site**.
+1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" aria-label="link-external" %} Visit site**.
{% data reusables.pages.twenty-minutes-to-publish %}
{% data reusables.pages.admin-must-push %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
index 6cd0712ffcd4..0c2adb01e54e 100644
--- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -38,7 +38,7 @@ You can create a branch in different ways on {% data variables.product.github %}
### Creating a branch using the branch dropdown
{% data reusables.repositories.navigate-to-repo %}
-1. Select the {% octicon "git-branch" aria-hidden="true" %} branch dropdown menu, in the file tree view or at the top of the integrated file editor.
+1. Select the {% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} branch dropdown menu, in the file tree view or at the top of the integrated file editor.
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
index 5367c97d5e97..412ab7d49248 100644
--- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
+++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -24,7 +24,7 @@ shortTitle: Check out a PR locally
{% data reusables.repositories.sidebar-pr %}
1. In the list of pull requests, click the pull request you'd like to modify.{% ifversion fpt or ghec %}
-1. To choose where you'd like to open the pull request, select the **{% octicon "code" aria-hidden="true" %} Code** dropdown and click one of the tabs.
+1. To choose where you'd like to open the pull request, select the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** dropdown and click one of the tabs.
{% else %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md
index 210cd714e249..5c6724b920de 100644
--- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md
+++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md
@@ -26,7 +26,7 @@ The summary list of methods and functions is created from these supported file t
{% data reusables.repositories.sidebar-pr %}
1. In the list of pull requests, click the pull request where you'd like to find the changed functions and methods.
{% data reusables.repositories.changed-files %}
-1. To see a summary list of the changed functions and methods, click **Jump to {% octicon "triangle-down" aria-hidden="true" %}**.
+1. To see a summary list of the changed functions and methods, click **Jump to {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}**.
diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md
index 47a5f9fbb389..7e97b6bef195 100644
--- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md
+++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md
@@ -24,7 +24,7 @@ You can set commit permissions when you first create a pull request from a fork.
## Enabling repository maintainer permissions on existing pull requests
1. On {% data variables.product.github %}, navigate to the main page of the upstream repository of your pull request.
-1. Under the upstream repository name, click **{% octicon "git-pull-request" aria-hidden="true" %} Pull requests**.
+1. Under the upstream repository name, click **{% octicon "git-pull-request" aria-hidden="true" aria-label="git-pull-request" %} Pull requests**.
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index b5d87b7f5802..e0a28c2c0319 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -30,7 +30,7 @@ Organizational rulesets that apply to branches of a repository will no longer al
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.navigate-to-branches %}
-1. Next to the branch you want to rename, select the {% octicon "kebab-horizontal" aria-label="More" %} dropdown menu, then click **{% octicon "pencil" aria-hidden="true" %} Rename branch**.
+1. Next to the branch you want to rename, select the {% octicon "kebab-horizontal" aria-label="More" %} dropdown menu, then click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Rename branch**.
1. Type a new name for the branch.
1. Review the information about local environments, then click **Rename branch**.
diff --git a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
index 71d93d13a725..c025ca114e25 100644
--- a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -87,7 +87,7 @@ An empty repository contains no files. It's often made if you don't initialize t
- Alternatively, to clone your repository in Desktop, click **{% octicon "desktop-download" aria-hidden="true" %} Set up in Desktop** and follow the prompts to complete the clone.
+ Alternatively, to clone your repository in Desktop, click **{% octicon "desktop-download" aria-hidden="true" aria-label="desktop-download" %} Set up in Desktop** and follow the prompts to complete the clone.
diff --git a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-projects-in-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-projects-in-a-repository.md
index d58ad9b583cb..888091bb7956 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-projects-in-a-repository.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-projects-in-a-repository.md
@@ -19,7 +19,7 @@ allowTitleToDifferFromFilename: true
## Disabling {% data variables.projects.projects_v2 %} in a repository
-When you disable {% data variables.projects.projects_v2 %} in a repository, linked projects will no longer be available in the repository's **{% octicon "table" aria-hidden="true" %} Projects** tab. Linked projects will remain accessible at an organization or user level.
+When you disable {% data variables.projects.projects_v2 %} in a repository, linked projects will no longer be available in the repository's **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects** tab. Linked projects will remain accessible at an organization or user level.
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
diff --git a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index d310350d294b..2eade1b0fe69 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -120,7 +120,7 @@ By default, when you create a new repository in your personal account, workflows
You can use the steps below to configure whether {% ifversion internal-actions %}actions and {% endif %}reusable workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see [AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise). Alternatively, you can use the REST API to set, or get details of the level of access. For more information, see [AUTOTITLE](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository) and [AUTOTITLE](/rest/actions/permissions#set-the-level-of-access-for-workflows-outside-of-the-repository).{% endif %}
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
-1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Under your repository name, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
{% data reusables.repositories.settings-sidebar-actions-general %}
1. Under **Access**, choose one of the access settings:
@@ -141,7 +141,7 @@ You can use the steps below to configure whether actions and reusable workflows
### Managing access for a private repository
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
-1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Under your repository name, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
{% data reusables.repositories.settings-sidebar-actions-general %}
1. Under **Access**, choose one of the access settings:
@@ -156,7 +156,7 @@ You can use the steps below to configure whether actions and reusable workflows
### Managing access for a private repository in an organization
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
-1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Under your repository name, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
{% data reusables.repositories.settings-sidebar-actions-general %}
1. Under **Access**, choose one of the access settings:
@@ -169,7 +169,7 @@ You can use the steps below to configure whether actions and reusable workflows
{% ifversion fpt %}{% else %}
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
-1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Under your repository name, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
{% data reusables.repositories.settings-sidebar-actions-general %}
1. Under **Access**, choose one of the access settings:
* **Not accessible** - Workflows in other repositories cannot access this repository.
diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
index becde5bd19ec..8eaa1d1d0193 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
@@ -31,7 +31,7 @@ This procedure demonstrates how to configure autolinks to reference external res
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-hidden="true" %} Autolink references**.
+1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-hidden="true" aria-label="cross-reference" %} Autolink references**.
1. At the top right of the page, click **Add autolink reference**.
diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
index c0440454efbc..a04a26963a4e 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
@@ -22,6 +22,6 @@ You can also enable code review limits for an organization. If you enable limits
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. Under **Access**, click **{% octicon "comment-discussion" aria-hidden="true" %} Moderation options**.
+1. Under **Access**, click **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Moderation options**.
1. Under **Moderation options**, click **Code review limits**.
1. Select or deselect **Limit to users explicitly granted read or higher access**.
diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository.md b/content/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository.md
index 5504df14831c..aef9d81e1471 100644
--- a/content/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository.md
+++ b/content/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository.md
@@ -22,25 +22,25 @@ For each activity, you can view the exact changes by clicking "Compare changes."
{% data reusables.repositories.navigate-to-repo %}
1. There are two ways to enter the activity view:
- * On the main page of the repository, to the right of the list of files, click **{% octicon "pulse" aria-hidden="true" %} Activity**.
+ * On the main page of the repository, to the right of the list of files, click **{% octicon "pulse" aria-hidden="true" aria-label="pulse" %} Activity**.
- * Alternatively, click **{% octicon "git-branch" aria-hidden="true" %} Branches**, then to the right of any branch, click **{% octicon "pulse" aria-label="View branch activity" %}**.
+ * Alternatively, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Branches**, then to the right of any branch, click **{% octicon "pulse" aria-label="View branch activity" %}**.
1. Use the dropdown menus to filter the activity view.
- * To see activity on a particular branch, select the **{% octicon "git-branch" aria-hidden="true" %} BRANCH NAME** dropdown menu, then click a branch name. Alternatively, within the dropdown menu, start typing a branch name into the search field. To view activity across all branches in the repository, click **View activity for all branches**.
+ * To see activity on a particular branch, select the **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} BRANCH NAME** dropdown menu, then click a branch name. Alternatively, within the dropdown menu, start typing a branch name into the search field. To view activity across all branches in the repository, click **View activity for all branches**.
- * To filter by activity type, select the **{% octicon "pulse" aria-hidden="true" %} All activity** dropdown menu, then click an activity type. You can choose to display direct pushes, pull request merges, force pushes, branch creations, and branch deletions.
+ * To filter by activity type, select the **{% octicon "pulse" aria-hidden="true" aria-label="pulse" %} All activity** dropdown menu, then click an activity type. You can choose to display direct pushes, pull request merges, force pushes, branch creations, and branch deletions.
- * To filter by user, select the **{% octicon "people" aria-hidden="true" %} All users** dropdown menu, then click a username. Alternatively, within the dropdown menu, start typing a username into the search field.
+ * To filter by user, select the **{% octicon "people" aria-hidden="true" aria-label="people" %} All users** dropdown menu, then click a username. Alternatively, within the dropdown menu, start typing a username into the search field.
- * To filter by time, select the **{% octicon "clock" aria-hidden="true" %} All time** dropdown menu, then click a time period.
+ * To filter by time, select the **{% octicon "clock" aria-hidden="true" aria-label="clock" %} All time** dropdown menu, then click a time period.
1. Optionally, to see some additional details about the activity, such as the incoming branch name from a pull request, hover over the embedded link.
-1. To see exactly what changes were introduced by a particular activity, to the right of the activity, select {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "git-compare" aria-hidden="true" %} Compare changes**.
+1. To see exactly what changes were introduced by a particular activity, to the right of the activity, select {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "git-compare" aria-hidden="true" aria-label="git-compare" %} Compare changes**.
diff --git a/content/repositories/working-with-files/using-files/downloading-source-code-archives.md b/content/repositories/working-with-files/using-files/downloading-source-code-archives.md
index 70eacf63d77f..eb019cb677c1 100644
--- a/content/repositories/working-with-files/using-files/downloading-source-code-archives.md
+++ b/content/repositories/working-with-files/using-files/downloading-source-code-archives.md
@@ -28,14 +28,14 @@ You can download the source code archives in three ways.
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.releases %}
1. Scroll down to the "Assets" section of the release.
-1. To download the source code, click **{% octicon "file-zip" aria-hidden="true" %} Source code (zip)** or **{% octicon "file-zip" aria-hidden="true" %} Source code (tar.gz)**.
+1. To download the source code, click **{% octicon "file-zip" aria-hidden="true" aria-label="file-zip" %} Source code (zip)** or **{% octicon "file-zip" aria-hidden="true" aria-label="file-zip" %} Source code (tar.gz)**.
### Downloading source code archives from a tag
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.releases %}
1. At the top of the Releases page, click **Tags**.
-1. To download the source code, click **{% octicon "file-zip" aria-hidden="true" %} zip** or **{% octicon "file-zip" aria-hidden="true" %} tar.gz**.
+1. To download the source code, click **{% octicon "file-zip" aria-hidden="true" aria-label="file-zip" %} zip** or **{% octicon "file-zip" aria-hidden="true" aria-label="file-zip" %} tar.gz**.
diff --git a/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/content/repositories/working-with-files/using-files/navigating-code-on-github.md
index 2f847453f1e4..9d3186f418e2 100644
--- a/content/repositories/working-with-files/using-files/navigating-code-on-github.md
+++ b/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -47,8 +47,8 @@ Symbol search is a feature of code search. For more information, see [AUTOTITLE]
* To search for a symbol in the repository as a whole, in the symbols pane, click **Search for this symbol in this repository**. To search for a symbol in all repositories on {% data variables.product.prodname_dotcom %}, click **all repositories**.
1. To navigate between references to a symbol, click {% octicon "chevron-down" aria-label="The downwards-facing chevron icon" %} or {% octicon "chevron-up" aria-label="The upwards-facing chevron icon" %}.
-1. To navigate to a specific reference to a symbol, click a result of the symbol search under **{% octicon "chevron-down" aria-hidden="true" %} In this file**.
-1. To exit the search for a specific symbol, click **{% octicon "arrow-left" aria-hidden="true" %} All Symbols**.
+1. To navigate to a specific reference to a symbol, click a result of the symbol search under **{% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} In this file**.
+1. To exit the search for a specific symbol, click **{% octicon "arrow-left" aria-hidden="true" aria-label="arrow-left" %} All Symbols**.
{% endif %}
## Jumping to the definition of a function or method
diff --git a/content/search-github/github-code-search/using-github-code-search.md b/content/search-github/github-code-search/using-github-code-search.md
index ace33bbd3cb9..d1d2a3840476 100644
--- a/content/search-github/github-code-search/using-github-code-search.md
+++ b/content/search-github/github-code-search/using-github-code-search.md
@@ -68,11 +68,11 @@ You can use {% data variables.product.prodname_copilot %} to ask questions about
## Creating and managing saved searches
1. In the top navigation of {% data variables.product.prodname_dotcom %}, click the search bar and type `saved:`.
-1. Under the search bar, in the "Saved queries" section, click **{% octicon "plus-circle" aria-hidden="true" %} Manage saved searches**.
+1. Under the search bar, in the "Saved queries" section, click **{% octicon "plus-circle" aria-hidden="true" aria-label="plus-circle" %} Manage saved searches**.
1. In the pop-up window, type both the name you want for your saved search and the query you want to save.
1. To finish creating your saved search, click **Create saved search**.
1. To see your saved search, click the search bar. Your saved search will be in the "Saved queries" section. Clicking on a saved search entry will add the query to the search bar and filter the suggestions accordingly.
-1. To manage a saved search, type `saved:` in the search bar, then click **{% octicon "plus-circle" aria-hidden="true" %} Manage saved searches**.
+1. To manage a saved search, type `saved:` in the search bar, then click **{% octicon "plus-circle" aria-hidden="true" aria-label="plus-circle" %} Manage saved searches**.
* To edit a saved search, to the right of the search, click {% octicon "pencil" aria-label="The pencil icon" %}.
* To delete a saved search, to the right of the search, click {% octicon "trash" aria-label="The trash icon" %}.
diff --git a/content/sponsors/getting-started-with-github-sponsors/navigating-your-sponsors-dashboard.md b/content/sponsors/getting-started-with-github-sponsors/navigating-your-sponsors-dashboard.md
index d9f60585b563..41235a09d8bc 100644
--- a/content/sponsors/getting-started-with-github-sponsors/navigating-your-sponsors-dashboard.md
+++ b/content/sponsors/getting-started-with-github-sponsors/navigating-your-sponsors-dashboard.md
@@ -23,7 +23,7 @@ You can also manage current sponsorships and view past sponsorships, and export
{% data reusables.organizations.sponsors-dashboard %}
{% data reusables.organizations.navigate-to-sponsoring %}
-1. From the left sidebar, click **{% octicon "heart" aria-hidden="true" %} Your sponsorships**.
+1. From the left sidebar, click **{% octicon "heart" aria-hidden="true" aria-label="heart" %} Your sponsorships**.
## Viewing dependencies
@@ -33,7 +33,7 @@ You can also export the list of dependencies as a CSV file.
{% data reusables.organizations.sponsors-dashboard %}
{% data reusables.organizations.navigate-to-sponsoring %}
-1. From the left sidebar, click **{% octicon "package-dependencies" aria-hidden="true" %} Dependencies**.
+1. From the left sidebar, click **{% octicon "package-dependencies" aria-hidden="true" aria-label="package-dependencies" %} Dependencies**.
## Viewing bulk sponsorships
@@ -49,7 +49,7 @@ You can manage your open and paid invoices from your sponsors dashboard. To be a
{% data reusables.organizations.sponsors-dashboard %}
{% data reusables.organizations.navigate-to-sponsoring %}
-1. From the left sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Invoices**.
+1. From the left sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Invoices**.
## Viewing settings
@@ -61,13 +61,13 @@ You can also choose to attribute your paid sponsorships to another account by li
{% data reusables.organizations.sponsors-dashboard %}
{% data reusables.organizations.navigate-to-sponsoring %}
-1. From the left sidebar, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. From the left sidebar, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. Under "Sponsorship log", click **log**.
### Link your sponsorships to another account
{% data reusables.organizations.sponsors-dashboard %}
{% data reusables.organizations.navigate-to-sponsoring %}
-1. From the left sidebar, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. From the left sidebar, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. Select the **Linked account** dropdown and click the account to use.
1. Click **Link account** to confirm your selection.
diff --git a/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
index 20aa9f28fc8f..4e1c935a9459 100644
--- a/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
+++ b/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -60,5 +60,5 @@ You can export your sponsorship transactions by month. {% data variables.product
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
{% data reusables.sponsors.your-sponsors-tab %}
-1. In the top-right, click **{% octicon "download" aria-hidden="true" %} Export**.
+1. In the top-right, click **{% octicon "download" aria-hidden="true" aria-label="download" %} Export**.
1. Choose a time frame and a format for the data you'd like to export, then click **Start export**.
diff --git a/content/sponsors/sponsoring-open-source-contributors/about-sponsorships-fees-and-taxes.md b/content/sponsors/sponsoring-open-source-contributors/about-sponsorships-fees-and-taxes.md
index 32269a088361..bc59c11e3cdd 100644
--- a/content/sponsors/sponsoring-open-source-contributors/about-sponsorships-fees-and-taxes.md
+++ b/content/sponsors/sponsoring-open-source-contributors/about-sponsorships-fees-and-taxes.md
@@ -63,7 +63,7 @@ You can access the sponsorships dashboard through your organization's profile.
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
-1. Under your organization name, click **{% octicon "heart" aria-hidden="true" %} Sponsoring**.
+1. Under your organization name, click **{% octicon "heart" aria-hidden="true" aria-label="heart" %} Sponsoring**.
## Sponsorship fees
diff --git a/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
index 5bd96432bea3..c1fbc6f569fc 100644
--- a/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
+++ b/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -17,7 +17,7 @@ shortTitle: Attribute sponsorships
1. Navigate to the organization whose sponsorships you want to attribute to another organization.
{% data reusables.organizations.navigate-to-sponsoring %}
-1. In the sidebar, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. In the sidebar, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
diff --git a/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md b/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
index 4c4ec8b1802b..215c253f65bf 100644
--- a/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
+++ b/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
@@ -40,7 +40,7 @@ If your organization currently pays for {% data variables.product.prodname_spons
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
1. Scroll to the "{% data variables.product.prodname_sponsors %}" section and click **Switch to invoiced billing**.
1. Compare credit card and invoice billing on the next page. To proceed with changing to invoiced billing, click **Switch to invoiced billing**.
1. Fill out the form and click **Submit**.
@@ -53,7 +53,7 @@ To add money to your balance, you need to create an invoice. You can then use yo
1. Navigate to the organization you want to create an invoice for.
{% data reusables.organizations.navigate-to-sponsoring %}
-1. In the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Invoices**.
+1. In the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Invoices**.
1. To create a new invoice, click **Create an invoice**.
@@ -73,7 +73,7 @@ You can view your {% data variables.product.company_short %} Invoiced Sponsor Ag
1. Navigate to the organization.
{% data reusables.organizations.navigate-to-sponsoring %}
-1. In the sidebar, click **{% octicon "graph" aria-hidden="true" %} Insights**.
+1. In the sidebar, click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} Insights**.
1. Under your balance, click **{% data variables.product.company_short %} Invoiced Sponsor Agreement** to view the agreement.
## Understanding your {% data variables.product.prodname_sponsors %} invoice
diff --git a/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor-through-github.md b/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor-through-github.md
index aa4b194da310..5d851a17890f 100644
--- a/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor-through-github.md
+++ b/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor-through-github.md
@@ -56,7 +56,7 @@ Before you can sponsor an account, you must have a verified email address. For m
To sponsor these maintainers using the downloaded file, in the corresponding cells of the "Sponsorship amount in USD" column, input sponsorship amounts in US dollars for each maintainer you want to sponsor.
1. On {% data variables.product.prodname_dotcom %}, in the "Bulk Sponsor" box above the list of developers who maintain your dependencies, click **Get started**. Organizations can also access the "Bulk Sponsor" functionality from the sponsors dashboard.
-1. Optionally, to change which account or organization you are sponsoring as, select the **Sponsor as USERNAME** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click the desired account or organization from the options that appear.
+1. Optionally, to change which account or organization you are sponsoring as, select the **Sponsor as USERNAME** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click the desired account or organization from the options that appear.
1. To upload the CSV file of accounts you would like to sponsor, in the "Import a CSV" section, click **Choose your file**, then navigate to the CSV file you would like to upload. Select the CSV file, then click **Open**.
diff --git a/content/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks.md b/content/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks.md
index bbdb16997876..e71b81d91213 100644
--- a/content/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks.md
+++ b/content/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks.md
@@ -22,7 +22,7 @@ You can use the {% data variables.product.company_short %} web interface or the
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Code and automation" section of the sidebar, click **{% octicon "webhook" aria-hidden="true" %} Webhooks**.
+1. In the "Code and automation" section of the sidebar, click **{% octicon "webhook" aria-hidden="true" aria-label="webhook" %} Webhooks**.
{% data reusables.webhooks.webhook_url_list_redeliver %}
{% data reusables.webhooks.webhook_recent_deliveries_tab %}
1. Click the delivery GUID for the delivery that you want to redeliver.
@@ -36,7 +36,7 @@ You can use the {% data variables.product.company_short %} web interface or the
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-1. In the "Code and automation" section of the sidebar, click **{% octicon "webhook" aria-hidden="true" %} Webhooks**.
+1. In the "Code and automation" section of the sidebar, click **{% octicon "webhook" aria-hidden="true" aria-label="webhook" %} Webhooks**.
{% data reusables.webhooks.webhook_url_list_redeliver %}
{% data reusables.webhooks.webhook_recent_deliveries_tab %}
1. Click the delivery GUID for the delivery that you want to redeliver.
diff --git a/content/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries.md b/content/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries.md
index 1efab22dd7cc..5420a94866b9 100644
--- a/content/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries.md
+++ b/content/webhooks/testing-and-troubleshooting-webhooks/viewing-webhook-deliveries.md
@@ -30,7 +30,7 @@ You can use the {% data variables.product.company_short %} web interface or the
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Code and automation" section of the sidebar, click **{% octicon "webhook" aria-hidden="true" %} Webhooks**.
+1. In the "Code and automation" section of the sidebar, click **{% octicon "webhook" aria-hidden="true" aria-label="webhook" %} Webhooks**.
{% data reusables.webhooks.webhook_url_list %}
{% data reusables.webhooks.webhook_recent_deliveries_tab %}
1. Click a delivery GUID to view details.
@@ -43,7 +43,7 @@ You can use the {% data variables.product.company_short %} web interface or the
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
-1. In the "Code and automation" section of the sidebar, click **{% octicon "webhook" aria-hidden="true" %} Webhooks**.
+1. In the "Code and automation" section of the sidebar, click **{% octicon "webhook" aria-hidden="true" aria-label="webhook" %} Webhooks**.
{% data reusables.webhooks.webhook_url_list %}
{% data reusables.webhooks.webhook_recent_deliveries_tab %}
1. Click a delivery GUID to view details.
diff --git a/data/reusables/accounts/set-profile-picture.md b/data/reusables/accounts/set-profile-picture.md
index 1c6acffc1a50..2f20ae37c9b0 100644
--- a/data/reusables/accounts/set-profile-picture.md
+++ b/data/reusables/accounts/set-profile-picture.md
@@ -1,4 +1,4 @@
-1. Under "Profile Picture", select **{% octicon "pencil" aria-hidden="true" %} Edit**, then click **Upload a photo...**.
+1. Under "Profile Picture", select **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit**, then click **Upload a photo...**.
1. Select an image, then click **Upload**.
diff --git a/data/reusables/actions/add-hosted-runner.md b/data/reusables/actions/add-hosted-runner.md
index d729a63cb118..6a5157070ae0 100644
--- a/data/reusables/actions/add-hosted-runner.md
+++ b/data/reusables/actions/add-hosted-runner.md
@@ -1,4 +1,4 @@
-1. Click **New runner**, then click **{% octicon "mark-github" aria-hidden="true" %} New {% data variables.product.prodname_dotcom %}-hosted runner**.
+1. Click **New runner**, then click **{% octicon "mark-github" aria-hidden="true" aria-label="mark-github" %} New {% data variables.product.prodname_dotcom %}-hosted runner**.
1. Complete the required details to configure your new runner:
* **Name:** Enter a name for your new runner. For easier identification, this should indicate its hardware and operating configuration, such as `ubuntu-20.04-16core`.
diff --git a/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
index d9e6ca974da1..09bf28b9ccc9 100644
--- a/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
+++ b/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
@@ -1,12 +1,12 @@
{% ifversion fpt %}
1. Navigate to the main page of the organization or repository.
-1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
1. In the left sidebar, click **Actions**, then click **Runners**.
{% elsif ghec %}
1. Navigate to your runner settings:
- * **In an organization or repository:** Navigate to the main page, then click **{% octicon "gear" aria-hidden="true" %} Settings**.
+ * **In an organization or repository:** Navigate to the main page, then click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
* **If using an enterprise account:** Navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.github %}, then clicking **Your enterprises**, then clicking the enterprise.
1. Navigate to the {% data variables.product.prodname_actions %} settings:
* **In an organization or repository:** Click **Actions** in the left sidebar, then click **Runners**.
- * **If using an enterprise account:** In the left sidebar, click **"{% octicon "law" aria-hidden="true" %} Policies"**, then click **Actions**, then click the **Runners** tab.
+ * **If using an enterprise account:** In the left sidebar, click **"{% octicon "law" aria-hidden="true" aria-label="law" %} Policies"**, then click **Actions**, then click the **Runners** tab.
{% endif %}
diff --git a/data/reusables/actions/runner-groups-org-navigation.md b/data/reusables/actions/runner-groups-org-navigation.md
index 92291984f152..fd40077bde26 100644
--- a/data/reusables/actions/runner-groups-org-navigation.md
+++ b/data/reusables/actions/runner-groups-org-navigation.md
@@ -1,3 +1,3 @@
1. Navigate to the main page of the organization where your runner groups are located.
-1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
diff --git a/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md b/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
index 242e3d822cb1..f2d6f421135b 100644
--- a/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
+++ b/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
@@ -1 +1 @@
-1. In your organization or repository, navigate to the main page and click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. In your organization or repository, navigate to the main page and click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
diff --git a/data/reusables/actions/self-hosted-runner-navigate-to-org.md b/data/reusables/actions/self-hosted-runner-navigate-to-org.md
index 1ed444c9a905..16cdbd9a3f42 100644
--- a/data/reusables/actions/self-hosted-runner-navigate-to-org.md
+++ b/data/reusables/actions/self-hosted-runner-navigate-to-org.md
@@ -1,3 +1,3 @@
1. Navigate to the main page of the organization where your self-hosted runner group is registered.
-1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
{% data reusables.organizations.settings-sidebar-actions-runners %}
diff --git a/data/reusables/actions/self-hosted-runner-navigate-to-repo.md b/data/reusables/actions/self-hosted-runner-navigate-to-repo.md
index d0076c416f48..e1e7e5a7201e 100644
--- a/data/reusables/actions/self-hosted-runner-navigate-to-repo.md
+++ b/data/reusables/actions/self-hosted-runner-navigate-to-repo.md
@@ -1,3 +1,3 @@
1. Navigate to the main page of the repository where your self-hosted runner group is registered.
-1. Click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
{% data reusables.organizations.settings-sidebar-actions-runners %}
diff --git a/data/reusables/actions/settings-ui/settings-actions-general.md b/data/reusables/actions/settings-ui/settings-actions-general.md
index 020c70803f24..b61fb18b44a4 100644
--- a/data/reusables/actions/settings-ui/settings-actions-general.md
+++ b/data/reusables/actions/settings-ui/settings-actions-general.md
@@ -1,2 +1,2 @@
{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%}
-1. In the left sidebar, click **{% octicon "play" aria-hidden="true" %} Actions**, then click **General**.
+1. In the left sidebar, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Actions**, then click **General**.
diff --git a/data/reusables/actions/settings-ui/settings-actions-runner-groups.md b/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
index acaabd6f864c..a7ff96eb501f 100644
--- a/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
+++ b/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
@@ -1,2 +1,2 @@
-1. In the left sidebar, click **{% octicon "play" aria-hidden="true" %} Actions**, then click **Runner groups**.
+1. In the left sidebar, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Actions**, then click **Runner groups**.
diff --git a/data/reusables/actions/settings-ui/settings-actions-runners.md b/data/reusables/actions/settings-ui/settings-actions-runners.md
index 834be542c77b..5e4f6f84de86 100644
--- a/data/reusables/actions/settings-ui/settings-actions-runners.md
+++ b/data/reusables/actions/settings-ui/settings-actions-runners.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "play" aria-hidden="true" %} Actions**, then click **Runners**.
+1. In the left sidebar, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Actions**, then click **Runners**.
diff --git a/data/reusables/actions/sidebar-secrets-and-variables.md b/data/reusables/actions/sidebar-secrets-and-variables.md
index ae625f4b7510..b6b105ce8f20 100644
--- a/data/reusables/actions/sidebar-secrets-and-variables.md
+++ b/data/reusables/actions/sidebar-secrets-and-variables.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, then click **Actions**.
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-hidden="true" aria-label="key-asterisk" %} Secrets and variables**, then click **Actions**.
diff --git a/data/reusables/actions/viewing-actions-metrics.md b/data/reusables/actions/viewing-actions-metrics.md
index 27918faf6afc..7559f4c46332 100644
--- a/data/reusables/actions/viewing-actions-metrics.md
+++ b/data/reusables/actions/viewing-actions-metrics.md
@@ -2,10 +2,10 @@
1. Optionally, to select a time period to view usage metrics for, choose an option from the **Period** drop down menu at the top right of the page. For more information, see [Understanding {% data variables.product.prodname_actions %} metrics aggregation](#understanding-github-actions-metrics-aggregation).
1. Click on the tab that contains the metrics you would like to view. For more information, see [About {% data variables.product.prodname_actions %} usage metrics](#about-github-actions-usage-metrics) or [About {% data variables.product.prodname_actions %} performance metrics](#about-github-actions-performance-metrics).
1. Optionally, to filter the data displayed in a tab, create a filter.
- 1. Click on the **{% octicon "filter" aria-hidden="true" %} Filter** button.
- 1. Click **{% octicon "plus" aria-hidden="true" %} Add a filter**.
+ 1. Click on the **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter** button.
+ 1. Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a filter**.
1. Choose a metric you would like to filter results by.
1. Depending on the metric you chose, fill out information in the "Qualifier," "Operator," and "Value" columns.
- 1. Optionally, click **{% octicon "plus" aria-hidden="true" %} Add a filter** to add another filter.
+ 1. Optionally, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a filter** to add another filter.
1. Click **Apply**.
1. Optionally, to download usage metrics to a CSV file, click {% octicon "download" aria-label="Download report" %}.
diff --git a/data/reusables/actions/workflows/approve-workflow-runs.md b/data/reusables/actions/workflows/approve-workflow-runs.md
index 77e53a89b3d8..619cf7865f2b 100644
--- a/data/reusables/actions/workflows/approve-workflow-runs.md
+++ b/data/reusables/actions/workflows/approve-workflow-runs.md
@@ -4,4 +4,4 @@ Maintainers with write access to a repository can use the following procedure to
{% data reusables.repositories.choose-pr-review %}
{% data reusables.repositories.changed-files %}
1. Inspect the proposed changes in the pull request and ensure that you are comfortable running your workflows on the pull request branch. You should be especially alert to any proposed changes in the `.github/workflows/` directory that affect workflow files.
-1. If you are comfortable with running workflows on the pull request branch, return to the **{% octicon "comment-discussion" aria-hidden="true" %} Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
+1. If you are comfortable with running workflows on the pull request branch, return to the **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
diff --git a/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
index 3fb740e5cbc6..77b53b3b388a 100644
--- a/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
+++ b/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
@@ -1,7 +1,7 @@
1. Enter the details for your new custom pattern. You must at least provide the name for your pattern, and a regular expression for the format of your secret pattern.
1. In the "Pattern name" field, type a name for your pattern.
1. In the "Secret format" field, type a regular expression for the format of your secret pattern.{% ifversion secret-scanning-custom-pattern-ai-generated %} Alternatively, you can use the generator to generate a regular expression for you. For more information, see [AUTOTITLE](/code-security/secret-scanning/copilot-secret-scanning/generating-regular-expressions-for-custom-patterns-with-copilot-secret-scanning).{% endif %}
- 1. You can click **More options {% octicon "chevron-down" aria-hidden="true" %}** to provide other surrounding content or additional match requirements for the secret format.
+ 1. You can click **More options {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %}** to provide other surrounding content or additional match requirements for the secret format.
1. Provide a sample test string to make sure your configuration is matching the patterns you expect.
{% ifversion fpt or ghec %}
diff --git a/data/reusables/advanced-security/secret-scanning-generate-regular-expression-custom-pattern.md b/data/reusables/advanced-security/secret-scanning-generate-regular-expression-custom-pattern.md
index 7cbdffaf806c..a8061a473eb8 100644
--- a/data/reusables/advanced-security/secret-scanning-generate-regular-expression-custom-pattern.md
+++ b/data/reusables/advanced-security/secret-scanning-generate-regular-expression-custom-pattern.md
@@ -13,4 +13,4 @@
-1. You can click **More options {% octicon "chevron-down" aria-hidden="true" %}** to provide other surrounding content or additional match requirements for the secret format. {% data variables.product.prodname_dotcom %} will add the examples you typed in the sliding panel to the **Test string** field.
+1. You can click **More options {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %}** to provide other surrounding content or additional match requirements for the secret format. {% data variables.product.prodname_dotcom %} will add the examples you typed in the sliding panel to the **Test string** field.
diff --git a/data/reusables/apps/enterprise-apps-steps.md b/data/reusables/apps/enterprise-apps-steps.md
index 7746ca61aeda..5f3f75bd2727 100644
--- a/data/reusables/apps/enterprise-apps-steps.md
+++ b/data/reusables/apps/enterprise-apps-steps.md
@@ -1,7 +1,7 @@
{% ifversion enterprise-apps-public-beta %}
1. Navigate to the {% data variables.product.prodname_github_app %} settings.
* For an app owned by a personal account or organization:
- 1. In the left sidebar, click **{% octicon "code" aria-hidden="true" %} Developer settings**, then click **{% data variables.product.prodname_github_apps %}**.
+ 1. In the left sidebar, click **{% octicon "code" aria-hidden="true" aria-label="code" %} Developer settings**, then click **{% data variables.product.prodname_github_apps %}**.
* For an app owned by an enterprise:
1. In the left sidebar, {% ifversion ghec %}under "Settings",{% elsif ghes %} click **Settings**, then{% endif %} click **{% data variables.product.prodname_github_apps %}**.{% else %}
{% data reusables.user-settings.developer_settings %}
diff --git a/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
index cd7f8f912b2e..4148a1c14e4d 100644
--- a/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
+++ b/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
@@ -1 +1 @@
-1. In the "Archive" section of the sidebar, click **{% octicon "log" aria-hidden="true" %} Logs**, then click **Audit log**.
+1. In the "Archive" section of the sidebar, click **{% octicon "log" aria-hidden="true" aria-label="log" %} Logs**, then click **Audit log**.
diff --git a/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
index ab12e111c51d..38f01e051166 100644
--- a/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
+++ b/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
@@ -1 +1 @@
-1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-hidden="true" %} Security log**.
+1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-hidden="true" aria-label="log" %} Security log**.
diff --git a/data/reusables/billing/enterprise-billing-menu.md b/data/reusables/billing/enterprise-billing-menu.md
index f76bed246a6b..55f6b4839d01 100644
--- a/data/reusables/billing/enterprise-billing-menu.md
+++ b/data/reusables/billing/enterprise-billing-menu.md
@@ -1 +1 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "credit-card" aria-hidden="true" %} Billing and licensing**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and licensing**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.{% endif %}
diff --git a/data/reusables/billing/org-billing-menu.md b/data/reusables/billing/org-billing-menu.md
index 7675281643dc..7b4c52054aab 100644
--- a/data/reusables/billing/org-billing-menu.md
+++ b/data/reusables/billing/org-billing-menu.md
@@ -1 +1 @@
-1. On the left side of the page, in the organization sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. On the left side of the page, in the organization sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**.
diff --git a/data/reusables/classroom/assignments-guide-create-the-assignment.md b/data/reusables/classroom/assignments-guide-create-the-assignment.md
index ad83a6e929db..60964153f262 100644
--- a/data/reusables/classroom/assignments-guide-create-the-assignment.md
+++ b/data/reusables/classroom/assignments-guide-create-the-assignment.md
@@ -1,5 +1,5 @@
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
1. Navigate to a classroom.
-1. In the **{% octicon "repo" aria-hidden="true" %} Assignments** tab, create the assignment.
+1. In the **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Assignments** tab, create the assignment.
* If this your first assignment, click **Create an assignment**.
* Otherwise, click **New assignment** on the right side.
diff --git a/data/reusables/classroom/clear-all-assignment-overview.md b/data/reusables/classroom/clear-all-assignment-overview.md
index 19f2c5220abb..9fc1ab139d41 100644
--- a/data/reusables/classroom/clear-all-assignment-overview.md
+++ b/data/reusables/classroom/clear-all-assignment-overview.md
@@ -1 +1 @@
-1. Optionally, to remove all filters, searches, and sorts, click **{% octicon "x" aria-hidden="true" %} Clear current search query, filters, and sorts**.
+1. Optionally, to remove all filters, searches, and sorts, click **{% octicon "x" aria-hidden="true" aria-label="x" %} Clear current search query, filters, and sorts**.
diff --git a/data/reusables/classroom/click-settings.md b/data/reusables/classroom/click-settings.md
index d746b0dd004a..29cb1807e935 100644
--- a/data/reusables/classroom/click-settings.md
+++ b/data/reusables/classroom/click-settings.md
@@ -1,3 +1,3 @@
-1. Under the classroom name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. Under the classroom name, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
diff --git a/data/reusables/classroom/click-students.md b/data/reusables/classroom/click-students.md
index 99524847143d..8000c378317d 100644
--- a/data/reusables/classroom/click-students.md
+++ b/data/reusables/classroom/click-students.md
@@ -1,3 +1,3 @@
-1. Under the classroom name, click **{% octicon "people" aria-hidden="true" %} Students**.
+1. Under the classroom name, click **{% octicon "people" aria-hidden="true" aria-label="people" %} Students**.
diff --git a/data/reusables/code-scanning/campaigns-click.md b/data/reusables/code-scanning/campaigns-click.md
index 5cd772cf5357..5dde362a342a 100644
--- a/data/reusables/code-scanning/campaigns-click.md
+++ b/data/reusables/code-scanning/campaigns-click.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "goal" aria-hidden="true" %} Campaigns**.
+1. In the left sidebar, click **{% octicon "goal" aria-hidden="true" aria-label="goal" %} Campaigns**.
diff --git a/data/reusables/code-scanning/click-code-security-enterprise.md b/data/reusables/code-scanning/click-code-security-enterprise.md
index acd413807e22..5d1b5d6b274a 100644
--- a/data/reusables/code-scanning/click-code-security-enterprise.md
+++ b/data/reusables/code-scanning/click-code-security-enterprise.md
@@ -1 +1 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "shield" aria-hidden="true" %} Security**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "shield" aria-hidden="true" %} Code Security**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Code Security**.{% endif %}
diff --git a/data/reusables/codespaces/accessing-prebuild-configuration.md b/data/reusables/codespaces/accessing-prebuild-configuration.md
index bcf06f34ab36..6894ed8c0d1c 100644
--- a/data/reusables/codespaces/accessing-prebuild-configuration.md
+++ b/data/reusables/codespaces/accessing-prebuild-configuration.md
@@ -1,3 +1,3 @@
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
-1. In the "Code & automation" section of the side bar, click **{% octicon "codespaces" aria-hidden="true" %} {% data variables.product.prodname_codespaces %}**.
+1. In the "Code & automation" section of the side bar, click **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} {% data variables.product.prodname_codespaces %}**.
diff --git a/data/reusables/codespaces/codespaces-org-policies.md b/data/reusables/codespaces/codespaces-org-policies.md
index a95b603c9b53..807edcf95265 100644
--- a/data/reusables/codespaces/codespaces-org-policies.md
+++ b/data/reusables/codespaces/codespaces-org-policies.md
@@ -1,3 +1,3 @@
-1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-hidden="true" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
1. On the "Codespaces policies" page, click **Create Policy**.
1. Enter a name for your new policy.
diff --git a/data/reusables/codespaces/navigating-to-a-codespace.md b/data/reusables/codespaces/navigating-to-a-codespace.md
index 22f34e2823a5..c11449595199 100644
--- a/data/reusables/codespaces/navigating-to-a-codespace.md
+++ b/data/reusables/codespaces/navigating-to-a-codespace.md
@@ -5,4 +5,4 @@
-Alternatively, you can see any of your codespaces for a specific repository by navigating to that repository, clicking the **{% octicon "code" aria-hidden="true" %} Code** button and selecting the **{% data variables.product.prodname_codespaces %}** tab. The dropdown menu will display all active codespaces for the repository.
+Alternatively, you can see any of your codespaces for a specific repository by navigating to that repository, clicking the **{% octicon "code" aria-hidden="true" aria-label="code" %} Code** button and selecting the **{% data variables.product.prodname_codespaces %}** tab. The dropdown menu will display all active codespaces for the repository.
diff --git a/data/reusables/codespaces/sidebar-secret.md b/data/reusables/codespaces/sidebar-secret.md
index c759e4ae3224..dfa6aad1bfe9 100644
--- a/data/reusables/codespaces/sidebar-secret.md
+++ b/data/reusables/codespaces/sidebar-secret.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, then click **{% data variables.product.prodname_codespaces %}**.
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-hidden="true" aria-label="key-asterisk" %} Secrets and variables**, then click **{% data variables.product.prodname_codespaces %}**.
diff --git a/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/data/reusables/codespaces/you-can-see-all-your-codespaces.md
index 27aece0a41b0..85952ad7a504 100644
--- a/data/reusables/codespaces/you-can-see-all-your-codespaces.md
+++ b/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -1 +1 @@
-You can see every available codespace that you have created on the "Your codespaces" page. To display this page, in the top-left corner of {% data variables.product.github %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "codespaces" aria-hidden="true" %} Codespaces**. This takes you to [github.com/codespaces](https://github.com/codespaces).
+You can see every available codespace that you have created on the "Your codespaces" page. To display this page, in the top-left corner of {% data variables.product.github %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} Codespaces**. This takes you to [github.com/codespaces](https://github.com/codespaces).
diff --git a/data/reusables/codespaces/your-codespaces-procedure-step.md b/data/reusables/codespaces/your-codespaces-procedure-step.md
index 4391227c7d75..09233ec0e898 100644
--- a/data/reusables/codespaces/your-codespaces-procedure-step.md
+++ b/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -1 +1 @@
-1. In the top-left corner of {% data variables.product.github %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "codespaces" aria-hidden="true" %} Codespaces** to take you to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces).
+1. In the top-left corner of {% data variables.product.github %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} Codespaces** to take you to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces).
diff --git a/data/reusables/copilot-business-for-non-ghe/assign-licenses.md b/data/reusables/copilot-business-for-non-ghe/assign-licenses.md
index a9fdf3f1fa30..ff24c468b183 100644
--- a/data/reusables/copilot-business-for-non-ghe/assign-licenses.md
+++ b/data/reusables/copilot-business-for-non-ghe/assign-licenses.md
@@ -1,7 +1,7 @@
When you have created a team in the enterprise, you can assign licenses to all members of the team.
{% data reusables.billing.enterprise-billing-menu %}
-1. Under **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**, click **Licensing**.
+1. Under **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**, click **Licensing**.
1. In the "{% data variables.product.prodname_copilot_business_short %}" section, click **Manage seats**.
diff --git a/data/reusables/copilot/access-settings.md b/data/reusables/copilot/access-settings.md
index df1d09ea8f3c..75623e8d0091 100644
--- a/data/reusables/copilot/access-settings.md
+++ b/data/reusables/copilot/access-settings.md
@@ -1 +1 @@
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**.
diff --git a/data/reusables/copilot/chat-about-specific-lines.md b/data/reusables/copilot/chat-about-specific-lines.md
index 56e0e5d16bad..1b10533821b7 100644
--- a/data/reusables/copilot/chat-about-specific-lines.md
+++ b/data/reusables/copilot/chat-about-specific-lines.md
@@ -1,13 +1,13 @@
1. On {% data variables.product.github %}, navigate to a repository and open a file.
1. Do one of the following:
- * To ask a question about the **entire file**, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) at the top right of the file view.
+ * To ask a question about the **entire file**, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) at the top right of the file view.
* To ask a question about **specific lines** within the file:
1. Click the line number for the first line you want to ask about, hold down Shift, then click the line number for the last line you want to select.
- 1. To ask your own question about the selected lines, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" %}) to the right of your selection, then type your question in the {% data variables.product.prodname_copilot_chat %} panel.
+ 1. To ask your own question about the selected lines, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) to the right of your selection, then type your question in the {% data variables.product.prodname_copilot_chat %} panel.
1. To ask a predefined question, click the drop-down menu beside the {% data variables.product.prodname_copilot_short %} icon, then choose one of the options.
diff --git a/data/reusables/copilot/chat-mobile-conversation-buttons.md b/data/reusables/copilot/chat-mobile-conversation-buttons.md
index 11a6da01e831..a6761667d010 100644
--- a/data/reusables/copilot/chat-mobile-conversation-buttons.md
+++ b/data/reusables/copilot/chat-mobile-conversation-buttons.md
@@ -1,5 +1,5 @@
-1. To jump back into a previous conversation you had with {% data variables.product.prodname_copilot_short %}, tap {% octicon "kebab-horizontal" %} in the top right corner of the screen. Either tap on one of the last three recently modified conversations shown, or tap **View all conversations {% octicon "comment-discussion" aria-hidden="true" %}**. This takes you to a list of all your previous conversations with {% data variables.product.prodname_copilot_short %}.
-1. To delete a conversation, tap {% octicon "kebab-horizontal" %} in the top right corner of the screen, and then tap **Delete conversation {% octicon "trash" aria-hidden="true" %}**. This removes the conversation from the list of previous conversations you've had with {% data variables.product.prodname_copilot_short %}.
-1. To start over, with a new conversation, tap {% octicon "kebab-horizontal" %} in the top right corner of the screen, and then tap **New conversation {% octicon "plus" aria-hidden="true" %}**.
+1. To jump back into a previous conversation you had with {% data variables.product.prodname_copilot_short %}, tap {% octicon "kebab-horizontal" aria-label="kebab-horizontal" %} in the top right corner of the screen. Either tap on one of the last three recently modified conversations shown, or tap **View all conversations {% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %}**. This takes you to a list of all your previous conversations with {% data variables.product.prodname_copilot_short %}.
+1. To delete a conversation, tap {% octicon "kebab-horizontal" aria-label="kebab-horizontal" %} in the top right corner of the screen, and then tap **Delete conversation {% octicon "trash" aria-hidden="true" aria-label="trash" %}**. This removes the conversation from the list of previous conversations you've had with {% data variables.product.prodname_copilot_short %}.
+1. To start over, with a new conversation, tap {% octicon "kebab-horizontal" aria-label="kebab-horizontal" %} in the top right corner of the screen, and then tap **New conversation {% octicon "plus" aria-hidden="true" aria-label="plus" %}**.
You should always start a new conversation if you want to ask a question that's unrelated to the current conversation.
diff --git a/data/reusables/copilot/chat-mobile-start-chat.md b/data/reusables/copilot/chat-mobile-start-chat.md
index 5b66dab45b81..ba95415633d3 100644
--- a/data/reusables/copilot/chat-mobile-start-chat.md
+++ b/data/reusables/copilot/chat-mobile-start-chat.md
@@ -1,4 +1,4 @@
-1. In {% data variables.product.prodname_mobile %}, tap the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
> [!NOTE]
- > The **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon is not shown on every page in {% data variables.product.prodname_mobile %}. If you don't see the icon, navigate to a different page in {% data variables.product.prodname_mobile %} and look for the icon there.
+ > The **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon is not shown on every page in {% data variables.product.prodname_mobile %}. If you don't see the icon, navigate to a different page in {% data variables.product.prodname_mobile %} and look for the icon there.
diff --git a/data/reusables/copilot/chat-previous-conversation.md b/data/reusables/copilot/chat-previous-conversation.md
index 40d596191b84..9f12986f1657 100644
--- a/data/reusables/copilot/chat-previous-conversation.md
+++ b/data/reusables/copilot/chat-previous-conversation.md
@@ -1 +1 @@
-1. If the panel contains a previous conversation you had with {% data variables.product.prodname_copilot_short %}, click the {% octicon "plus" aria-hidden="true" %} plus sign icon at the top right of the {% data variables.product.prodname_copilot_short %} panel to start a new conversation.
+1. If the panel contains a previous conversation you had with {% data variables.product.prodname_copilot_short %}, click the {% octicon "plus" aria-hidden="true" aria-label="plus" %} plus sign icon at the top right of the {% data variables.product.prodname_copilot_short %} panel to start a new conversation.
diff --git a/data/reusables/copilot/coding-agent-settings.md b/data/reusables/copilot/coding-agent-settings.md
index a5f1b3e49a54..42342391c970 100644
--- a/data/reusables/copilot/coding-agent-settings.md
+++ b/data/reusables/copilot/coding-agent-settings.md
@@ -1 +1 @@
-1. In the sidebar, under "Code, planning, and automation", click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **{% data variables.copilot.coding_agent_UI %}**.
+1. In the sidebar, under "Code, planning, and automation", click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, and then click **{% data variables.copilot.coding_agent_UI %}**.
diff --git a/data/reusables/copilot/disable-copilot-organization.md b/data/reusables/copilot/disable-copilot-organization.md
index 708d27fcc026..eb1d94104914 100644
--- a/data/reusables/copilot/disable-copilot-organization.md
+++ b/data/reusables/copilot/disable-copilot-organization.md
@@ -1,6 +1,6 @@
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & licensing** and then **Licensing** (new platform). Alternatively, in the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access** (original platform).
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & licensing** and then **Licensing** (new platform). Alternatively, in the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access** (original platform).
>[!IMPORTANT] If you have not configured all policies for {% data variables.product.prodname_copilot_short %}, you will not be able to complete the following steps. If that is the case, click **Go to policies** and ensure all policies are configured before proceeding.
diff --git a/data/reusables/copilot/enabling-or-disabling-in-vsc.md b/data/reusables/copilot/enabling-or-disabling-in-vsc.md
index 3319075efcce..7bc0e08ea764 100644
--- a/data/reusables/copilot/enabling-or-disabling-in-vsc.md
+++ b/data/reusables/copilot/enabling-or-disabling-in-vsc.md
@@ -2,7 +2,7 @@
You can enable or disable {% data variables.product.prodname_copilot %} from within {% data variables.product.prodname_vscode %}.
-1. To configure code completions, click the arrow next to the **{% octicon "copilot" aria-hidden="true" %}** icon in the title bar of {% data variables.product.prodname_vscode %}, then select **Configure code completions**.
+1. To configure code completions, click the arrow next to the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** icon in the title bar of {% data variables.product.prodname_vscode %}, then select **Configure code completions**.
diff --git a/data/reusables/copilot/go-to-copilot-page.md b/data/reusables/copilot/go-to-copilot-page.md
index 1bc4b9df8bc9..e1e365a69489 100644
--- a/data/reusables/copilot/go-to-copilot-page.md
+++ b/data/reusables/copilot/go-to-copilot-page.md
@@ -1,4 +1,4 @@
-1. In the top right of any page on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon next to the search bar.
+1. In the top right of any page on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon next to the search bar.
The {% data variables.product.prodname_copilot_chat %} panel is displayed. To resize the panel, click and drag the top or left edge.
diff --git a/data/reusables/copilot/open-chat-panel.md b/data/reusables/copilot/open-chat-panel.md
index c154cc67be9a..e9b6f1e2fcd3 100644
--- a/data/reusables/copilot/open-chat-panel.md
+++ b/data/reusables/copilot/open-chat-panel.md
@@ -1 +1 @@
-1. At the top right of the page, click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon next to the search bar.
+1. At the top right of the page, click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon next to the search bar.
diff --git a/data/reusables/copilot/open-copilot.md b/data/reusables/copilot/open-copilot.md
index d7f935fe6416..410bd55260b7 100644
--- a/data/reusables/copilot/open-copilot.md
+++ b/data/reusables/copilot/open-copilot.md
@@ -1,5 +1,5 @@
-1. In the top right of any page on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon next to the search bar.
+1. In the top right of any page on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon next to the search bar.
The {% data variables.product.prodname_copilot_chat %} panel is displayed. To resize the panel, click and drag the top or left edge.
-1. If the panel contains a previous conversation you had with {% data variables.product.prodname_copilot_short %}, click the {% octicon "plus" aria-hidden="true" %} plus sign icon at the top right of the {% data variables.product.prodname_copilot_short %} panel to start a new conversation.
+1. If the panel contains a previous conversation you had with {% data variables.product.prodname_copilot_short %}, click the {% octicon "plus" aria-hidden="true" aria-label="plus" %} plus sign icon at the top right of the {% data variables.product.prodname_copilot_short %} panel to start a new conversation.
diff --git a/data/reusables/copilot/policy-settings.md b/data/reusables/copilot/policy-settings.md
index d9c2f3f7cf02..b7aa6c65ffa9 100644
--- a/data/reusables/copilot/policy-settings.md
+++ b/data/reusables/copilot/policy-settings.md
@@ -1 +1 @@
-1. In the sidebar, under "Code, planning, and automation", click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Policies**.
+1. In the sidebar, under "Code, planning, and automation", click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}**, and then click **Policies**.
diff --git a/data/reusables/copilot/quickstart-signup.md b/data/reusables/copilot/quickstart-signup.md
index 2cd1c1f7ccc2..2327b11eaa71 100644
--- a/data/reusables/copilot/quickstart-signup.md
+++ b/data/reusables/copilot/quickstart-signup.md
@@ -2,7 +2,7 @@
## Sign up for {% data variables.product.prodname_copilot %}
-Get started for free {% octicon "link-external" height:16 %}
+Get started for free {% octicon "link-external" height:16 aria-label="link-external" %}
To use {% data variables.product.prodname_copilot_short %}, you’ll need a personal {% data variables.product.github %} account with access to a {% data variables.product.prodname_copilot_short %} plan. You can:
diff --git a/data/reusables/copilot/signup-procedure-org.md b/data/reusables/copilot/signup-procedure-org.md
index 6e6c0d304a2c..48ed0af0f84e 100644
--- a/data/reusables/copilot/signup-procedure-org.md
+++ b/data/reusables/copilot/signup-procedure-org.md
@@ -1,4 +1,4 @@
1. Navigate to the [{% data variables.product.prodname_copilot %} sign up page](https://github.com/github-copilot/purchase).
-1. Ensure you are signed in to the right organization account. If you are not, click **{% octicon "arrow-switch" aria-hidden="true" %} Switch** and select the organization for which you want to purchase {% data variables.product.prodname_copilot %}.
+1. Ensure you are signed in to the right organization account. If you are not, click **{% octicon "arrow-switch" aria-hidden="true" aria-label="arrow-switch" %} Switch** and select the organization for which you want to purchase {% data variables.product.prodname_copilot %}.
1. Click **Enable {% data variables.product.prodname_copilot %}**.
1. Enable {% data variables.product.prodname_copilot_short %} for some or all members of your organization. For more information about assigning seats, see [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization).
diff --git a/data/reusables/dependabot/sidebar-secret.md b/data/reusables/dependabot/sidebar-secret.md
index 9a8439990623..2838b80e000e 100644
--- a/data/reusables/dependabot/sidebar-secret.md
+++ b/data/reusables/dependabot/sidebar-secret.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, then click **{% data variables.product.prodname_dependabot %}**.
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-hidden="true" aria-label="key-asterisk" %} Secrets and variables**, then click **{% data variables.product.prodname_dependabot %}**.
diff --git a/data/reusables/desktop/click-base-branch-in-drop-down.md b/data/reusables/desktop/click-base-branch-in-drop-down.md
index 65512e5f302c..8598f3b90fc1 100644
--- a/data/reusables/desktop/click-base-branch-in-drop-down.md
+++ b/data/reusables/desktop/click-base-branch-in-drop-down.md
@@ -1,3 +1,3 @@
-1. At the top of the app, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch** and then in the list of branches, click the branch that you want to base your new branch on.
+1. At the top of the app, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch** and then in the list of branches, click the branch that you want to base your new branch on.
diff --git a/data/reusables/desktop/current-branch-menu.md b/data/reusables/desktop/current-branch-menu.md
index d347145c8e84..05b369d2198d 100644
--- a/data/reusables/desktop/current-branch-menu.md
+++ b/data/reusables/desktop/current-branch-menu.md
@@ -1,3 +1,3 @@
-1. In {% data variables.product.prodname_desktop %}, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch**.
+1. In {% data variables.product.prodname_desktop %}, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch**.
diff --git a/data/reusables/desktop/navigate-to-stashed-changes.md b/data/reusables/desktop/navigate-to-stashed-changes.md
index 752f8435da82..4ebde2eb8900 100644
--- a/data/reusables/desktop/navigate-to-stashed-changes.md
+++ b/data/reusables/desktop/navigate-to-stashed-changes.md
@@ -1,3 +1,3 @@
-1. If you are not already on the branch where the changes are stashed, in the repository bar, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch**, then click the branch with stashed changes.
+1. If you are not already on the branch where the changes are stashed, in the repository bar, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch**, then click the branch with stashed changes.
diff --git a/data/reusables/desktop/select-branch-to-delete.md b/data/reusables/desktop/select-branch-to-delete.md
index c3f662c1c7dd..2146d9fbcc08 100644
--- a/data/reusables/desktop/select-branch-to-delete.md
+++ b/data/reusables/desktop/select-branch-to-delete.md
@@ -1,2 +1,2 @@
-1. In the repository bar, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch**, then click the branch that you want to delete.
+1. In the repository bar, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Current Branch**, then click the branch that you want to delete.
diff --git a/data/reusables/discussions/discussions-tab.md b/data/reusables/discussions/discussions-tab.md
index 8e3bcf9a1643..c5881ace4630 100644
--- a/data/reusables/discussions/discussions-tab.md
+++ b/data/reusables/discussions/discussions-tab.md
@@ -1,3 +1,3 @@
-1. Under your repository or organization name, click **{% octicon "comment-discussion" aria-hidden="true" %} Discussions**.
+1. Under your repository or organization name, click **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Discussions**.
diff --git a/data/reusables/discussions/starting-a-poll.md b/data/reusables/discussions/starting-a-poll.md
index 41eaf73319dc..c9071835cb86 100644
--- a/data/reusables/discussions/starting-a-poll.md
+++ b/data/reusables/discussions/starting-a-poll.md
@@ -11,7 +11,7 @@
1. Under "Poll question", type a question for your poll.
1. Under "Poll options", type at least two options for your poll.
-1. Optionally, to add an extra poll option, click **{% octicon "plus" aria-hidden="true" %} Add an option**.
+1. Optionally, to add an extra poll option, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add an option**.
diff --git a/data/reusables/dotcom_billing/update_payment_method_organization_account.md b/data/reusables/dotcom_billing/update_payment_method_organization_account.md
index 8fc0efc8edb3..31570c2da18f 100644
--- a/data/reusables/dotcom_billing/update_payment_method_organization_account.md
+++ b/data/reusables/dotcom_billing/update_payment_method_organization_account.md
@@ -1,3 +1,3 @@
-1. At the top of the page, click **Payment information** {% octicon "arrow-right" aria-hidden="true" %}.
+1. At the top of the page, click **Payment information** {% octicon "arrow-right" aria-hidden="true" aria-label="arrow-right" %}.
diff --git a/data/reusables/enterprise-accounts/actions-tab.md b/data/reusables/enterprise-accounts/actions-tab.md
index 0985def0f8d9..270ff60b1f9b 100644
--- a/data/reusables/enterprise-accounts/actions-tab.md
+++ b/data/reusables/enterprise-accounts/actions-tab.md
@@ -1 +1 @@
-1. Under "{% octicon "law" aria-hidden="true" %} Policies", click **Actions**.
+1. Under "{% octicon "law" aria-hidden="true" aria-label="law" %} Policies", click **Actions**.
diff --git a/data/reusables/enterprise-accounts/administrators-tab.md b/data/reusables/enterprise-accounts/administrators-tab.md
index ad09b040b2dc..ba5dfe7a7623 100644
--- a/data/reusables/enterprise-accounts/administrators-tab.md
+++ b/data/reusables/enterprise-accounts/administrators-tab.md
@@ -1 +1 @@
-1. Under "{% octicon "person" aria-hidden="true" %} People", click **Administrators**.
+1. Under "{% octicon "person" aria-hidden="true" aria-label="person" %} People", click **Administrators**.
diff --git a/data/reusables/enterprise-accounts/advanced-security-tab.md b/data/reusables/enterprise-accounts/advanced-security-tab.md
index 798b2e4ea60c..b33806df6902 100644
--- a/data/reusables/enterprise-accounts/advanced-security-tab.md
+++ b/data/reusables/enterprise-accounts/advanced-security-tab.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" %} {% data variables.product.UI_advanced_security_ent %}**.
+1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} {% data variables.product.UI_advanced_security_ent %}**.
diff --git a/data/reusables/enterprise-accounts/audit-log-tab.md b/data/reusables/enterprise-accounts/audit-log-tab.md
index 39ee90c969af..eda8d1c5ac40 100644
--- a/data/reusables/enterprise-accounts/audit-log-tab.md
+++ b/data/reusables/enterprise-accounts/audit-log-tab.md
@@ -1 +1 @@
-1. Under "Settings", click **{% octicon "log" aria-hidden="true" %} Audit log**.
+1. Under "Settings", click **{% octicon "log" aria-hidden="true" aria-label="log" %} Audit log**.
diff --git a/data/reusables/enterprise-accounts/billing-tab-both-platforms.md b/data/reusables/enterprise-accounts/billing-tab-both-platforms.md
index 21bdf77e0990..602cb450b50d 100644
--- a/data/reusables/enterprise-accounts/billing-tab-both-platforms.md
+++ b/data/reusables/enterprise-accounts/billing-tab-both-platforms.md
@@ -1 +1 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "credit-card" aria-hidden="true" %} Billing and licensing** (visible if you use the new billing platform). Alternatively, click **{% octicon "gear" aria-hidden="true" %} Settings** and then **Billing**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing** (visible if you use the new billing platform). Alternatively, click **{% octicon "gear" aria-hidden="true" %} Settings** and then **Billing**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and licensing** (visible if you use the new billing platform). Alternatively, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings** and then **Billing**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing** (visible if you use the new billing platform). Alternatively, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings** and then **Billing**.{% endif %}
diff --git a/data/reusables/enterprise-accounts/billing-tab.md b/data/reusables/enterprise-accounts/billing-tab.md
index 530622cbb8a2..5ce8a6a0f63a 100644
--- a/data/reusables/enterprise-accounts/billing-tab.md
+++ b/data/reusables/enterprise-accounts/billing-tab.md
@@ -1 +1 @@
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Billing**.
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Billing**.
diff --git a/data/reusables/enterprise-accounts/click-identity-provider.md b/data/reusables/enterprise-accounts/click-identity-provider.md
index d11d877affb5..86a7ab047b4c 100644
--- a/data/reusables/enterprise-accounts/click-identity-provider.md
+++ b/data/reusables/enterprise-accounts/click-identity-provider.md
@@ -1 +1 @@
-1. To review a list of IdP groups, in the left sidebar, click **{% octicon "key" aria-hidden="true" %} Identity provider**.
+1. To review a list of IdP groups, in the left sidebar, click **{% octicon "key" aria-hidden="true" aria-label="key" %} Identity provider**.
diff --git a/data/reusables/enterprise-accounts/code-security-and-analysis-policies.md b/data/reusables/enterprise-accounts/code-security-and-analysis-policies.md
index b61c2267ab6f..3d4aaac2bca8 100644
--- a/data/reusables/enterprise-accounts/code-security-and-analysis-policies.md
+++ b/data/reusables/enterprise-accounts/code-security-and-analysis-policies.md
@@ -1 +1 @@
-1. Under {% octicon "law" aria-hidden="true" %} "Policies", click **{% data variables.product.UI_advanced_security_ent %}**.
+1. Under {% octicon "law" aria-hidden="true" aria-label="law" %} "Policies", click **{% data variables.product.UI_advanced_security_ent %}**.
diff --git a/data/reusables/enterprise-accounts/copilot-tab.md b/data/reusables/enterprise-accounts/copilot-tab.md
index 1e5409ba4a58..b60c0167152c 100644
--- a/data/reusables/enterprise-accounts/copilot-tab.md
+++ b/data/reusables/enterprise-accounts/copilot-tab.md
@@ -1 +1 @@
-1. In the "{% octicon "law" aria-hidden="true" %} Policies" section, click **{% data variables.product.prodname_copilot_short %}**.
+1. In the "{% octicon "law" aria-hidden="true" aria-label="law" %} Policies" section, click **{% data variables.product.prodname_copilot_short %}**.
diff --git a/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md b/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md
index 4fc67d570c23..89e256c4daf4 100644
--- a/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md
+++ b/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md
@@ -1 +1 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "checklist" aria-hidden="true" %} Compliance**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "checklist" aria-hidden="true" %} Compliance**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "checklist" aria-hidden="true" aria-label="checklist" %} Compliance**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "checklist" aria-hidden="true" aria-label="checklist" %} Compliance**.{% endif %}
diff --git a/data/reusables/enterprise-accounts/github-connect-tab.md b/data/reusables/enterprise-accounts/github-connect-tab.md
index e0fce67f30a6..e04ba89a0ec6 100644
--- a/data/reusables/enterprise-accounts/github-connect-tab.md
+++ b/data/reusables/enterprise-accounts/github-connect-tab.md
@@ -1 +1 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "plug" aria-hidden="true" %} {% data variables.product.prodname_github_connect %}**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "plug" aria-hidden="true" %} {% data variables.product.prodname_github_connect %}**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "plug" aria-hidden="true" aria-label="plug" %} {% data variables.product.prodname_github_connect %}**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "plug" aria-hidden="true" aria-label="plug" %} {% data variables.product.prodname_github_connect %}**.{% endif %}
diff --git a/data/reusables/enterprise-accounts/hooks-tab.md b/data/reusables/enterprise-accounts/hooks-tab.md
index 4887327ba93a..0b345e35f8bf 100644
--- a/data/reusables/enterprise-accounts/hooks-tab.md
+++ b/data/reusables/enterprise-accounts/hooks-tab.md
@@ -1 +1 @@
-1. Under "{% octicon "gear" aria-hidden="true" %} Settings", click **Hooks**.
+1. Under "{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings", click **Hooks**.
diff --git a/data/reusables/enterprise-accounts/license-tab.md b/data/reusables/enterprise-accounts/license-tab.md
index 4bf0f5a07727..30e55cfd7242 100644
--- a/data/reusables/enterprise-accounts/license-tab.md
+++ b/data/reusables/enterprise-accounts/license-tab.md
@@ -1,3 +1,3 @@
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **{% ifversion ghec %}Licensing{% elsif ghes %}License{% endif %}**. {% ifversion enhanced-billing-platform %}
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **{% ifversion ghec %}Licensing{% elsif ghes %}License{% endif %}**. {% ifversion enhanced-billing-platform %}
>[!NOTE] If you are on the new billing platform, the licensing page has been relocated. See [AUTOTITLE](/billing/using-the-enhanced-billing-platform-for-enterprises/gathering-insights-on-your-spending#viewing-license-usage).{% endif %}
diff --git a/data/reusables/enterprise-accounts/licensing-tab-both-platforms.md b/data/reusables/enterprise-accounts/licensing-tab-both-platforms.md
index 2a013e326a57..9653b0298b54 100644
--- a/data/reusables/enterprise-accounts/licensing-tab-both-platforms.md
+++ b/data/reusables/enterprise-accounts/licensing-tab-both-platforms.md
@@ -1,2 +1,2 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "credit-card" aria-hidden="true" %} Billing and licensing** (visible if you use the new billing platform). Alternatively, click **{% octicon "gear" aria-hidden="true" %} Settings**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing** (visible if you use the new billing platform). Alternatively, click **{% octicon "gear" aria-hidden="true" %} Settings**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and licensing** (visible if you use the new billing platform). Alternatively, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing** (visible if you use the new billing platform). Alternatively, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.{% endif %}
1. Click **Licensing** to show detailed information on license use.
diff --git a/data/reusables/enterprise-accounts/messages-tab.md b/data/reusables/enterprise-accounts/messages-tab.md
index f5bec8fd1209..a5ab7ad862cd 100644
--- a/data/reusables/enterprise-accounts/messages-tab.md
+++ b/data/reusables/enterprise-accounts/messages-tab.md
@@ -1 +1 @@
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **{% ifversion ghes %}Messages{% elsif ghec %}Announcement{% endif %}**.
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **{% ifversion ghes %}Messages{% elsif ghec %}Announcement{% endif %}**.
diff --git a/data/reusables/enterprise-accounts/models-policies.md b/data/reusables/enterprise-accounts/models-policies.md
index b92069b60c16..e3e5c1ed3605 100644
--- a/data/reusables/enterprise-accounts/models-policies.md
+++ b/data/reusables/enterprise-accounts/models-policies.md
@@ -1 +1 @@
-1. Under {% octicon "law" aria-hidden="true" %} "Policies", click **{% octicon "ai-model" aria-hidden="true" %} Models**.
+1. Under {% octicon "law" aria-hidden="true" aria-label="law" %} "Policies", click **{% octicon "ai-model" aria-hidden="true" aria-label="ai-model" %} Models**.
diff --git a/data/reusables/enterprise-accounts/options-tab.md b/data/reusables/enterprise-accounts/options-tab.md
index 738c4354af72..523928c3fc38 100644
--- a/data/reusables/enterprise-accounts/options-tab.md
+++ b/data/reusables/enterprise-accounts/options-tab.md
@@ -1 +1 @@
-1. Under {% ifversion ghes %} **{% octicon "law" aria-hidden="true" %} Policies**{% else %}"{% octicon "gear" aria-hidden="true" %} Settings"{% endif %}, click **Options**.
+1. Under {% ifversion ghes %} **{% octicon "law" aria-hidden="true" aria-label="law" %} Policies**{% else %}"{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings"{% endif %}, click **Options**.
diff --git a/data/reusables/enterprise-accounts/people-tab.md b/data/reusables/enterprise-accounts/people-tab.md
index 1a3a9ed4bd75..7cbe5e7f4183 100644
--- a/data/reusables/enterprise-accounts/people-tab.md
+++ b/data/reusables/enterprise-accounts/people-tab.md
@@ -1 +1 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "person" aria-hidden="true" %} People**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "person" aria-hidden="true" %} People**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "person" aria-hidden="true" aria-label="person" %} People**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "person" aria-hidden="true" aria-label="person" %} People**.{% endif %}
diff --git a/data/reusables/enterprise-accounts/policies-tab.md b/data/reusables/enterprise-accounts/policies-tab.md
index 07e8f1701d08..e3de1b87c064 100644
--- a/data/reusables/enterprise-accounts/policies-tab.md
+++ b/data/reusables/enterprise-accounts/policies-tab.md
@@ -1 +1 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "law" aria-hidden="true" %} Policies**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "law" aria-hidden="true" %} Policies**.{% endif %}
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "law" aria-hidden="true" aria-label="law" %} Policies**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "law" aria-hidden="true" aria-label="law" %} Policies**.{% endif %}
diff --git a/data/reusables/enterprise-accounts/projects-tab.md b/data/reusables/enterprise-accounts/projects-tab.md
index ec14ae993120..7ef36d3ae6bc 100644
--- a/data/reusables/enterprise-accounts/projects-tab.md
+++ b/data/reusables/enterprise-accounts/projects-tab.md
@@ -1 +1 @@
-1. Under "{% octicon "law" aria-hidden="true" %} Policies", click **Projects**.
+1. Under "{% octicon "law" aria-hidden="true" aria-label="law" %} Policies", click **Projects**.
diff --git a/data/reusables/enterprise-accounts/repositories-tab.md b/data/reusables/enterprise-accounts/repositories-tab.md
index f4db4ec2973f..12aeb8aac97b 100644
--- a/data/reusables/enterprise-accounts/repositories-tab.md
+++ b/data/reusables/enterprise-accounts/repositories-tab.md
@@ -1 +1 @@
-1. Under "{% octicon "law" aria-hidden="true" %} Policies", click {% ifversion ghes < 3.16 %}**Repositories**{% else %}**Member privileges**{% endif %}.
+1. Under "{% octicon "law" aria-hidden="true" aria-label="law" %} Policies", click {% ifversion ghes < 3.16 %}**Repositories**{% else %}**Member privileges**{% endif %}.
diff --git a/data/reusables/enterprise-accounts/security-tab.md b/data/reusables/enterprise-accounts/security-tab.md
index e684287d88ab..5197e91a50f6 100644
--- a/data/reusables/enterprise-accounts/security-tab.md
+++ b/data/reusables/enterprise-accounts/security-tab.md
@@ -1 +1 @@
-1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Authentication security**.
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Authentication security**.
diff --git a/data/reusables/enterprise-accounts/settings-tab.md b/data/reusables/enterprise-accounts/settings-tab.md
index 3130e0bc6dd1..f971a09d1ca4 100644
--- a/data/reusables/enterprise-accounts/settings-tab.md
+++ b/data/reusables/enterprise-accounts/settings-tab.md
@@ -1 +1 @@
-1. {% ifversion horizontal-nav %}At the top of the page, click {% octicon "gear" aria-hidden="true" %} **Settings**{% else %}On the left side of the page, in the enterprise account sidebar, click {% octicon "gear" aria-hidden="true" %} **Settings**{% endif %}.
+1. {% ifversion horizontal-nav %}At the top of the page, click {% octicon "gear" aria-hidden="true" aria-label="gear" %} **Settings**{% else %}On the left side of the page, in the enterprise account sidebar, click {% octicon "gear" aria-hidden="true" aria-label="gear" %} **Settings**{% endif %}.
diff --git a/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md b/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md
index 4511339006a2..1a0fdc624e24 100644
--- a/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md
+++ b/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md
@@ -1,3 +1,3 @@
-Optionally, to view the current configuration for all organizations in the enterprise account before you change the setting, click **{% octicon "eye" aria-hidden="true" %} View your organizations' current configurations**.
+Optionally, to view the current configuration for all organizations in the enterprise account before you change the setting, click **{% octicon "eye" aria-hidden="true" aria-label="eye" %} View your organizations' current configurations**.
diff --git a/data/reusables/enterprise-migration-tool/import-export-tab.md b/data/reusables/enterprise-migration-tool/import-export-tab.md
index e9d77f8cd607..56cb35a11d70 100644
--- a/data/reusables/enterprise-migration-tool/import-export-tab.md
+++ b/data/reusables/enterprise-migration-tool/import-export-tab.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "arrow-switch" aria-hidden="true" %} Import/Export**.
+1. In the "Access" section of the sidebar, click **{% octicon "arrow-switch" aria-hidden="true" aria-label="arrow-switch" %} Import/Export**.
diff --git a/data/reusables/enterprise_site_admin_settings/admin-top-tab.md b/data/reusables/enterprise_site_admin_settings/admin-top-tab.md
index 547aba0cd5ca..3c85418ad2d8 100644
--- a/data/reusables/enterprise_site_admin_settings/admin-top-tab.md
+++ b/data/reusables/enterprise_site_admin_settings/admin-top-tab.md
@@ -1,2 +1,2 @@
-1. In the upper-right corner of the page, click **{% octicon "gear" aria-hidden="true" %} Admin**.
+1. In the upper-right corner of the page, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Admin**.
diff --git a/data/reusables/enterprise_site_admin_settings/management-console.md b/data/reusables/enterprise_site_admin_settings/management-console.md
index 1162c4067be7..38d259132ad0 100644
--- a/data/reusables/enterprise_site_admin_settings/management-console.md
+++ b/data/reusables/enterprise_site_admin_settings/management-console.md
@@ -1 +1 @@
-1. In the "{% octicon "rocket" aria-hidden="true" %} Site admin" sidebar, click **{% data variables.enterprise.management_console %}**.
+1. In the "{% octicon "rocket" aria-hidden="true" aria-label="rocket" %} Site admin" sidebar, click **{% data variables.enterprise.management_console %}**.
diff --git a/data/reusables/enterprise_site_admin_settings/security-tab.md b/data/reusables/enterprise_site_admin_settings/security-tab.md
index 747464430eef..0e965e2c3d4d 100644
--- a/data/reusables/enterprise_site_admin_settings/security-tab.md
+++ b/data/reusables/enterprise_site_admin_settings/security-tab.md
@@ -1,2 +1,2 @@
-1. In the upper-right corner of the page, click **{% octicon "shield" aria-hidden="true" %} Security**.
+1. In the upper-right corner of the page, click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security**.
diff --git a/data/reusables/files/add-file.md b/data/reusables/files/add-file.md
index d0e4ca7d5fc7..3114f1b91ebc 100644
--- a/data/reusables/files/add-file.md
+++ b/data/reusables/files/add-file.md
@@ -1,4 +1,4 @@
-1. Above the list of files, select the **Add file** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %} dropdown menu, then click **{% octicon "plus" aria-hidden="true" %} Create new file**.
+1. Above the list of files, select the **Add file** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %} dropdown menu, then click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Create new file**.
Alternatively, you can click {% octicon "plus" aria-label="The plus sign icon" %} in the file tree view on the left.
diff --git a/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md b/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md
index 8df6cbea7438..e2954ce19643 100644
--- a/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md
+++ b/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md
@@ -1 +1 @@
-1. Click **{% octicon "plus" aria-hidden="true" %} Add**.
+1. Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add**.
diff --git a/data/reusables/issues/access-issue-types-settings.md b/data/reusables/issues/access-issue-types-settings.md
index 433269e963bc..01ffc487b727 100644
--- a/data/reusables/issues/access-issue-types-settings.md
+++ b/data/reusables/issues/access-issue-types-settings.md
@@ -1,3 +1,3 @@
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "table" aria-hidden="true" %} Planning**, then click **Issue types**.
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "table" aria-hidden="true" aria-label="table" %} Planning**, then click **Issue types**.
diff --git a/data/reusables/marketplace/cancel-app-billing-settings.md b/data/reusables/marketplace/cancel-app-billing-settings.md
index 4025c8ed355c..dbec1fbfc246 100644
--- a/data/reusables/marketplace/cancel-app-billing-settings.md
+++ b/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -1 +1 @@
-1. Under "{% data variables.product.prodname_marketplace %}," next to the app you want to cancel, select the **Edit** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Cancel plan**.
+1. Under "{% data variables.product.prodname_marketplace %}," next to the app you want to cancel, select the **Edit** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Cancel plan**.
diff --git a/data/reusables/marketplace/downgrade-app-billing-settings.md b/data/reusables/marketplace/downgrade-app-billing-settings.md
index 201a62ff13bc..d5acb9c9d84a 100644
--- a/data/reusables/marketplace/downgrade-app-billing-settings.md
+++ b/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Under "{% data variables.product.prodname_marketplace %}," next to the app you'd like to downgrade, select the **Edit** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Change plan** or **Cancel plan**.
+1. Under "{% data variables.product.prodname_marketplace %}," next to the app you'd like to downgrade, select the **Edit** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Change plan** or **Cancel plan**.
diff --git a/data/reusables/marketplace/marketplace-app-page.md b/data/reusables/marketplace/marketplace-app-page.md
index 7baf26b8b6f3..0e18c0d547f0 100644
--- a/data/reusables/marketplace/marketplace-app-page.md
+++ b/data/reusables/marketplace/marketplace-app-page.md
@@ -1 +1 @@
->[!IMPORTANT] If you created a personal account (either on a {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} plan) after February 13, 2025, these settings are available on the "Marketplace apps" page, which is located under "{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing" in the "Access" section of the sidebar.
+>[!IMPORTANT] If you created a personal account (either on a {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} plan) after February 13, 2025, these settings are available on the "Marketplace apps" page, which is located under "{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing" in the "Access" section of the sidebar.
diff --git a/data/reusables/marketplace/upgrade-app-billing-settings.md b/data/reusables/marketplace/upgrade-app-billing-settings.md
index 53ba21548dad..02baaa2383fd 100644
--- a/data/reusables/marketplace/upgrade-app-billing-settings.md
+++ b/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Under "{% data variables.product.prodname_marketplace %}," next to the app you want to upgrade, select the **Edit** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Change plan**.
+1. Under "{% data variables.product.prodname_marketplace %}," next to the app you want to upgrade, select the **Edit** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Change plan**.
diff --git a/data/reusables/marketplace/visit-marketplace.md b/data/reusables/marketplace/visit-marketplace.md
index 347175597a04..3c3d2c700c3b 100644
--- a/data/reusables/marketplace/visit-marketplace.md
+++ b/data/reusables/marketplace/visit-marketplace.md
@@ -1,3 +1,3 @@
-1. To open {% data variables.product.prodname_marketplace %}, in the top-left corner of {% data variables.product.prodname_dotcom %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "gift" aria-hidden="true" %} Marketplace**.
+1. To open {% data variables.product.prodname_marketplace %}, in the top-left corner of {% data variables.product.prodname_dotcom %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "gift" aria-hidden="true" aria-label="gift" %} Marketplace**.
diff --git a/data/reusables/models/steps-to-open-model-playground.md b/data/reusables/models/steps-to-open-model-playground.md
index 1fe45a6265b8..cda401b53d3a 100644
--- a/data/reusables/models/steps-to-open-model-playground.md
+++ b/data/reusables/models/steps-to-open-model-playground.md
@@ -2,4 +2,4 @@
1. Click **Model: Select a Model** at the top left of the page.
1. Choose a model from the dropdown menu.
- Alternatively, in the dropdown menu, click **View all models**, click a model in the Marketplace, then click **{% octicon "command-palette" aria-hidden="true" %} Playground**.
+ Alternatively, in the dropdown menu, click **View all models**, click a model in the Marketplace, then click **{% octicon "command-palette" aria-hidden="true" aria-label="command-palette" %} Playground**.
diff --git a/data/reusables/organizations/access-custom-properties.md b/data/reusables/organizations/access-custom-properties.md
index bbdb496b4635..e67040a41e59 100644
--- a/data/reusables/organizations/access-custom-properties.md
+++ b/data/reusables/organizations/access-custom-properties.md
@@ -1,3 +1,3 @@
-1. In the left sidebar, in the "Code, planning, and automation" section, click **{% octicon "repo" aria-hidden="true" %} Repository**, then click **Custom properties**.
+1. In the left sidebar, in the "Code, planning, and automation" section, click **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Repository**, then click **Custom properties**.
diff --git a/data/reusables/organizations/access-ruleset-settings.md b/data/reusables/organizations/access-ruleset-settings.md
index 9e6321141677..e1da69893ac2 100644
--- a/data/reusables/organizations/access-ruleset-settings.md
+++ b/data/reusables/organizations/access-ruleset-settings.md
@@ -1,3 +1,3 @@
-1. In the left sidebar, in the "Code, planning, and automation" section, click **{% octicon "repo" aria-hidden="true" %} Repository**, then click **Rulesets**.
+1. In the left sidebar, in the "Code, planning, and automation" section, click **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Repository**, then click **Rulesets**.
diff --git a/data/reusables/organizations/billing-settings.md b/data/reusables/organizations/billing-settings.md
index f93bf34bba6b..da0cab98851d 100644
--- a/data/reusables/organizations/billing-settings.md
+++ b/data/reusables/organizations/billing-settings.md
@@ -1,4 +1,4 @@
{% data reusables.user-settings.access_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organizations**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Organizations**.
{% data reusables.profile.org_settings %}
-1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
diff --git a/data/reusables/organizations/billing_plans.md b/data/reusables/organizations/billing_plans.md
index f5680093a033..2e8fc1795a4b 100644
--- a/data/reusables/organizations/billing_plans.md
+++ b/data/reusables/organizations/billing_plans.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**.
diff --git a/data/reusables/organizations/billing_plans_or_licensing.md b/data/reusables/organizations/billing_plans_or_licensing.md
index d5bf6c671d18..1ac9a4df74fd 100644
--- a/data/reusables/organizations/billing_plans_or_licensing.md
+++ b/data/reusables/organizations/billing_plans_or_licensing.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & licensing** and then **Licensing** (new platform). Alternatively, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans** (original platform).
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & licensing** and then **Licensing** (new platform). Alternatively, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans** (original platform).
diff --git a/data/reusables/organizations/block_users.md b/data/reusables/organizations/block_users.md
index 63b5020a6e62..9bd1ea11c8bc 100644
--- a/data/reusables/organizations/block_users.md
+++ b/data/reusables/organizations/block_users.md
@@ -1 +1 @@
-1. In the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation**, then click **Blocked users**.
+1. In the sidebar, select **{% octicon "report" aria-hidden="true" aria-label="report" %} Moderation**, then click **Blocked users**.
diff --git a/data/reusables/organizations/click-codespaces.md b/data/reusables/organizations/click-codespaces.md
index 6254d36b5c3c..ec6f2800006e 100644
--- a/data/reusables/organizations/click-codespaces.md
+++ b/data/reusables/organizations/click-codespaces.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "codespaces" aria-hidden="true" %} Codespaces**.
+1. In the left sidebar, click **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} Codespaces**.
diff --git a/data/reusables/organizations/click-general.md b/data/reusables/organizations/click-general.md
index 8632f334208e..003c08402c37 100644
--- a/data/reusables/organizations/click-general.md
+++ b/data/reusables/organizations/click-general.md
@@ -1 +1 @@
-1. Under **{% octicon "codespaces" aria-hidden="true" %} Codespaces**, in the left sidebar, click **General**.
+1. Under **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} Codespaces**, in the left sidebar, click **General**.
diff --git a/data/reusables/organizations/compliance.md b/data/reusables/organizations/compliance.md
index dff64e523e22..6802045c7aae 100644
--- a/data/reusables/organizations/compliance.md
+++ b/data/reusables/organizations/compliance.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, click **{% octicon "checklist" aria-hidden="true" %} Compliance**.
+1. In the "Security" section of the sidebar, click **{% octicon "checklist" aria-hidden="true" aria-label="checklist" %} Compliance**.
diff --git a/data/reusables/organizations/custom-org-roles-assign-role-step.md b/data/reusables/organizations/custom-org-roles-assign-role-step.md
index 9726236c8bb4..c258249e001d 100644
--- a/data/reusables/organizations/custom-org-roles-assign-role-step.md
+++ b/data/reusables/organizations/custom-org-roles-assign-role-step.md
@@ -1,4 +1,4 @@
-1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organization roles**, then click **Role assignments**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Organization roles**, then click **Role assignments**.
1. Click **New role assignment**.
1. Search for users or teams that you want to assign a role to, then select the role you want to give to these users and teams.
1. Click **Add new assignment**.
diff --git a/data/reusables/organizations/custom-org-roles-remove-assignment-step.md b/data/reusables/organizations/custom-org-roles-remove-assignment-step.md
index c494eefa368d..1957720bb1c9 100644
--- a/data/reusables/organizations/custom-org-roles-remove-assignment-step.md
+++ b/data/reusables/organizations/custom-org-roles-remove-assignment-step.md
@@ -1,4 +1,4 @@
-1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organization roles**, then click **Role assignments**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Organization roles**, then click **Role assignments**.
{% data reusables.organizations.custom-org-roles-filter %}
1. To delete a role, to the right of the role, click **NUMBER roles**. Then click **Remove**.
1. In the pop-up window, click **Remove**.
diff --git a/data/reusables/organizations/custom-org-roles-settings-step.md b/data/reusables/organizations/custom-org-roles-settings-step.md
index c6d1d49f2600..f55e801afea4 100644
--- a/data/reusables/organizations/custom-org-roles-settings-step.md
+++ b/data/reusables/organizations/custom-org-roles-settings-step.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organization roles**, then click {% ifversion org-pre-defined-roles %}**Role management**{% else %}**Custom roles**{% endif %}.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Organization roles**, then click {% ifversion org-pre-defined-roles %}**Role management**{% else %}**Custom roles**{% endif %}.
diff --git a/data/reusables/organizations/custom-org-roles-view-assignments-step.md b/data/reusables/organizations/custom-org-roles-view-assignments-step.md
index 9e895a3e6cc0..38215d4edb5d 100644
--- a/data/reusables/organizations/custom-org-roles-view-assignments-step.md
+++ b/data/reusables/organizations/custom-org-roles-view-assignments-step.md
@@ -1,3 +1,3 @@
-1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organization roles**, then click **Role assignments**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Organization roles**, then click **Role assignments**.
{% data reusables.organizations.custom-org-roles-filter %}
1. To view role assignments, to the right of the user or team, click **NUMBER roles**.
diff --git a/data/reusables/organizations/github-apps-settings-sidebar.md b/data/reusables/organizations/github-apps-settings-sidebar.md
index cf65ad706a07..f747a0996f05 100644
--- a/data/reusables/organizations/github-apps-settings-sidebar.md
+++ b/data/reusables/organizations/github-apps-settings-sidebar.md
@@ -1 +1 @@
-1. In the left sidebar, select **{% octicon "code" aria-hidden="true" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
+1. In the left sidebar, select **{% octicon "code" aria-hidden="true" aria-label="code" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
diff --git a/data/reusables/organizations/insights.md b/data/reusables/organizations/insights.md
index dcfff974944f..7933d6dfb03f 100644
--- a/data/reusables/organizations/insights.md
+++ b/data/reusables/organizations/insights.md
@@ -1,3 +1,3 @@
-1. Under your organization name, click **{% octicon "graph" aria-hidden="true" %} Insights**.
+1. Under your organization name, click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} Insights**.
diff --git a/data/reusables/organizations/member-privileges.md b/data/reusables/organizations/member-privileges.md
index 378dda0af2d8..beac58dcb902 100644
--- a/data/reusables/organizations/member-privileges.md
+++ b/data/reusables/organizations/member-privileges.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" %} Member privileges**.
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" aria-label="people" %} Member privileges**.
diff --git a/data/reusables/organizations/mixed-roles-warning.md b/data/reusables/organizations/mixed-roles-warning.md
index f2af1e91a199..d26e42be4844 100644
--- a/data/reusables/organizations/mixed-roles-warning.md
+++ b/data/reusables/organizations/mixed-roles-warning.md
@@ -1 +1 @@
-If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-hidden="true" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**.
+If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-hidden="true" aria-label="alert" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**.
diff --git a/data/reusables/organizations/models.md b/data/reusables/organizations/models.md
index 58010e58a092..d5aaef5186c8 100644
--- a/data/reusables/organizations/models.md
+++ b/data/reusables/organizations/models.md
@@ -1 +1 @@
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "ai-model" aria-hidden="true" %} Models**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "ai-model" aria-hidden="true" aria-label="ai-model" %} Models**.
diff --git a/data/reusables/organizations/navigate-to-sponsoring.md b/data/reusables/organizations/navigate-to-sponsoring.md
index 949cac13252a..2f7a578fa6bc 100644
--- a/data/reusables/organizations/navigate-to-sponsoring.md
+++ b/data/reusables/organizations/navigate-to-sponsoring.md
@@ -1,3 +1,3 @@
-1. Under your organization name, click **{% octicon "heart" aria-hidden="true" %} Sponsoring**.
+1. Under your organization name, click **{% octicon "heart" aria-hidden="true" aria-label="heart" %} Sponsoring**.
diff --git a/data/reusables/organizations/oauth_app_access.md b/data/reusables/organizations/oauth_app_access.md
index bff4b3ed96dd..9a91d7fdd9d4 100644
--- a/data/reusables/organizations/oauth_app_access.md
+++ b/data/reusables/organizations/oauth_app_access.md
@@ -1 +1 @@
-1. In the "Third-party Access" section of the sidebar, click **{% octicon "person" aria-hidden="true" %} OAuth app policy**.
+1. In the "Third-party Access" section of the sidebar, click **{% octicon "person" aria-hidden="true" aria-label="person" %} OAuth app policy**.
diff --git a/data/reusables/organizations/org-settings-repository-roles.md b/data/reusables/organizations/org-settings-repository-roles.md
index f34b3574e1bb..c883142905cb 100644
--- a/data/reusables/organizations/org-settings-repository-roles.md
+++ b/data/reusables/organizations/org-settings-repository-roles.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-hidden="true" %} Repository roles**.
+1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-hidden="true" aria-label="id-badge" %} Repository roles**.
diff --git a/data/reusables/organizations/org_settings.md b/data/reusables/organizations/org_settings.md
index bbd617acd4b4..0860da491072 100644
--- a/data/reusables/organizations/org_settings.md
+++ b/data/reusables/organizations/org_settings.md
@@ -1,3 +1,3 @@
-1. Under your organization name, click **{% octicon "gear" aria-hidden="true" %} Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-label="More" %}** dropdown menu, then click **Settings**.
+1. Under your organization name, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-label="More" %}** dropdown menu, then click **Settings**.
diff --git a/data/reusables/organizations/organization-rulesets-targeting-repositories-step.md b/data/reusables/organizations/organization-rulesets-targeting-repositories-step.md
index 4b6413966690..083a3558f311 100644
--- a/data/reusables/organizations/organization-rulesets-targeting-repositories-step.md
+++ b/data/reusables/organizations/organization-rulesets-targeting-repositories-step.md
@@ -6,12 +6,12 @@ If a repository is targeted by a ruleset created at the organization level, only
#### Targeting all repositories in your organization
-To target all repositories in your organization, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" %} Target: REPOSITORIES**, then click **All repositories**.
+To target all repositories in your organization, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" aria-label="goal" %} Target: REPOSITORIES**, then click **All repositories**.
#### Targeting repositories by naming convention in your organization
-1. To target a dynamic list of repositories in your organization by naming convention, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" %} Target: REPOSITORIES**, then click **Dynamic list of repositories**.
-1. To begin defining a targeting pattern, in the "Targeting criteria" section, select **Add a target** {% octicon "triangle-down" aria-hidden="true" %}, then click **Include by pattern** or **Exclude by pattern**.
+1. To target a dynamic list of repositories in your organization by naming convention, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" aria-label="goal" %} Target: REPOSITORIES**, then click **Dynamic list of repositories**.
+1. To begin defining a targeting pattern, in the "Targeting criteria" section, select **Add a target** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click **Include by pattern** or **Exclude by pattern**.
1. In the modal dialog that appears, enter a repository naming pattern using `fnmatch` syntax, then click **Add Inclusion pattern** or **Add Exclusion pattern**. For more information on `fnmatch` syntax, see [Using `fnmatch` syntax](#using-fnmatch-syntax).
> [!NOTE]
@@ -23,12 +23,12 @@ To target all repositories in your organization, in the "Target repositories" se
You can target repositories in your organization by custom properties. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization).
-1. To target a dynamic list of repositories in your organization by properties, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" %} Target: REPOSITORIES**, then click **Dynamic list by property**.
-1. To add a target, in the "Targeting criteria" section, select **Add a target** {% octicon "triangle-down" aria-hidden="true" %}, then click **Include by property** or **Exclude by property**.
+1. To target a dynamic list of repositories in your organization by properties, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" aria-label="goal" %} Target: REPOSITORIES**, then click **Dynamic list by property**.
+1. To add a target, in the "Targeting criteria" section, select **Add a target** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click **Include by property** or **Exclude by property**.
1. In the modal dialog that appears, select a custom or system property from the dropdown menu, then select a value for the property.
1. Click **Add target**.
#### Targeting select repositories in your organization
-1. To target a static, manually selected list of repositories in your organization, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" %} Target: REPOSITORIES**, then click **Select repositories**.
-1. To select repositories to target, in the "Targeting criteria" section, select **{% octicon "repo" aria-hidden="true" %} Select repositories**, then search for the name of each repository you would like to target. Select each repository from the search results.
+1. To target a static, manually selected list of repositories in your organization, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" aria-label="goal" %} Target: REPOSITORIES**, then click **Select repositories**.
+1. To select repositories to target, in the "Targeting criteria" section, select **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Select repositories**, then search for the name of each repository you would like to target. Select each repository from the search results.
diff --git a/data/reusables/organizations/organization-wide-project.md b/data/reusables/organizations/organization-wide-project.md
index fcf0e74b12ca..b1801fe58af0 100644
--- a/data/reusables/organizations/organization-wide-project.md
+++ b/data/reusables/organizations/organization-wide-project.md
@@ -1,3 +1,3 @@
-1. Under your organization name, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. Under your organization name, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
diff --git a/data/reusables/organizations/people.md b/data/reusables/organizations/people.md
index c38aeab8e8fb..d5fcf49c1dfb 100644
--- a/data/reusables/organizations/people.md
+++ b/data/reusables/organizations/people.md
@@ -1,3 +1,3 @@
-1. Under your organization name, click **{% octicon "person" aria-hidden="true" %} People**.
+1. Under your organization name, click **{% octicon "person" aria-hidden="true" aria-label="person" %} People**.
diff --git a/data/reusables/organizations/repository-defaults.md b/data/reusables/organizations/repository-defaults.md
index 653eed94f2b4..4b8d22ee774a 100644
--- a/data/reusables/organizations/repository-defaults.md
+++ b/data/reusables/organizations/repository-defaults.md
@@ -1 +1 @@
-1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-hidden="true" %} Repository**, then click **Repository defaults**.
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Repository**, then click **Repository defaults**.
diff --git a/data/reusables/organizations/security-and-analysis.md b/data/reusables/organizations/security-and-analysis.md
index 64e48bcb6ca6..4be8a126a23e 100644
--- a/data/reusables/organizations/security-and-analysis.md
+++ b/data/reusables/organizations/security-and-analysis.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" %} Code security and analysis**.
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} Code security and analysis**.
diff --git a/data/reusables/organizations/security-overview.md b/data/reusables/organizations/security-overview.md
index f5c3dff5da15..c5114d77e64d 100644
--- a/data/reusables/organizations/security-overview.md
+++ b/data/reusables/organizations/security-overview.md
@@ -1,3 +1,3 @@
-1. Under your organization name, click **{% octicon "shield" aria-hidden="true" %} Security**.
+1. Under your organization name, click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security**.
diff --git a/data/reusables/organizations/security.md b/data/reusables/organizations/security.md
index e4c9b5acf565..f58223784495 100644
--- a/data/reusables/organizations/security.md
+++ b/data/reusables/organizations/security.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" %} Authentication security**.
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" aria-label="shield-lock" %} Authentication security**.
diff --git a/data/reusables/organizations/sidebar-moderators.md b/data/reusables/organizations/sidebar-moderators.md
index 79006e7a3d55..e7921b33f131 100644
--- a/data/reusables/organizations/sidebar-moderators.md
+++ b/data/reusables/organizations/sidebar-moderators.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation** then click **Moderators**.
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" aria-label="report" %} Moderation** then click **Moderators**.
diff --git a/data/reusables/organizations/team_members_tab.md b/data/reusables/organizations/team_members_tab.md
index d9f9c21cd38c..c145edf20aab 100644
--- a/data/reusables/organizations/team_members_tab.md
+++ b/data/reusables/organizations/team_members_tab.md
@@ -1,3 +1,3 @@
-1. At the top of the team page, click **{% octicon "organization" aria-hidden="true" %} Members**.
+1. At the top of the team page, click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Members**.
diff --git a/data/reusables/organizations/team_settings.md b/data/reusables/organizations/team_settings.md
index 811f55883216..2f0ffab59969 100644
--- a/data/reusables/organizations/team_settings.md
+++ b/data/reusables/organizations/team_settings.md
@@ -1,3 +1,3 @@
-1. At the top of the team page, click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. At the top of the team page, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
diff --git a/data/reusables/organizations/teams.md b/data/reusables/organizations/teams.md
index e92a73bc04fb..ecdaf8d0ec2d 100644
--- a/data/reusables/organizations/teams.md
+++ b/data/reusables/organizations/teams.md
@@ -1,3 +1,3 @@
-1. Under your organization name, click **{% octicon "people" aria-hidden="true" %} Teams**.
+1. Under your organization name, click **{% octicon "people" aria-hidden="true" aria-label="people" %} Teams**.
diff --git a/data/reusables/organizations/teams_sidebar.md b/data/reusables/organizations/teams_sidebar.md
index c965b1932790..f46c335f47c0 100644
--- a/data/reusables/organizations/teams_sidebar.md
+++ b/data/reusables/organizations/teams_sidebar.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-hidden="true" %} Team discussions**.
+1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Team discussions**.
diff --git a/data/reusables/organizations/verified-domains.md b/data/reusables/organizations/verified-domains.md
index 4371a8c2d3e1..f9e8dd44d1e7 100644
--- a/data/reusables/organizations/verified-domains.md
+++ b/data/reusables/organizations/verified-domains.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-hidden="true" %} Verified and approved domains**.
+1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-hidden="true" aria-label="verified" %} Verified and approved domains**.
diff --git a/data/reusables/package_registry/package-settings-delete-versions.md b/data/reusables/package_registry/package-settings-delete-versions.md
index 566f45152b8e..5da2507a5b52 100644
--- a/data/reusables/package_registry/package-settings-delete-versions.md
+++ b/data/reusables/package_registry/package-settings-delete-versions.md
@@ -1,5 +1,5 @@
1. In the list of packages, find the version of the package that you want to delete.
- * _If your package is a container_, to the right of the package version click {% octicon "kebab-horizontal" aria-hidden="true" %}, then select **Delete version** from the dropdown menu.
+ * _If your package is a container_, to the right of the package version click {% octicon "kebab-horizontal" aria-hidden="true" aria-label="kebab-horizontal" %}, then select **Delete version** from the dropdown menu.
* _For types of packages other than containers_, to the right of the package version click **Delete**.
diff --git a/data/reusables/package_registry/package-settings-from-org-level.md b/data/reusables/package_registry/package-settings-from-org-level.md
index 93630fe1c1fe..f05aa130d6b5 100644
--- a/data/reusables/package_registry/package-settings-from-org-level.md
+++ b/data/reusables/package_registry/package-settings-from-org-level.md
@@ -1,4 +1,4 @@
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization.
-1. Under your organization name, click the **{% octicon "package" aria-hidden="true" %} Packages** tab.
+1. Under your organization name, click the **{% octicon "package" aria-hidden="true" aria-label="package" %} Packages** tab.
diff --git a/data/reusables/package_registry/package-settings-from-user-level.md b/data/reusables/package_registry/package-settings-from-user-level.md
index c43e02808e0d..77dd5d7638b8 100644
--- a/data/reusables/package_registry/package-settings-from-user-level.md
+++ b/data/reusables/package_registry/package-settings-from-user-level.md
@@ -3,4 +3,4 @@
-1. On your profile page, in the header, click the **{% octicon "package" aria-hidden="true" %} Packages** tab.
+1. On your profile page, in the header, click the **{% octicon "package" aria-hidden="true" aria-label="package" %} Packages** tab.
diff --git a/data/reusables/package_registry/package-settings-manage-versions-menu.md b/data/reusables/package_registry/package-settings-manage-versions-menu.md
index af42ff3020d2..e1ea03d37d79 100644
--- a/data/reusables/package_registry/package-settings-manage-versions-menu.md
+++ b/data/reusables/package_registry/package-settings-manage-versions-menu.md
@@ -6,7 +6,7 @@
* _If your package is a container_, under the "Recent Versions" section, click **View and manage all versions**.
* _For types of packages other than containers_:
- 1. On the right-hand side, click **{% octicon "gear" aria-hidden="true" %} Package settings**.
+ 1. On the right-hand side, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Package settings**.
1. On the left click **Manage versions**.
diff --git a/data/reusables/package_registry/package-settings-option.md b/data/reusables/package_registry/package-settings-option.md
index abe8e28814f3..2ce816d764f1 100644
--- a/data/reusables/package_registry/package-settings-option.md
+++ b/data/reusables/package_registry/package-settings-option.md
@@ -1,4 +1,4 @@
1. Search for and then click the name of the package that you want to manage.
-1. On your package's landing page, on the right-hand side, click **{% octicon "gear" aria-hidden="true" %} Package settings**.
+1. On your package's landing page, on the right-hand side, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Package settings**.
diff --git a/data/reusables/pages/sidebar-pages.md b/data/reusables/pages/sidebar-pages.md
index e185edb68b62..60e5efae95fc 100644
--- a/data/reusables/pages/sidebar-pages.md
+++ b/data/reusables/pages/sidebar-pages.md
@@ -1 +1 @@
-1. In the "Code and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" %} Pages**.
+1. In the "Code and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" aria-label="browser" %} Pages**.
diff --git a/data/reusables/pages/visit-site.md b/data/reusables/pages/visit-site.md
index ad7d4517c2f8..b24d06a037ee 100644
--- a/data/reusables/pages/visit-site.md
+++ b/data/reusables/pages/visit-site.md
@@ -1,4 +1,4 @@
-1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" %} Visit site**.
+1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" aria-label="link-external" %} Visit site**.
{% data reusables.pages.twenty-minutes-to-publish %}
diff --git a/data/reusables/profile/access_org.md b/data/reusables/profile/access_org.md
index 5fe636173383..6923b552b030 100644
--- a/data/reusables/profile/access_org.md
+++ b/data/reusables/profile/access_org.md
@@ -1 +1 @@
-1. In the upper-right corner of {% data variables.product.prodname_dotcom %}, select your profile photo, then click **{% octicon "organization" aria-hidden="true" %} Your organizations**.
+1. In the upper-right corner of {% data variables.product.prodname_dotcom %}, select your profile photo, then click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Your organizations**.
diff --git a/data/reusables/project-management/click-menu.md b/data/reusables/project-management/click-menu.md
index 6dc89ee78398..475dae7148b3 100644
--- a/data/reusables/project-management/click-menu.md
+++ b/data/reusables/project-management/click-menu.md
@@ -1 +1 @@
-1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click **{% octicon "three-bars" aria-hidden="true" %} Menu**.
+1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click **{% octicon "three-bars" aria-hidden="true" aria-label="three-bars" %} Menu**.
diff --git a/data/reusables/project-management/link-repos-to-project-board.md b/data/reusables/project-management/link-repos-to-project-board.md
index a677ca4e6e87..6edf10ad9c91 100644
--- a/data/reusables/project-management/link-repos-to-project-board.md
+++ b/data/reusables/project-management/link-repos-to-project-board.md
@@ -1 +1 @@
-You can link up to twenty-five repositories to your organization or user-owned {% data variables.projects.projects_v1_board %}. Linking repositories makes it easier to add issues and pull requests from those repositories to your {% data variables.projects.projects_v1_board %} using **{% octicon "plus" aria-hidden="true" %} Add cards** or from the issue or pull requests sidebar.
+You can link up to twenty-five repositories to your organization or user-owned {% data variables.projects.projects_v1_board %}. Linking repositories makes it easier to add issues and pull requests from those repositories to your {% data variables.projects.projects_v1_board %} using **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add cards** or from the issue or pull requests sidebar.
diff --git a/data/reusables/projects/access-workflows.md b/data/reusables/projects/access-workflows.md
index 6669fbb6933c..515fe55c5007 100644
--- a/data/reusables/projects/access-workflows.md
+++ b/data/reusables/projects/access-workflows.md
@@ -3,4 +3,4 @@
-1. In the menu, click **{% octicon "workflow" aria-hidden="true" %} Workflows**.
+1. In the menu, click **{% octicon "workflow" aria-hidden="true" aria-label="workflow" %} Workflows**.
diff --git a/data/reusables/projects/create-project.md b/data/reusables/projects/create-project.md
index 447680995bb4..9b94492e5aca 100644
--- a/data/reusables/projects/create-project.md
+++ b/data/reusables/projects/create-project.md
@@ -1,6 +1,6 @@
{% data reusables.profile.access_org %}
{% data reusables.user-settings.access_org %}
-1. Under your organization name, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. Under your organization name, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
1. Click **New project**.
diff --git a/data/reusables/projects/create-user-project.md b/data/reusables/projects/create-user-project.md
index 4fc6132282c9..133402c3e7e5 100644
--- a/data/reusables/projects/create-user-project.md
+++ b/data/reusables/projects/create-user-project.md
@@ -1,5 +1,5 @@
{% data reusables.profile.access_profile %}
-1. On your profile, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. On your profile, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
diff --git a/data/reusables/projects/customize/group-fields.md b/data/reusables/projects/customize/group-fields.md
index b7d7b6713b1f..137d452c8da5 100644
--- a/data/reusables/projects/customize/group-fields.md
+++ b/data/reusables/projects/customize/group-fields.md
@@ -2,6 +2,6 @@
> You cannot group by title, labels, reviewers, or linked pull requests.
{% data reusables.projects.open-view-menu %}
-1. Click **{% octicon "rows" aria-hidden="true" %} Group by**.
+1. Click **{% octicon "rows" aria-hidden="true" aria-label="rows" %} Group by**.
1. Click the field you want to group by.
-1. Optionally, to disable grouping, click **{% octicon "x" aria-hidden="true" %} No grouping** at the bottom of the list.
+1. Optionally, to disable grouping, click **{% octicon "x" aria-hidden="true" aria-label="x" %} No grouping** at the bottom of the list.
diff --git a/data/reusables/projects/customize/show-hide-field.md b/data/reusables/projects/customize/show-hide-field.md
index b5fdc2ef2dc5..61c7efbf6d29 100644
--- a/data/reusables/projects/customize/show-hide-field.md
+++ b/data/reusables/projects/customize/show-hide-field.md
@@ -1,3 +1,3 @@
{% data reusables.projects.open-view-menu %}
-1. Under "Configuration", click **{% octicon "note" aria-hidden="true" %} Fields**.
+1. Under "Configuration", click **{% octicon "note" aria-hidden="true" aria-label="note" %} Fields**.
1. Select or deselect the fields you want to show or hide.
diff --git a/data/reusables/projects/customize/slice-panel.md b/data/reusables/projects/customize/slice-panel.md
index 8605f741c6f9..76e3b2b8f682 100644
--- a/data/reusables/projects/customize/slice-panel.md
+++ b/data/reusables/projects/customize/slice-panel.md
@@ -6,6 +6,6 @@ You can slice your items by a field to view a list of the field values in a sepa
{% data reusables.projects.open-view-menu %}
1. Click **Slice by**.
1. Click the field you want to slice by.
-1. Optionally, to disable slicing, click **{% octicon "x" aria-hidden="true" %} No slicing** at the bottom of the list.
+1. Optionally, to disable slicing, click **{% octicon "x" aria-hidden="true" aria-label="x" %} No slicing** at the bottom of the list.
With the slice panel open, you can change the current field by using the menu at the top of the slice panel.
diff --git a/data/reusables/projects/customize/sort.md b/data/reusables/projects/customize/sort.md
index cf95db92ec2c..415662f24520 100644
--- a/data/reusables/projects/customize/sort.md
+++ b/data/reusables/projects/customize/sort.md
@@ -6,4 +6,4 @@
{% ifversion projects-v2-sorting-update %}{% else %}{% endif %}
-1. Optionally, to remove a sort,{% ifversion projects-v2-sorting-update %} click one of the sorted fields, or{% endif %} {% octicon "x" aria-hidden="true" %} click **No sorting** at the bottom of the list.
+1. Optionally, to remove a sort,{% ifversion projects-v2-sorting-update %} click one of the sorted fields, or{% endif %} {% octicon "x" aria-hidden="true" aria-label="x" %} click **No sorting** at the bottom of the list.
diff --git a/data/reusables/projects/customize/sum.md b/data/reusables/projects/customize/sum.md
index 3abb3ff22798..805fe92e032e 100644
--- a/data/reusables/projects/customize/sum.md
+++ b/data/reusables/projects/customize/sum.md
@@ -3,5 +3,5 @@ You can configure a view to show the sum of one of more number fields, including
In a board layout, field sums are displayed at the top of each column. In table and roadmap layouts, when you enable grouping by a field, field sums are included in each group's header.
{% data reusables.projects.open-view-menu %}
-1. Click **{% octicon "number" aria-hidden="true" %} Field sum**.
+1. Click **{% octicon "number" aria-hidden="true" aria-label="number" %} Field sum**.
1. Select the fields you want to include.
diff --git a/data/reusables/projects/open-item-menu.md b/data/reusables/projects/open-item-menu.md
index 4c16b8edea43..869f9ae48d8f 100644
--- a/data/reusables/projects/open-item-menu.md
+++ b/data/reusables/projects/open-item-menu.md
@@ -1 +1 @@
-1. Click {% octicon "triangle-down" aria-label="Row actions" %} (in table or roadmap layout) or {% octicon "kebab-horizontal" aria-hidden="true" %} (in board layout).
+1. Click {% octicon "triangle-down" aria-label="Row actions" %} (in table or roadmap layout) or {% octicon "kebab-horizontal" aria-hidden="true" aria-label="kebab-horizontal" %} (in board layout).
diff --git a/data/reusables/projects/project-settings.md b/data/reusables/projects/project-settings.md
index 02594682a88d..9961c6ce75c9 100644
--- a/data/reusables/projects/project-settings.md
+++ b/data/reusables/projects/project-settings.md
@@ -3,4 +3,4 @@
-1. In the menu, click **{% octicon "gear" aria-hidden="true" %} Settings** to access the project settings.
+1. In the menu, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings** to access the project settings.
diff --git a/data/reusables/projects/projects-tab.md b/data/reusables/projects/projects-tab.md
index df490e18c4f1..abdc197288b0 100644
--- a/data/reusables/projects/projects-tab.md
+++ b/data/reusables/projects/projects-tab.md
@@ -1,3 +1,3 @@
-1. At the top of the screen, click **{% octicon "table" aria-hidden="true" %} Projects**.
+1. At the top of the screen, click **{% octicon "table" aria-hidden="true" aria-label="table" %} Projects**.
diff --git a/data/reusables/projects/reopen-a-project.md b/data/reusables/projects/reopen-a-project.md
index 8723999329a9..34141d1f6fc1 100644
--- a/data/reusables/projects/reopen-a-project.md
+++ b/data/reusables/projects/reopen-a-project.md
@@ -4,5 +4,5 @@
-1. In the menu, click **{% octicon "gear" aria-hidden="true" %} Settings** to access the project settings.
+1. In the menu, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings** to access the project settings.
1. In the "Danger Zone" section, click **Re-open this project**.
diff --git a/data/reusables/projects/templates-tab.md b/data/reusables/projects/templates-tab.md
index 8ef5fe54b985..3623bc239145 100644
--- a/data/reusables/projects/templates-tab.md
+++ b/data/reusables/projects/templates-tab.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "project-template" aria-hidden="true" %} Templates**.
+1. In the left sidebar, click **{% octicon "project-template" aria-hidden="true" aria-label="project-template" %} Templates**.
diff --git a/data/reusables/reminders/scheduled-reminders.md b/data/reusables/reminders/scheduled-reminders.md
index cf950f1aa0a7..3a6e41f3a8bf 100644
--- a/data/reusables/reminders/scheduled-reminders.md
+++ b/data/reusables/reminders/scheduled-reminders.md
@@ -1 +1 @@
-1. In the "Integrations" section of the sidebar, click **{% octicon "clock" aria-hidden="true" %} Scheduled reminders**.
+1. In the "Integrations" section of the sidebar, click **{% octicon "clock" aria-hidden="true" aria-label="clock" %} Scheduled reminders**.
diff --git a/data/reusables/repositories/accessing-repository-graphs.md b/data/reusables/repositories/accessing-repository-graphs.md
index ac48b2c5ec52..b519da7c3025 100644
--- a/data/reusables/repositories/accessing-repository-graphs.md
+++ b/data/reusables/repositories/accessing-repository-graphs.md
@@ -1,3 +1,3 @@
-1. Under your repository name, click **{% octicon "graph" aria-hidden="true" %} Insights**.
+1. Under your repository name, click **{% octicon "graph" aria-hidden="true" aria-label="graph" %} Insights**.
diff --git a/data/reusables/repositories/actions-cache-list.md b/data/reusables/repositories/actions-cache-list.md
index e44a948459e7..a8fe460fb05d 100644
--- a/data/reusables/repositories/actions-cache-list.md
+++ b/data/reusables/repositories/actions-cache-list.md
@@ -1 +1 @@
-1. In the left sidebar, under the "Management" section, click **{% octicon "cache" aria-hidden="true" %} Caches**.
+1. In the left sidebar, under the "Management" section, click **{% octicon "cache" aria-hidden="true" aria-label="cache" %} Caches**.
diff --git a/data/reusables/repositories/actions-tab.md b/data/reusables/repositories/actions-tab.md
index 2fa6b2c25d2c..fd86b19c38d2 100644
--- a/data/reusables/repositories/actions-tab.md
+++ b/data/reusables/repositories/actions-tab.md
@@ -1,3 +1,3 @@
-1. Under your repository name, click **{% octicon "play" aria-hidden="true" %} Actions**.
+1. Under your repository name, click **{% octicon "play" aria-hidden="true" aria-label="play" %} Actions**.
diff --git a/data/reusables/repositories/changed-files.md b/data/reusables/repositories/changed-files.md
index 1286274aec4f..cab1e44626e3 100644
--- a/data/reusables/repositories/changed-files.md
+++ b/data/reusables/repositories/changed-files.md
@@ -1,3 +1,3 @@
-1. On the pull request, click **{% octicon "file-diff" aria-hidden="true" %} Files changed**.
+1. On the pull request, click **{% octicon "file-diff" aria-hidden="true" aria-label="file-diff" %} Files changed**.
diff --git a/data/reusables/repositories/click-code-dropdown.md b/data/reusables/repositories/click-code-dropdown.md
index 08a1ba863f26..32d89145b156 100644
--- a/data/reusables/repositories/click-code-dropdown.md
+++ b/data/reusables/repositories/click-code-dropdown.md
@@ -1,3 +1,3 @@
-1. Above the list of files, click **{% octicon "code" aria-hidden="true" %} Code**.
+1. Above the list of files, click **{% octicon "code" aria-hidden="true" aria-label="code" %} Code**.
diff --git a/data/reusables/repositories/click-collaborators-teams.md b/data/reusables/repositories/click-collaborators-teams.md
index 59e2ed7def1a..d4903eb51974 100644
--- a/data/reusables/repositories/click-collaborators-teams.md
+++ b/data/reusables/repositories/click-collaborators-teams.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" %} Collaborators & teams**.
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" aria-label="people" %} Collaborators & teams**.
diff --git a/data/reusables/repositories/code-scanning-enable.md b/data/reusables/repositories/code-scanning-enable.md
index 9fac5de44ce9..9a305aabac01 100644
--- a/data/reusables/repositories/code-scanning-enable.md
+++ b/data/reusables/repositories/code-scanning-enable.md
@@ -1,4 +1,4 @@
{% ifversion ghas-products %}
1. To the right of "{% data variables.product.prodname_code_security %}", click **Enable**.
-1. Under "{% data variables.product.prodname_code_security %}", to the right of "{% data variables.product.prodname_codeql %} analysis", select **Set up** {% octicon "triangle-down" aria-hidden="true" %}, then click **Default**.{% else %}
-1. In the "{% data variables.product.prodname_code_scanning_caps %}" section, select **Set up** {% octicon "triangle-down" aria-hidden="true" %}, then click **Default**.{% endif %}
+1. Under "{% data variables.product.prodname_code_security %}", to the right of "{% data variables.product.prodname_codeql %} analysis", select **Set up** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click **Default**.{% else %}
+1. In the "{% data variables.product.prodname_code_scanning_caps %}" section, select **Set up** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %}, then click **Default**.{% endif %}
diff --git a/data/reusables/repositories/copy-clone-url.md b/data/reusables/repositories/copy-clone-url.md
index 9426f31aacc3..35ef5b7ac264 100644
--- a/data/reusables/repositories/copy-clone-url.md
+++ b/data/reusables/repositories/copy-clone-url.md
@@ -1,4 +1,4 @@
-1. Above the list of files, click **{% octicon "code" aria-hidden="true" %} Code**.
+1. Above the list of files, click **{% octicon "code" aria-hidden="true" aria-label="code" %} Code**.
diff --git a/data/reusables/repositories/delete-ruleset-steps.md b/data/reusables/repositories/delete-ruleset-steps.md
index 6cbc7da27523..6ab8b4c2c36a 100644
--- a/data/reusables/repositories/delete-ruleset-steps.md
+++ b/data/reusables/repositories/delete-ruleset-steps.md
@@ -1,4 +1,4 @@
1. Click the name of the ruleset you want to delete.
-1. To the right of the ruleset's name, select {% octicon "kebab-horizontal" aria-label="Open additional options" %}, then click **{% octicon "trash" aria-hidden="true" %} Delete ruleset**.
+1. To the right of the ruleset's name, select {% octicon "kebab-horizontal" aria-label="Open additional options" %}, then click **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete ruleset**.
diff --git a/data/reusables/repositories/download-zip.md b/data/reusables/repositories/download-zip.md
index 5ed93906bba7..779569d41525 100644
--- a/data/reusables/repositories/download-zip.md
+++ b/data/reusables/repositories/download-zip.md
@@ -1 +1 @@
-1. Click **{% octicon "file-zip" aria-hidden="true" %} Download ZIP**.
+1. Click **{% octicon "file-zip" aria-hidden="true" aria-label="file-zip" %} Download ZIP**.
diff --git a/data/reusables/repositories/navigate-to-branches.md b/data/reusables/repositories/navigate-to-branches.md
index 642f3c221cb3..33c28dff4c23 100644
--- a/data/reusables/repositories/navigate-to-branches.md
+++ b/data/reusables/repositories/navigate-to-branches.md
@@ -1,3 +1,3 @@
-1. From the file tree view on the left, select the {% octicon "git-branch" aria-hidden="true" %} branch dropdown menu, then click **View all branches**. You can also find the branch dropdown menu at the top of the integrated file editor.
+1. From the file tree view on the left, select the {% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} branch dropdown menu, then click **View all branches**. You can also find the branch dropdown menu at the top of the integrated file editor.
diff --git a/data/reusables/repositories/navigate-to-code-security-and-analysis.md b/data/reusables/repositories/navigate-to-code-security-and-analysis.md
index cf61e30e7391..2f65de1644e1 100644
--- a/data/reusables/repositories/navigate-to-code-security-and-analysis.md
+++ b/data/reusables/repositories/navigate-to-code-security-and-analysis.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" %} {% data variables.product.UI_advanced_security %}**.
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} {% data variables.product.UI_advanced_security %}**.
diff --git a/data/reusables/repositories/navigate-to-commit-page.md b/data/reusables/repositories/navigate-to-commit-page.md
index 9bbd5ed8bc9a..16809a5975ca 100644
--- a/data/reusables/repositories/navigate-to-commit-page.md
+++ b/data/reusables/repositories/navigate-to-commit-page.md
@@ -1,3 +1,3 @@
-1. On the main page of the repository, above the file list, click **{% octicon "history" aria-hidden="true" %} commits**.
+1. On the main page of the repository, above the file list, click **{% octicon "history" aria-hidden="true" aria-label="history" %} commits**.
diff --git a/data/reusables/repositories/navigate-to-insights.md b/data/reusables/repositories/navigate-to-insights.md
index c3d6d4298562..88c98863604d 100644
--- a/data/reusables/repositories/navigate-to-insights.md
+++ b/data/reusables/repositories/navigate-to-insights.md
@@ -1 +1 @@
-1. Under your repository name, click the **{% octicon "graph" aria-hidden="true" %} Insights** tab.
+1. Under your repository name, click the **{% octicon "graph" aria-hidden="true" aria-label="graph" %} Insights** tab.
diff --git a/data/reusables/repositories/navigate-to-models.md b/data/reusables/repositories/navigate-to-models.md
index e900f7165329..fb5f0d93fcfc 100644
--- a/data/reusables/repositories/navigate-to-models.md
+++ b/data/reusables/repositories/navigate-to-models.md
@@ -1 +1 @@
-At the top of the page for your repository, click **{% octicon "ai-model" aria-hidden="true" %} Models**.
+At the top of the page for your repository, click **{% octicon "ai-model" aria-hidden="true" aria-label="ai-model" %} Models**.
diff --git a/data/reusables/repositories/navigate-to-tags.md b/data/reusables/repositories/navigate-to-tags.md
index 3c89c6559504..963eb0ececb1 100644
--- a/data/reusables/repositories/navigate-to-tags.md
+++ b/data/reusables/repositories/navigate-to-tags.md
@@ -1 +1 @@
-1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-hidden="true" %} Tags**.
+1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-hidden="true" aria-label="tag" %} Tags**.
diff --git a/data/reusables/repositories/open-with-github-desktop.md b/data/reusables/repositories/open-with-github-desktop.md
index c1edea8c47e2..73de653e3f1b 100644
--- a/data/reusables/repositories/open-with-github-desktop.md
+++ b/data/reusables/repositories/open-with-github-desktop.md
@@ -1,6 +1,6 @@
-1. Above the list of files, click **{% octicon "code" aria-hidden="true" %} Code**.
+1. Above the list of files, click **{% octicon "code" aria-hidden="true" aria-label="code" %} Code**.
-1. To clone and open the repository with {% data variables.product.prodname_desktop %}, click **{% octicon "desktop-download" aria-hidden="true" %} Open with {% data variables.product.prodname_desktop %}**.
+1. To clone and open the repository with {% data variables.product.prodname_desktop %}, click **{% octicon "desktop-download" aria-hidden="true" aria-label="desktop-download" %} Open with {% data variables.product.prodname_desktop %}**.
diff --git a/data/reusables/repositories/repository-branches.md b/data/reusables/repositories/repository-branches.md
index be7b424fab86..f7e78c8c6c6e 100644
--- a/data/reusables/repositories/repository-branches.md
+++ b/data/reusables/repositories/repository-branches.md
@@ -1 +1 @@
-1. In the "Code and automation" section of the sidebar, click **{% octicon "git-branch" aria-hidden="true" %} Branches**.
+1. In the "Code and automation" section of the sidebar, click **{% octicon "git-branch" aria-hidden="true" aria-label="git-branch" %} Branches**.
diff --git a/data/reusables/repositories/repository-runners.md b/data/reusables/repositories/repository-runners.md
index 88c5dc5a27d0..940ab4e8a5f7 100644
--- a/data/reusables/repositories/repository-runners.md
+++ b/data/reusables/repositories/repository-runners.md
@@ -1 +1 @@
-1. In the left sidebar, under the "Management" section, click **{% octicon "server" aria-hidden="true" %} Runners**.
+1. In the left sidebar, under the "Management" section, click **{% octicon "server" aria-hidden="true" aria-label="server" %} Runners**.
diff --git a/data/reusables/repositories/review-pr-commits.md b/data/reusables/repositories/review-pr-commits.md
index 0c45e66510cc..5307554b1254 100644
--- a/data/reusables/repositories/review-pr-commits.md
+++ b/data/reusables/repositories/review-pr-commits.md
@@ -1,3 +1,3 @@
-1. On the pull request, click **{% octicon "git-commit" aria-hidden="true" %} Commits**.
+1. On the pull request, click **{% octicon "git-commit" aria-hidden="true" aria-label="git-commit" %} Commits**.
diff --git a/data/reusables/repositories/ruleset-history.md b/data/reusables/repositories/ruleset-history.md
index ffcb234fe612..56f1ef504365 100644
--- a/data/reusables/repositories/ruleset-history.md
+++ b/data/reusables/repositories/ruleset-history.md
@@ -1,4 +1,4 @@
-1. To view the history of changes to the ruleset, select {% octicon "kebab-horizontal" aria-label="Open additional options" %} to the right of the ruleset's name, then click **{% octicon "history" aria-hidden="true" %} History**.
+1. To view the history of changes to the ruleset, select {% octicon "kebab-horizontal" aria-label="Open additional options" %} to the right of the ruleset's name, then click **{% octicon "history" aria-hidden="true" aria-label="history" %} History**.
diff --git a/data/reusables/repositories/rulesets-about-enforcement-statuses.md b/data/reusables/repositories/rulesets-about-enforcement-statuses.md
index b8f8f17e558a..bc711a95a704 100644
--- a/data/reusables/repositories/rulesets-about-enforcement-statuses.md
+++ b/data/reusables/repositories/rulesets-about-enforcement-statuses.md
@@ -2,9 +2,9 @@ While creating or editing your ruleset, you can use enforcement statuses to conf
You can select any of the following enforcement statuses for your ruleset.
- * **{% octicon "play" aria-hidden="true" %} Active:** your ruleset will be enforced upon creation.{% ifversion repo-rules-enterprise %}
- * **{% octicon "meter" aria-hidden="true" %} Evaluate:** your ruleset will not be enforced, but you will be able to monitor which actions would or would not violate rules on the "Rule Insights" page.{% endif %}
- * **{% octicon "skip" aria-hidden="true" %} Disabled:** your ruleset will not be enforced{% ifversion repo-rules-enterprise %} or evaluated{% endif %}.
+ * **{% octicon "play" aria-hidden="true" aria-label="play" %} Active:** your ruleset will be enforced upon creation.{% ifversion repo-rules-enterprise %}
+ * **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Evaluate:** your ruleset will not be enforced, but you will be able to monitor which actions would or would not violate rules on the "Rule Insights" page.{% endif %}
+ * **{% octicon "skip" aria-hidden="true" aria-label="skip" %} Disabled:** your ruleset will not be enforced{% ifversion repo-rules-enterprise %} or evaluated{% endif %}.
{% ifversion repo-rules-enterprise %}
diff --git a/data/reusables/repositories/rulesets-bypass-step.md b/data/reusables/repositories/rulesets-bypass-step.md
index 3165e7a7370e..68e59d61270b 100644
--- a/data/reusables/repositories/rulesets-bypass-step.md
+++ b/data/reusables/repositories/rulesets-bypass-step.md
@@ -9,5 +9,5 @@ You can grant certain roles, teams, or apps bypass permissions {% ifversion push
* {% data variables.product.prodname_github_apps %}
* {% data variables.product.prodname_dependabot %}. For more information about {% data variables.product.prodname_dependabot %}, see [AUTOTITLE](/code-security/getting-started/dependabot-quickstart-guide).
-1. To grant bypass permissions for the ruleset, in the "Bypass list" section, click **{% octicon "plus" aria-hidden="true" %} Add bypass**.
+1. To grant bypass permissions for the ruleset, in the "Bypass list" section, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add bypass**.
1. In the "Add bypass" modal dialog that appears, search for the role, team, or app you would like to grant bypass permissions, then select the role, team, or app from the "Suggestions" section and click **Add Selected**.
diff --git a/data/reusables/repositories/rulesets-general-step.md b/data/reusables/repositories/rulesets-general-step.md
index 260ee2742f99..306272d42933 100644
--- a/data/reusables/repositories/rulesets-general-step.md
+++ b/data/reusables/repositories/rulesets-general-step.md
@@ -1,2 +1,2 @@
1. Under "Ruleset name," type a name for the ruleset.
-1. Optionally, to change the default enforcement status, click **{% octicon "skip" aria-hidden="true" %} Disabled** {% octicon "triangle-down" aria-hidden="true" %} and select an enforcement status. For more information about enforcement statuses, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#using-ruleset-enforcement-statuses).
+1. Optionally, to change the default enforcement status, click **{% octicon "skip" aria-hidden="true" aria-label="skip" %} Disabled** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} and select an enforcement status. For more information about enforcement statuses, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#using-ruleset-enforcement-statuses).
diff --git a/data/reusables/repositories/rulesets-require-code-scanning-results.md b/data/reusables/repositories/rulesets-require-code-scanning-results.md
index 041aed307bae..22e2c0be89ed 100644
--- a/data/reusables/repositories/rulesets-require-code-scanning-results.md
+++ b/data/reusables/repositories/rulesets-require-code-scanning-results.md
@@ -1,5 +1,5 @@
1. Under "Branch protections", select **Require {% data variables.product.prodname_code_scanning %} results**.
-1. Under "Required tools and alert thresholds", click **{% octicon "plus" aria-hidden="true" %} Add tool** and select a {% data variables.product.prodname_code_scanning %} tool with the dropdown. For example, "{% data variables.product.prodname_codeql %}".
+1. Under "Required tools and alert thresholds", click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add tool** and select a {% data variables.product.prodname_code_scanning %} tool with the dropdown. For example, "{% data variables.product.prodname_codeql %}".
1. Next to the name of a {% data variables.product.prodname_code_scanning %} tool:
* Click **Alerts** and select one of: **None**, **Errors**, **Errors and Warnings** or **All**.
* Click **Security alerts** and select one of: **None**, **Critical**, **High or higher**, **Medium or higher**, or **All**.
diff --git a/data/reusables/repositories/sidebar-advisories.md b/data/reusables/repositories/sidebar-advisories.md
index 0d3a9c55f6ad..66a2905bb735 100644
--- a/data/reusables/repositories/sidebar-advisories.md
+++ b/data/reusables/repositories/sidebar-advisories.md
@@ -1 +1 @@
-1. In the left sidebar, under "Reporting", click **{% octicon "shield" aria-hidden="true" %} Advisories**.
+1. In the left sidebar, under "Reporting", click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Advisories**.
diff --git a/data/reusables/repositories/sidebar-code-scanning-alerts.md b/data/reusables/repositories/sidebar-code-scanning-alerts.md
index 248feafc6b30..fbe6e2afbf26 100644
--- a/data/reusables/repositories/sidebar-code-scanning-alerts.md
+++ b/data/reusables/repositories/sidebar-code-scanning-alerts.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" %} {% data variables.product.prodname_code_scanning_caps %}**.
+1. In the left sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} {% data variables.product.prodname_code_scanning_caps %}**.
diff --git a/data/reusables/repositories/sidebar-issue-pr.md b/data/reusables/repositories/sidebar-issue-pr.md
index 9911991ea068..04254fc4c3e0 100644
--- a/data/reusables/repositories/sidebar-issue-pr.md
+++ b/data/reusables/repositories/sidebar-issue-pr.md
@@ -1,3 +1,3 @@
-1. Under your repository name, click **{% octicon "issue-opened" aria-hidden="true" %} Issues** or **{% octicon "git-pull-request" aria-hidden="true" %} Pull requests**.
+1. Under your repository name, click **{% octicon "issue-opened" aria-hidden="true" aria-label="issue-opened" %} Issues** or **{% octicon "git-pull-request" aria-hidden="true" aria-label="git-pull-request" %} Pull requests**.
diff --git a/data/reusables/repositories/sidebar-issues.md b/data/reusables/repositories/sidebar-issues.md
index d542018d9f3e..c6cc936d942f 100644
--- a/data/reusables/repositories/sidebar-issues.md
+++ b/data/reusables/repositories/sidebar-issues.md
@@ -1,3 +1,3 @@
-1. Under your repository name, click **{% octicon "issue-opened" aria-hidden="true" %} Issues**.
+1. Under your repository name, click **{% octicon "issue-opened" aria-hidden="true" aria-label="issue-opened" %} Issues**.
diff --git a/data/reusables/repositories/sidebar-moderation-reported-content.md b/data/reusables/repositories/sidebar-moderation-reported-content.md
index 3873a7ad314e..e337cc1a069b 100644
--- a/data/reusables/repositories/sidebar-moderation-reported-content.md
+++ b/data/reusables/repositories/sidebar-moderation-reported-content.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" %} Moderation options**, then click **Reported content**.
+1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Moderation options**, then click **Reported content**.
diff --git a/data/reusables/repositories/sidebar-notifications.md b/data/reusables/repositories/sidebar-notifications.md
index 289f6a5e2811..9e786d06669e 100644
--- a/data/reusables/repositories/sidebar-notifications.md
+++ b/data/reusables/repositories/sidebar-notifications.md
@@ -1 +1 @@
-1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-hidden="true" %} Email notifications**.
+1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-hidden="true" aria-label="mail" %} Email notifications**.
diff --git a/data/reusables/repositories/sidebar-pr.md b/data/reusables/repositories/sidebar-pr.md
index ec408301e3a1..49b4d724f06f 100644
--- a/data/reusables/repositories/sidebar-pr.md
+++ b/data/reusables/repositories/sidebar-pr.md
@@ -1,3 +1,3 @@
-1. Under your repository name, click **{% octicon "git-pull-request" aria-hidden="true" %} Pull requests**.
+1. Under your repository name, click **{% octicon "git-pull-request" aria-hidden="true" aria-label="git-pull-request" %} Pull requests**.
diff --git a/data/reusables/repositories/sidebar-security.md b/data/reusables/repositories/sidebar-security.md
index d05117689264..fca36539bcdc 100644
--- a/data/reusables/repositories/sidebar-security.md
+++ b/data/reusables/repositories/sidebar-security.md
@@ -1,2 +1,2 @@
-1. Under the repository name, click **{% octicon "shield" aria-hidden="true" %} Security**. If you cannot see the "Security" tab, select the **{% octicon "kebab-horizontal" aria-hidden="true" %}** dropdown menu, and then click **Security**.
+1. Under the repository name, click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Security**. If you cannot see the "Security" tab, select the **{% octicon "kebab-horizontal" aria-hidden="true" aria-label="kebab-horizontal" %}** dropdown menu, and then click **Security**.
diff --git a/data/reusables/repositories/sidebar-settings.md b/data/reusables/repositories/sidebar-settings.md
index 11b7bb98f936..b421a1e1f7ae 100644
--- a/data/reusables/repositories/sidebar-settings.md
+++ b/data/reusables/repositories/sidebar-settings.md
@@ -1,3 +1,3 @@
-1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-label="More" %}** dropdown menu, then click **Settings**.
+1. Under your repository name, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-label="More" %}** dropdown menu, then click **Settings**.
diff --git a/data/reusables/repositories/sidebar-wiki.md b/data/reusables/repositories/sidebar-wiki.md
index 86d7887959ec..ea3bc66aaf7d 100644
--- a/data/reusables/repositories/sidebar-wiki.md
+++ b/data/reusables/repositories/sidebar-wiki.md
@@ -1,3 +1,3 @@
-1. Under your repository name, click **{% octicon "book" aria-hidden="true" %} Wiki**.
+1. Under your repository name, click **{% octicon "book" aria-hidden="true" aria-label="book" %} Wiki**.
diff --git a/data/reusables/security-configurations/apply-configuration-by-default.md b/data/reusables/security-configurations/apply-configuration-by-default.md
index e2a28a3e632d..8a3f1c6c24d7 100644
--- a/data/reusables/security-configurations/apply-configuration-by-default.md
+++ b/data/reusables/security-configurations/apply-configuration-by-default.md
@@ -1,2 +1,2 @@
-1. Optionally, in the confirmation dialog, you can choose to automatically apply the {% data variables.product.prodname_security_configuration %} to newly created repositories depending on their visibility. Select the **None** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Public**, or **Private and internal**, or both.
+1. Optionally, in the confirmation dialog, you can choose to automatically apply the {% data variables.product.prodname_security_configuration %} to newly created repositories depending on their visibility. Select the **None** {% octicon "triangle-down" aria-hidden="true" aria-label="triangle-down" %} dropdown menu, then click **Public**, or **Private and internal**, or both.
diff --git a/data/reusables/security-configurations/display-global-settings.md b/data/reusables/security-configurations/display-global-settings.md
index e7157e4f8452..3f6f2d171be5 100644
--- a/data/reusables/security-configurations/display-global-settings.md
+++ b/data/reusables/security-configurations/display-global-settings.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" %} {% data variables.product.UI_advanced_security %}** then **Global settings**.
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} {% data variables.product.UI_advanced_security %}** then **Global settings**.
diff --git a/data/reusables/security-configurations/view-configurations-page.md b/data/reusables/security-configurations/view-configurations-page.md
index 22f108c0f9f7..f81e47af8c59 100644
--- a/data/reusables/security-configurations/view-configurations-page.md
+++ b/data/reusables/security-configurations/view-configurations-page.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, select the **{% octicon "codescan" aria-hidden="true" %} {% data variables.product.UI_advanced_security %}** dropdown menu, then click **Configurations**.
+1. In the "Security" section of the sidebar, select the **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} {% data variables.product.UI_advanced_security %}** dropdown menu, then click **Configurations**.
diff --git a/data/reusables/security-overview/filter-and-toggle.md b/data/reusables/security-overview/filter-and-toggle.md
index 961ea62da1d9..00a61035aa55 100644
--- a/data/reusables/security-overview/filter-and-toggle.md
+++ b/data/reusables/security-overview/filter-and-toggle.md
@@ -7,5 +7,5 @@
{% endif %}
{% ifversion security-overview-3-tab-dashboard %}{% else %}
-1. For the alert trends graph at the top of the page, you can click **{% octicon "shield" aria-hidden="true" %} Open alerts** or **{% octicon "shield-x" aria-hidden="true" %} Closed alerts** to toggle between showing the trends for open or closed alerts. The toggle will only affect the alert trends graph. For more information, see [Alert trends graph](#alert-trends-graph).
+1. For the alert trends graph at the top of the page, you can click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Open alerts** or **{% octicon "shield-x" aria-hidden="true" aria-label="shield-x" %} Closed alerts** to toggle between showing the trends for open or closed alerts. The toggle will only affect the alert trends graph. For more information, see [Alert trends graph](#alert-trends-graph).
{% endif %}
diff --git a/data/reusables/security-overview/open-security-risk-view.md b/data/reusables/security-overview/open-security-risk-view.md
index 64fb0f67b3c3..6bd34be59579 100644
--- a/data/reusables/security-overview/open-security-risk-view.md
+++ b/data/reusables/security-overview/open-security-risk-view.md
@@ -1 +1 @@
-1. To display the "Security risk" view, in the sidebar, click **{% octicon "shield" aria-hidden="true" %} Risk**.
+1. To display the "Security risk" view, in the sidebar, click **{% octicon "shield" aria-hidden="true" aria-label="shield" %} Risk**.
diff --git a/data/reusables/security-overview/security-overview-coverage-view.md b/data/reusables/security-overview/security-overview-coverage-view.md
index ad020050e4b0..9bee2c6e2123 100644
--- a/data/reusables/security-overview/security-overview-coverage-view.md
+++ b/data/reusables/security-overview/security-overview-coverage-view.md
@@ -1,3 +1,3 @@
-1. In the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage** to display the "Security coverage" view.
+1. In the sidebar, click **{% octicon "meter" aria-hidden="true" aria-label="meter" %} Coverage** to display the "Security coverage" view.
diff --git a/data/reusables/sponsors/sponsorship-dashboard.md b/data/reusables/sponsors/sponsorship-dashboard.md
index fc902cec4c9a..0186554f7842 100644
--- a/data/reusables/sponsors/sponsorship-dashboard.md
+++ b/data/reusables/sponsors/sponsorship-dashboard.md
@@ -2,5 +2,5 @@
* If you're sponsoring a personal account, under the user's name, click **Sponsoring**.
- * If you're sponsoring an organization, to the right of the organization's name, click **{% octicon "heart-fill" aria-hidden="true" %} Sponsoring**.
+ * If you're sponsoring an organization, to the right of the organization's name, click **{% octicon "heart-fill" aria-hidden="true" aria-label="heart-fill" %} Sponsoring**.
1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** dropdown menu, then click the organization.
diff --git a/data/reusables/sponsors/tax-form-link.md b/data/reusables/sponsors/tax-form-link.md
index ef35a85aa917..832d2ec7e970 100644
--- a/data/reusables/sponsors/tax-form-link.md
+++ b/data/reusables/sponsors/tax-form-link.md
@@ -1,4 +1,4 @@
-1. Click **tax forms** {% octicon "link-external" aria-hidden="true" %}.
+1. Click **tax forms** {% octicon "link-external" aria-hidden="true" aria-label="link-external" %}.
diff --git a/data/reusables/user-settings/access_applications.md b/data/reusables/user-settings/access_applications.md
index 08ffbff169fb..a9d4425b7c14 100644
--- a/data/reusables/user-settings/access_applications.md
+++ b/data/reusables/user-settings/access_applications.md
@@ -1 +1 @@
-1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-hidden="true" %} Applications**.
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-hidden="true" aria-label="apps" %} Applications**.
diff --git a/data/reusables/user-settings/access_settings.md b/data/reusables/user-settings/access_settings.md
index 3934efb5a263..b88cbc905943 100644
--- a/data/reusables/user-settings/access_settings.md
+++ b/data/reusables/user-settings/access_settings.md
@@ -1 +1 @@
-1. In the upper-right corner of any page on {% data variables.product.prodname_dotcom %}, click your profile photo, then click **{% octicon "gear" aria-hidden="true" %} Settings**.
+1. In the upper-right corner of any page on {% data variables.product.prodname_dotcom %}, click your profile photo, then click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**.
diff --git a/data/reusables/user-settings/accessibility_settings.md b/data/reusables/user-settings/accessibility_settings.md
index 602884da4e4b..de18ddc11871 100644
--- a/data/reusables/user-settings/accessibility_settings.md
+++ b/data/reusables/user-settings/accessibility_settings.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "accessibility" aria-hidden="true" %} Accessibility**.
+1. In the left sidebar, click **{% octicon "accessibility" aria-hidden="true" aria-label="accessibility" %} Accessibility**.
diff --git a/data/reusables/user-settings/account_settings.md b/data/reusables/user-settings/account_settings.md
index ade24a8eaf09..570158c177ba 100644
--- a/data/reusables/user-settings/account_settings.md
+++ b/data/reusables/user-settings/account_settings.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "gear" aria-hidden="true" %} Account**.
+1. In the left sidebar, click **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Account**.
diff --git a/data/reusables/user-settings/appearance-settings.md b/data/reusables/user-settings/appearance-settings.md
index c2ffb928e118..13c969e91b19 100644
--- a/data/reusables/user-settings/appearance-settings.md
+++ b/data/reusables/user-settings/appearance-settings.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "paintbrush" aria-hidden="true" %} Appearance**.
+1. In the left sidebar, click **{% octicon "paintbrush" aria-hidden="true" aria-label="paintbrush" %} Appearance**.
diff --git a/data/reusables/user-settings/billing-plans-two-platforms.md b/data/reusables/user-settings/billing-plans-two-platforms.md
index af76b88e4ae3..cdc0193948f4 100644
--- a/data/reusables/user-settings/billing-plans-two-platforms.md
+++ b/data/reusables/user-settings/billing-plans-two-platforms.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & licensing** and then **Licensing** (new platform). Alternatively, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**, then click **Plans and usage** (original platform).
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & licensing** and then **Licensing** (new platform). Alternatively, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**, then click **Plans and usage** (original platform).
diff --git a/data/reusables/user-settings/billing_plans.md b/data/reusables/user-settings/billing_plans.md
index 75ab1a3abecf..217c2255d827 100644
--- a/data/reusables/user-settings/billing_plans.md
+++ b/data/reusables/user-settings/billing_plans.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**, then click **Plans and usage**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**, then click **Plans and usage**.
diff --git a/data/reusables/user-settings/billing_plans_payment.md b/data/reusables/user-settings/billing_plans_payment.md
index 2ed8b68088b9..f5d30d61d454 100644
--- a/data/reusables/user-settings/billing_plans_payment.md
+++ b/data/reusables/user-settings/billing_plans_payment.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**, then click **Payment information**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**, then click **Payment information**.
diff --git a/data/reusables/user-settings/billing_plans_spending.md b/data/reusables/user-settings/billing_plans_spending.md
index 0495c24aca64..17bdf243976e 100644
--- a/data/reusables/user-settings/billing_plans_spending.md
+++ b/data/reusables/user-settings/billing_plans_spending.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**, then click **Spending limits**.
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing and plans**, then click **Spending limits**.
diff --git a/data/reusables/user-settings/blocked_users.md b/data/reusables/user-settings/blocked_users.md
index 7d9b674c27d8..7d8d06387359 100644
--- a/data/reusables/user-settings/blocked_users.md
+++ b/data/reusables/user-settings/blocked_users.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation** then click **Blocked users**.
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" aria-label="report" %} Moderation** then click **Blocked users**.
diff --git a/data/reusables/user-settings/codespaces-tab.md b/data/reusables/user-settings/codespaces-tab.md
index dd0058d6698e..9b5c4da22e81 100644
--- a/data/reusables/user-settings/codespaces-tab.md
+++ b/data/reusables/user-settings/codespaces-tab.md
@@ -1 +1 @@
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-hidden="true" %} Codespaces**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-hidden="true" aria-label="codespaces" %} Codespaces**.
diff --git a/data/reusables/user-settings/copilot-settings.md b/data/reusables/user-settings/copilot-settings.md
index 6af5224a5e21..370cee7e57e4 100644
--- a/data/reusables/user-settings/copilot-settings.md
+++ b/data/reusables/user-settings/copilot-settings.md
@@ -1 +1 @@
-1. In the upper-right corner of any page on {% data variables.product.prodname_dotcom %}, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" %} Your Copilot**.
+1. In the upper-right corner of any page on {% data variables.product.prodname_dotcom %}, click your profile photo, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Your Copilot**.
diff --git a/data/reusables/user-settings/developer_settings.md b/data/reusables/user-settings/developer_settings.md
index f0ed9a4dae08..fe39eba9a64d 100644
--- a/data/reusables/user-settings/developer_settings.md
+++ b/data/reusables/user-settings/developer_settings.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "code" aria-hidden="true" %} Developer settings**.
+1. In the left sidebar, click **{% octicon "code" aria-hidden="true" aria-label="code" %} Developer settings**.
diff --git a/data/reusables/user-settings/emails.md b/data/reusables/user-settings/emails.md
index bc665dc4bf2e..79a18760e297 100644
--- a/data/reusables/user-settings/emails.md
+++ b/data/reusables/user-settings/emails.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-hidden="true" %} Emails**.
+1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-hidden="true" aria-label="mail" %} Emails**.
diff --git a/data/reusables/user-settings/organizations.md b/data/reusables/user-settings/organizations.md
index 91e1eb770a42..ccfd18b224e2 100644
--- a/data/reusables/user-settings/organizations.md
+++ b/data/reusables/user-settings/organizations.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organizations**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" aria-label="organization" %} Organizations**.
diff --git a/data/reusables/user-settings/repo-tab.md b/data/reusables/user-settings/repo-tab.md
index 48e149115804..0ad12ef25793 100644
--- a/data/reusables/user-settings/repo-tab.md
+++ b/data/reusables/user-settings/repo-tab.md
@@ -1 +1 @@
-1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-hidden="true" %} Repositories**.
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-hidden="true" aria-label="repo" %} Repositories**.
diff --git a/data/reusables/user-settings/saved_replies.md b/data/reusables/user-settings/saved_replies.md
index bd75d9972b21..38a0b4e2d89a 100644
--- a/data/reusables/user-settings/saved_replies.md
+++ b/data/reusables/user-settings/saved_replies.md
@@ -1 +1 @@
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-hidden="true" %} Saved replies**.
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-hidden="true" aria-label="reply" %} Saved replies**.
diff --git a/data/reusables/user-settings/security-analysis.md b/data/reusables/user-settings/security-analysis.md
index 457daa1c00c5..4c60ecfc6085 100644
--- a/data/reusables/user-settings/security-analysis.md
+++ b/data/reusables/user-settings/security-analysis.md
@@ -1 +1 @@
-1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" %} Code security**.
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-hidden="true" aria-label="codescan" %} Code security**.
diff --git a/data/reusables/user-settings/security.md b/data/reusables/user-settings/security.md
index 25064dbd2952..360a47b55fd1 100644
--- a/data/reusables/user-settings/security.md
+++ b/data/reusables/user-settings/security.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" %} Password and authentication**.
+1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" aria-label="shield-lock" %} Password and authentication**.
diff --git a/data/reusables/user-settings/sessions.md b/data/reusables/user-settings/sessions.md
index 45da7e631406..8390b8928243 100644
--- a/data/reusables/user-settings/sessions.md
+++ b/data/reusables/user-settings/sessions.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "broadcast" aria-hidden="true" %} Sessions**.
+1. In the "Access" section of the sidebar, click **{% octicon "broadcast" aria-hidden="true" aria-label="broadcast" %} Sessions**.
diff --git a/data/reusables/user-settings/ssh.md b/data/reusables/user-settings/ssh.md
index bc3941d34326..ede59460382e 100644
--- a/data/reusables/user-settings/ssh.md
+++ b/data/reusables/user-settings/ssh.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "key" aria-hidden="true" %} SSH and GPG keys**.
+1. In the "Access" section of the sidebar, click **{% octicon "key" aria-hidden="true" aria-label="key" %} SSH and GPG keys**.
diff --git a/data/reusables/webhooks/sidebar_webhooks.md b/data/reusables/webhooks/sidebar_webhooks.md
index 07d9df024cbc..9c6bcc570147 100644
--- a/data/reusables/webhooks/sidebar_webhooks.md
+++ b/data/reusables/webhooks/sidebar_webhooks.md
@@ -1 +1 @@
-1. In the left sidebar, click **{% octicon "webhook" aria-hidden="true" %} Webhooks**.
+1. In the left sidebar, click **{% octicon "webhook" aria-hidden="true" aria-label="webhook" %} Webhooks**.
diff --git a/package-lock.json b/package-lock.json
index d1cd2faef7d3..74072633e74a 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -11,8 +11,8 @@
"@elastic/elasticsearch": "8.13.1",
"@github/failbot": "0.8.3",
"@horizon-rs/language-guesser": "0.1.1",
- "@octokit/plugin-retry": "7.1.4",
- "@octokit/request-error": "6.1.8",
+ "@octokit/plugin-retry": "8.0.1",
+ "@octokit/request-error": "7.0.0",
"@primer/behaviors": "^1.7.2",
"@primer/css": "^21.3.1",
"@primer/live-region-element": "^0.7.2",
@@ -133,7 +133,7 @@
"@typescript-eslint/parser": "^8.7.0",
"chalk": "^5.0.1",
"change-case": "^5.4.4",
- "commander": "^13.0.0",
+ "commander": "^14.0.0",
"cross-env": "^7.0.3",
"csp-parse": "0.0.2",
"csv-parse": "5.5.6",
@@ -2326,60 +2326,109 @@
}
},
"node_modules/@octokit/auth-token": {
- "version": "5.1.1",
- "resolved": "https://registry.npmjs.org/@octokit/auth-token/-/auth-token-5.1.1.tgz",
- "integrity": "sha512-rh3G3wDO8J9wSjfI436JUKzHIxq8NaiL0tVeB2aXmG6p/9859aUOAjA9pmSPNGGZxfwmaJ9ozOJImuNVJdpvbA==",
+ "version": "6.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/auth-token/-/auth-token-6.0.0.tgz",
+ "integrity": "sha512-P4YJBPdPSpWTQ1NU4XYdvHvXJJDxM6YwpS0FZHRgP7YFkdVxsWcpWGy/NVqlAA7PcPCnMacXlRm1y2PFZRWL/w==",
+ "peer": true,
"engines": {
- "node": ">= 18"
+ "node": ">= 20"
}
},
"node_modules/@octokit/core": {
- "version": "6.1.2",
- "resolved": "https://registry.npmjs.org/@octokit/core/-/core-6.1.2.tgz",
- "integrity": "sha512-hEb7Ma4cGJGEUNOAVmyfdB/3WirWMg5hDuNFVejGEDFqupeOysLc2sG6HJxY2etBp5YQu5Wtxwi020jS9xlUwg==",
+ "version": "7.0.2",
+ "resolved": "https://registry.npmjs.org/@octokit/core/-/core-7.0.2.tgz",
+ "integrity": "sha512-ODsoD39Lq6vR6aBgvjTnA3nZGliknKboc9Gtxr7E4WDNqY24MxANKcuDQSF0jzapvGb3KWOEDrKfve4HoWGK+g==",
+ "peer": true,
"dependencies": {
- "@octokit/auth-token": "^5.0.0",
- "@octokit/graphql": "^8.0.0",
- "@octokit/request": "^9.0.0",
- "@octokit/request-error": "^6.0.1",
- "@octokit/types": "^13.0.0",
- "before-after-hook": "^3.0.2",
+ "@octokit/auth-token": "^6.0.0",
+ "@octokit/graphql": "^9.0.1",
+ "@octokit/request": "^10.0.2",
+ "@octokit/request-error": "^7.0.0",
+ "@octokit/types": "^14.0.0",
+ "before-after-hook": "^4.0.0",
"universal-user-agent": "^7.0.0"
},
"engines": {
- "node": ">= 18"
+ "node": ">= 20"
+ }
+ },
+ "node_modules/@octokit/core/node_modules/@octokit/openapi-types": {
+ "version": "25.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-25.0.0.tgz",
+ "integrity": "sha512-FZvktFu7HfOIJf2BScLKIEYjDsw6RKc7rBJCdvCTfKsVnx2GEB/Nbzjr29DUdb7vQhlzS/j8qDzdditP0OC6aw==",
+ "peer": true
+ },
+ "node_modules/@octokit/core/node_modules/@octokit/types": {
+ "version": "14.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/types/-/types-14.0.0.tgz",
+ "integrity": "sha512-VVmZP0lEhbo2O1pdq63gZFiGCKkm8PPp8AUOijlwPO6hojEVjspA0MWKP7E4hbvGxzFKNqKr6p0IYtOH/Wf/zA==",
+ "peer": true,
+ "dependencies": {
+ "@octokit/openapi-types": "^25.0.0"
}
},
"node_modules/@octokit/endpoint": {
- "version": "10.1.3",
- "resolved": "https://registry.npmjs.org/@octokit/endpoint/-/endpoint-10.1.3.tgz",
- "integrity": "sha512-nBRBMpKPhQUxCsQQeW+rCJ/OPSMcj3g0nfHn01zGYZXuNDvvXudF/TYY6APj5THlurerpFN4a/dQAIAaM6BYhA==",
- "license": "MIT",
+ "version": "11.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/endpoint/-/endpoint-11.0.0.tgz",
+ "integrity": "sha512-hoYicJZaqISMAI3JfaDr1qMNi48OctWuOih1m80bkYow/ayPw6Jj52tqWJ6GEoFTk1gBqfanSoI1iY99Z5+ekQ==",
+ "peer": true,
"dependencies": {
- "@octokit/types": "^13.6.2",
+ "@octokit/types": "^14.0.0",
"universal-user-agent": "^7.0.2"
},
"engines": {
- "node": ">= 18"
+ "node": ">= 20"
+ }
+ },
+ "node_modules/@octokit/endpoint/node_modules/@octokit/openapi-types": {
+ "version": "25.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-25.0.0.tgz",
+ "integrity": "sha512-FZvktFu7HfOIJf2BScLKIEYjDsw6RKc7rBJCdvCTfKsVnx2GEB/Nbzjr29DUdb7vQhlzS/j8qDzdditP0OC6aw==",
+ "peer": true
+ },
+ "node_modules/@octokit/endpoint/node_modules/@octokit/types": {
+ "version": "14.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/types/-/types-14.0.0.tgz",
+ "integrity": "sha512-VVmZP0lEhbo2O1pdq63gZFiGCKkm8PPp8AUOijlwPO6hojEVjspA0MWKP7E4hbvGxzFKNqKr6p0IYtOH/Wf/zA==",
+ "peer": true,
+ "dependencies": {
+ "@octokit/openapi-types": "^25.0.0"
}
},
"node_modules/@octokit/graphql": {
- "version": "8.1.1",
- "resolved": "https://registry.npmjs.org/@octokit/graphql/-/graphql-8.1.1.tgz",
- "integrity": "sha512-ukiRmuHTi6ebQx/HFRCXKbDlOh/7xEV6QUXaE7MJEKGNAncGI/STSbOkl12qVXZrfZdpXctx5O9X1AIaebiDBg==",
+ "version": "9.0.1",
+ "resolved": "https://registry.npmjs.org/@octokit/graphql/-/graphql-9.0.1.tgz",
+ "integrity": "sha512-j1nQNU1ZxNFx2ZtKmL4sMrs4egy5h65OMDmSbVyuCzjOcwsHq6EaYjOTGXPQxgfiN8dJ4CriYHk6zF050WEULg==",
+ "peer": true,
"dependencies": {
- "@octokit/request": "^9.0.0",
- "@octokit/types": "^13.0.0",
+ "@octokit/request": "^10.0.2",
+ "@octokit/types": "^14.0.0",
"universal-user-agent": "^7.0.0"
},
"engines": {
- "node": ">= 18"
+ "node": ">= 20"
+ }
+ },
+ "node_modules/@octokit/graphql/node_modules/@octokit/openapi-types": {
+ "version": "25.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-25.0.0.tgz",
+ "integrity": "sha512-FZvktFu7HfOIJf2BScLKIEYjDsw6RKc7rBJCdvCTfKsVnx2GEB/Nbzjr29DUdb7vQhlzS/j8qDzdditP0OC6aw==",
+ "peer": true
+ },
+ "node_modules/@octokit/graphql/node_modules/@octokit/types": {
+ "version": "14.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/types/-/types-14.0.0.tgz",
+ "integrity": "sha512-VVmZP0lEhbo2O1pdq63gZFiGCKkm8PPp8AUOijlwPO6hojEVjspA0MWKP7E4hbvGxzFKNqKr6p0IYtOH/Wf/zA==",
+ "peer": true,
+ "dependencies": {
+ "@octokit/openapi-types": "^25.0.0"
}
},
"node_modules/@octokit/openapi-types": {
"version": "23.0.1",
"resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-23.0.1.tgz",
"integrity": "sha512-izFjMJ1sir0jn0ldEKhZ7xegCTj/ObmEDlEfpFrx4k/JyZSMRHbO3/rBwgE7f3m2DHt+RrNGIVw4wSmwnm3t/g==",
+ "dev": true,
"license": "MIT"
},
"node_modules/@octokit/plugin-paginate-rest": {
@@ -2428,48 +2477,59 @@
}
},
"node_modules/@octokit/plugin-retry": {
- "version": "7.1.4",
- "resolved": "https://registry.npmjs.org/@octokit/plugin-retry/-/plugin-retry-7.1.4.tgz",
- "integrity": "sha512-7AIP4p9TttKN7ctygG4BtR7rrB0anZqoU9ThXFk8nETqIfvgPUANTSYHqWYknK7W3isw59LpZeLI8pcEwiJdRg==",
- "license": "MIT",
+ "version": "8.0.1",
+ "resolved": "https://registry.npmjs.org/@octokit/plugin-retry/-/plugin-retry-8.0.1.tgz",
+ "integrity": "sha512-KUoYR77BjF5O3zcwDQHRRZsUvJwepobeqiSSdCJ8lWt27FZExzb0GgVxrhhfuyF6z2B2zpO0hN5pteni1sqWiw==",
"dependencies": {
- "@octokit/request-error": "^6.1.7",
- "@octokit/types": "^13.6.2",
+ "@octokit/request-error": "^7.0.0",
+ "@octokit/types": "^14.0.0",
"bottleneck": "^2.15.3"
},
"engines": {
- "node": ">= 18"
+ "node": ">= 20"
},
"peerDependencies": {
- "@octokit/core": ">=6"
+ "@octokit/core": ">=7"
+ }
+ },
+ "node_modules/@octokit/plugin-retry/node_modules/@octokit/openapi-types": {
+ "version": "25.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-25.0.0.tgz",
+ "integrity": "sha512-FZvktFu7HfOIJf2BScLKIEYjDsw6RKc7rBJCdvCTfKsVnx2GEB/Nbzjr29DUdb7vQhlzS/j8qDzdditP0OC6aw=="
+ },
+ "node_modules/@octokit/plugin-retry/node_modules/@octokit/types": {
+ "version": "14.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/types/-/types-14.0.0.tgz",
+ "integrity": "sha512-VVmZP0lEhbo2O1pdq63gZFiGCKkm8PPp8AUOijlwPO6hojEVjspA0MWKP7E4hbvGxzFKNqKr6p0IYtOH/Wf/zA==",
+ "dependencies": {
+ "@octokit/openapi-types": "^25.0.0"
}
},
"node_modules/@octokit/request": {
- "version": "9.2.2",
- "resolved": "https://registry.npmjs.org/@octokit/request/-/request-9.2.2.tgz",
- "integrity": "sha512-dZl0ZHx6gOQGcffgm1/Sf6JfEpmh34v3Af2Uci02vzUYz6qEN6zepoRtmybWXIGXFIK8K9ylE3b+duCWqhArtg==",
- "license": "MIT",
+ "version": "10.0.2",
+ "resolved": "https://registry.npmjs.org/@octokit/request/-/request-10.0.2.tgz",
+ "integrity": "sha512-iYj4SJG/2bbhh+iIpFmG5u49DtJ4lipQ+aPakjL9OKpsGY93wM8w06gvFbEQxcMsZcCvk5th5KkIm2m8o14aWA==",
+ "peer": true,
"dependencies": {
- "@octokit/endpoint": "^10.1.3",
- "@octokit/request-error": "^6.1.7",
- "@octokit/types": "^13.6.2",
- "fast-content-type-parse": "^2.0.0",
+ "@octokit/endpoint": "^11.0.0",
+ "@octokit/request-error": "^7.0.0",
+ "@octokit/types": "^14.0.0",
+ "fast-content-type-parse": "^3.0.0",
"universal-user-agent": "^7.0.2"
},
"engines": {
- "node": ">= 18"
+ "node": ">= 20"
}
},
"node_modules/@octokit/request-error": {
- "version": "6.1.8",
- "resolved": "https://registry.npmjs.org/@octokit/request-error/-/request-error-6.1.8.tgz",
- "integrity": "sha512-WEi/R0Jmq+IJKydWlKDmryPcmdYSVjL3ekaiEL1L9eo1sUnqMJ+grqmC9cjk7CA7+b2/T397tO5d8YLOH3qYpQ==",
- "license": "MIT",
+ "version": "7.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/request-error/-/request-error-7.0.0.tgz",
+ "integrity": "sha512-KRA7VTGdVyJlh0cP5Tf94hTiYVVqmt2f3I6mnimmaVz4UG3gQV/k4mDJlJv3X67iX6rmN7gSHCF8ssqeMnmhZg==",
"dependencies": {
"@octokit/types": "^14.0.0"
},
"engines": {
- "node": ">= 18"
+ "node": ">= 20"
}
},
"node_modules/@octokit/request-error/node_modules/@octokit/openapi-types": {
@@ -2487,6 +2547,21 @@
"@octokit/openapi-types": "^25.0.0"
}
},
+ "node_modules/@octokit/request/node_modules/@octokit/openapi-types": {
+ "version": "25.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-25.0.0.tgz",
+ "integrity": "sha512-FZvktFu7HfOIJf2BScLKIEYjDsw6RKc7rBJCdvCTfKsVnx2GEB/Nbzjr29DUdb7vQhlzS/j8qDzdditP0OC6aw==",
+ "peer": true
+ },
+ "node_modules/@octokit/request/node_modules/@octokit/types": {
+ "version": "14.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/types/-/types-14.0.0.tgz",
+ "integrity": "sha512-VVmZP0lEhbo2O1pdq63gZFiGCKkm8PPp8AUOijlwPO6hojEVjspA0MWKP7E4hbvGxzFKNqKr6p0IYtOH/Wf/zA==",
+ "peer": true,
+ "dependencies": {
+ "@octokit/openapi-types": "^25.0.0"
+ }
+ },
"node_modules/@octokit/rest": {
"version": "21.0.2",
"resolved": "https://registry.npmjs.org/@octokit/rest/-/rest-21.0.2.tgz",
@@ -2503,10 +2578,130 @@
"node": ">= 18"
}
},
+ "node_modules/@octokit/rest/node_modules/@octokit/auth-token": {
+ "version": "5.1.2",
+ "resolved": "https://registry.npmjs.org/@octokit/auth-token/-/auth-token-5.1.2.tgz",
+ "integrity": "sha512-JcQDsBdg49Yky2w2ld20IHAlwr8d/d8N6NiOXbtuoPCqzbsiJgF633mVUw3x4mo0H5ypataQIX7SFu3yy44Mpw==",
+ "dev": true,
+ "engines": {
+ "node": ">= 18"
+ }
+ },
+ "node_modules/@octokit/rest/node_modules/@octokit/core": {
+ "version": "6.1.5",
+ "resolved": "https://registry.npmjs.org/@octokit/core/-/core-6.1.5.tgz",
+ "integrity": "sha512-vvmsN0r7rguA+FySiCsbaTTobSftpIDIpPW81trAmsv9TGxg3YCujAxRYp/Uy8xmDgYCzzgulG62H7KYUFmeIg==",
+ "dev": true,
+ "dependencies": {
+ "@octokit/auth-token": "^5.0.0",
+ "@octokit/graphql": "^8.2.2",
+ "@octokit/request": "^9.2.3",
+ "@octokit/request-error": "^6.1.8",
+ "@octokit/types": "^14.0.0",
+ "before-after-hook": "^3.0.2",
+ "universal-user-agent": "^7.0.0"
+ },
+ "engines": {
+ "node": ">= 18"
+ }
+ },
+ "node_modules/@octokit/rest/node_modules/@octokit/endpoint": {
+ "version": "10.1.4",
+ "resolved": "https://registry.npmjs.org/@octokit/endpoint/-/endpoint-10.1.4.tgz",
+ "integrity": "sha512-OlYOlZIsfEVZm5HCSR8aSg02T2lbUWOsCQoPKfTXJwDzcHQBrVBGdGXb89dv2Kw2ToZaRtudp8O3ZIYoaOjKlA==",
+ "dev": true,
+ "dependencies": {
+ "@octokit/types": "^14.0.0",
+ "universal-user-agent": "^7.0.2"
+ },
+ "engines": {
+ "node": ">= 18"
+ }
+ },
+ "node_modules/@octokit/rest/node_modules/@octokit/graphql": {
+ "version": "8.2.2",
+ "resolved": "https://registry.npmjs.org/@octokit/graphql/-/graphql-8.2.2.tgz",
+ "integrity": "sha512-Yi8hcoqsrXGdt0yObxbebHXFOiUA+2v3n53epuOg1QUgOB6c4XzvisBNVXJSl8RYA5KrDuSL2yq9Qmqe5N0ryA==",
+ "dev": true,
+ "dependencies": {
+ "@octokit/request": "^9.2.3",
+ "@octokit/types": "^14.0.0",
+ "universal-user-agent": "^7.0.0"
+ },
+ "engines": {
+ "node": ">= 18"
+ }
+ },
+ "node_modules/@octokit/rest/node_modules/@octokit/openapi-types": {
+ "version": "25.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-25.0.0.tgz",
+ "integrity": "sha512-FZvktFu7HfOIJf2BScLKIEYjDsw6RKc7rBJCdvCTfKsVnx2GEB/Nbzjr29DUdb7vQhlzS/j8qDzdditP0OC6aw==",
+ "dev": true
+ },
+ "node_modules/@octokit/rest/node_modules/@octokit/request": {
+ "version": "9.2.3",
+ "resolved": "https://registry.npmjs.org/@octokit/request/-/request-9.2.3.tgz",
+ "integrity": "sha512-Ma+pZU8PXLOEYzsWf0cn/gY+ME57Wq8f49WTXA8FMHp2Ps9djKw//xYJ1je8Hm0pR2lU9FUGeJRWOtxq6olt4w==",
+ "dev": true,
+ "dependencies": {
+ "@octokit/endpoint": "^10.1.4",
+ "@octokit/request-error": "^6.1.8",
+ "@octokit/types": "^14.0.0",
+ "fast-content-type-parse": "^2.0.0",
+ "universal-user-agent": "^7.0.2"
+ },
+ "engines": {
+ "node": ">= 18"
+ }
+ },
+ "node_modules/@octokit/rest/node_modules/@octokit/request-error": {
+ "version": "6.1.8",
+ "resolved": "https://registry.npmjs.org/@octokit/request-error/-/request-error-6.1.8.tgz",
+ "integrity": "sha512-WEi/R0Jmq+IJKydWlKDmryPcmdYSVjL3ekaiEL1L9eo1sUnqMJ+grqmC9cjk7CA7+b2/T397tO5d8YLOH3qYpQ==",
+ "dev": true,
+ "dependencies": {
+ "@octokit/types": "^14.0.0"
+ },
+ "engines": {
+ "node": ">= 18"
+ }
+ },
+ "node_modules/@octokit/rest/node_modules/@octokit/types": {
+ "version": "14.0.0",
+ "resolved": "https://registry.npmjs.org/@octokit/types/-/types-14.0.0.tgz",
+ "integrity": "sha512-VVmZP0lEhbo2O1pdq63gZFiGCKkm8PPp8AUOijlwPO6hojEVjspA0MWKP7E4hbvGxzFKNqKr6p0IYtOH/Wf/zA==",
+ "dev": true,
+ "dependencies": {
+ "@octokit/openapi-types": "^25.0.0"
+ }
+ },
+ "node_modules/@octokit/rest/node_modules/before-after-hook": {
+ "version": "3.0.2",
+ "resolved": "https://registry.npmjs.org/before-after-hook/-/before-after-hook-3.0.2.tgz",
+ "integrity": "sha512-Nik3Sc0ncrMK4UUdXQmAnRtzmNQTAAXmXIopizwZ1W1t8QmfJj+zL4OA2I7XPTPW5z5TDqv4hRo/JzouDJnX3A==",
+ "dev": true
+ },
+ "node_modules/@octokit/rest/node_modules/fast-content-type-parse": {
+ "version": "2.0.1",
+ "resolved": "https://registry.npmjs.org/fast-content-type-parse/-/fast-content-type-parse-2.0.1.tgz",
+ "integrity": "sha512-nGqtvLrj5w0naR6tDPfB4cUmYCqouzyQiz6C5y/LtcDllJdrcc6WaWW6iXyIIOErTa/XRybj28aasdn4LkVk6Q==",
+ "dev": true,
+ "funding": [
+ {
+ "type": "github",
+ "url": "https://github.com/sponsors/fastify"
+ },
+ {
+ "type": "opencollective",
+ "url": "https://opencollective.com/fastify"
+ }
+ ]
+ },
"node_modules/@octokit/types": {
"version": "13.8.0",
"resolved": "https://registry.npmjs.org/@octokit/types/-/types-13.8.0.tgz",
"integrity": "sha512-x7DjTIbEpEWXK99DMd01QfWy0hd5h4EN+Q7shkdKds3otGQP+oWE/y0A76i1OvH9fygo4ddvNf7ZvF0t78P98A==",
+ "dev": true,
"license": "MIT",
"dependencies": {
"@octokit/openapi-types": "^23.0.1"
@@ -5601,9 +5796,10 @@
}
},
"node_modules/before-after-hook": {
- "version": "3.0.2",
- "resolved": "https://registry.npmjs.org/before-after-hook/-/before-after-hook-3.0.2.tgz",
- "integrity": "sha512-Nik3Sc0ncrMK4UUdXQmAnRtzmNQTAAXmXIopizwZ1W1t8QmfJj+zL4OA2I7XPTPW5z5TDqv4hRo/JzouDJnX3A=="
+ "version": "4.0.0",
+ "resolved": "https://registry.npmjs.org/before-after-hook/-/before-after-hook-4.0.0.tgz",
+ "integrity": "sha512-q6tR3RPqIB1pMiTRMFcZwuG5T8vwp+vUvEG0vuI6B+Rikh5BfPp2fQ82c925FOs+b0lcFQ8CFrL+KbilfZFhOQ==",
+ "peer": true
},
"node_modules/binary-extensions": {
"version": "2.2.0",
@@ -6225,13 +6421,12 @@
}
},
"node_modules/commander": {
- "version": "13.1.0",
- "resolved": "https://registry.npmjs.org/commander/-/commander-13.1.0.tgz",
- "integrity": "sha512-/rFeCpNJQbhSZjGVwO9RFV3xPqbnERS8MmIQzCtD/zl6gpJuV/bMLuN92oG3F7d8oDEHHRrujSXNUr8fpjntKw==",
+ "version": "14.0.0",
+ "resolved": "https://registry.npmjs.org/commander/-/commander-14.0.0.tgz",
+ "integrity": "sha512-2uM9rYjPvyq39NwLRqaiLtWHyDC1FvryJDa2ATTVims5YAS4PupsEQsDvP14FqhFr0P49CYDugi59xaxJlTXRA==",
"dev": true,
- "license": "MIT",
"engines": {
- "node": ">=18"
+ "node": ">=20"
}
},
"node_modules/compute-gcd": {
@@ -8181,9 +8376,9 @@
}
},
"node_modules/fast-content-type-parse": {
- "version": "2.0.1",
- "resolved": "https://registry.npmjs.org/fast-content-type-parse/-/fast-content-type-parse-2.0.1.tgz",
- "integrity": "sha512-nGqtvLrj5w0naR6tDPfB4cUmYCqouzyQiz6C5y/LtcDllJdrcc6WaWW6iXyIIOErTa/XRybj28aasdn4LkVk6Q==",
+ "version": "3.0.0",
+ "resolved": "https://registry.npmjs.org/fast-content-type-parse/-/fast-content-type-parse-3.0.0.tgz",
+ "integrity": "sha512-ZvLdcY8P+N8mGQJahJV5G4U88CSvT1rP8ApL6uETe88MBXrBHAkZlSEySdUlyztF7ccb+Znos3TFqaepHxdhBg==",
"funding": [
{
"type": "github",
@@ -8194,7 +8389,7 @@
"url": "https://opencollective.com/fastify"
}
],
- "license": "MIT"
+ "peer": true
},
"node_modules/fast-deep-equal": {
"version": "3.1.3",
@@ -10359,6 +10554,15 @@
"url": "https://opencollective.com/lint-staged"
}
},
+ "node_modules/lint-staged/node_modules/commander": {
+ "version": "13.1.0",
+ "resolved": "https://registry.npmjs.org/commander/-/commander-13.1.0.tgz",
+ "integrity": "sha512-/rFeCpNJQbhSZjGVwO9RFV3xPqbnERS8MmIQzCtD/zl6gpJuV/bMLuN92oG3F7d8oDEHHRrujSXNUr8fpjntKw==",
+ "dev": true,
+ "engines": {
+ "node": ">=18"
+ }
+ },
"node_modules/liquidjs": {
"version": "10.21.0",
"resolved": "https://registry.npmjs.org/liquidjs/-/liquidjs-10.21.0.tgz",
@@ -15431,9 +15635,9 @@
}
},
"node_modules/universal-user-agent": {
- "version": "7.0.2",
- "resolved": "https://registry.npmjs.org/universal-user-agent/-/universal-user-agent-7.0.2.tgz",
- "integrity": "sha512-0JCqzSKnStlRRQfCdowvqy3cy0Dvtlb8xecj/H8JFZuCze4rwjPZQOgvFvn0Ws/usCHQFGpyr+pB9adaGwXn4Q=="
+ "version": "7.0.3",
+ "resolved": "https://registry.npmjs.org/universal-user-agent/-/universal-user-agent-7.0.3.tgz",
+ "integrity": "sha512-TmnEAEAsBJVZM/AADELsK76llnwcf9vMKuPz8JflO1frO8Lchitr0fNaN9d+Ap0BjKtqWqd/J17qeDnXh8CL2A=="
},
"node_modules/universalify": {
"version": "2.0.0",
diff --git a/package.json b/package.json
index f13a312198e6..13b67feee402 100644
--- a/package.json
+++ b/package.json
@@ -246,8 +246,8 @@
"@elastic/elasticsearch": "8.13.1",
"@github/failbot": "0.8.3",
"@horizon-rs/language-guesser": "0.1.1",
- "@octokit/plugin-retry": "7.1.4",
- "@octokit/request-error": "6.1.8",
+ "@octokit/plugin-retry": "8.0.1",
+ "@octokit/request-error": "7.0.0",
"@primer/behaviors": "^1.7.2",
"@primer/css": "^21.3.1",
"@primer/live-region-element": "^0.7.2",
@@ -368,7 +368,7 @@
"@typescript-eslint/parser": "^8.7.0",
"chalk": "^5.0.1",
"change-case": "^5.4.4",
- "commander": "^13.0.0",
+ "commander": "^14.0.0",
"cross-env": "^7.0.3",
"csp-parse": "0.0.2",
"csv-parse": "5.5.6",
diff --git a/src/frame/components/context/CTAContext.tsx b/src/frame/components/context/CTAContext.tsx
index 474e8f0e870f..8f033c0a5cf8 100644
--- a/src/frame/components/context/CTAContext.tsx
+++ b/src/frame/components/context/CTAContext.tsx
@@ -13,59 +13,89 @@ import {
type CTAPopoverState = {
isOpen: boolean
initializeCTA: () => void // Call to "open" the CTA if it's not already been dismissed by the user
- dismiss: () => void // Call to "close" the CTA and store the dismissal in local storage
+ dismiss: () => void // Call to "close" the CTA and store the dismissal in local storage. Will be shown again after 24 hours for a max of 3 times
+ permanentDismiss: () => void // Call to permanently dismiss the CTA and store the dismissal in local storage
}
-type StoredValue = { dismissed: true }
+type StoredValue = {
+ dismissedCount: number
+ lastDismissedAt: number | null
+ permanentlyDismissed: boolean
+}
const CTAPopoverContext = createContext(undefined)
-const STORAGE_KEY = 'ctaPopoverDismissed'
+const STORAGE_KEY = 'ctaPopoverState'
+const MAX_DISMISSES = 3
+const HIDE_CTA_FOR_MS = 24 * 60 * 60 * 1000 // Every 24 hours we show the CTA again, unless permanently dismissed
-const isDismissed = (): boolean => {
+const shouldHide = (): boolean => {
if (typeof window === 'undefined') return false // SSR guard
try {
const raw = localStorage.getItem(STORAGE_KEY)
if (!raw) return false
const parsed = JSON.parse(raw) as StoredValue
- return parsed?.dismissed
+ if (parsed.permanentlyDismissed) return true
+ if (parsed.dismissedCount >= MAX_DISMISSES) return true
+ if (parsed.lastDismissedAt && Date.now() - parsed.lastDismissedAt < HIDE_CTA_FOR_MS) return true
+ return false
} catch {
return false // corruption / quota / disabled storage
}
}
+const readStored = (): StoredValue => {
+ const emptyValue = { dismissedCount: 0, lastDismissedAt: null, permanentlyDismissed: false }
+ try {
+ const raw = localStorage.getItem(STORAGE_KEY)
+ if (!raw) {
+ return emptyValue
+ }
+ return JSON.parse(raw) as StoredValue
+ } catch {
+ return emptyValue // corruption / quota / disabled storage
+ }
+}
+
+const writeStored = (v: StoredValue) => {
+ try {
+ localStorage.setItem(STORAGE_KEY, JSON.stringify(v))
+ } catch {
+ /* ignore */
+ }
+}
+
export function CTAPopoverProvider({ children }: PropsWithChildren) {
// We start closed because we might only want to "turn on" the CTA if an experiment is active
const [isOpen, setIsOpen] = useState(false)
- const persistDismissal = useCallback(() => {
+ const dismiss = useCallback(() => {
+ const stored = readStored()
+ writeStored({
+ ...stored,
+ dismissedCount: stored.dismissedCount + 1,
+ lastDismissedAt: Date.now(),
+ })
+ setIsOpen(false)
+ }, [])
+
+ const permanentDismiss = useCallback(() => {
+ const stored = readStored()
+ writeStored({ ...stored, permanentlyDismissed: true })
setIsOpen(false)
- try {
- const obj: StoredValue = { dismissed: true }
- localStorage.setItem(STORAGE_KEY, JSON.stringify(obj))
- } catch {
- /* ignore */
- }
}, [])
- const dismiss = useCallback(() => persistDismissal(), [persistDismissal])
const initializeCTA = useCallback(() => {
- const dismissed = isDismissed()
- if (dismissed) {
- setIsOpen(false)
- } else {
- setIsOpen(true)
- }
- }, [isDismissed])
+ setIsOpen(!shouldHide())
+ }, [])
// Wrap in a useEffect to avoid a hydration mismatch (SSR guard)
useEffect(() => {
- const stored = isDismissed()
- setIsOpen(!stored)
+ setIsOpen(!shouldHide())
}, [])
return (
-
+
{children}
)
diff --git a/src/search/components/input/AskAIResults.tsx b/src/search/components/input/AskAIResults.tsx
index 86d1e9cd46b4..d3b09beea4c9 100644
--- a/src/search/components/input/AskAIResults.tsx
+++ b/src/search/components/input/AskAIResults.tsx
@@ -83,7 +83,7 @@ export function AskAIResults({
aiCouldNotAnswer: boolean
connectedEventId?: string
}>('ai-query-cache', 1000, 7)
- const { isOpen: isCTAOpen, dismiss: dismissCTA } = useCTAPopoverContext()
+ const { isOpen: isCTAOpen, permanentDismiss: permanentlyDismissCTA } = useCTAPopoverContext()
const [isCopied, setCopied] = useClipboard(message, { successDuration: 1400 })
const [feedbackSelected, setFeedbackSelected] = useState(null)
@@ -138,9 +138,10 @@ export function AskAIResults({
setResponseLoading(true)
disclaimerRef.current?.focus()
- // Upon performing an AI Search, dismiss the CTA if it is open
+ // We permanently dismiss the CTA after performing an AI Search because the
+ // user has tried it and doesn't require additional CTA prompting to try it
if (isCTAOpen) {
- dismissCTA()
+ permanentlyDismissCTA()
}
const cachedData = getItem(query, version, router.locale || 'en')