feedback1

Signed-off-by: Craig <[email protected]>

Author: craig-osterhout

content/manuals/docker-hub/repos/_index.md

@@ -16,36 +16,39 @@ particular application, microservice, or project. Content in repositories is
 organized by tags, which represent different versions of the same application,
 allowing users to pull the right version when needed.
 
-## Key features and concepts
-
-- [Repository information](./manage/information.md): Each repository can include a
-  description, an overview, and categories to help users understand its purpose
-  and usage. Adding clear repository information ensures that others can find
-  your images and know how to use them.
-
-- [Access management](./manage/access.md): Docker Hub repositories offer flexible
-  access options. You can make repositories public or private and add
-  collaborators. For organizations, teams, roles, and access tokens enable
-  fine-grained access, providing security and control at scale.
-
-- [Image management](./manage/hub-images/_index.md): Repositories support
-  various types of content, including OCI artifacts, and provide robust version
-  control with tagging. You can push new images and move existing content
-  between repositories, ensuring flexibility in managing different versions and
-  types of container images.
-
-- [Webhooks](./manage/webhooks.md): Webhooks let you automate responses to repository
-  events. For instance, you can set up notifications or trigger actions in
-  external systems whenever an image is pushed or updated, helping to streamline
-  workflows.
-
-- [Automated builds](./manage/builds/_index.md): Docker Hub
-  repositories integrate with GitHub or Bitbucket for automated builds, ensuring
-  that every code change triggers an image rebuild. This feature supports
-  continuous integration and delivery, keeping images up-to-date and
-  streamlining development pipelines.
-
-- [Image security insights](./manage/vulnerability-scanning.md): Docker Hub repositories
-  provide powerful features and controls to help uncover, understand, and fix
-  issues with container images. Options for image security insights include
-  continuous Docker Scout image analysis and static vulnerability scanning.
+In this section, learn how to:
+
+- [Create](./create.md) a repository.
+- Manage a repository, including how to manage:
+
+   - [Repository information](./manage/information.md): Add descriptions,
+     overviews, and categories to help users understand the purpose and usage of
+     your repository. Clear repository information aids discoverability and
+     usability.
+
+   - [Access](./manage/access.md): Control who can access your repositories with
+     flexible options. Make repositories public or private, add collaborators,
+     and, for organizations, manage roles and teams to maintain security and
+     control.
+
+   - [Images](./manage/hub-images/_index.md): Repositories support diverse
+     content types, including OCI artifacts, and allow version control through
+     tagging. Push new images and manage existing content across repositories
+     for flexibility.
+
+   - [Image security insights](./manage/vulnerability-scanning.md): Utilize
+     continuous Docker Scout analysis and static vulnerability scanning to
+     detect, understand, and address security issues within container images.
+
+   - [Webhooks](./manage/webhooks.md): Automate responses to repository events
+     like image pushes or updates by setting up webhooks, which can trigger
+     notifications or actions in external systems, streamlining workflows.
+
+   - [Automated builds](./manage/builds/_index.md): Integrate with GitHub or
+     Bitbucket for automated builds. Every code change triggers an image
+     rebuild, supporting continuous integration and delivery.
+  
+- [Delete](./delete.md) a repository.
+- [Manage personal settings](./settings.md): For your account, you can set personal
+  settings for repositories, including default repository privacy and autobuild
+  notifications.

content/manuals/docker-hub/repos/manage/access.md

@@ -31,11 +31,10 @@ roles, teams, or organization access tokens.
 
 ### Change repository visibility
 
-When creating a repository in Docker Hub, you are given the option to set the
-repository visibility. In addition, you can set the default repository
-visibility when a repository is created in your personal repository settings.
-The following describes how to change the visibility after the repository has
-been created.
+When creating a repository in Docker Hub, you can set the repository visibility.
+In addition, you can set the default repository visibility when a repository is
+created in your personal repository settings. The following describes how to
+change the visibility after the repository has been created.
 
 To change repository visibility:
 
@@ -104,8 +103,8 @@ access.
 
 ### Configure team repository permissions
 
-You must create a team before you are able to assign in permissions. For more
-details, see [Create and manage a
+You must create a team before you are able to configure repository permissions.
+For more details, see [Create and manage a
 team](/manuals/admin/organization/manage-a-team.md).
 
 To configure team repository permissions:

content/manuals/docker-hub/repos/manage/hub-images/move.md

@@ -16,14 +16,20 @@ organized under the correct accounts or namespaces.
 
 When consolidating personal repositories, you can pull private images from the initial repository and push them into another repository owned by you. To avoid losing your private images, perform the following steps:
 
-1. Navigate to [Docker Hub](https://hub.docker.com) create a new Docker account and select a personal subscription.
-2. Using `docker login` from the CLI, sign in using your original Docker account and pull your private images.
-3. Tag your private images with your newly created Docker  username, for example:
+1. [Sign up](https://app.docker.com/signup) for a new Docker account with a personal subscription.
+2. Sign in to [Docker](https://app.docker.com/login) using your original Docker account
+3. Pull your images:
+
+   ```console
+   $ docker pull namespace1/docker101tutorial
+   ```
+
+4. Tag your private images with your newly created Docker username, for example:
 
    ```console
    $ docker tag namespace1/docker101tutorial new_namespace/docker101tutorial
    ```
-4. Using `docker login` from the CLI, sign in with your newly created Docker account, and push your newly tagged private images to your new Docker account namespace:
+5. Using `docker login` from the CLI, sign in with your newly created Docker account, and push your newly tagged private images to your new Docker account namespace:
 
    ```console
    $ docker push new_namespace/docker101tutorial

content/manuals/docker-hub/repos/manage/vulnerability-scanning.md

@@ -13,8 +13,8 @@ scanning or always up-to-date image analysis using Docker Scout.
 
 ## Docker Scout image analysis
 
-When you have an image in your Docker Hub repository after turning on Docker
-Scout image analysis, Docker Scout automatically analyzes the image.
+After turning on Docker Scout image analysis, Docker Scout automatically
+analyzes images in your Docker Hub repository.
 
 Image analysis extracts the Software Bill of Material (SBOM) and other image
 metadata, and evaluates it against vulnerability data from security advisories.

content/manuals/subscription/core-subscription/details.md

@@ -45,7 +45,7 @@ Docker Pro includes:
 - Unlimited private repositories
 - 5000 image [pulls per day](../../docker-hub/download-rate-limit.md)
 - [Auto Builds](../../docker-hub/repos/manage/builds/_index.md) with 5 concurrent builds
-- 300 [Vulnerability Scans](../../docker-hub/repos//manage/vulnerability-scanning.md)
+- 300 [Vulnerability Scans](../../docker-hub/repos/manage/vulnerability-scanning.md)
 
 For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/).