diff --git a/assets/images/enterprise/3.1/help/repository/enable-ghas.png b/assets/images/enterprise/3.1/help/repository/enable-ghas.png
deleted file mode 100644
index 91b15bf8168a..000000000000
Binary files a/assets/images/enterprise/3.1/help/repository/enable-ghas.png and /dev/null differ
diff --git a/assets/images/help/actions/environments.png b/assets/images/help/actions/environments.png
new file mode 100644
index 000000000000..f13cba276a96
Binary files /dev/null and b/assets/images/help/actions/environments.png differ
diff --git a/assets/images/help/actions/workflow-run-kebab-horizontal-icon.png b/assets/images/help/actions/workflow-run-kebab-horizontal-icon.png
new file mode 100644
index 000000000000..c79bcb093bd6
Binary files /dev/null and b/assets/images/help/actions/workflow-run-kebab-horizontal-icon.png differ
diff --git a/assets/images/help/repository/copy-default-branch-only.png b/assets/images/help/repository/copy-default-branch-only.png
deleted file mode 100644
index 41b1ebdab94e..000000000000
Binary files a/assets/images/help/repository/copy-default-branch-only.png and /dev/null differ
diff --git a/assets/images/help/repository/default-commit-message-dropdown.png b/assets/images/help/repository/default-commit-message-dropdown.png
deleted file mode 100644
index 2a35b46e0b4f..000000000000
Binary files a/assets/images/help/repository/default-commit-message-dropdown.png and /dev/null differ
diff --git a/assets/images/help/repository/default-file-repository-name.png b/assets/images/help/repository/default-file-repository-name.png
deleted file mode 100644
index 36ee341d2119..000000000000
Binary files a/assets/images/help/repository/default-file-repository-name.png and /dev/null differ
diff --git a/assets/images/help/repository/default-squash-message-dropdown.png b/assets/images/help/repository/default-squash-message-dropdown.png
deleted file mode 100644
index 27fe0c2bb26d..000000000000
Binary files a/assets/images/help/repository/default-squash-message-dropdown.png and /dev/null differ
diff --git a/assets/images/help/repository/delete-all-logs-updated-2.png b/assets/images/help/repository/delete-all-logs-updated-2.png
deleted file mode 100644
index 791a2f27ec73..000000000000
Binary files a/assets/images/help/repository/delete-all-logs-updated-2.png and /dev/null differ
diff --git a/assets/images/help/repository/delete-branch-protection-rule.png b/assets/images/help/repository/delete-branch-protection-rule.png
deleted file mode 100644
index 076ad664b49f..000000000000
Binary files a/assets/images/help/repository/delete-branch-protection-rule.png and /dev/null differ
diff --git a/assets/images/help/repository/edit-readme-preview-changes.png b/assets/images/help/repository/edit-readme-preview-changes.png
index 0240397bd8af..4b613da2f71e 100644
Binary files a/assets/images/help/repository/edit-readme-preview-changes.png and b/assets/images/help/repository/edit-readme-preview-changes.png differ
diff --git a/assets/images/help/repository/empty-desktop-clone-button.png b/assets/images/help/repository/empty-desktop-clone-button.png
index f4d865fe4497..8d86ce1f8900 100644
Binary files a/assets/images/help/repository/empty-desktop-clone-button.png and b/assets/images/help/repository/empty-desktop-clone-button.png differ
diff --git a/assets/images/help/repository/empty-https-url-clone-button.png b/assets/images/help/repository/empty-https-url-clone-button.png
index 0d485aec9aed..9f954bdb0ec3 100644
Binary files a/assets/images/help/repository/empty-https-url-clone-button.png and b/assets/images/help/repository/empty-https-url-clone-button.png differ
diff --git a/assets/images/help/repository/enable-debug-logging.png b/assets/images/help/repository/enable-debug-logging.png
deleted file mode 100644
index d02e0a916c80..000000000000
Binary files a/assets/images/help/repository/enable-debug-logging.png and /dev/null differ
diff --git a/assets/images/help/repository/enable-ghas-dotcom.png b/assets/images/help/repository/enable-ghas-dotcom.png
deleted file mode 100644
index c44b0ad0a812..000000000000
Binary files a/assets/images/help/repository/enable-ghas-dotcom.png and /dev/null differ
diff --git a/assets/images/help/repository/enable-git-read-access-for-a-repo.png b/assets/images/help/repository/enable-git-read-access-for-a-repo.png
deleted file mode 100644
index 515a42b24604..000000000000
Binary files a/assets/images/help/repository/enable-git-read-access-for-a-repo.png and /dev/null differ
diff --git a/assets/images/help/repository/export-personal-data.png b/assets/images/help/repository/export-personal-data.png
deleted file mode 100644
index be0ddddbeb28..000000000000
Binary files a/assets/images/help/repository/export-personal-data.png and /dev/null differ
diff --git a/assets/images/help/repository/export-repository-permissions.png b/assets/images/help/repository/export-repository-permissions.png
deleted file mode 100644
index 828fdaf9cc83..000000000000
Binary files a/assets/images/help/repository/export-repository-permissions.png and /dev/null differ
diff --git a/assets/images/help/repository/fetch-and-merge-button.png b/assets/images/help/repository/fetch-and-merge-button.png
deleted file mode 100644
index b049880cd88f..000000000000
Binary files a/assets/images/help/repository/fetch-and-merge-button.png and /dev/null differ
diff --git a/assets/images/help/repository/fetch-upstream-drop-down.png b/assets/images/help/repository/fetch-upstream-drop-down.png
index 3d5ea3781c6c..0c280b6fa200 100644
Binary files a/assets/images/help/repository/fetch-upstream-drop-down.png and b/assets/images/help/repository/fetch-upstream-drop-down.png differ
diff --git a/assets/images/help/repository/file-tree.png b/assets/images/help/repository/file-tree.png
index 88987f55ffe9..c5302ebbf4d4 100644
Binary files a/assets/images/help/repository/file-tree.png and b/assets/images/help/repository/file-tree.png differ
diff --git a/assets/images/help/repository/find-all-references-tab.png b/assets/images/help/repository/find-all-references-tab.png
index c6a3d4c86a13..bd90f1618986 100644
Binary files a/assets/images/help/repository/find-all-references-tab.png and b/assets/images/help/repository/find-all-references-tab.png differ
diff --git a/assets/images/help/repository/first-commit.png b/assets/images/help/repository/first-commit.png
deleted file mode 100644
index 0036d4bcc769..000000000000
Binary files a/assets/images/help/repository/first-commit.png and /dev/null differ
diff --git a/assets/images/help/repository/fork-choose-owner.png b/assets/images/help/repository/fork-choose-owner.png
deleted file mode 100644
index 2ddc4087b57c..000000000000
Binary files a/assets/images/help/repository/fork-choose-owner.png and /dev/null differ
diff --git a/assets/images/help/repository/fork-choose-repo-name.png b/assets/images/help/repository/fork-choose-repo-name.png
deleted file mode 100644
index 574716d2b4d3..000000000000
Binary files a/assets/images/help/repository/fork-choose-repo-name.png and /dev/null differ
diff --git a/assets/images/help/repository/fork-create-button.png b/assets/images/help/repository/fork-create-button.png
deleted file mode 100644
index ed90512b6ab4..000000000000
Binary files a/assets/images/help/repository/fork-create-button.png and /dev/null differ
diff --git a/assets/images/help/repository/fork-description.png b/assets/images/help/repository/fork-description.png
deleted file mode 100644
index 935ffad94958..000000000000
Binary files a/assets/images/help/repository/fork-description.png and /dev/null differ
diff --git a/assets/images/help/repository/fork_button.png b/assets/images/help/repository/fork_button.png
index 8fda1517cd15..c8fb42e0f4da 100644
Binary files a/assets/images/help/repository/fork_button.png and b/assets/images/help/repository/fork_button.png differ
diff --git a/assets/images/help/repository/git_blame.png b/assets/images/help/repository/git_blame.png
index 35cc8c73221b..2325a178f823 100644
Binary files a/assets/images/help/repository/git_blame.png and b/assets/images/help/repository/git_blame.png differ
diff --git a/assets/images/help/repository/github-archive-program-checkbox.png b/assets/images/help/repository/github-archive-program-checkbox.png
deleted file mode 100644
index 4e0f4e537d68..000000000000
Binary files a/assets/images/help/repository/github-archive-program-checkbox.png and /dev/null differ
diff --git a/assets/images/help/repository/hello-world-repo.png b/assets/images/help/repository/hello-world-repo.png
deleted file mode 100644
index 7229418f5f29..000000000000
Binary files a/assets/images/help/repository/hello-world-repo.png and /dev/null differ
diff --git a/assets/images/help/repository/https-url-clone-cli.png b/assets/images/help/repository/https-url-clone-cli.png
index d888ecda7846..8c245d429bbc 100644
Binary files a/assets/images/help/repository/https-url-clone-cli.png and b/assets/images/help/repository/https-url-clone-cli.png differ
diff --git a/assets/images/help/repository/initialize-with-readme.png b/assets/images/help/repository/initialize-with-readme.png
deleted file mode 100644
index 5ad39d652453..000000000000
Binary files a/assets/images/help/repository/initialize-with-readme.png and /dev/null differ
diff --git a/assets/images/help/repository/new-branch.png b/assets/images/help/repository/new-branch.png
index 2237e730ec49..6f6932c6cbf7 100644
Binary files a/assets/images/help/repository/new-branch.png and b/assets/images/help/repository/new-branch.png differ
diff --git a/assets/images/help/repository/open-with-desktop.png b/assets/images/help/repository/open-with-desktop.png
index 5fb7b63e32b5..65797b120d6c 100644
Binary files a/assets/images/help/repository/open-with-desktop.png and b/assets/images/help/repository/open-with-desktop.png differ
diff --git a/assets/images/help/repository/save-branch-protection-rule.png b/assets/images/help/repository/save-branch-protection-rule.png
deleted file mode 100644
index a01d4985d732..000000000000
Binary files a/assets/images/help/repository/save-branch-protection-rule.png and /dev/null differ
diff --git a/assets/images/help/repository/sync-fork-dropdown.png b/assets/images/help/repository/sync-fork-dropdown.png
index d2667c981a41..8fc4487cee21 100644
Binary files a/assets/images/help/repository/sync-fork-dropdown.png and b/assets/images/help/repository/sync-fork-dropdown.png differ
diff --git a/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index 0af9b46407ff..ddf6b45a650c 100644
--- a/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -63,7 +63,6 @@ You can download the log files from your workflow run. You can also download a w
 
   ![Screenshot of the log for a job. In the header, a gear icon is outlined in dark orange.](/assets/images/help/actions/download-logs-drop-down.png)
 
