reference docs: reformat notes

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
(cherry picked from commit 6ae5df423a29a2bc118d6613da6db5f72d9d12bb)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Upstream-commit: 6ba9a3e4c9bbcf940f333b47e2b1c82100144b2c
Component: cli

Author: thaJeztah

components/cli/docs/reference/commandline/build.md

@@ -78,7 +78,8 @@ that succeeds, the directory is sent to the Docker daemon as the context.
 Local copy gives you the ability to access private repositories using local
 user credentials, VPN's, and so forth.
 
-> **Note:**
+> **Note**
+>
 > If the `URL` parameter contains a fragment the system will recursively clone
 > the repository and its submodules using a `git clone --recursive` command.
 
@@ -577,7 +578,9 @@ $ ls ./out
 vndr
 ```
 
-> **Note**: This feature requires the BuildKit backend. You can either
+> **Note**
+>
+> This feature requires the BuildKit backend. You can either
 > [enable BuildKit](../builder.md#buildkit) or use the [buildx](https://github.com/docker/buildx)
 > plugin which provides more output type options.
 
@@ -616,7 +619,9 @@ BuildKit automatically pulls the image from the registry if needed.
 $ docker build --cache-from myname/myapp .
 ```
 
-> **Note**: This feature requires the BuildKit backend. You can either
+> **Note**
+>
+> This feature requires the BuildKit backend. You can either
 > [enable BuildKit](../builder.md#buildkit) or use the [buildx](https://github.com/docker/buildx)
 > plugin. The previous builder has limited support for reusing cache from
 > pre-pulled images.

components/cli/docs/reference/commandline/cli.md

@@ -402,7 +402,9 @@ Sometimes, multiple options can call for a more complex value string as for
 $ docker run -v /host:/container example/mysql
 ```
 
-> **Note**: Do not use the `-t` and `-a stderr` options together due to
+> **Note**
+>
+> Do not use the `-t` and `-a stderr` options together due to
 > limitations in the `pty` implementation. All `stderr` in `pty` mode
 > simply goes to `stdout`.
 

components/cli/docs/reference/commandline/dockerd.md

@@ -107,10 +107,10 @@ type `dockerd`.
 To run the daemon with debug output, use `dockerd -D` or add `"debug": true` to
 the `daemon.json` file.
 
-> **Note**: In Docker 1.13 and higher, enable experimental features by starting
-> `dockerd` with the `--experimental` flag or adding `"experimental": true` to the
-> `daemon.json` file. In earlier Docker versions, a different build was required
-> to enable experimental features.
+> **Enabling experimental features**
+> 
+> Enable experimental features by starting `dockerd` with the `--experimental`
+> flag or adding `"experimental": true` to the `daemon.json` file.
 
 ## Examples
 
@@ -133,7 +133,9 @@ interface using its IP address: `-H tcp://192.168.59.103:2375`. It is
 conventional to use port `2375` for un-encrypted, and port `2376` for encrypted
 communication with the daemon.
 
-> **Note**: If you're using an HTTPS encrypted socket, keep in mind that only
+> **Note**
+>
+> If you're using an HTTPS encrypted socket, keep in mind that only
 > TLS1.0 and greater are supported. Protocols SSLv3 and under are not
 > supported anymore for security reasons.
 
@@ -298,20 +300,24 @@ The `overlay` is a very fast union filesystem. It is now merged in the main
 Linux kernel as of [3.18.0](https://lkml.org/lkml/2014/10/26/137). `overlay`
 also supports page cache sharing, this means multiple containers accessing
 the same file can share a single page cache entry (or entries), it makes
-`overlay` as efficient with memory as `aufs` driver. Call
-`dockerd -s overlay` to use it.
-
-> **Note**: As promising as `overlay` is, the feature is still quite young and
-> should not be used in production. Most notably, using `overlay` can cause
-> excessive inode consumption (especially as the number of images grows), as
-> well as being incompatible with the use of RPMs.
+`overlay` as efficient with memory as `aufs` driver. Call `dockerd -s overlay`
+to use it.
 
 The `overlay2` uses the same fast union filesystem but takes advantage of
 [additional features](https://lkml.org/lkml/2015/2/11/106) added in Linux
 kernel 4.0 to avoid excessive inode consumption. Call `dockerd -s overlay2`
 to use it.
 
-> **Note**: Both `overlay` and `overlay2` are currently unsupported on `btrfs`
+> **Note**
+>
+> The `overlay` storage driver can cause excessive inode consumption (especially
+> as the number of images grows). We recommend using the `overlay2` storage
+> driver instead.
+
+
+> **Note**
+>
+> Both `overlay` and `overlay2` are currently unsupported on `btrfs`
 > or any Copy on Write filesystem and should only be used over `ext4` partitions.
 
 On Windows, the Docker daemon supports a single image layer storage driver
@@ -458,7 +464,9 @@ $ sudo service docker start
 
 ##### `dm.loopdatasize`
 
-> **Note**: This option configures devicemapper loopback, which should not
+> **Note**
+>
+> This option configures devicemapper loopback, which should not
 > be used in production.
 
 Specifies the size to use when creating the loopback file for the
@@ -474,7 +482,9 @@ $ sudo dockerd --storage-opt dm.loopdatasize=200G
 
 ##### `dm.loopmetadatasize`
 
-> **Note**: This option configures devicemapper loopback, which should not
+> **Note**
+>
+> This option configures devicemapper loopback, which should not
 > be used in production.
 
 Specifies the size to use when creating the loopback file for the
@@ -621,7 +631,9 @@ $ sudo dockerd --storage-opt dm.override_udev_sync_check=true
 When this value is `true`, the  `devicemapper` continues and simply warns
 you the errors are happening.
 
-> **Note**: The ideal is to pursue a `docker` daemon and environment that does
+> **Note**
+>
+> The ideal is to pursue a `docker` daemon and environment that does
 > support synchronizing with `udev`. For further discussion on this
 > topic, see [docker#4036](https://github.com/docker/docker/issues/4036).
 > Otherwise, set this flag for migrating existing Docker daemons to
@@ -953,7 +965,9 @@ This is the same example via the command line:
 $ sudo dockerd --add-runtime runc=runc --add-runtime custom=/usr/local/bin/my-runc-replacement
 ```
 
-> **Note**: Defining runtime arguments via the command line is not supported.
+> **Note**
+>
+> Defining runtime arguments via the command line is not supported.
 
 #### Options for the runtime
 

components/cli/docs/reference/commandline/image_prune.md

@@ -190,7 +190,9 @@ This example removes images which have a maintainer label not set to `john`:
 $ docker image prune --filter="label!=maintainer=john"
 ```
 
-> **Note**: You are prompted for confirmation before the `prune` removes
+> **Note**
+>
+> You are prompted for confirmation before the `prune` removes
 > anything, but you are not shown a list of what will potentially be removed.
 > In addition, `docker image ls` does not support negative filtering, so it
 > difficult to predict what images will actually be removed.

components/cli/docs/reference/commandline/images.md

@@ -184,8 +184,7 @@ dea752e4e117
 511136ea3c5a
 ```
 
-> **Note**: Docker warns you if any containers exist that are using these
-> untagged images.
+Docker warns you if any containers exist that are using these untagged images.
 
 
 #### Show images with a given label

components/cli/docs/reference/commandline/logs.md

@@ -25,8 +25,10 @@ Options:
 
 The `docker logs` command batch-retrieves logs present at the time of execution.
 
-> **Note**: this command is only functional for containers that are started with
-> the `json-file` or `journald` logging driver.
+> **Note**
+>
+> This command is only functional for containers that are started with the
+> `json-file` or `journald` logging driver.
 
 For more information about selecting and configuring logging drivers, refer to
 [Configure logging drivers](https://docs.docker.com/config/containers/logging/configure/).

components/cli/docs/reference/commandline/node_demote.md

@@ -20,7 +20,9 @@ Options:
 
 Demotes an existing manager so that it is no longer a manager.
 
-> **Note**: This is a cluster management command, and must be executed on a swarm
+> **Note**
+>
+> This is a cluster management command, and must be executed on a swarm
 > manager node. To learn about managers and workers, refer to the [Swarm mode
 > section](https://docs.docker.com/engine/swarm/) in the documentation.
 

components/cli/docs/reference/commandline/node_inspect.md

@@ -25,9 +25,12 @@ given template for each result. Go's
 [text/template](http://golang.org/pkg/text/template/) package describes all the
 details of the format.
 
-> **Note**: This is a cluster management command, and must be executed on a swarm
-> manager node. To learn about managers and workers, refer to the [Swarm mode
-> section](https://docs.docker.com/engine/swarm/) in the documentation.
+> **Note**
+>
+> This is a cluster management command, and must be executed on a swarm
+> manager node. To learn about managers and workers, refer to the
+> [Swarm mode section](https://docs.docker.com/engine/swarm/) in the
+> documentation.
 
 ## Examples
 

components/cli/docs/reference/commandline/node_ls.md

@@ -27,9 +27,12 @@ Lists all the nodes that the Docker Swarm manager knows about. You can filter
 using the `-f` or `--filter` flag. Refer to the [filtering](#filtering) section
 for more information about available filter options.
 
-> **Note**: This is a cluster management command, and must be executed on a swarm
-> manager node. To learn about managers and workers, refer to the [Swarm mode
-> section](https://docs.docker.com/engine/swarm/) in the documentation.
+> **Note**
+>
+> This is a cluster management command, and must be executed on a swarm
+> manager node. To learn about managers and workers, refer to the
+> [Swarm mode section](https://docs.docker.com/engine/swarm/) in the
+> documentation.
 
 ## Examples
 
@@ -41,10 +44,11 @@ ID                           HOSTNAME        STATUS  AVAILABILITY  MANAGER STATU
 38ciaotwjuritcdtn9npbnkuz    swarm-worker1   Ready   Active
 e216jshn25ckzbvmwlnh5jr3g *  swarm-manager1  Ready   Active        Leader
 ```
-> **Note**:
-> In the above example output, there is a hidden column of `.Self` that indicates if the
-> node is the same node as the current docker daemon. A `*` (e.g., `e216jshn25ckzbvmwlnh5jr3g *`)
-> means this node is the current docker daemon.
+> **Note**
+>
+> In the above example output, there is a hidden column of `.Self` that indicates
+> if the node is the same node as the current docker daemon. A `*` (e.g.,
+> `e216jshn25ckzbvmwlnh5jr3g *`) means this node is the current docker daemon.
 
 
 ### Filtering

components/cli/docs/reference/commandline/node_promote.md

@@ -19,9 +19,12 @@ Options:
 
 Promotes a node to manager. This command can only be executed on a manager node.
 
-> **Note**: This is a cluster management command, and must be executed on a swarm
-> manager node. To learn about managers and workers, refer to the [Swarm mode
-> section](https://docs.docker.com/engine/swarm/) in the documentation.
+> **Note**
+>
+> This is a cluster management command, and must be executed on a swarm
+> manager node. To learn about managers and workers, refer to the
+> [Swarm mode section](https://docs.docker.com/engine/swarm/) in the
+> documentation.
 
 ## Examples