Make images accessible in the images/help/repository directory (P-Z) (1/4) (#35958)

Co-authored-by: Jules <19994093+jules-p@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

@@ -43,20 +43,19 @@ You can send an invitation to collaborate in your repository directly to someone
 
 {% endif %}
 
-1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)".{% endif %}
+1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)."{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4%}
 1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" %} Collaborators**.
 1. Click **Add people**.
-2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
-3. Click **Add NAME to REPOSITORY**.
+1. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
+1. Click **Add NAME to REPOSITORY**.
     ![Button to add collaborator](/assets/images/help/repository/add-collaborator-user-repo.png)
 {% else %}
-5. In the left sidebar, click **Collaborators**.
-![Repository settings sidebar with Collaborators highlighted](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
-6. Under "Collaborators", start typing the collaborator's username.
-7. Select the collaborator's username from the drop-down menu.
+1. In the left sidebar, click **Collaborators**.
+1. Under "Collaborators", start typing the collaborator's username.
+1. Select the collaborator's username from the dropdown menu.
    ![Collaborator list drop-down menu](/assets/images/help/repository/repo-settings-collab-autofill.png)
 8. Click **Add collaborator**.
    !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png)

content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md

@@ -38,30 +38,18 @@ For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-w
 {% ifversion fpt or ghec %}
 ### Viewing job execution time
 
-To identify how long a job took to run, you can view its execution time. For example:
-
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
-
-For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)."
+To identify how long a job took to run, you can view its execution time. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)."
 {% endif %}
 
 ### Viewing workflow run history
 
-You can view the status of each job and step in a workflow. For example:
-
-   ![Name of workflow run](/assets/images/help/repository/run-name.png)
-
-For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+You can view the status of each job and step in a workflow. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
 
 ## Troubleshooting your workflows
 
 ### Using workflow run logs
 
-Each workflow run generates activity logs that you can view, search, and download. For example:
-
-   ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
-
-For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)."
+Each workflow run generates activity logs that you can view, search, and download. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)."
 
 ### Enabling debug logging
 

content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md

@@ -18,9 +18,8 @@ Billable job execution minutes are only shown for jobs run on private repositori
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-label="The stopwatch icon" %} Usage**.
-
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+1. Under the job summary, you can view the job's execution time.
+1. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-hidden="true" %} Usage**.
 
    {% note %}
 

content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md

@@ -86,7 +86,7 @@ You may notice some repositories have a "Used by" section in the sidebar of the
 
 The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
 
-!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png)
+![Screenshot of the "Used by" section for a repository. To the right of the "Used by" header is "13.4m." Under the header are 8 avatars and "+13,435,819."](/assets/images/help/repository/used-by-section.png)
 
 Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
 

content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md

@@ -57,9 +57,8 @@ Users in India can contact GitHub's Grievance Officer for India [here](https://s
 ## Reporting contact link abuse in the template chooser
 
 1. Navigate to the repository that contains the contact link you'd like to report.
-1. Under the repository name, click {% octicon "issue-opened" aria-label="The issues icon" %} **Issues**.
+1. Under the repository name, click {% octicon "issue-opened" aria-hidden="true" %} **Issues**.
 1. In the lower-right corner of the template chooser, click **Report abuse**.
-  ![Link to report an abuse](/assets/images/help/repository/template-chooser-report-abuse.png)
 1. Complete the contact form to tell {% data variables.contact.contact_support %} about the contact link's behavior, then click **Send request**.
 
 ## Further reading

content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md

@@ -28,6 +28,5 @@ You can also block users. For more information, see "[AUTOTITLE](/communities/ma
 ## Limiting interactions for your personal account
 
 {% data reusables.user-settings.access_settings %}
-1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**.
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation** then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
-  ![Temporary interaction limit options](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png)

content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md

@@ -33,12 +33,11 @@ Organization owners and moderators can also block users for a specific amount of
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. _For organization owners:_ In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**.
+1. _For organization owners:_ In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation**, then click **Interaction limits**.
 
    _For organization moderators:_ In the sidebar, click **Interaction limits**.
 
 {% data reusables.community.set-interaction-limit %}