-
   {% ifversion re-run-jobs %}
 
   {% note %}
@@ -82,11 +81,11 @@ You can delete the log files from your workflow run. {% data reusables.repositor
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="Show options" %}.
+1. In the upper-right corner, select the {% octicon "kebab-horizontal" aria-label="Show workflow options" %} dropdown menu, then click **Delete all logs**.
 
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
+    ![Screenshot of the page for a workflow run. In the top-right corner, a button, labeled with a kebab icon, is outlined in dark orange.](/assets/images/help/actions/workflow-run-kebab-horizontal-icon.png)
 
-2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt.
+1. Review the confirmation prompt.
 
 After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
 
diff --git a/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
index 107e35483f11..e796977514ea 100644
--- a/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
+++ b/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
@@ -46,14 +46,12 @@ You can enable {% data variables.secret-scanning.user_alerts %} for any {% ifver
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}{% ifversion ghec or ghes or ghae %}
 1. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
-   {% ifversion ghec %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
-   {% elsif ghes or ghae %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
 1. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
-1. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. 
-   
+1. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled.
+
    ![Screenshot of the "{% data variables.product.prodname_secret_scanning_caps %}" section of the "Code security and analysis" page, with the "Enable" button highlighted in a dark orange outline.](/assets/images/help/repository/enable-secret-scanning-alerts.png){% endif %}{% ifversion fpt %}
-1. Scroll down to the bottom of the page, and click **Enable** for {% data variables.product.prodname_secret_scanning %}. If you see a **Disable** button, it means that {% data variables.product.prodname_secret_scanning %} is already enabled for the repository. 
-   
+1. Scroll down to the bottom of the page, and click **Enable** for {% data variables.product.prodname_secret_scanning %}. If you see a **Disable** button, it means that {% data variables.product.prodname_secret_scanning %} is already enabled for the repository.
+
    ![Screenshot of the "{% data variables.product.prodname_secret_scanning_caps %}" section of the "Code security and analysis" page, with the "Enable" button highlighted in a dark orange outline.](/assets/images/help/repository/enable-secret-scanning-alerts.png){% endif %}
 
 {% ifversion secret-scanning-push-protection %}
diff --git a/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index fb4b05d00056..33007b889e50 100644
--- a/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -46,12 +46,12 @@ You cannot create a default license file. License files must be added to individ
 ## Creating a repository for default files
 
 {% data reusables.repositories.create_new %}
-2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
+1. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
   ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png)
-3. Type **.github** as the name for your repository, and an optional description.
-  ![Create repository field](/assets/images/help/repository/default-file-repository-name.png)
-4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+1. In the "Repository name" field, type **.github**.
+1. Optionally, in the "Description" field, type a description.
+1. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
   ![Radio buttons to select private or public status](/assets/images/help/repository/create-repository-public-private.png)
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
-7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."
+1. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."
diff --git a/content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md b/content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md
index bd09f181ee2e..b289ab2ca4c9 100644
--- a/content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md
+++ b/content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md
@@ -19,8 +19,7 @@ If you opt out of the {% data variables.product.prodname_archive %} for a reposi
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Features", select or unselect **Preserve this repository**.
-    ![Checkbox for allowing {% data variables.product.prodname_dotcom %} to include your code in the {% data variables.product.prodname_archive %}](/assets/images/help/repository/github-archive-program-checkbox.png)
+1. Under "Features", select or deselect **Preserve this repository**.
 
 ## Further reading
 - [{% data variables.product.prodname_archive %} FAQ](https://archiveprogram.github.com/faq/)
diff --git a/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md b/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md
index 27dbad6ae60c..a3be162ffccc 100644
--- a/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md
+++ b/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md
@@ -30,12 +30,10 @@ The generated `tar.gz` file reflects the data stored at the time you started the
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.account_settings %}
-3. Under "Export account data", click **Start export** or **New export**.
-![Start personal data export button highlighted](/assets/images/help/repository/export-personal-data.png)
-![New personal data export button highlighted](/assets/images/help/repository/new-export.png)
-4. Once the export is ready to download, {% data variables.product.product_name %} will send you a download link to your primary email address.
-5. Click the download link in your email and re-enter your password if prompted.
-6. You'll be redirected to a `tar.gz` file that you can download.
+1. Under "Export account data", click **Start export** or **New export**.
+1. Once the export is ready to download, {% data variables.product.product_name %} will send you a download link to your primary email address.
+1. Click the download link in your email and re-enter your password if prompted.
+1. You'll be redirected to a `tar.gz` file that you can download.
 
 ## Deleting access to an archive of your personal account's data
 
@@ -43,4 +41,4 @@ You can disable the download link sent to your email before an export expires by
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.account_settings %}
-3. In the "Export account data" section, next to the data export download you want to disable, click **Delete**.
+1. In the "Export account data" section, next to the data export download you want to disable, click **Delete**.
diff --git a/content/get-started/quickstart/contributing-to-projects.md b/content/get-started/quickstart/contributing-to-projects.md
index 766c81b100a6..5381b31e5256 100644
--- a/content/get-started/quickstart/contributing-to-projects.md
+++ b/content/get-started/quickstart/contributing-to-projects.md
@@ -16,7 +16,7 @@ topics:
 
 ## About forking
 
