Make some more images in the images/help/repository directory (D-O) accessible (3/4) (#35897)

Co-authored-by: Sam Browning <106113886+sabrowning1@users.noreply.github.com>

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

@@ -47,11 +47,9 @@ You can send an invitation to collaborate in your repository directly to someone
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4%}
-{% data reusables.repositories.click-collaborators-teams %}
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" %} Collaborators**.
-1. Click **Invite a collaborator**.
+1. Click **Add people**.
-  !["Invite a collaborator" button](/assets/images/help/repository/invite-a-collaborator-button.png)
 2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field-user.png)
 3. Click **Add NAME to REPOSITORY**.
     ![Button to add collaborator](/assets/images/help/repository/add-collaborator-user-repo.png)
 {% else %}

content/actions/creating-actions/creating-a-javascript-action.md

@@ -267,9 +267,9 @@ jobs:
         run: echo "The time was {% raw %}${{ steps.hello.outputs.time }}{% endraw %}"
 ```
 
-From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**.
 
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
+Click **Hello world action step**, and you should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input printed in the log. To see the timestamp, click **Get the output time**.
 
 ## Template repositories for creating JavaScript actions
 

content/actions/managing-workflow-runs/canceling-a-workflow.md

@@ -20,7 +20,6 @@ versions:
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel.
-![Name of workflow run](/assets/images/help/repository/in-progress-run.png)
 1. In the upper-right corner of the workflow, click **Cancel workflow**.
 ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite-updated.png)
 

content/communities/moderating-comments-and-conversations/locking-conversations.md

@@ -24,14 +24,10 @@ While a conversation is locked, only [people with write access](/organizations/m
 To search for locked conversations in a repository that is not archived, you can use the search qualifiers `is:locked` and `archived:false`. Conversations are automatically locked in archived repositories. For more information, see "[AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)."
 
 1. Optionally, write a comment explaining why you're locking the conversation.
-2. In the right margin of the issue or pull request, or above the comment box on the commit page, click **Lock conversation**.
+1. In the right sidebar of the issue or pull request, or above the comment box on the commit page, click **Lock conversation**.
-![Lock conversation link](/assets/images/help/repository/lock-conversation.png)
+1. Optionally, select the **Choose a reason** dropdown menu, then click a reason for locking the conversation.
-3. Optionally, choose a reason for locking the conversation.
+1. Read the information about locking conversations and click **Lock conversation on this issue**, **Lock conversation on this pull request**, or **Lock conversation on this commit**.
-![Reason for locking a conversation menu](/assets/images/help/repository/locking-conversation-reason-menu.png)
+1. When you're ready to unlock the conversation, in the right sidebar of the issue or pull request, or above the comment box on the commit page, click **Unlock conversation**.
-4. Read the information about locking conversations and click **Lock conversation on this issue**, **Lock conversation on this pull request**, or **Lock conversation on this commit**.
-![Confirm lock with a reason dialog box](/assets/images/help/repository/lock-conversation-confirm-with-reason.png)
-5. When you're ready to unlock the conversation, click **Unlock conversation**.
-![Unlock conversation link](/assets/images/help/repository/unlock-conversation.png)
 
 ## Further reading
 
@@ -40,5 +36,4 @@ To search for locked conversations in a repository that is not archived, you can
 - "[AUTOTITLE](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"{% ifversion fpt or ghec %}
 - "[AUTOTITLE](/communities/maintaining-your-safety-on-github)"
 - "[AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
-- "[AUTOTITLE](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)"
 {% endif %}

content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md

@@ -22,7 +22,7 @@ shortTitle: Manage comments
 
 If a comment is off-topic, outdated, or resolved, you may want to hide a comment to keep a discussion focused or make a pull request easier to navigate and review. Hidden comments are minimized but people with read access to the repository can expand them.
 
-![Minimized comment](/assets/images/help/repository/hidden-comment.png)
+![Screenshot of a hidden comment. The only visible content is "This comment has been minimized", with a button to show the comment.](/assets/images/help/repository/hidden-comment.png)
 
 1. Navigate to the comment you'd like to hide.
 2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Hide**.
@@ -39,9 +39,8 @@ 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.
-2. In the upper-right corner of the comment, click **{% octicon "fold" aria-label="The fold icon" %} Show comment**.
+1. On the right side of the comment, click **{% octicon "fold" aria-hidden="true" %} Show comment**.
-   ![Show comment text](/assets/images/help/repository/hidden-comment-show.png)
+1. On the right side of the expanded comment, select the {% octicon "kebab-horizontal" aria-label="Show options" %} dropdown menu, then click **Unhide**.
-3. On the right side of the expanded comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Unhide**.
    ![The horizontal kebab icon and comment moderation menu showing the edit, unhide, delete options](/assets/images/help/repository/comment-menu-hidden.png)
 
 ## Editing a comment

content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md

@@ -24,18 +24,16 @@ Open source licenses enable others to freely use, change, and distribute the pro
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field, type *LICENSE* or *LICENSE.md* (with all caps).
+1. In the file name field, type *LICENSE* or *LICENSE.md* (with all caps).
-4. To the right of the file name field, click **Choose a license template**.
+1. Under the file name, click **Choose a license template**.
-  ![Choose a license template button](/assets/images/help/repository/license-tool.png)
+
-5. On the left side of the page, under "Add a license to your project," review the available licenses, then select a license from the list.
+   ![Screenshot of the new file form, with "LICENSE" entered in the file name field. A button, labeled "Choose a license template," is outlined in dark orange.](/assets/images/help/repository/license-tool.png)
-  ![List of available licenses](/assets/images/help/repository/license-tool-picker.png)
+1. On the left side of the page, under "Add a license to your project," review the available licenses, then select a license from the list.
-6. Click **Review and submit**.
+1. Click **Review and submit**.
-  ![Review and submit button](/assets/images/help/repository/license-review-tool.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.choose-commit-email %}
-10. Click **Commit new file**.
+1. Click **Commit new file**.
-  ![Commit license to branch](/assets/images/help/repository/license-submit-tool.png)
 
 {% endif %}
 
@@ -50,8 +48,7 @@ Open source licenses enable others to freely use, change, and distribute the pro
 {% data reusables.files.choose-commit-email %}
 7. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is `main`, you should choose to create a new branch for your commit and then create a pull request. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)".
 ![Commit branch options](/assets/images/help/repository/choose-commit-branch.png)
-8. Click **Commit new file**.
+1. Click **Commit new file**.
-  ![Commit license to branch](/assets/images/help/repository/license-submit-tool.png)
 
 {% endif %}
 

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md

@@ -25,22 +25,20 @@ shortTitle: Configure
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. In the "Features" section, under "Issues," click **Set up templates**. You may need to enable "Issues" and refresh the page before you can see the button.
+1. In the "Features" section, under **Issues**, click **Set up templates**. You may need to enable **Issues** and refresh the page before you can see the button.
-4. Use the Add template dropdown menu, and click on the type of template you'd like to create.
+1. Use the **Add template** dropdown menu, and click on the type of template you'd like to create.
 
    ![Screenshot of the "Add template" dropdown menu expanded to show the standard "Bug report" and "Feature request" templates. In addition, the "Custom template" is listed.](/assets/images/help/repository/add-template-drop-down-menu.png)
-5. To preview or edit the template before committing it to the repository, click **Preview and edit**.
+1. To preview or edit the template before committing it to the repository, click **Preview and edit**.
 ![Preview and edit button](/assets/images/help/repository/preview-and-edit-button.png)
-6. To edit the template, click {% octicon "pencil" aria-label="The edit icon" %}, and type in the fields to edit their contents.
+1. To edit the template, click {% octicon "pencil" aria-label="Edit template" %}, and type in the fields to edit their contents.
-![Issue template edit button](/assets/images/help/repository/issue-template-edit-button.png)
+
-7. To automatically set a default issue title, assign the issue to people with read access to the repository, or apply labels to issues raised from the template, use the fields under "Optional additional information." You can also add these details in the issue template with `title`, `labels`, or `assignees` in a YAML frontmatter format.
+   ![Screenshot of the preview of an issue template. To the right of the template name, a pencil icon is outlined in dark orange.](/assets/images/help/repository/issue-template-edit-button.png)
-8. When you're finished editing and previewing your template, click **Propose changes** in the upper right corner of the page.
+1. To automatically set a default issue title, assign the issue to people with read access to the repository, or apply labels to issues raised from the template, use the fields under "Optional additional information." You can also add these details in the issue template with `title`, `labels`, or `assignees` in a YAML frontmatter format.
-![Propose changes button](/assets/images/help/repository/propose-changes-button.png)
+1. When you're finished editing and previewing your template, click **Propose changes** in the upper right corner of the page.
-9. Enter a commit message describing your changes.
+1. In the "Commit message" field, type a commit message describing your changes.
-![Issue template commit message field](/assets/images/help/repository/issue-template-commit-message-field.png)
+1. Below the commit message fields, select whether to commit your template directly to the default branch, or to create a new branch and open a pull request. For more information about pull requests, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
-10. Below the commit message fields, decide whether to commit your template directly to the default branch, or to create a new branch and open a pull request. For more information about pull requests, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+1. Click **Commit changes**. Once these changes are merged into the default branch, the template will be available for contributors to use when they open new issues in the repository.
-![Issue template commit to main or open pull request choice](/assets/images/help/repository/issue-template-commit-to-master-or-open-pull-request.png)
-11. Click **Commit changes**. Once these changes are merged into the default branch, the template will be available for contributors to use when they open new issues in the repository.
 
 {% ifversion fpt or ghec %}
 

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md

@@ -56,13 +56,9 @@ assignees: octocat
 {% data reusables.files.add-file %}
 3. In the file name field:
     -  To make your issue template visible in the repository's root directory, type the name of your *issue_template*. For example, `issue_template.md`.
-  ![New issue template name in root directory](/assets/images/help/repository/issue-template-file-name.png)
     - To make your issue template visible in the repository's `docs` directory, type *docs/* followed by the name of your *issue_template*. For example, `docs/issue_template.md`,
-  ![New issue template in docs directory](/assets/images/help/repository/issue-template-file-name-docs.png)
     - To store your file in a hidden directory, type *.github/* followed by the name of your *issue_template*. For example, `.github/issue_template.md`.
-  ![New issue template in hidden directory](/assets/images/help/repository/issue-template-hidden-directory.png)
     - To create multiple issue templates and use the `template` query parameter to specify a template to fill the issue body, type *.github/ISSUE_TEMPLATE/*, then the name of your issue template. For example, `.github/ISSUE_TEMPLATE/issue_template.md`. You can also store multiple issue templates in an `ISSUE_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue)."