-  ![Temporary interaction limit options](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
 
 ## Further reading
 - "[AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"

content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md

@@ -28,9 +28,8 @@ You can also enable activity limitations on all repositories owned by your perso
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. In the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**.
+1. In the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" %} Moderation options**, then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
-  ![Temporary interaction limit options](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
 ## Further reading
 - "[AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"

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

@@ -95,10 +95,8 @@ Your configuration file will customize the template chooser when the file is mer
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field, type `.github/ISSUE_TEMPLATE/config.yml`.
-  ![Configuration filename](/assets/images/help/repository/template-config-file-name.png)
-4. In the body of the new file, type the contents of your configuration file.
-  ![Configuration file content](/assets/images/help/repository/template-config-file-content.png)
+1. In the file name field, type `.github/ISSUE_TEMPLATE/config.yml`.
+1. In the body of the new file, type the contents of your configuration file.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}

content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md

@@ -33,13 +33,10 @@ People or teams who are mentioned in the issue will receive a notification letti
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
-3. In the list of issues, click the issue you'd like to transfer.
-4. In the right sidebar, click **Transfer issue**.
-![Button to transfer issue](/assets/images/help/repository/transfer-issue.png)
-5. Use the **Choose a repository** drop-down menu, and select the repository you want to transfer the issue to.
-![Choose a repository selection](/assets/images/help/repository/choose-a-repository.png)
-6. Click **Transfer issue**.
-![Transfer issue button](/assets/images/help/repository/transfer-issue-button.png)
+1. In the list of issues, click the issue you'd like to transfer.
+1. In the right sidebar, click **Transfer issue**.
+1. Select the **Choose a repository** dropdown menu, and click the repository you want to transfer the issue to.
+1. Click **Transfer issue**.
 
 {% endwebui %}
 

content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md

@@ -29,7 +29,6 @@ permissions: People with write access for a forked repository can sync the fork
 
     ![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.
 1. Above the list of files, select the **Fetch upstream** dropdown menu.

content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md

@@ -56,13 +56,10 @@ The new commit, message, and badge will appear on {% data variables.location.pro
 
 After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a commit on behalf of your organization by adding an `on-behalf-of:` trailer to the commit's message.
 
-1. After making your changes, at the bottom of the page, type a short, meaningful commit message that describes the changes you made.
-  ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
-
-2. In the text box below your commit message, add `on-behalf-of: @org <name@organization.com>`.
-
-  ![Commit message on-behalf-of trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png)
-4. Click **Commit changes** or **Propose changes**.
+1. Click **Commit changes...**
+1. In the "Commit message" field, type a short, meaningful commit message that describes the changes you made.
+1. In the text box below your commit message, add `on-behalf-of: @org <name@organization.com>`.
+1. Click **Commit changes** or **Propose changes**.
 
 The new commit, message, and badge will appear on {% data variables.location.product_location %}.
 

content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md

@@ -70,12 +70,10 @@ The new commit and message will appear on {% data variables.location.product_loc
 After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message.
 
 {% data reusables.pull_requests.collect-co-author-commit-git-config-info %}
-2. After making your changes together, at the bottom of the page, type a short, meaningful commit message that describes the changes you made.
-  ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
-3. In the text box below your commit message, add `Co-authored-by: name <name@example.com>` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer.
-
-  ![Commit message co-author trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-co-author-trailer.png)
-4. Click **Commit changes** or **Propose changes**.
+1. Click **Commit changes...**
+1. In the "Commit message" field, type a short, meaningful commit message that describes the changes you made.
+1. In the text box below your commit message, add `Co-authored-by: name <name@example.com>` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer.
+1. Click **Commit changes** or **Propose changes**.
 
 The new commit and message will appear on {% data variables.location.product_location %}.
 

content/repositories/archiving-a-github-repository/archiving-repositories.md

@@ -60,9 +60,7 @@ You can search for archived repositories. For more information, see "[AUTOTITLE]
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", click **Unarchive this repository**
-  ![Unarchive this repository button](/assets/images/help/repository/unarchive-repository.png)
-4. Read the warnings.
-5. Type the name of the repository you want to unarchive.
-  ![Unarchive repository warnings](/assets/images/help/repository/unarchive-repository-warnings.png)
-6. Click **I understand the consequences, unarchive this repository**.  
+1. In the "Danger Zone" section, click **Unarchive this repository**
+1. Read the warnings.
+1. In the text box, type the name of the repository you want to unarchive.
+1. Click **I understand the consequences, unarchive this repository**.

content/repositories/archiving-a-github-repository/referencing-and-citing-content.md

@@ -25,12 +25,11 @@ To make your repositories easier to reference in academic literature, you can cr
 
 {% endtip %}
 
-1. Navigate to [Zenodo](http://zenodo.org/).
-2. In the upper-left corner of the screen, click **Log in**. ![Zenodo log in button](/assets/images/help/repository/zenodo_login.png)
-3. Click **Log in with GitHub**. ![Log into Zenodo with GitHub](/assets/images/help/repository/zenodo_login_with_github.png)
-4. Review the information about access permissions, then click **Authorize application**. ![Authorize Zenodo](/assets/images/help/repository/zenodo_authorize.png)
-5. Navigate to the [Zenodo GitHub page](https://zenodo.org/account/settings/github/). ![Zenodo GitHub page](/assets/images/help/repository/zenodo_github_page.png)
-6. To the right of the name of the repository you want to archive, toggle the button from **Off** to **On** to enable it for archiving. ![Enable Zenodo archiving on repository](/assets/images/help/repository/zenodo_toggle_on.png)
+1. Navigate to the [login page](https://zenodo.org/login) for Zenodo.
+1. Click **Log in with {% data variables.product.prodname_dotcom %}**.
+1. Review the information about access permissions, then click **Authorize zenodo**.
+1. Navigate to the [Zenodo {% data variables.product.prodname_dotcom %} page](https://zenodo.org/account/settings/github/).
+1. To the right of the name of the repository you want to archive, toggle the button to **On**.
 
 Zenodo archives your repository and issues a new DOI each time you create a new {% data variables.product.product_name %} [release](/repositories/releasing-projects-on-github/about-releases). Follow the steps at "[AUTOTITLE](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)" to create a new one.
 

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

@@ -32,21 +32,20 @@ topics:
 {% endtip %}
 
 {% data reusables.repositories.create_new %}
-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**.
-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)
+1. Optionally, to create a repository with the directory structure and files of an existing repository, select the **Choose a template** dropdown menu and click 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)."
+1. 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**.
+1. In the Owner dropdown, select the account you wish to create the repository on.
+   ![Owner dropdown menu](/assets/images/help/repository/create-repository-owner.png)
 {% data reusables.repositories.repo-name %}
 {% data reusables.repositories.choose-repo-visibility %}
-6. If you're not using a template, there are a number of optional items you can pre-populate your repository with. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line)," "[AUTOTITLE](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts)."
+1. If you're not using a template, there are a number of optional items you can pre-populate your repository with. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line)," "[AUTOTITLE](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts)."
     - You can create a README, which is a document describing your project. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)."
     - You can create a *.gitignore* file, which is a set of ignore rules. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/ignoring-files)."{% ifversion fpt or ghec %}
     - You can choose to add a software license for your project. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)."{% endif %}
 {% data reusables.repositories.select-marketplace-apps %}
 {% data reusables.repositories.create-repo %}
 {% ifversion fpt or ghec %}
-9. At the bottom of the resulting Quick Setup page, under "Import code from an old repository", you can choose to import a project to your new repository. To do so, click **Import code**.
+1. At the bottom of the resulting Quick Setup page, under "Import code from an old repository", you can choose to import a project to your new repository. To do so, click **Import code**.
 {% endif %}
 
 ## Further reading

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

@@ -36,5 +36,3 @@ After you make your repository a template, anyone with access to the repository
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 1. Select **Template repository**.
-  ![Checkbox to make a repository a template](/assets/images/help/repository/template-repository-checkbox.png)
-

content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md

@@ -40,8 +40,6 @@ If a repository contains more than one README file, then the file shown is chose
 
 {% endif %}
 
-![README file on your username/username repository](/assets/images/help/repository/username-repo-with-readme.png)
-
 ## Auto-generated table of contents for README files
 
 For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %}  menu icon at the top left of the rendered page.

content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md

@@ -33,13 +33,13 @@ Files that you add to a repository via a browser are limited to {% data variable
 {% endtip %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Above the list of files, using the **Add file** drop-down, click **Upload files**.
-  !["Upload files" in the "Add file" dropdown](/assets/images/help/repository/upload-files-button.png)
-3. Drag and drop the file or folder you'd like to upload to your repository onto the file tree.
-![Drag and drop area](/assets/images/help/repository/upload-files-drag-and-drop.png)
+1. Above the list of files, select the **Add file** dropdown menu and click **Upload files**.
+
+   ![Screenshot of the main page of the repository. Above the list of a files, a button, labeled "Add file," is outlined in dark orange.](/assets/images/help/repository/upload-files-button.png)
+1. To select the files you want to upload, drag and drop the file or folder, or click **choose your files**.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
-6. Click **Commit changes**.
+1. Click **Commit changes**.
 ![Commit changes button](/assets/images/help/repository/commit-changes-button.png)
 
 ## Adding a file to a repository using the command line

content/repositories/working-with-files/using-files/viewing-a-file.md

@@ -33,9 +33,9 @@ Within the blame view, you can view the line-by-line revision history for an ent
 
 ![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.
+In a file or pull request, you can also view Git blame for a selected line or range of lines by selecting the {% octicon "kebab-horizontal" aria-label="Code line X options" %} dropdown menu, then clicking **View git blame**.
 
-![Kebab menu with option to view Git blame for a selected line](/assets/images/help/repository/view-git-blame-specific-line.png)
+![Screenshot of a file, with 8 lines selected. To the left of the first selected line, a button labeled with a kebab icon is outlined in dark orange.](/assets/images/help/repository/open-new-issue-specific-line.png)
 
 {% tip %}
 

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

@@ -301,9 +301,7 @@ The underlying map data (street names, roads, etc.) are driven by [OpenStreetMap
 
 If you're having trouble rendering GeoJSON files, ensure you have a valid GeoJSON file by running it through a [GeoJSON linter](http://geojsonlint.com/). If your points aren't appearing where you'd expect (<em>e.g.</em>, in the middle of the ocean), it's likely that the data is in a projection which is currently unsupported. Currently, {% data variables.product.product_name %} only supports the `urn:ogc:def:crs:OGC:1.3:CRS84` projection.
 
-Additionally, if your `.geojson` file is especially large (over 10 MB), it is not possible to render within the browser. If that's the case, you'll generally see a message that looks something like this:
-
-![Large file](/assets/images/help/repository/view_raw.png)
+Additionally, if your `.geojson` file is especially large (over 10 MB), it is not possible to render within the browser. If that's the case, you'll generally see a message that says we can't show files that large.
 
 It may still be possible to render the data by converting the `.geojson` file to [TopoJSON](https://github.com/mbostock/topojson), a compression format that, in some cases, can reduce filesize by up to 80%. Of course, you can always break the file into smaller chunks (such as by state or by year), and store the data as multiple files within the repository.
 

data/reusables/community/set-interaction-limit.md

@@ -1 +1 @@
-5. Under "Temporary interaction limits", to the right of the type of interaction limit you want to set, use the **Enable** drop-down menu, then click the duration you want for your interaction limit.
+1. Under "Temporary interaction limits", to the right of the type of interaction limit you want to set, select the **Enable** dropdown menu, then click the duration you want for your interaction limit.

data/reusables/files/write_commit_message.md

@@ -1,2 +1,2 @@
-1. At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see "[AUTOTITLE](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)."
-![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
+1. Click **Commit changes...**
+1. In the "Commit message" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see "[AUTOTITLE](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)."

data/reusables/repositories/navigate-to-job.md

@@ -1,3 +1 @@
 1. Under **Jobs** or in the visualization graph, click the job you want to see.
-
-   ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png)

data/reusables/repositories/navigate-to-workflow.md

@@ -1,2 +1,3 @@
 1. In the left sidebar, click the workflow you want to see.
-  ![Workflow list in left sidebar](/assets/images/help/repository/superlinter-workflow-sidebar.png)
+
+   ![Screenshot of the left sidebar of the "Actions" tab. A workflow, "CodeQL," is outlined in dark orange.](/assets/images/help/actions/superlinter-workflow-sidebar.png)

data/reusables/repositories/transfer-repository-steps.md

@@ -1,39 +1,21 @@
-{% ifversion rename-and-transfer-repository %}
+{%- ifversion rename-and-transfer-repository %}
 1. At the bottom of the page, in the "Danger Zone" section, click **Transfer**.
+1. Read the information about transferring a repository, then, under "New owner", choose how to specify the new owner.
+  - To choose one of your organizations, select **Select one of my organizations**.
 
-   ![Screenshot of the transfer button](/assets/images/help/repository/repo-transfer.png)
-
-1. Read the information about transferring a repository, then, following "New owner", select one of the options.
-   - To choose one of your organizations, select **Select one of my organizations**, then use the dropdown menu to specify an organization.
-     - Optionally, to rename the repository, enter a new name in the **Repository name** field.
+      - Select the dropdown menu and click an organization.
+      - Optionally, in the "Repository name" field, type a new name for the repository.
 
        {% note %}
 
-       **Note:** You must be an admin on the target organization to rename the repository.
+       **Note:** You must be an owner of the target organization to rename the repository.
 
        {% endnote %}
-
-       ![Screenshot of the information about repository transfer and options to select the new owner](/assets/images/help/repository/rename-repo-during-transfer.png)
-
-   - To specify an organization or username, select **Specify an organization or username**, then enter the organization name or the new owner's username.
-
-     ![Screenshot of the information about repository transfer and options to select the new owner](/assets/images/help/repository/transfer-repo-new-owner-name.png)
-
+   - To specify an organization or username, select **Specify an organization or username**, then type the organization name or the new owner's username.
 1. Read the warnings about potential loss of features depending on the new owner's {% data variables.product.prodname_dotcom %} subscription.
-
-   ![Screenshot of the warnings about transferring a repository to a person using a free product](/assets/images/help/repository/repo-transfer-free-plan-warnings.png)
-
-1. Following **Type REPOSITORY NAME to confirm.**, type the name of the repository you'd like to transfer, then click **I understand, transfer this repository**.
-
-   ![Screenshot of the transfer screen](/assets/images/help/repository/repo-transfer-overview.png)
-
-{% else %}
+1. Following **Type REPOSITORY NAME to confirm**, type the name of the repository you'd like to transfer, then click **I understand, transfer this repository**.
+{%- else %}
 1. At the bottom of the page, under "Danger Zone", click **Transfer**.
-
-   ![Screenshot of the transfer button in the danger zone section](/assets/images/help/repository/repo-transfer.png)
-
 1. Read the warnings and enter the repository name to confirm that you've done so.
-1. Type the name of the new owner and click **I understand, transfer this repo**.
-
-   ![Screenshot of the transfer screen](/assets/images/help/repository/repo-transfer-complete.png)
-{% endif %}
+1. In the text box, type the name of the new owner and click **I understand, transfer this repo**.
+{%- endif %}

data/reusables/repositories/view-failed-job-results.md

@@ -1,3 +1 @@
 1. Any failed steps are automatically expanded to display the results.
-
-   ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)

data/reusables/repositories/view-run.md

@@ -1,3 +1 @@
 1. From the list of workflow runs, click the name of the run to see the workflow run summary.
-
-   ![Name of workflow run](/assets/images/help/repository/run-name.png)