-If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow. 
+If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
 
 {% data reusables.repositories.fork-definition-long %}
 
@@ -27,18 +27,17 @@ You can contribute by submitting pull requests from your fork to the upstream re
 This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Knife), a test repository that's hosted on {% data variables.product.prodname_dotcom_the_website %} that lets you test the fork and pull request workflow.
 
 1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife.
-2. Click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
-3. Select an owner for the forked repository.
-   ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
-4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further. 
-   ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
-5. Optionally, add a description of your fork.
-   ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
-6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
-   ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
-7. Click **Create fork**.
-   ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+1. Click **Fork**.
+
+   ![Screenshot of the main page of repository. A button, labeled with a fork icon and "Fork 59.3k," is outlined in dark orange.](/assets/images/help/repository/fork_button.png)
+{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+1. Under "Owner," select the dropdown menu and click an owner for the forked repository.
+1. By default, forks are named the same as their upstream repositories. Optionally, to further distinguish your fork, in the "Repository name" field, type a name.
+1. Optionally, in the "Description" field, type a description of your fork.
+1. Optionally, select **Copy the DEFAULT branch only**.
+
+    For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. If you do not select this option, all branches will be copied into the new fork.
+1. Click **Create fork**.
 
 {% note %}
 
diff --git a/content/get-started/quickstart/fork-a-repo.md b/content/get-started/quickstart/fork-a-repo.md
index 6c3efb2e5693..5ac0b5824c2e 100644
--- a/content/get-started/quickstart/fork-a-repo.md
+++ b/content/get-started/quickstart/fork-a-repo.md
@@ -56,20 +56,19 @@ If you haven't yet, first set up Git and authentication with {% data variables.l
 You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
-2. In the top-right corner of the page, click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
-3. Select an owner for the forked repository.
-   ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
-4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
-   ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
-5. Optionally, add a description of your fork.
-   ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
+1. In the top-right corner of the page, click **Fork**.
+
+   ![Screenshot of the main page of repository. A button, labeled with a fork icon and "Fork 59.3k," is outlined in dark orange.](/assets/images/help/repository/fork_button.png)
+{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+1. Under "Owner," select the dropdown menu and click an owner for the forked repository.
+1. By default, forks are named the same as their upstream repositories. Optionally, to further distinguish your fork, in the "Repository name" field, type a name.
+1. Optionally, in the "Description" field, type a description of your fork.
 {%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
-6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
-   ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
+1. Optionally, select **Copy the DEFAULT branch only**.
+
+   For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. If you do not select this option, all branches will be copied into the new fork.
 {%- endif %}
-7. Click **Create fork**.
-   ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+1. Click **Create fork**.
 
 
 {% note %}
diff --git a/content/get-started/quickstart/hello-world.md b/content/get-started/quickstart/hello-world.md
index ab93c04145b3..29c47788ef22 100644
--- a/content/get-started/quickstart/hello-world.md
+++ b/content/get-started/quickstart/hello-world.md
@@ -34,13 +34,11 @@ A repository is usually used to organize a single project. Repositories can cont
 Your `hello-world` repository can be a place where you store ideas, resources, or even share and discuss things with others.
 
 {% data reusables.repositories.create_new %}
-1. In the **Repository name** box, enter `hello-world`.
-2. In the **Description** box, write a short description.
-3. Select **Add a README file**.
-4. Select whether your repository will be **Public** or **Private**.
-5. Click **Create repository**.
-
-   ![Create a hello world repository](/assets/images/help/repository/hello-world-repo.png)
+1. In the "Repository name" box, type `hello-world`.
+1. In the "Description" box, type a short description.
+1. Select whether your repository will be **Public** or **Private**.
+1. Select **Add a README file**.
+1. Click **Create repository**.
 
 ## Creating a branch
 
@@ -77,7 +75,7 @@ Here at {% data variables.product.product_name %}, our developers, writers, and
 1. Type a branch name, `readme-edits`, into the text box.
 1. Click **Create branch: readme-edits from main**.
 
-![Branch menu](/assets/images/help/repository/new-branch.png)
+   ![Screenshot of the branch dropdown for a repository. "Create branch: readme-edits from 'main'" is outlined in dark orange.](/assets/images/help/repository/new-branch.png)
 
 Now you have two branches, `main` and `readme-edits`. Right now, they look exactly the same. Next you'll add changes to the new branch.
 
@@ -88,12 +86,10 @@ When you created a new branch in the previous step, {% data variables.product.pr
 You can make and save changes to the files in your repository. On {% data variables.product.product_name %}, saved changes are called commits. Each commit has an associated commit message, which is a description explaining why a particular change was made. Commit messages capture the history of your changes so that other contributors can understand what you’ve done and why.
 
 1. Under the `readme-edits` branch you created, click the _README.md_ file.
-2. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
-3. In the editor, write a bit about yourself. Try using different Markdown elements.
-4. In the **Commit changes** box, write a commit message that describes your changes.
-5. Click **Commit changes**.
-
-   ![Commit example](/assets/images/help/repository/first-commit.png)
+1. To edit the file, click {% octicon "pencil" aria-label="Edit file" %}.
+1. In the editor, write a bit about yourself. Try using different Markdown elements.
+1. In the "Commit changes" box, write a commit message that describes your changes.
+1. Click **Commit changes**.
 
 These changes will be made only to the README file on your `readme-edits` branch, so now this branch contains content that's different from `main`.
 
diff --git a/content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
index 38ad7ac982ae..df8eecf7878e 100644
--- a/content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
+++ b/content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
@@ -45,6 +45,5 @@ You can see a combined overview of teams and people with access to your reposito
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
 {% data reusables.repositories.accessing-repository-people %}
-4. Click **Export CSV**.
-  ![People tab in the repository sidebar](/assets/images/help/repository/export-repository-permissions.png)
+1. Above the list of people, click **Export CSV**.
 {% endif %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
index d9a1c26d9c27..9442250807d3 100644
--- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
+++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
@@ -52,8 +52,7 @@ You can filter files in a pull request by file extension type, such as `.html` o
 
    {% endnote %}
 
-   ![Screenshot of filter changed files search box and file tree emphasized](/assets/images/help/repository/file-tree.png)
-
+   ![Screenshot of the "Files changed" tab of a pull request. In the left sidebar, the file tree is outlined in dark orange.](/assets/images/help/repository/file-tree.png)
 1. To filter by file path, enter part or all of the file path in the **Filter changed files** search box. Alternatively, use the file filter dropdown. For more information, see "[Using the file filter dropdown](#using-the-file-filter-dropdown)."
 
 {% endif %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 3bc9e86fe231..585db79c9a8a 100644
--- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -25,16 +25,18 @@ permissions: People with write access for a forked repository can sync the fork
 
 {% ifversion syncing-fork-web-ui %}
 1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
-2. Select the **Sync fork** dropdown.
-    !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png)
-3. Review the details about the commits from the upstream repository, then click **Update branch**.
+1. Above the list of files, select the **Sync fork** dropdown menu.
+
+    ![Screenshot of the main page of a fork. A dropdown menu, labeled with a sync icon and "Sync fork," is outlined in dark orange.](/assets/images/help/repository/sync-fork-dropdown.png)
+1. Review the details about the commits from the upstream repository, then click **Update branch**.
     ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png)
 {% else %}
 1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
-2. Select the **Fetch upstream** dropdown.
-    !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png)
-3. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
-    !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %}
+1. Above the list of files, select the **Fetch upstream** dropdown menu.
+
+    ![Screenshot of the main page of a fork. A dropdown menu, labeled with a sync icon and "Fetch upstream," is outlined in dark orange.](/assets/images/help/repository/fetch-upstream-drop-down.png)
+1. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
+{% endif %}
 
 If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
 
@@ -87,7 +89,7 @@ Before you can sync your fork with an upstream repository, you must configure a
   >  delete mode 100644 README
   >  create mode 100644 README.md
   ```
-  
+
   If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation.
   ```shell
   $ git merge upstream/main
@@ -95,7 +97,7 @@ Before you can sync your fork with an upstream repository, you must configure a
   > Fast-forward
   >  README.md                 |    5 +++--
   >  1 file changed, 3 insertions(+), 2 deletions(-)
-  ``` 
+  ```
   If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts)."
 
 {% tip %}
diff --git a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index 7bb823897c3c..615d312f58c6 100644
--- a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -61,7 +61,7 @@ You can use the file tree to navigate between files in a commit.
 
   {% endnote %}
 
-  ![Screenshot of filter changed files search box and file tree emphasized](/assets/images/help/repository/file-tree.png)
+  ![Screenshot of the "Files changed" tab of a pull request. In the left sidebar, the file tree is outlined in dark orange.](/assets/images/help/repository/file-tree.png)
 1. To filter by file path, enter part or all of the file path in the **Filter changed files** search box.
 
 {% endif %}
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md
index b9a745db44c4..39d97e972903 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md
@@ -20,8 +20,9 @@ shortTitle: Configure commit merging
 {% ifversion ghes < 3.6  %}
  ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png){% endif %}
 {% ifversion default-merge-squash-commit-message %}
