diff --git a/docker-hub/images/repo-overview.png b/docker-hub/images/repo-overview.png
index b9f5c26fa2..b6d1d9c3c2 100644
Binary files a/docker-hub/images/repo-overview.png and b/docker-hub/images/repo-overview.png differ
diff --git a/docker-hub/images/repo-tags-list.png b/docker-hub/images/repo-tags-list.png
index aefbee08b3..06a1a50e11 100644
Binary files a/docker-hub/images/repo-tags-list.png and b/docker-hub/images/repo-tags-list.png differ
diff --git a/docker-hub/images/repos-create.png b/docker-hub/images/repos-create.png
index a5e4ba5e47..4301613b83 100644
Binary files a/docker-hub/images/repos-create.png and b/docker-hub/images/repos-create.png differ
diff --git a/docker-hub/repos.md b/docker-hub/repos.md
index b44a6ae526..b547f589bd 100644
--- a/docker-hub/repos.md
+++ b/docker-hub/repos.md
@@ -128,6 +128,23 @@ To view individual tags, click on the **Tags** tab.
 
 ![Manage Repo Tags](images/repo-tags-list.png)
 
+An image is considered stale if there has been no push/pull activity for more
+than 1 month, i.e.:
+
+* It has not been pulled for more than 1 month
+* And it has not been pushed for more than 1 month
+
+A multi-architecture image is considered stale if all single-architecture images
+part of its manifest are stale.
+
+To delete a tag, select the corresponding checkbox and select **Delete** from the
+**Action** drop-down list.
+
+> **Note**
+>
+> Only a user with administrative access (owner or team member with Admin
+> permission) over the repository can delete tags.
+
 Select a tag's digest to view details.
 
 ![View Tag](images/repo-image-layers.png)
@@ -185,20 +202,21 @@ workflows, and do not share Docker IDs with the members in the Team plan.
 
 To create a new service account for your Team account:
 
- 1. Create a new Docker ID.
- 2. Create a [team](orgs.md#create-a-team) in your organization and grant it read-only access to your private repositories.
- 3. Add the new Docker ID to your [organization](orgs.md#working-with-organizations).
- 4. Add the new Docker ID  to the [team](orgs.md#add-a-member-to-a-team) you created earlier.
- 5. Create a new [personal access token (PAT)](/access-tokens.md) from the user account and use it for CI.
+1. Create a new Docker ID.
+2. Create a [team](orgs.md#create-a-team) in your organization and grant it read-only access to your private repositories.
+3. Add the new Docker ID to your [organization](orgs.md#working-with-organizations).
+4. Add the new Docker ID  to the [team](orgs.md#add-a-member-to-a-team) you created earlier.
+5. Create a new [personal access token (PAT)](/access-tokens.md) from the user account and use it for CI.
 
 To create a new service account for your Pro account:
 
- 1. Create a new Docker ID.
- 2. Click **Repositories** from the main menu.
- 3. Select a repository from the list and go to the **Collaborators** tab.
- 4. Add the new Docker ID as a collaborator.
- 5. Create a new [personal access token (PAT)](/access-tokens.md) from the user account and use it for CI.
+1. Create a new Docker ID.
+2. Click **Repositories** from the main menu.
+3. Select a repository from the list and go to the **Collaborators** tab.
+4. Add the new Docker ID as a collaborator.
+5. Create a new [personal access token (PAT)](/access-tokens.md) from the user account and use it for CI.
 
- > **Note**
- >
- > If you want a read-only PAT just for your open source repos, or to access official images and other public images, you do not have to grant any access permissions to the new Docker ID.
+> **Note**
+>
+> If you want a read-only PAT just for your open source repos, or to access
+> official images and other public images, you do not have to grant any access permissions to the new Docker ID.