Mini freshness update (#19162)

* tier 1 updates

* update overview and refresh quickstart steps

* update description and refresh for accuracy

* fix capitalization

* optimize image and replace low res image with console example

content/docker-hub/_index.md

@@ -1,22 +1,30 @@
 ---
 description: Learn about Docker Hub features and the administrative tasks available
   in Docker Hub
-keywords: Docker, docker, docker hub, hub, overview
+keywords: Docker, docker, docker hub, hub, repositories, docker account
 title: Overview of Docker Hub
 grid:
 - title: Create a Docker ID
   description: Register and create a new Docker ID.
   icon: fingerprint
   link: /docker-id
+- title: Quickstart
+  description: Step-by-step instructions on getting started on Docker Hub.
+  icon: explore
+  link: /docker-hub/quickstart
 - title: Create a repository
   description: Create a repository to share your images with your team, customers,
     or the Docker community.
   icon: inbox
   link: /docker-hub/repos
-- title: Quickstart
-  description: Step-by-step instructions on getting started on Docker Hub.
-  icon: explore
-  link: /docker-hub/quickstart
+- title: Manage repository access
+  description: Manage access to push and pull to your repository and assign permissions.
+  icon: key
+  link: /docker-hub/repos/access
+- title: Automated builds
+  description: Learn how you can automatically build images from source code to push to your repositories.
+  icon: build
+  link: /docker-hub/builds/how-builds-work
 - title: Release notes
   description: Find out about new features, improvements, and bug fixes.
   icon: note_add

content/docker-hub/quickstart.md

@@ -2,7 +2,7 @@
 description: Learn how to get started using Docker Hub
 keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, accounts,
   organizations, repositories, groups, teams
-title: Docker Hub Quickstart
+title: Docker Hub quickstart
 aliases:
 - /apidocs/docker-cloud/
 - /docker-cloud/
@@ -83,19 +83,19 @@ The following section contains step-by-step instructions on how to get started w
 
 Start by creating a [Docker ID](https://hub.docker.com/signup).
 
-A Docker ID grants you access to Docker Hub repositories and lets you explore available images from the community and verified publishers. You also need a Docker ID to share images on Docker Hub.
+A [Docker ID](../docker-id/_index.md) grants you access to Docker Hub repositories and lets you explore available images from the community and verified publishers. You also need a Docker ID to share images on Docker Hub.
 
 ### Step 2: Create your first repository
 
 To create a repository:
 
 1. Sign in to [Docker Hub](https://hub.docker.com).
-2. Select **Create a Repository** on the Docker Hub welcome page.
+2. On the Repositories page, select **Create repository**.
 3. Name it **<your-username>/my-private-repo**.
 4. Set the visibility to **Private**.
 5. Select **Create**.
 
-    You've created your first repository. 
+You've created your first repository.
 
 ### Step 3: Download and install Docker Desktop
 
@@ -163,7 +163,31 @@ Docker image locally.
 
 4. Run `docker push <your_username>/my-private-repo` to push your Docker image to Docker Hub. You should see output similar to:
 
-    ![Terminal](images/index-terminal.png)
+   ```console
+   $ cat > Dockerfile <<EOF
+   FROM busybox
+   CMD echo "Hello world! This is my first Docker image."
+   EOF
+   $ docker build -t mobythewhale/my-private-repo .
+   [+] Building 1.2s (5/5) FINISHED
+   => [internal] load build definition from Dockerfile
+   => => transferring dockerfile: 110B
+   => [internal] load .dockerignore
+   => => transferring context: 2B
+   => [internal] load metadata for docker.io/library/busybox:latest
+   => CACHED [1/1] FROM docker.io/library/busybox@sha256:a9286defaba7n3a519
+   => exporting to image
+   => => exporting layers
+   => => writing image sha256:dcdb1fd928bf257bfc0122ea47accd911a3a386ce618
+   => => naming to docker.io/mobythewhale/my-private-repo
+   $ docker run mobythewhale/my-private-repo
+   Hello world! This is my first Docker image.
+   $ docker push mobythewhale/my-private-repo
+   The push refers to repository [docker.io/mobythewhale/my-private-repo]
+   d2421964bad1: Layer already exists
+   latest: digest: sha256:7604fbf8eeb03d866fd005fa95cdbb802274bf9fa51f7dafba6658294
+   efa9baa size: 526
+   ```
 
     >**Note**
     >
@@ -171,7 +195,7 @@ Docker image locally.
 
 5. Your repository in Docker Hub should now display a new `latest` tag under **Tags**:
 
-    ![Tag created](images/index-tag.png)
+    ![Tag created](images/index-tag.webp)
 
 You've successfully:
 

content/docker-hub/repos/_index.md

@@ -1,5 +1,5 @@
 ---
-description: Learn how to use repositories on Docker Hub
+description: Learn how to manage repositories on Docker Hub
 keywords: Docker, docker, trusted, registry, accounts, plans, Dockerfile, Docker Hub,
   webhooks, docs, documentation, manage, repos
 title: Manage repositories
@@ -24,7 +24,7 @@ repositories for your user account, upgrade your Docker Hub subscription from yo
 
 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 ID and select the personal subscription.
+1. Navigate to [Docker Hub](https://hub.docker.com) create a new Docker ID and select a personal subscription.
 2. Using `docker login` from the CLI, sign in using your original Docker ID and pull your private images.
 3. Tag your private images with your newly created Docker ID, for example:
 

content/network/drivers/overlay.md

@@ -40,23 +40,21 @@ apply to overlay networks used by standalone containers.
 
 ### Create an overlay network
 
-> **Prerequisites**:
->
-> - Firewall rules for Docker daemons using overlay networks
->
->   You need the following ports open to traffic to and from each Docker host
->   participating on an overlay network:
->
->   - TCP port 2377 for cluster management communications
->   - TCP and UDP port 7946 for communication among nodes
->   - UDP port 4789 for overlay network traffic
->
-> - Before you can create an overlay network, you need to either initialize your
->   Docker daemon as a swarm manager using `docker swarm init` or join it to an
->   existing swarm using `docker swarm join`. Either of these creates the default
->   `ingress` overlay network which is used by swarm services by default. You need
->   to do this even if you never plan to use swarm services. Afterward, you can
->   create additional user-defined overlay networks.
+Take note of the following prerequisites:
+
+- Firewall rules for Docker daemons using overlay networks.
+
+  You need the following ports open to traffic to and from each Docker host participating on an overlay network:
+  - TCP port 2377 for cluster management communications
+  - TCP and UDP port 7946 for communication among nodes
+  - UDP port 4789 for overlay network traffic
+
+- Before you can create an overlay network, you need to either initialize your
+  Docker daemon as a swarm manager using `docker swarm init` or join it to an
+  existing swarm using `docker swarm join`. Either of these creates the default
+  `ingress` overlay network which swarm services use by default. You need
+  to do this even if you never plan to use swarm services. Afterward, you can
+  create additional user-defined overlay networks.
 
 To create an overlay network for use with swarm services, use a command like
 the following:
@@ -65,7 +63,7 @@ the following:
 $ docker network create -d overlay my-overlay
 ```
 
-To create an overlay network which can be used by swarm services **or**
+To create an overlay network which can be used by swarm services or
 standalone containers to communicate with other standalone containers running on
 other Docker daemons, add the `--attachable` flag:
 
@@ -93,9 +91,9 @@ nodes where tasks are scheduled for services attached to the overlay network.
 These tunnels also use the AES algorithm in GCM mode and manager nodes
 automatically rotate the keys every 12 hours.
 
-> **Do not attach Windows nodes to encrypted overlay networks.**
+> **Warning**
 >
-> Overlay network encryption is not supported on Windows. If a Windows node
+> Do not attach Windows nodes to encrypted overlay networks. Overlay network encryption is not supported on Windows. If a Windows node
 > attempts to connect to an encrypted overlay network, no error is detected but
 > the node cannot communicate.
 { .warning }
@@ -123,8 +121,7 @@ remove the `ingress` network.
 
 During the time that no `ingress` network exists, existing services which do not
 publish ports continue to function but are not load-balanced. This affects
-services which publish ports, such as a WordPress service which publishes port
-80.
+services which publish ports.
 
 1.  Inspect the `ingress` network using `docker network inspect ingress`, and
     remove any services whose containers are connected to it. These are services
@@ -157,7 +154,9 @@ services which publish ports, such as a WordPress service which publishes port
       my-ingress
     ```
 
-    > **Note**: You can name your `ingress` network something other than
+    > **Note**
+    >
+    > You can name your `ingress` network something other than
     > `ingress`, but you can only have one. An attempt to create a second one
     > fails.
 
@@ -199,8 +198,7 @@ from the swarm.
     docker_gwbridge
     ```
 
-5.  Initialize or join the swarm. Since the bridge already exists, Docker does
-    not create it with automatic settings.
+5.  Initialize or join the swarm. Since the bridge already exists, Docker doesn't create it with automatic settings.
 
 ## Operations for swarm services
 
@@ -208,7 +206,7 @@ from the swarm.
 
 Swarm services connected to the same overlay network effectively expose all
 ports to each other. For a port to be accessible outside of the service, that
-port must be _published_ using the `-p` or `--publish` flag on `docker service
+port must be published using the `-p` or `--publish` flag on `docker service
 create` or `docker service update`. Both the legacy colon-separated syntax and
 the newer comma-separated value syntax are supported. The longer syntax is
 preferred because it is somewhat self-documenting.