-1. Optionally, under **Allow merge commits**, use the dropdown to choose the format of the commit message presented to contributors when merging. The default message includes the pull request number and title. For example, `Merge pull request #123 from patch-1`. You can also choose to use just the pull request title, or the pull request title and description. 
-![Screenshot of emphasized default commit message dropdown](/assets/images/help/repository/default-commit-message-dropdown.png)
+1. Optionally, under **Allow merge commits**, select the dropdown menu, then click the format of the commit message presented to contributors when merging.
+
+   The default message includes the pull request number and title. For example, `Merge pull request #123 from patch-1`. You can also choose to use just the pull request title, or the pull request title and description.
 {% endif %}
 
 If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
index f5185933f293..76048e0ca005 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -20,14 +20,15 @@ shortTitle: Configure commit squashing
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. The default commit message presented to contributors when merging is the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. {% ifversion ghes = 3.6 %} To always use the title of the pull request regardless of the number of commits in the pull request select **Default to PR title for squash merge commits**.{% endif %}{% ifversion default-merge-squash-commit-message %} 
+1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. The default commit message presented to contributors when merging is the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. {% ifversion ghes = 3.6 %} To always use the title of the pull request regardless of the number of commits in the pull request select **Default to PR title for squash merge commits**.{% endif %}{% ifversion default-merge-squash-commit-message %}
  ![Pull request squashed commits](/assets/images/help/repository/allow-squash-merging.png){% endif %}{% ifversion ghes = 3.6 %}
  ![Screenshot of Pull Request settings with allow merge commits checkbox emphasized](/assets/images/help/repository/allow-squash-merging-no-dropdown.png){% endif %}
 {% ifversion ghes < 3.6  %}
  ![Pull request squashed commits](/assets/images/enterprise/3.5/repository/pr-merge-squash.png){% endif %}
 {% ifversion default-merge-squash-commit-message %}