-  ![New multiple issue template in hidden directory](/assets/images/help/repository/issue-template-multiple-hidden-directory.png)
 4. In the body of the new file, add your issue template. This could include:
     - YAML frontmatter
     - Expected behavior and actual behavior

content/issues/tracking-your-work-with-issues/creating-an-issue.md

@@ -85,8 +85,6 @@ You can open a new issue from a comment in an issue or pull request. When you op
 
 You can open a new issue from a specific line or lines of code in a file or pull request. When you open an issue from code, the issue contains a snippet showing the line or range of code you chose. You can only open an issue in the same repository where the code is stored.
 
-![Code snippet rendered in an issue opened from code](/assets/images/help/repository/issue-opened-from-code.png)
-
 {% 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.

content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md

@@ -25,8 +25,6 @@ You can use this information to help off-board people, gather data for complianc
 Organizations that use {% data variables.product.prodname_ghe_cloud %} can also export a CSV list of people who have access to a repository. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository).
 {% endif %}
 
-![Access management overview](/assets/images/help/repository/manage-access-overview.png)
-
 ## Viewing people with access to your repository
 
 You can see a combined overview of teams and people with access to your repository in your repository settings. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#about-access-management-for-repositories)."

content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md

@@ -66,7 +66,6 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
      ![Restrict who can dismiss pull request reviews checkbox]{% ifversion integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %}
 {% ifversion last-pusher-require-approval %}
    - Optionally, to require someone other than the last person to push to a branch to approve a pull request prior to merging, select **Require approval from someone other than the last pusher**. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging)."
