Found more outdated callouts, fixed whitespacing

Author: sarahsanders-docker

_vendor/github.com/moby/moby/docs/api/v1.24.md

@@ -52,7 +52,7 @@ The following diagram shows the relationship between a registry, repositories, a
 +---------------------------------------+
 ```
 
->**Note**
+> [!NOTE]
 >
 > You can create one private repository and unlimited public repositories using the free version of Docker Hub. For more information, visit the [Docker Hub subscription page](https://www.docker.com/pricing/).
 
@@ -112,7 +112,7 @@ Don't worry about the specifics of the Dockerfile, as you'll learn about that in
     docker build -t <YOUR_DOCKER_USERNAME>/docker-quickstart .
     ```
 
-    >**Note**
+    > [!NOTE]
     >
     > Make sure you include the dot (.) at the end of the `docker build` command. This tells Docker where to find the Dockerfile.
 

content/get-started/docker-concepts/the-basics/what-is-a-registry.md

@@ -72,9 +72,9 @@ To remove a container, you first need to stop it. Once it has stopped, you can r
    $ docker rm <the-container-id>
    ```
 
->**Note**
+> [!NOTE]
 >
->You can stop and remove a container in a single command by adding the `force` flag to the `docker rm` command. For example: `docker rm -f <the-container-id>`
+> You can stop and remove a container in a single command by adding the `force` flag to the `docker rm` command. For example: `docker rm -f <the-container-id>`
 
 {{< /tab >}}
 {{< tab name="Docker Desktop" >}}

content/get-started/workshop/03_updating_app.md

@@ -93,14 +93,14 @@ multiple Dockerfiles that can't be easily merged into one.
 
 ## Deduplicate context transfer
 
-> **Note**
+> [!NOTE]
 >
-> As of Buildx version 0.17.0 and later, Bake automatically deduplicates
+> As of Buildx version 0.17.0 and later, Bake automatically de-duplicates
 > context transfer for targets that share the same context. In addition to
 > Buildx version 0.17.0, the builder must be running BuildKit version 0.16.0 or
 > later, and the Dockerfile syntax must be `docker/dockerfile:1.10` or later.
 >
-> If you meet these requirements, you don't need to manually deduplicate
+> If you meet these requirements, you don't need to manually de-duplicate
 > context transfer as described in this section.
 >
 > - To check your Buildx version, run `docker buildx version`.

content/manuals/build/bake/contexts.md

@@ -19,13 +19,13 @@ Computing components of an application are defined as [services](/reference/comp
 
 Services communicate with each other through [networks](/reference/compose-file/networks.md). In the Compose Specification, a network is a platform capability abstraction to establish an IP route between containers within services connected together.
 
-Services store and share persistent data into [volumes](/reference/compose-file/volumes.md). The Specification describes such a persistent data as a high-level filesystem mount with global options. 
+Services store and share persistent data into [volumes](/reference/compose-file/volumes.md). The Specification describes such a persistent data as a high-level filesystem mount with global options.
 
 Some services require configuration data that is dependent on the runtime or platform. For this, the Specification defines a dedicated [configs](/reference/compose-file/configs.md) concept. From a service container point of view, configs are comparable to volumes, in that they are files mounted into the container. But the actual definition involves distinct platform resources and services, which are abstracted by this type.
 
 A [secret](/reference/compose-file/secrets.md) is a specific flavor of configuration data for sensitive data that should not be exposed without security considerations. Secrets are made available to services as files mounted into their containers, but the platform-specific resources to provide sensitive data are specific enough to deserve a distinct concept and definition within the Compose specification.
 
->**Note**
+> [!NOTE]
 >
 > With volumes, configs and secrets you can have a simple declaration at the top-level and then add more platform-specific information at the service level.
 

content/manuals/compose/intro/compose-application-model.md

@@ -1450,7 +1450,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 36 Release Notes (2017-01-12 1.13.0-rc6-beta36)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Upgrades**
 
@@ -1464,7 +1466,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 35 Release Notes (2017-01-06 1.13.0-rc5-beta35)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Upgrades**
 
@@ -1475,7 +1479,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 34.1 Release Notes (2016-12-22 1.13.0-rc4-beta34.1)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Hotfix**
 
@@ -1487,7 +1493,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 34 Release Notes (2016-12-20 1.13.0-rc4-beta34)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **New**
 
@@ -1509,15 +1517,19 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 33.1 Release Notes (2016-12-16 1.13.0-rc3-beta33.1)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Hotfix**
 
 - Fixed issue where sometimes TRIM would cause the virtual machine to hang
 
 ### Beta 33 Release Notes (2016-12-15 1.13.0-rc3-beta33)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **New**
 
@@ -1926,7 +1938,7 @@ events or unexpected unmounts.
 
 ### Beta 18.1 Release Notes (2016-07-07 1.12.0-rc3-beta18.1)
 
->[!NOTE] 
+> [!NOTE]
 >
 > Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
 

content/manuals/desktop/previous-versions/edge-releases-mac.md

@@ -1627,7 +1627,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 36 Release Notes (2017-01-12 1.13.0-rc6-beta36)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Upgrades**
 
@@ -1641,7 +1643,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 35 Release Notes (2017-01-06 1.13.0-rc5-beta35)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Upgrades**
 
@@ -1670,7 +1674,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 33 Release Notes (2016-12-15 1.13.0-rc3-beta33)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **New**
 
@@ -1687,7 +1693,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 32.1 Release Notes (2016-12-09 1.13.0-rc3-beta32.1)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Hotfixes**
 
@@ -1717,9 +1725,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 32 Release Notes (2016-12-07 1.13.0-rc3-beta32)
 
->**Important Note**:
+> [!IMPORTANT]
 >
->  Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **New**
 

content/manuals/desktop/previous-versions/edge-releases-windows.md

@@ -10,8 +10,7 @@ aliases:
 
 > [!NOTE]
 >
-> Automated builds require a
-> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
+> Automated builds require a [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
 
 To automate building and testing of your images, you link to your hosted source
 code service to Docker Hub so that it can access your source code
@@ -38,7 +37,7 @@ If you are linking a source code provider to create autobuilds for a team, follo
 
     ![Granting access to GitHub account](images/authorize-builder.png)
 
-    >**Note**
+    > [!NOTE]
     >
     > If you are the owner of any GitHub organizations, you might see
     options to grant Docker Hub access to them from this screen. You can also
@@ -140,6 +139,7 @@ unlink it both from Docker Hub, and revoke authorization in your Bitbucket accou
 3. From the **Linked accounts** tab, select the **Plug** icon next to the source provider you want to remove.
 
 > [!IMPORTANT]
+>
 > After unlinking the account on Docker Hub, you must also revoke the authorization on the Bitbucket end.
 
 To revoke authorization in your Bitbucket account:

content/manuals/docker-hub/builds/link-source.md

@@ -6,8 +6,7 @@ keywords: autobuilds, automated, docker hub, registry
 
 > [!NOTE]
 >
-> Automated builds require a
-> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
+> Automated builds require a [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
 
 ## Cancel or retry a build
 
@@ -32,11 +31,9 @@ From either location, you can select a build job to view its build report. The
 build report shows information about the build job. This includes the source
 repository and branch, or tag, the build logs, the build duration, creation time and location, and the user account the build occurred in.
 
->**Note**
+> [!NOTE]
 >
-> You can now view the progress of your builds every 30 seconds when you
-> refresh the **Builds** page. With the in-progress build logs, you can debug your
-> builds before they're finished.
+> You can now view the progress of your builds every 30 seconds when you refresh the **Builds** page. With the in-progress build logs, you can debug your builds before they're finished.
 
 ![Build report](/docker-hub/images/index-report.png)
 

content/manuals/docker-hub/builds/manage-builds.md

@@ -213,7 +213,7 @@ docker-ratelimit-source
 
 These headers are returned on both GET and HEAD requests.
 
->**Note**
+> [!NOTE]
 >
 > Using GET emulates a real pull and counts towards the limit. Using HEAD won't.
 > To check your limits, you need `curl`, `grep`, and `jq` installed.