reference docs: fix broken links and markdown touch-ups

- fix various broken links
- fix incorrect anchors
- updated links for content that moved, so that no
  redirect to the new location is needed.
- touched-up Markdown;
  - re-format some JSON output
  - add blank line betweeen command and command output
  - format "note" blocks

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
(cherry picked from commit 8919c228bdcd8bd366dee9589d22001c856e9e76)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Upstream-commit: 96eb0888fa6be0f087c1b177134255a104bfdf83
Component: cli

Author: thaJeztah

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

@@ -396,13 +396,13 @@ the command line.
 
 When `docker build` is run with the `--cgroup-parent` option the containers
 used in the build will be run with the [corresponding `docker run`
-flag](../run.md#specifying-custom-cgroups).
+flag](../run.md#specify-custom-cgroups).
 
 ### Set ulimits in container (--ulimit)
 
 Using the `--ulimit` option with `docker build` will cause each build step's
 container to be started using those [`--ulimit`
-flag values](./run.md#set-ulimits-in-container-ulimit).
+flag values](run.md#set-ulimits-in-container---ulimit).
 
 ### Set build-time variables (--build-arg)
 

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

@@ -90,7 +90,7 @@ you must be explicit with a relative or absolute path, for example:
     `/path/to/file:name.txt` or `./file:name.txt`
 
 It is not possible to copy certain system files such as resources under
-`/proc`, `/sys`, `/dev`, [tmpfs](run.md#mount-tmpfs-tmpfs), and mounts created by
+`/proc`, `/sys`, `/dev`, [tmpfs](run.md#mount-tmpfs---tmpfs), and mounts created by
 the user in the container. However, you can still copy such files by manually
 running `tar` in `docker exec`. Both of the following examples do the same thing
 in different ways (consider `SRC_PATH` and `DEST_PATH` are directories):

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

@@ -60,7 +60,7 @@ $ docker import http://example.com/exampleimage.tgz
 - Import to docker from a local archive.
 
   ```bash
-    $ docker import /path/to/exampleimage.tgz
+  $ docker import /path/to/exampleimage.tgz
   ```
 
 ### Import from a local directory
@@ -81,9 +81,12 @@ archiving with tar. If you are not root (or the sudo command) when you
 tar, then the ownerships might not get preserved.
 
 ## When the daemon supports multiple operating systems
+
 If the daemon supports multiple operating systems, and the image being imported
 does not match the default operating system, it may be necessary to add
 `--platform`. This would be necessary when importing a Linux image into a Windows
 daemon.
 
-    # docker import --platform=linux .\linuximage.tar
+```bash
+$ docker import --platform=linux .\linuximage.tar
+```

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

@@ -23,7 +23,9 @@ inside the container is sent `SIGKILL` signal (default), or the signal that is
 specified with the `--signal` option. You can kill a container using the
 container's ID, ID-prefix, or name.
 
-> **Note**: `ENTRYPOINT` and `CMD` in the *shell* form run as a subcommand of
+> **Note**
+>
+> `ENTRYPOINT` and `CMD` in the *shell* form run as a child process of
 > `/bin/sh -c`, which does not pass signals. This means that the executable is
 > not the container’s PID 1 and does not receive Unix signals.
 

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

@@ -73,4 +73,4 @@ $ docker logs -f --until=2s
 Tue 14 Nov 2017 16:40:00 CET
 Tue 14 Nov 2017 16:40:01 CET
 Tue 14 Nov 2017 16:40:02 CET
-```
+```

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

@@ -40,7 +40,7 @@ to two images -- one for windows on amd64, and one for darwin on amd64.
 
 ### manifest inspect
 
-```
+```bash
 manifest inspect --help
 
 Usage:  docker manifest inspect [OPTIONS] [MANIFEST_LIST] MANIFEST
@@ -275,9 +275,10 @@ $ docker manifest create --insecure myprivateregistry.mycompany.com/repo/image:1
 $ docker manifest push --insecure myprivateregistry.mycompany.com/repo/image:tag
 ```
 
-> **Note**: the `--insecure` flag is not required to annotate a manifest list,
+> **Note**
+>
+> The `--insecure` flag is not required to annotate a manifest list,
 > since annotations are to a locally-stored copy of a manifest list. You may also
 > skip the `--insecure` flag if you are performing a `docker manifest inspect`
 > on a locally-stored manifest list. Be sure to keep in mind that locally-stored
 > manifest lists are never used by the engine on a `docker pull`.
-

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

@@ -35,7 +35,7 @@ prune, connect, and disconnect networks.
 
 * [network create](network_create.md)
 * [network inspect](network_inspect.md)
-* [network list](network_list.md)
+* [network list](network_ls.md)
 * [network rm](network_rm.md)
 * [network prune](network_prune.md)
 * [network connect](network_connect.md)

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

@@ -24,7 +24,7 @@ disconnect it from the network.
 ## Examples
 
 ```bash
-  $ docker network disconnect multi-host-network container1
+$ docker network disconnect multi-host-network container1
 ```
 
 

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

@@ -96,7 +96,7 @@ f949d337b1f5        none                null                local
 * [network ls](network_ls.md)
 * [network inspect](network_inspect.md)
 * [network rm](network_rm.md)
-* [Understand Docker container networks](https://docs.docker.com/engine/userguide/networking/)
+* [Understand Docker container networks](https://docs.docker.com/network/)
 * [system df](system_df.md)
 * [container prune](container_prune.md)
 * [image prune](image_prune.md)

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

@@ -56,4 +56,4 @@ deletion.
 * [network ls](network_ls.md)
 * [network inspect](network_inspect.md)
 * [network prune](network_prune.md)
-* [Understand Docker container networks](https://docs.docker.com/engine/userguide/networking/)
+* [Understand Docker container networks](https://docs.docker.com/network/)