-     ![Require review from someone other than the last pusher](/assets/images/help/repository/last-pusher-review-required.png)
 {% endif %}
 1. Optionally, enable required status checks. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
    - Select **Require status checks to pass before merging**.
@@ -95,10 +94,9 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
    ![Require successful deployment option](/assets/images/help/repository/require-successful-deployment.png)
 {%- endif %}
 {% ifversion lock-branch %}
-1. Optionally, select **Lock branch** to make branch read-only.
+1. Optionally, make the branch read-only.
-![Screenshot of the checkbox to lock a branch](/assets/images/help/repository/lock-branch.png)
+   - Select **Lock branch**.
    - Optionally, to allow fork syncing, select **Allow fork syncing**.
-![Screenshot of the checkbox to allow fork syncing](/assets/images/help/repository/lock-branch-forksync.png)
 {%- endif %}
 1. Optionally, select {% ifversion bypass-branch-protections %}**Do not allow bypassing the above settings**{% else %}**Apply the rules above to administrators**{% endif %}.
 1. Optionally,{% ifversion fpt or ghec %} in public repositories owned by a {% data variables.product.prodname_free_user %} organization and in all repositories owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions.

content/repositories/creating-and-managing-repositories/creating-a-new-repository.md

@@ -35,7 +35,6 @@ topics:
 2. Optionally, to create a repository with the directory structure and files of an existing repository, use the **Choose a template** drop-down and select a template repository. You'll see template repositories that are owned by you and organizations you're a member of or that you've used before. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)."
   ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png)
 3. Optionally, if you chose to use a template, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
