[Accessibility] Update screenshots in the images/help/package-registry directory (#35072)

Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
Co-authored-by: Jess Hosman <1183847+jhosman@users.noreply.github.com>

content/admin/packages/enabling-github-packages-with-aws.md

@@ -40,8 +40,7 @@ Ensure your AWS access key ID and secret have the following permissions:
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_site_admin_settings.packages-tab %}
 {% data reusables.package_registry.enable-enterprise-github-packages %}
-
-{% ifversion ghes %}
+{% ifversion ghes -%}
 1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details:
     - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`.
 
@@ -51,9 +50,7 @@ Ensure your AWS access key ID and secret have the following permissions:
     - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket.
 
       For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)."
-
-    ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png)
-{% endif %}
+{%- endif %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 ## Next steps

content/admin/packages/enabling-github-packages-with-azure-blob-storage.md

@@ -32,15 +32,13 @@ Before you can enable and configure {% data variables.product.prodname_registry
 {% data reusables.package_registry.enable-enterprise-github-packages %}
 1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
 
-    - You must create a storage container prior to setting the container name and connection string.
-
-  ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png)
+   You must create a storage container prior to setting the container name and connection string.
 
   {% note %}
 
-  **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account. 
+  **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
   Usage of a SAS Token or SAS URL as connection string is not currently supported.
-  
+
   {% endnote %}
 
 {% data reusables.enterprise_management_console.save-settings %}

content/admin/packages/enabling-github-packages-with-minio.md

@@ -41,16 +41,13 @@ Although MinIO does not currently appear in the user interface under "Package St
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_site_admin_settings.packages-tab %}
 {% data reusables.package_registry.enable-enterprise-github-packages %}
-
-{% ifversion ghes %}
+{% ifversion ghes -%}
 1. Under "Packages Storage", select **Amazon S3**.
 1. Enter your MinIO storage bucket's details in the AWS storage settings.
     - **AWS Service URL:** The hosting URL for your MinIO bucket.
     - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}.
     - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket.
-
-    ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png)
-{% endif %}
+{%- endif %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 ## Next steps

content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md

@@ -34,10 +34,8 @@ If you have admin permissions to a package that's scoped to a personal account,
 If your package is private or internal and scoped to an organization, then you can only give access to other organization members or teams.
 
 {% data reusables.package_registry.package-settings-option %}
-1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a package that is scoped to a personal account.
-  ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
-1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level.
-  {% ifversion packages-delete-with-github-token-api %}![Permission access levels to give to repositories](/assets/images/help/package-registry/package-access-control-options.png){% else %}![Permission access levels to give to repositories](/assets/images/help/package-registry/container-access-control-options.png){% endif %}
+{% data reusables.package_registry.package-settings-manage-access-people %} Teams cannot be given access to a package that is scoped to a personal account.
+{% data reusables.package_registry.package-settings-user-access %}
 
 The selected users will automatically be given access and don't need to accept an invitation first.
 
@@ -49,10 +47,8 @@ If your package is private or internal and scoped to an organization, then you c
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access.
-  ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
-1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level.
-  {% ifversion packages-delete-with-github-token-api %}![Container access options](/assets/images/help/package-registry/package-access-control-options.png){% else %}![Container access options](/assets/images/help/package-registry/container-access-control-options.png){% endif %}
+{% data reusables.package_registry.package-settings-manage-access-people %} You can also enter a team name from the organization to give all team members access.
+{% data reusables.package_registry.package-settings-user-access %}
 
 The selected users or teams will automatically be given access and don't need to accept an invitation first.
 
@@ -67,8 +63,7 @@ Once a repository is synced, you can't access the package's granular access sett
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-2. Under "Repository source", select **Inherit access from repository (recommended)**.
-  ![Inherit repo access checkbox](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+1. Under "Manage access" or "Inherited access", select the **Inherit access from repository (recommended)** checkbox.
 
 ## Ensuring workflow access to your package
 
@@ -78,19 +73,16 @@ The specified repository does not need to be the repository where the source cod
 
 {% note %}
 
-**Note:** Syncing your package with a repository through the **Actions access** menu option is different than connecting your package to a repository. For more information about linking a repository to your package, see "[AUTOTITLE](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+**Note:** Syncing your package with a repository {% data variables.package_registry.package-settings-actions-access-menu %} is different than connecting your package to a repository. For more information about linking a repository to your package, see "[AUTOTITLE](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
 
 {% endnote %}
 
-### {% data variables.product.prodname_actions %} access for packages scoped to personal accounts 
+### {% data variables.product.prodname_actions %} access for packages scoped to personal accounts
 
 {% data reusables.package_registry.package-settings-option %}
-1. In the left sidebar, click **Actions access**.
-  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
-2. To ensure your workflow has access to your package, you must add the repository where the workflow is stored. Click **Add repository** and search for the repository you want to add.
-   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
-3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your package.
-  {% ifversion packages-delete-with-github-token-api %}![Permission access levels to give to repositories](/assets/images/help/package-registry/package-access-control-options.png){% else %}![Permission access levels to give to repositories](/assets/images/help/package-registry/container-access-control-options.png){% endif %}
+{% data reusables.package_registry.package-settings-actions-access %}
+1. To ensure your workflow has access to your package, you must add the repository where the workflow is stored. {% data reusables.package_registry.package-settings-add-repo %}
+{% data reusables.package_registry.package-settings-actions-access-role-repo %}
 
 To further customize access to your package, see "[Configuring access to packages for your personal account](#configuring-access-to-packages-for-your-personal-account)."
 
@@ -98,12 +90,9 @@ To further customize access to your package, see "[Configuring access to package
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-1. In the left sidebar, click **Actions access**.
-  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
-2. Click **Add repository** and search for the repository you want to add.
-   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
-3. Using the "role" drop-down menu, select the default access level that you'd like repository members to have to your package. Outside collaborators will not be included.
-  {% ifversion packages-delete-with-github-token-api %}![Permission access levels to give to repositories](/assets/images/help/package-registry/package-access-control-options.png){% else %}![Permission access levels to give to repositories](/assets/images/help/package-registry/container-access-control-options.png){% endif %}
+{% data reusables.package_registry.package-settings-actions-access %}
+1. {% data reusables.package_registry.package-settings-add-repo %}
+{% data reusables.package_registry.package-settings-actions-access-role-repo %}
 
 To further customize access to your package, see "[Configuring access to packages for an organization](#configuring-access-to-packages-for-an-organization)."
 {% endif %}
@@ -119,23 +108,19 @@ The specified repository does not need to be the repository where the source cod
 
 Once you've selected the package you're interested in sharing with codespaces in a repository, you can grant that repo access.
 
-1. In the right sidebar, click **Package settings**.
-
-   !["Package settings" option in right menu](/assets/images/help/package-registry/package-settings.png)
+{% data reusables.package_registry.package-settings-option %}
 
 2. Under "Manage Codespaces access", click **Add repository**.
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
+   ![Screenshot of the "Manage Codespaces access" section of the package settings page. The "Add repository" button is highlighted with an orange outline.](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
 
 3. Search for the repository you want to add.
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-search.png)
-
 4. Repeat for any additional repositories you would like to allow access.
 
-5. If the codespaces for a repository no longer need access to a package, you can remove access.
+5. If the codespaces for a repository no longer need access to a package, you can remove access. Click **{% octicon "trash" aria-label="remove access to repository from this package" %}**.
 
-   !["Remove repository" button](/assets/images/help/package-registry/manage-codespaces-access-item.png)
+   ![Screenshot of the "Manage Codespaces access" section of the package settings page. The trash icon is highlighted with an orange outline.](/assets/images/help/package-registry/manage-codespaces-access-item.png)
 
 {% endif %}
 ## Configuring visibility of packages for your personal account
@@ -145,15 +130,16 @@ When you first publish a package that is scoped to your personal account, the de
 A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
 
 {% data reusables.package_registry.package-settings-option %}
-5. Under "Danger Zone", choose a visibility setting:
-    - To make the package visible to anyone, click **Make public**.
-    {% warning %}
+1. At the bottom of the page, under "Danger Zone", click **Change visibility**.
+1. Select a visibility setting:
+   - To make the package visible to anyone, select **Public**.
+     {% warning %}
 
-    **Warning:** Once you make a package public, you cannot make it private again.
+     **Warning:** Once you make a package public, you cannot make it private again.
 
-    {% endwarning %}
-    - To make the package visible to a custom selection of people, click **Make private**.
-  ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
+     {% endwarning %}
+   - To make the package visible to a custom selection of people, select **Private**.
+1. To confirm, type the name of the package, then click **I understand the consequences, change package visibility**.
 
 ## Package creation visibility for organization members
 
@@ -161,8 +147,8 @@ For registries that support granular permissions, you can choose the visibility
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-4. On the left, click **Packages**.
-6. Under "Package Creation", choose whether you want to enable the creation of public, private, or internal packages.
+1. On the left, click **Packages**.
+1. Under "Package Creation", choose whether you want to enable the creation of public, private, or internal packages.
     - To enable organization members to create public packages, click **Public**.
     - To enable organization members to create private packages that are only visible to other organization members, click **Private**. You can further customize the visibility of private packages.
     - To enable organization members to create internal packages that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the packages will be visible to all enterprise members.
@@ -175,12 +161,12 @@ A public package can be accessed anonymously without authentication. Once you ma
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. Under "Danger Zone", choose a visibility setting:
-    - To make the package visible to anyone, click **Make public**.
-    {% warning %}
+1. At the bottom of the page, under "Danger Zone", click **Change visibility** and choose a visibility setting:
+    - To make the package visible to anyone, click **Public**.
+     {% warning %}
 
-    **Warning:** Once you make a package public, you cannot make it private again.
+     **Warning:** Once you make a package public, you cannot make it private again.
 
-    {% endwarning %}
-    - To make the package visible to a custom selection of people, click **Make private**.
-  ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
+     {% endwarning %}
+    - To make the package visible to a custom selection of people in your organization, click **Private**.{% ifversion not fpt %}
+    - To make the package visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the packages will be visible to all enterprise members.{% endif %}

content/packages/learn-github-packages/connecting-a-repository-to-a-package.md

@@ -17,13 +17,13 @@ When you publish a package that is scoped to a personal account or an organizati
 ## Connecting a repository to a user-scoped package on {% data variables.product.prodname_dotcom %}
 
 {% data reusables.package_registry.package-settings-from-user-level %}
-
+1. Search for and then click the name of the package that you want to manage.
 {% data reusables.package_registry.repository_connection_steps %}
 
 ## Connecting a repository to an organization-scoped package on {% data variables.product.prodname_dotcom %}
 
 {% data reusables.package_registry.package-settings-from-org-level %}
-
+1. Search for and then click the name of the package that you want to manage.
 {% data reusables.package_registry.repository_connection_steps %}
 
 {% ifversion fpt or ghec or ghes > 3.4 %}

content/packages/learn-github-packages/deleting-and-restoring-a-package.md

@@ -80,12 +80,10 @@ To delete a version of a {% ifversion packages-registries-v2 %}repository-scoped
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
-{% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+1. Search for and then click the name of the package that you want to manage.
+{% data reusables.package_registry.package-settings-manage-versions-menu %}
+{% data reusables.package_registry.package-settings-delete-versions %}
+1. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
 
 {% ifversion fpt or ghec or ghes %}
 ### Deleting a version of a {% ifversion packages-registries-v2 %}repository-scoped{% endif %} package with GraphQL
@@ -121,11 +119,10 @@ To review who can delete a package version, see "[Required permissions](#require
 
 {% data reusables.package_registry.package-settings-from-user-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
+{% data reusables.package_registry.package-settings-manage-versions-menu %}
+{% data reusables.package_registry.package-settings-delete-versions %}
+1. In the confirmation box, type the name of the package to confirm you want to delete the chosen version of it.
+1. Click **I understand the consequences, delete this version**.
 
 ### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
 
@@ -136,11 +133,10 @@ To review who can delete a package version, see "[Required permissions to delete
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
+{% data reusables.package_registry.package-settings-manage-versions-menu %}
+{% data reusables.package_registry.package-settings-delete-versions %}
+1. In the confirmation box, type the name of the package to confirm you want to delete the chosen version of it.
+1. Click **I understand the consequences, delete this version**.
 {% endif %}
 
 ## Deleting an entire package
@@ -152,23 +148,20 @@ To delete an entire repository-scoped package, you must have admin permissions t
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-4. Under "Danger Zone", click **Delete this package**.
-5. To confirm, review the confirmation message, enter your package name, and click **I understand, delete this package.**
-  ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+1. At the bottom of the page, under "Danger Zone", click **Delete this package**.
+1. To confirm, review the confirmation message, enter your package name, and click **I understand, delete this package.**
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes %}
 ### Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}
 
 To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
 
 {% data reusables.package_registry.package-settings-from-user-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Options**.
-  !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png)
-6. Under "Danger zone", click **Delete this package**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-button.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
-  ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png)
+{% data reusables.package_registry.package-settings-options-menu %}
+1. At the bottom of the page, under "Danger zone", click **Delete this package**.
+1. In the confirmation box, type the name of the package to confirm you want to delete it.
+1. Click **I understand the consequences, delete this package**.
 
 ### Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}
 
@@ -176,12 +169,10 @@ To review who can delete a package, see "[Required permissions](#required-permis
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Options**.
-  !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png)
-6. Under "Danger zone", click **Delete this package**.
-  ![Delete package button](/assets/images/help/package-registry/delete-container-package-button.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png)
+{% data reusables.package_registry.package-settings-options-menu %}
+1. At the bottom of the page, under "Danger zone", click **Delete this package**.
+1. In the confirmation box, type the name of the package to confirm you want to delete it.
+1. Click **I understand the consequences, delete this package**.
 {% endif %}
 
 ## Restoring packages
@@ -215,24 +206,20 @@ To review who can restore a package in an organization, see "[Required permissio
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-3. On the left, click **Packages**.
-4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
-  ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
-5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
-  ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
+1. On the left, click **Packages**.
+1. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
+1. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
 
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec or ghes %}
 
 ### Restoring a user-account scoped package
 
 You can restore a deleted package through your personal account settings, if the package was in one of your repositories or scoped to your personal account. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
 
 {% data reusables.user-settings.access_settings %}
-2. On the left, click **Packages**.
-4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
-  ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
-5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
-  ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
+1. In the left sidebar, click **Packages**.
+1. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
+1. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
 
 {% endif %}
 
@@ -241,11 +228,8 @@ You can restore a deleted package through your personal account settings, if the
 You can restore a package version from your package's landing page. To review who can restore a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
 
 1. Navigate to your package's landing page.
-2. On the right, click **Package settings**.
-2. On the left, click **Manage versions**.
-3. On the top right, use the "Versions" drop-down menu and select **Deleted**.
-  ![Versions drop-down menu showing the deleted option](/assets/images/help/package-registry/versions-drop-down-menu.png)
-4. Next to the deleted package version you want to restore, click **Restore**.
-  ![Restore option next to a deleted package version](/assets/images/help/package-registry/restore-package-version.png)
-5. To confirm, click **I understand the consequences, restore this version.**
-  ![Confirm package version restoration](/assets/images/help/package-registry/confirm-package-version-restoration.png)
+{% data reusables.package_registry.package-settings-option %}
+{% data reusables.package_registry.package-settings-manage-versions-menu %}
+{% data reusables.package_registry.package-settings-versions-deleted-dropdown %}
+1. Next to the deleted package version you want to restore, click **Restore**.
+1. To confirm, click **I understand the consequences, restore this version.**

content/packages/learn-github-packages/introduction-to-github-packages.md

@@ -29,16 +29,6 @@ You can integrate {% data variables.product.prodname_registry %} with {% ifversi
 
 {% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[AUTOTITLE](/packages/working-with-a-github-packages-registry)."
 
-{% ifversion fpt or ghec %}
-
-![Diagram showing packages support for the Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
-
-{% else %}
-
-![Diagram showing packages support for the Docker registry, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
-
-{% endif %}
-
 You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/packages/learn-github-packages/viewing-packages)."
 
 {% ifversion ghes %}

content/packages/learn-github-packages/viewing-packages.md

@@ -55,11 +55,9 @@ You can find and view a package located in the repositories of an organization y
 
 ## Viewing your packages
 
-You can find and view any package you've published across all organizations and repositories. 
+You can find and view any package you've published across all organizations and repositories.
 
-{% data reusables.profile.access_profile %}
-2. On the top of the profile page, in the main navigation, click **Packages**.
-  ![Project tab](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.package-settings-from-user-level %}
 {% data reusables.package_registry.navigate-to-packages %}
 
 ## Further reading

content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md

@@ -26,7 +26,7 @@ You can extend the CI and CD capabilities of your repository by publishing or in
 {% ifversion packages-registries-v2 %}
 ### Authenticating to package registries with granular permissions
 
-Some {% data variables.product.prodname_registry %} registries support granular permissions. This means you can choose to allow packages to be scoped to a user or an organization, or linked to a repository. For the list of registries that support granular permissions, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)." 
+Some {% data variables.product.prodname_registry %} registries support granular permissions. This means you can choose to allow packages to be scoped to a user or an organization, or linked to a repository. For the list of registries that support granular permissions, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)."
 
 {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %}
 
@@ -498,17 +498,14 @@ For more information about the `GITHUB_TOKEN`, see "[AUTOTITLE](/actions/securit
 Using the `GITHUB_TOKEN`, instead of a {% data variables.product.pat_v1 %} with the `repo` scope, increases the security of your repository as you don't need to use a long-lived {% data variables.product.pat_generic %} that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#using-secrets)."
 
 1. Navigate to your package landing page.
-1. In the left sidebar, click **Actions access**.
-  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
-1. To ensure your package has access to your workflow, you must add the repository where the workflow is stored to your package. Click **Add repository** and search for the repository you want to add.
-   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+{% data reusables.package_registry.package-settings-actions-access %}
+1. To ensure your package has access to your workflow, you must add the repository where the workflow is stored to your package. {% data reusables.package_registry.package-settings-add-repo %}
   {% note %}
 
-  **Note:** Adding a repository to your package through the **Actions access** menu option is different than connecting your package to a repository. For more information, see "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[AUTOTITLE](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+  **Note:** Adding a repository to your package {% data variables.package_registry.package-settings-actions-access-menu %} is different than connecting your package to a repository. For more information, see "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[AUTOTITLE](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
 
   {% endnote %}
-1. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your package.
-  {% ifversion packages-delete-with-github-token-api %}![Permission access levels to give to repositories](/assets/images/help/package-registry/package-access-control-options.png){% else %}![Permission access levels to give to repositories](/assets/images/help/package-registry/container-access-control-options.png){% endif %}
+1. Optionally, use {% data variables.package_registry.package-settings-actions-access-role-dropdown %}
 1. Open your workflow file. On the line where you log in to the registry, replace your {% data variables.product.pat_generic %} with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
 
 For example, this workflow publishes a Docker image to the {% data variables.product.prodname_container_registry %} and uses {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.

content/packages/working-with-a-github-packages-registry/index.md

@@ -25,8 +25,3 @@ children:
 ---
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
-{% ifversion fpt or ghec %}
-![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
-{% else %}
-![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
-{% endif %}

content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md

@@ -39,15 +39,9 @@ topics:
 
 After a Docker image has been migrated to the {% data variables.product.prodname_container_registry %}, you'll see the following changes to the details for the package.
 
-- The icon will be the {% data variables.product.prodname_container_registry %} logo instead of the Docker logo.
+- The package icon will be the {% data variables.product.prodname_container_registry %} logo (a {% octicon "container" aria-label="The container icon" %} icon) instead of the Docker logo.
 - The domain in the pull URL will be {% data variables.product.prodname_container_registry_namespace %} instead of {% data variables.product.prodname_docker_registry_namespace %}.
 
-{% ifversion fpt or ghec %}
-
-![Screenshot of a Docker image migrated to the {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png)
-
-{% endif %}
-
 {% data reusables.package_registry.container-registry-migration-namespaces %}
 
 {% ifversion fpt or ghec %}

data/reusables/package_registry/enable-enterprise-github-packages.md

@@ -1,4 +1,3 @@
 {% ifversion ghes %}
-1. Under "GitHub Packages", select **Enable GitHub Packages**.
-  ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png)
+1. Under "GitHub Packages", select the **Enable GitHub Packages** checkbox.
 {% endif %}

data/reusables/package_registry/navigate-to-packages.md

@@ -1,2 +1 @@
-1. Click the name of the package that you want to view.
-![Package name](/assets/images/help/package-registry/package-name.png)
+1. Search for and then click the name of the package that you want to view.

data/reusables/package_registry/package-settings-actions-access-role-repo.md

@@ -0,0 +1 @@
+1. Use {% data variables.package_registry.package-settings-actions-access-role-dropdown %}

data/reusables/package_registry/package-settings-actions-access.md

@@ -0,0 +1,3 @@
+{% ifversion ghes or ghae -%}
+1. In the left sidebar, click **Actions access**.
+{%- endif %}

data/reusables/package_registry/package-settings-add-repo.md

@@ -0,0 +1,2 @@
+{% ifversion fpt or ghec %}Under "Manage Actions access", c{% else %}C{% endif %}lick **Add repository** and search for the repository you want to add.
+   ![Screenshot of the "Manage Actions access" section of the package settings page. The "Add repository" button is highlighted with an orange outline.](/assets/images/help/package-registry/add-repository-button.png)

data/reusables/package_registry/package-settings-delete-versions.md

@@ -0,0 +1,5 @@
+1. In the list of packages, find the version of the package that you want to delete.
+   * If your package is a container, to the right of the package version click {% octicon "kebab-horizontal" aria-label="" %}, then select **Delete version** from the dropdown menu.
+   ![Screenshot of a package version with a dropdown menu button, labeled with a kebab icon. The "Delete version" link in the menu is highlighted with an orange outline.](/assets/images/help/package-registry/delete-container-package-version.png)
+   * For types of packages other than containers, to the right of the package version click **Delete**.
+   ![Screenshot of a package version with a "Delete" button. The button is highlighted with an orange outline.](/assets/images/help/package-registry/delete-noncontainer-package-version.png)

data/reusables/package_registry/package-settings-from-org-level.md

@@ -1,7 +1,3 @@
 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization.
-2. Under your organization name, click **Packages**.
-  {% ifversion fpt or ghes or ghec %}
-  ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png)
-  {% else %}
-  ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages.png)
-  {% endif %}
+2. Under your organization name, click the {% octicon "package" aria-label="" %} **Packages** tab.
+  ![Screenshot of @octo-org's profile page. The "Packages" tab is highlighted with an orange outline.](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png)

data/reusables/package_registry/package-settings-from-user-level.md

@@ -2,5 +2,4 @@
 2. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Your profile**.
 
    ![Screenshot of the dropdown menu under @octocat's profile picture. "Your profile" is outlined in dark orange.](/assets/images/help/profile/top_right_avatar.png)
-3. On your profile page, in the top right, click **Packages**.
-  ![Packages option on profile page](/assets/images/help/package-registry/packages-from-user-profile.png)
+3. On your profile page, in the header, click the {% octicon "package" aria-label="" %} **Packages** tab.

data/reusables/package_registry/package-settings-manage-access-people.md

@@ -0,0 +1 @@
+1. Under "Manage access" or "Inherited access", click **Invite teams or people** and enter the name, username, or email of the person you want to give access.

data/reusables/package_registry/package-settings-manage-versions-menu.md

@@ -0,0 +1,18 @@
+{% ifversion fpt or ghec %}
+1. Under the "Recent Versions" list of packages, click **View and manage all versions**.
+   ![Screenshot of a package's "Recent Versions" section. Underneath, the "View and manage all versions" link is highlighted with an orange outline.](/assets/images/help/package-registry/packages-recent-versions-manage-link.png)
+{% elsif ghes %}
+1. Navigate to where you can manage versions for your type of package.
+   * **If your package is a container**, under the "Recent Versions" section, click **View and manage all versions**.
+     ![Screenshot of a package's "Recent Versions" section. Underneath, the "View and manage all versions" link is highlighted with an orange outline.](/assets/images/help/package-registry/packages-recent-versions-manage-link.png)
+   * **For types of packages other than containers**:
+     1. On the right-hand side, click **{% octicon "gear" aria-label="" %} Package settings**.
+     ![Screenshot of a package's landing page. In the lower right corner, "Package settings" is highlighted with an orange outline.](/assets/images/help/package-registry/package-settings.png)
+     1. On the left click **Manage versions**.
+     ![Screenshot of a package's "Manage versions" menu. In the lower right corner, "Manage versions" is highlighted with an orange outline.](/assets/images/help/package-registry/packages-settings-manage-versions-menu.png)
+{% elsif ghae %}
+1. On the right-hand side, click **{% octicon "gear" aria-label="" %} Package settings**.
+   ![Screenshot of a package's landing page. In the lower right corner, "Package settings" is highlighted with an orange outline.](/assets/images/help/package-registry/package-settings.png)
+1. On the left click **Manage versions**.
+   ![Screenshot of a package's "Manage versions" menu. In the lower right corner, "Manage versions" is highlighted with an orange outline.](/assets/images/help/package-registry/packages-settings-manage-versions-menu.png)
+{% endif %}

data/reusables/package_registry/package-settings-options-menu.md

@@ -0,0 +1,4 @@
+{% ifversion ghes or ghae %}
+1. On the left click **Options**.
+   ![Screenshot of a package's "Options" menu. In the lower right corner, "Options" is highlighted with an orange outline.](/assets/images/help/package-registry/packages-settings-options-menu.png)
+{% endif %}

data/reusables/package_registry/package-settings-user-access.md

@@ -0,0 +1 @@
+1. Next to the username or team name, use the **Role** drop-down menu to select a desired permission level.

data/reusables/package_registry/package-settings-versions-deleted-dropdown.md

@@ -0,0 +1,2 @@
+1. At the top right corner of the list of package versions, use the **Select versions view** dropdown and select **Deleted**.
+  ![Screenshot of a list of package versions. The "Deleted" selection in the versions view is highlighted with an orange outline.](/assets/images/help/package-registry/versions-drop-down-menu.png)

data/reusables/package_registry/packages-from-code-tab.md

@@ -1,6 +1,2 @@
-1. To the right of the list of files, click **Packages**.
-  {% ifversion fpt or ghec %}
-  ![Packages link on repo overview page](/assets/images/help/package-registry/packages-link.png)
-  {% else %}
-  ![Packages link on repo overview page](/assets/images/help/package-registry/packages-from-repo.png)
-  {% endif %}
+1. In the right sidebar of your repository, click **Packages**.
+  ![Screenshot of the sidebar of a repository page. The "Packages" section is outlined in orange.](/assets/images/help/package-registry/packages-from-repo.png)

data/reusables/package_registry/repository_connection_steps.md

@@ -1,5 +1,2 @@
 1. Under your package versions, click **Connect repository**.
-  ![Connect a repository button on packages landing page](/assets/images/help/package-registry/connect-repository.png)
-
-1. Select a repository, then click **Connect repository**.
-  ![Connect a repository button in repository selection pop-up window](/assets/images/help/package-registry/select_a_repo.png)
+1. Select a repository to link to the package, then click **Connect repository**.

data/reusables/package_registry/visibility-and-access-permissions.md

@@ -1,13 +1,13 @@
 If a package belongs to a registry that supports granular permissions, anyone with admin permissions to the package can set the package to private or public. Public packages allow anonymous access and can be pulled without authentication or signing in via the CLI. For the list of registries that support granular permissions, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)."
 
-Anyone with admin permissions to the package can also grant access permissions for the package that are separate from the permissions set at the organization and repository levels. 
+Anyone with admin permissions to the package can also grant access permissions for the package that are separate from the permissions set at the organization and repository levels.
 
 When you publish a package, you automatically get admin permissions to the package. If you publish a package to an organization, anyone with the `owner` role in the organization also gets admin permissions to the package.
 
 For packages scoped to a personal account, you can give any person an access role. For packages scoped to an organization, you can give any person or team in the organization an access role.
 
 {% ifversion packages-delete-with-github-token-api %}
-If you are using a {% data variables.product.prodname_actions %} workflow to manage your container images, you can grant an access role to the repository the workflow is stored in by using the **Actions access** option in the package's settings. For more information, see "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+If you are using a {% data variables.product.prodname_actions %} workflow to manage your packages, you can grant an access role to the repository the workflow is stored in {% data variables.package_registry.package-settings-actions-access-menu %}. For more information, see "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
 {% endif %}
 
 | Permission | Access description |

data/variables/package_registry.yml

@@ -0,0 +1,5 @@
+# sentence fragments
+package-settings-actions-access-menu: >-
+  {% ifversion ghes or ghae %}through the **Actions access** menu option{% else %}by using the **Add Repository** button under "Manage Actions access" in the package's settings{% endif %}
+package-settings-actions-access-role-dropdown: >-
+  the **Role** drop-down menu to select the default access level that you'd like the repository to have to your package.