-1. Optionally, under **Allow squash merging**, use the dropdown to choose the format of the default squash commit message presented to contributors when merging. The default message uses the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. You can also choose to use just the pull request title, the pull request title and commit details, or the pull request title and description.
-![Screenshot of emphasized default squash message dropdown](/assets/images/help/repository/default-squash-message-dropdown.png)
+1. Optionally, under **Allow squash merging**, select the dropdown menu, then click the format of the default squash commit message presented to contributors when merging.
+
+   The default message uses the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. You can also choose to use just the pull request title, the pull request title and commit details, or the pull request title and description.
 {% endif %}
 
 If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index 07120fce2289..65779ff9b5be 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -127,7 +127,6 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
 1. To the right of the branch protection rule you want to edit, click **Edit**.
 1. Make your desired changes to the branch protection rule.
 1. Click **Save changes**.
-  ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png)
 
 ## Deleting a branch protection rule
 
@@ -135,4 +134,3 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}
 1. To the right of the branch protection rule you want to delete, click **Delete**.
-    ![Delete button](/assets/images/help/repository/delete-branch-protection-rule.png)
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 cbff45472fad..56f29ee4d0fc 100644
--- a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -84,11 +84,13 @@ For more information, see "[AUTOTITLE](/desktop/contributing-and-collaborating-u
 An empty repository contains no files. It's often made if you don't initialize the repository with a README when creating it.
 
 {% data reusables.repositories.navigate-to-repo %}