-    ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png)
 3. In the Owner drop-down, select the account you wish to create the repository on.
    ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png)
 {% data reusables.repositories.repo-name %}

content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md

@@ -52,6 +52,5 @@ For more information about forks, see "[AUTOTITLE](/pull-requests/collaborating-
 {% data reusables.repositories.repo-name %}
 {% data reusables.repositories.choose-repo-visibility %}
 1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
-  ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png)
 {% data reusables.repositories.select-marketplace-apps %}
 1. Click **Create repository from template**.

content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md

@@ -25,4 +25,3 @@ If you use an external LFS server (configured in your *.lfsconfig*), those LFS f
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 3. Under "Archives", select or deselect **Include {% data variables.large_files.product_name_short %} objects in archives**.
-  ![Checkbox to include {% data variables.large_files.product_name_short %} objects in archives](/assets/images/help/repository/include-git-lfs-objects-checkbox.png)

content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md

@@ -25,4 +25,3 @@ You can also enable code review limits for an organization. If you enable limits
 1. Under **Access**, click **{% octicon "comment-discussion" aria-hidden="true" %} Moderation options**.
 1. Under **Moderation options**, click **Code review limits**.
 1. Select or deselect **Limit to users explicitly granted read or higher access**.
-![Limit review in repository](/assets/images/help/repository/limit-reviews-in-repository.png)

content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md

@@ -26,7 +26,7 @@ This overview can help you audit access to your repository, onboard or off-board
 
 For more information about repository roles, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository)" and "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-![Access management overview](/assets/images/help/repository/manage-access-overview.png)
+![Screenshot of the "Manage access" page for a repository.](/assets/images/help/repository/manage-access-overview.png)
 
 ## Filtering the list of teams and people
 
@@ -38,7 +38,6 @@ For more information about repository roles, see "[AUTOTITLE](/account-and-profi
 {% data reusables.repositories.navigate-to-manage-access %}
 {% endif %}
 1. Under "Manage access", in the search field, start typing the name of the team or person you'd like to find. Optionally, use the dropdown menus to filter your search.
-  ![Search field for filtering list of teams or people with access](/assets/images/help/repository/manage-access-filter.png)
 
 ## Changing permissions for a team or person
 
@@ -49,8 +48,7 @@ For more information about repository roles, see "[AUTOTITLE](/account-and-profi
 {% else %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% endif %}
-4. Under "Manage access", find the team or person whose role you'd like to change, then select the Role drop-down and click a new role.
+1. Under "Manage access", next to the team or person whose role you'd like to change, select the **Role** dropdown menu, and click a new role.
-  ![Using the "Role" drop-down to select new permissions for a team or person](/assets/images/help/repository/manage-access-role-drop-down.png)
 
 ## Inviting a team or person
 
@@ -62,10 +60,8 @@ For more information about repository roles, see "[AUTOTITLE](/account-and-profi
 {% data reusables.repositories.navigate-to-manage-access %}
 {% endif %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of the team or person to invite, then click a name in the list of matches.
+1. In the search field, start typing the name of the team or person to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png)
+1. Under "Choose a role", select the repository role to grant to the team or person, then click **Add NAME to REPOSITORY**.
-6. Under "Choose a role", select the repository role to grant to the team or person, then click **Add NAME to REPOSITORY**.
-  ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
 ## Removing access for a team or person
 
@@ -76,8 +72,7 @@ For more information about repository roles, see "[AUTOTITLE](/account-and-profi
 {% else %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% endif %}
-4. Under "Manage access", find the team or person whose access you'd like to remove, then click {% octicon "trash" aria-label="The trash icon" %}.
+1. Under "Manage access", next to the team or person whose access you'd like to remove, click **Remove**.
-  ![trash icon for removing access](/assets/images/help/repository/manage-access-remove.png)
 
 ## Further reading
 