-2. To clone your repository using the command line using HTTPS, under "Quick setup", click {% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.
-   ![Empty repository clone URL button](/assets/images/help/repository/empty-https-url-clone-button.png)
+1. To clone your repository using the command line using HTTPS, under "Quick setup", click {% octicon "copy" aria-label="Copy to clipboard" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "copy" aria-label="Copy to clipboard" %}.
 
-   Alternatively, to clone your repository in Desktop, click {% octicon "desktop-download" aria-label="The desktop download button" %} **Set up in Desktop** and follow the prompts to complete the clone.
-   ![Empty repository clone desktop button](/assets/images/help/repository/empty-desktop-clone-button.png)
+   ![Screenshot of the quick setup instructions for an empty repository. To the right of the HTTPS URL for the repository, a copy icon is outlined in dark orange.](/assets/images/help/repository/empty-https-url-clone-button.png)
+
+   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.
+
+   ![Screenshot of the quick setup instructions for an empty repository. A button, labeled with a download icon and "Set up in Desktop," is outlined in dark orange.](/assets/images/help/repository/empty-desktop-clone-button.png)
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.change-current-directory-clone %}
diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md
index b53513d3a4c0..c7eb7fdc03d8 100644
--- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md
+++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md
@@ -18,6 +18,5 @@ Repository administrators can change the anonymous Git read access setting for a
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Next to "Enable anonymous Git read access", click **Enable**.
-!["Enabled" button under "Anonymous Git read access"](/assets/images/help/repository/enable-git-read-access-for-a-repo.png)
-4. Review the changes. To confirm, type in the name of the repository and click **I understand, enable anonymous Git read access.**
+1. In the "Danger zone" section, next to "Enable anonymous Git read access", click **Enable**.
+1. Review the changes. To confirm, type in the name of the repository and click **I understand, enable anonymous Git read access.**
diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md
index 3d09c901b786..8ccc56a78670 100644
--- a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md
+++ b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md
@@ -27,8 +27,9 @@ You can also see deployment information on the "Conversation" tab of a pull requ
 ## Viewing the deployments dashboard
 
 {% data reusables.repositories.navigate-to-repo %}