content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md

@@ -27,11 +27,7 @@ The push policy also blocks the Git command: `git push --mirror`. This is a pote
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Pushes", select **Limit how many branches and tags can be updated in a single push**.
+1. Under "Pushes", select **Limit how many branches and tags can be updated in a single push**.
-
+1. After "Up to", type the number of branches and tags you want to limit in a single push. Lower numbers are more restrictive of which pushes are allowed, and higher numbers are less restrictive but have more potential for being destructive.
-   ![Screenshot of the limit how many branches and tags can be updated in a single push option](/assets/images/help/repository/limit-branches-and-tags-single-push.png)
-4. Enter the number of branches and tags you want to limit in a single push. Lower numbers are more restrictive of which pushes are allowed, and higher numbers are less restrictive but have more potential for being destructive.
 
    We recommend the default maximum of `5` branch or tag updates allowed in one push. The minimum value is `2`, because Git requires two branch updates to rename a branch in a single push: *delete branch* and *create branch*.
-
-   ![Screenshot of the field where you enter the number of branches and tags you want to limit](/assets/images/help/repository/set-limit-branch-tags-single-push.png)

content/repositories/working-with-files/using-files/navigating-code-on-github.md

@@ -53,7 +53,7 @@ Future releases will add *precise code navigation* for more languages, which is
 
 You can jump to a function or method's definition within the same repository by clicking the function or method call in a file.
 
-![Jump-to-definition tab](/assets/images/help/repository/jump-to-definition-tab.png)
+![Screenshot of the function window. A section, titled "Definition," is outlined in dark orange.](/assets/images/help/repository/jump-to-definition-tab.png)
 
 ## Finding all references of a function or method
 

content/repositories/working-with-files/using-files/working-with-non-code-files.md

@@ -61,20 +61,18 @@ You can visually compare images in three different modes: [2-up](#2-up), [swipe]
 
 **2-up** is the default mode; it gives you a quick glimpse of both images. In addition, if the image has changed size between versions, the actual dimension change is displayed. This should make it very apparent when things are resized, such as when assets are upgraded to higher resolutions.
 
-![2-up](/assets/images/help/repository/images-2up-view.png)
+![Screenshot of a diff for an image in 2-up mode. The image on the right is outlined in green and larger than the image on the left, which is outlined in red.](/assets/images/help/repository/images-2up-view.png)
 
 #### Swipe
 
 **Swipe** lets you view portions of your image side by side. Not sure if colors shifted between different versions? Drag the swipe slider over the area in question and compare the pixels for yourself.
 
-![Swipe](/assets/images/help/repository/images-swipe-view.png)
+![Screenshot of a diff for an image in swipe mode. A line down the center divides the image into new, outlined in green, and old, outlined in red.](/assets/images/help/repository/images-swipe-view.png)
 
 #### Onion skin
 
 **Onion Skin** really comes in handy when elements move around by small, hard to notice amounts. Did an icon shift two pixels to the left? Drag the opacity slider back a bit and notice if things move around.
 
-![Onion skin](/assets/images/help/repository/images-onion-view.gif)
-
 ## 3D File Viewer
 
 {% data variables.product.product_name %} can host and render 3D files with the *.stl* extension.

data/reusables/organizations/invite-teams-or-people.md

@@ -1,2 +1 @@
 1. To the right of "Manage access", click **Add people** or **Add teams**.
-  !["Invite teams or people" button](/assets/images/help/repository/manage-access-invite-button.png)

data/reusables/repositories/choose-line-or-range.md

@@ -1,5 +1,4 @@
-1. Choose whether to select a single line or a range:
+1. Choose whether to select a single line or a range.
+
    - To select a single line of code, click the line number to highlight the line.
-    ![File with a single line of code selected](/assets/images/help/repository/highlight-line-of-code.png)
    - To select a range of code, click the number of the first line in the range to highlight the line of code. Then, hover over the last line of the code range, press <kbd>Shift</kbd>, and click the line number to highlight the range.
-    ![File with a range of code selected](/assets/images/help/repository/highlight-range-of-code.png)

data/reusables/repositories/navigate-to-manage-access.md

@@ -1,2 +1 @@
 1. In the left sidebar, click **Manage access**.
-  !["Manage access" tab](/assets/images/help/repository/manage-access-tab.png)