-2. To the right of the list of files, click **Environments**.
-![Environments on the right of the repository page](/assets/images/help/repository/environments.png)
+1. In the right sidebar, click **Environments**.
+
+   ![Screenshot of the main page of a repository. In the right sidebar, "Environments" is outlined in dark orange.](/assets/images/help/actions/environments.png)
 
 ## Further reading
  - "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
diff --git a/content/repositories/working-with-files/managing-files/navigating-files-with-the-new-code-view.md b/content/repositories/working-with-files/managing-files/navigating-files-with-the-new-code-view.md
index 69b9c7a07ad5..9beeb0f4420b 100644
--- a/content/repositories/working-with-files/managing-files/navigating-files-with-the-new-code-view.md
+++ b/content/repositories/working-with-files/managing-files/navigating-files-with-the-new-code-view.md
@@ -30,17 +30,17 @@ To provide feedback on the new code view beta, see the [discussion forum](https:
 The new file tree view is a panel that displays a repository's directories and files within an easily navigable tree. You can move between directories and files quickly and understand the context for each item you view.
 
 1. Select a repository, then click a directory or file within that repository to open the file tree view.
-1. To search for a specific directory or file, in the file tree view, click the {% octicon "filter" aria-label="The filter icon" %} **Jump to file** search bar, then type the directory or file name and select the directory or file from the results. You can view the file path for a directory or file below each search result.
+1. To search for a specific directory or file, in the file tree view, click the {% octicon "filter" aria-hidden="true" %} **Jump to file** search bar, then type the directory or file name and select the directory or file from the results. You can view the file path for a directory or file below each search result.
 
   ![Screenshot of the file tree view for a repository. A search bar, labeled "Jump to file", is outlined in dark orange.](/assets/images/help/repository/file-tree-view-jump-to-file.png)
 
      - To search within the repository using the {% data variables.product.prodname_dotcom %} search bar, click {% octicon "search" aria-label="The search icon" %} in the file tree view.
 
-1. To switch between branches, select the {% octicon "git-branch" aria-label="The branch icon" %} branch dropdown menu, then click the desired branch from the results. To view all branches for a repository, click **View all branches**.
+1. To switch between branches, select the {% octicon "git-branch" aria-hidden="true" %} branch dropdown menu, then click the desired branch from the results. To view all branches for a repository, click **View all branches**.
 
   ![Screenshot of the file tree view for a repository. A dropdown menu for switching branches is expanded and outlined in dark orange.](/assets/images/help/repository/file-tree-view-branch-dropdown.png)
 
-1. To switch between tags, select the {% octicon "git-branch" aria-label="The branch icon" %} branch dropdown menu, click the **Tags** tab, then click the desired tag from the results. To view all tags for a repository, click **View all tags**.
+1. To switch between tags, select the {% octicon "git-branch" aria-hidden="true" %} branch dropdown menu, click the **Tags** tab, then click the desired tag from the results. To view all tags for a repository, click **View all tags**.
 
   ![Screenshot of the file tree view. A dropdown menu for switching branches is expanded, and a tab, labeled "Tags", is outlined in dark orange.](/assets/images/help/repository/file-tree-view-branch-dropdown-tags.png)
 
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 615e6169cb5b..98dfacee7959 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
@@ -57,9 +57,9 @@ You can jump to a function or method's definition within the same repository by
 
 ## Finding all references of a function or method
 
-You can find all references for a function or method within the same repository by clicking the function or method call in a file, then clicking the **References** tab.
+You can find all references for a function or method within the same repository by clicking the function or method call in a file.
 
-![Find all references tab](/assets/images/help/repository/find-all-references-tab.png)
+![Screenshot of the function window. A section, titled "3 References," is outlined in dark orange.](/assets/images/help/repository/find-all-references-tab.png)
 
 ## Precise and search-based navigation
 
diff --git a/content/repositories/working-with-files/using-files/viewing-a-file.md b/content/repositories/working-with-files/using-files/viewing-a-file.md
index ea88316e23e3..9a6c758bbbbd 100644
--- a/content/repositories/working-with-files/using-files/viewing-a-file.md
+++ b/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -29,9 +29,9 @@ With the raw view, you can view or copy the raw content of a file without any st
 
 ## Viewing the line-by-line revision history for a file
 
-With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
+Within the blame view, you can view the line-by-line revision history for an entire file. To view the revision history of a single line within a file, click {% octicon "versions" aria-label="View blame prior to this change" %}. Each time you click {% octicon "versions" aria-label="View blame prior to this change" %}, you'll see the previous revision information for that line, including who committed the change and when.
 
-![Git blame view](/assets/images/help/repository/git_blame.png)
+![Screenshot of the "Blame" view of a file. To the right of a commit message, the versions icon is outlined in dark orange.](/assets/images/help/repository/git_blame.png)
 
 In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
 
diff --git a/data/reusables/actions/enable-debug-logging.md b/data/reusables/actions/enable-debug-logging.md
index 6dea252aef6a..289dbc08f7c8 100644
--- a/data/reusables/actions/enable-debug-logging.md
+++ b/data/reusables/actions/enable-debug-logging.md
@@ -1,4 +1,4 @@
 {% ifversion debug-reruns %}
 1. Optionally, to enable runner diagnostic logging and step debug logging for the re-run, select **Enable debug logging**.
-   ![Enable debug logging](/assets/images/help/repository/enable-debug-logging.png)
+1. Click **Re-run jobs**.
 {% endif %}
diff --git a/data/reusables/files/preview_change.md b/data/reusables/files/preview_change.md
index 7bee4a156a2e..fdd0d7a6d258 100644
--- a/data/reusables/files/preview_change.md
+++ b/data/reusables/files/preview_change.md
@@ -1,2 +1,3 @@
-1. Above the new content, click **Preview changes**.
-![File preview button](/assets/images/help/repository/edit-readme-preview-changes.png)
+1. Above the new content, click **Preview**.
+
+   ![Screenshot of a file in edit mode. Above the file's contents, a tab labeled "Preview" is outlined in dark orange.](/assets/images/help/repository/edit-readme-preview-changes.png)
diff --git a/data/reusables/repositories/copy-clone-url.md b/data/reusables/repositories/copy-clone-url.md
index 6890b61434cd..72670ee13138 100644
--- a/data/reusables/repositories/copy-clone-url.md
+++ b/data/reusables/repositories/copy-clone-url.md
@@ -1,8 +1,9 @@
-1. Above the list of files, click {% octicon "download" aria-label="The download icon" %} **Code**.
+1. Above the list of files, click {% octicon "download" aria-hidden="true" %} **Code**.
   !["Code" button](/assets/images/help/repository/code-button.png)
 1. Copy the URL for the repository.
 
-   - To clone the repository using HTTPS, under "HTTPS", click {% octicon "clippy" aria-label="The clipboard icon" %}. 
-   - To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. 
-   - To clone a repository using {% data variables.product.prodname_cli %}, click **{% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.
-  ![The clipboard icon for copying the URL to clone a repository with GitHub CLI](/assets/images/help/repository/https-url-clone-cli.png)
+   - To clone the repository using HTTPS, under "HTTPS", click {% octicon "clippy" aria-label="Copy to clipboard" %}.
+   - To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="Copy to clipboard" %}.
+   - To clone a repository using {% data variables.product.prodname_cli %}, click **{% data variables.product.prodname_cli %}**, then click {% octicon "copy" aria-label="Copy to clipboard" %}.
+
+      ![Screenshot of the "Code" dropdown menu. To the right of the HTTPS URL for the repository, a copy icon is outlined in dark orange.](/assets/images/help/repository/https-url-clone-cli.png)
diff --git a/data/reusables/repositories/initialize-with-readme.md b/data/reusables/repositories/initialize-with-readme.md
index 450dae8219f0..8a2367b8df89 100644
--- a/data/reusables/repositories/initialize-with-readme.md
+++ b/data/reusables/repositories/initialize-with-readme.md
@@ -1,2 +1 @@
 1. Select **Initialize this repository with a README**.
-  ![Initialize this repository with a README checkbox](/assets/images/help/repository/initialize-with-readme.png)
diff --git a/data/reusables/repositories/open-with-github-desktop.md b/data/reusables/repositories/open-with-github-desktop.md
index 4999f66798fc..b3174571d425 100644
--- a/data/reusables/repositories/open-with-github-desktop.md
+++ b/data/reusables/repositories/open-with-github-desktop.md
@@ -1,4 +1,5 @@
-1. Above the list of files, click {% octicon "download" aria-label="The download icon" %} **Code**.
+1. Above the list of files, click {% octicon "download" aria-hidden="true" %} **Code**.
   !["Code" button](/assets/images/help/repository/code-button.png)
-1. Click {% octicon "desktop-download" aria-label="The GitHub Desktop download icon" %} **Open with {% data variables.product.prodname_desktop %}** to clone and open the repository with {% data variables.product.prodname_desktop %}.
-  !["Open with {% data variables.product.prodname_desktop %}" button](/assets/images/help/repository/open-with-desktop.png)
+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 %}**.
+
+  ![Screenshot of the "Code" dropdown for a repository. A button, labeled "Open with GitHub Desktop" is outlined in dark orange.](/assets/images/help/repository/open-with-desktop.png)