Sync docker/docker refs with files mistakenly edited in docker.github.io repo

Signed-off-by: Misty Stanley-Jones <misty@docker.com>

docs/README.md

@@ -1,5 +1,14 @@
 # The non-reference docs have been moved!
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 The documentation for Docker Engine has been merged into
 [the general documentation repo](https://github.com/docker/docker.github.io).
 

docs/deprecated.md

@@ -5,6 +5,15 @@ description: "Deprecated Features."
 keywords: ["docker, documentation, about, technology, deprecate"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Deprecated Engine Features
 
 The following list of features are deprecated in Engine.

docs/extend/index.md

@@ -8,6 +8,15 @@ keywords: ["API, Usage, plugins, documentation, developer"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Docker Engine managed plugin system
 
 This document describes the plugin system available today in the **experimental

docs/extend/legacy_plugins.md

@@ -5,6 +5,15 @@ description: "How to add additional functionality to Docker with plugins extensi
 keywords: ["Examples, Usage, plugins, docker, documentation, user guide"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Use Docker Engine plugins
 
 This document describes the Docker Engine plugins generally available in Docker

docs/extend/manifest.md

@@ -8,6 +8,15 @@ keywords: ["API, Usage, plugins, documentation, developer"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Plugin Manifest Version 0 of Plugin V2
 
 This document outlines the format of the V0 plugin manifest. The plugin

docs/extend/menu.md

@@ -6,5 +6,13 @@ type: "menu"
 identifier: "engine_extend"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
 
 <!--menu page not rendered-->

docs/extend/plugin_api.md

@@ -4,6 +4,15 @@ description: "How to write Docker plugins extensions "
 keywords: ["API, Usage, plugins, documentation, developer"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Docker Plugin API
 
 Docker plugins are out-of-process extensions which add capabilities to the

docs/extend/plugins_authorization.md

@@ -5,6 +5,14 @@ keywords: ["security, authorization, authentication, docker, documentation, plug
 aliases: ["/engine/extend/authorization/"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
 
 # Create an authorization plugin
 

docs/extend/plugins_network.md

@@ -4,6 +4,15 @@ description: "Network driver plugins."
 keywords: ["Examples, Usage, plugins, docker, documentation, user guide"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Engine network driver plugins
 
 This document describes Docker Engine network driver plugins generally

docs/extend/plugins_volume.md

@@ -4,6 +4,15 @@ description: "How to manage data with external volume plugins"
 keywords: ["Examples, Usage, volume, docker, data, volumes, plugin, api"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Write a volume plugin
 
 Docker Engine volume plugins enable Engine deployments to be integrated with

docs/reference/builder.md

@@ -4,6 +4,15 @@ description: "Dockerfiles use a simple DSL which allows you to automate the step
 keywords: ["builder, docker, Dockerfile, automation,  image creation"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Dockerfile reference
 
 Docker can build images automatically by reading the instructions from a
@@ -129,7 +138,7 @@ instruction must be \`FROM\`** in order to specify the [*Base
 Image*](glossary.md#base-image) from which you are building.
 
 Docker treats lines that *begin* with `#` as a comment, unless the line is
-a valid [parser directive](builder.md#parser-directives). A `#` marker anywhere
+a valid [parser directive](#parser-directives). A `#` marker anywhere
 else in a line is treated as an argument. This allows statements like:
 
 ```Dockerfile
@@ -1265,9 +1274,9 @@ The output of the final `pwd` command in this `Dockerfile` would be
     ARG <name>[=<default value>]
 
 The `ARG` instruction defines a variable that users can pass at build-time to
-the builder with the `docker build` command using the `--build-arg
-<varname>=<value>` flag. If a user specifies a build argument that was not
-defined in the Dockerfile, the build outputs an error.
+the builder with the `docker build` command using the
+`--build-arg <varname>=<value>` flag. If a user specifies a build argument
+that was not defined in the Dockerfile, the build outputs an error.
 
 ```
 One or more build-args were not consumed, failing build.
@@ -1380,8 +1389,11 @@ corresponding `ARG` instruction in the Dockerfile.
 * `NO_PROXY`
 * `no_proxy`
 
-To use these, simply pass them on the command line using the `--build-arg
-<varname>=<value>` flag.
+To use these, simply pass them on the command line using the flag:
+
+```
+--build-arg <varname>=<value>
+```
 
 ### Impact on build caching
 

docs/reference/commandline/attach.md

@@ -4,6 +4,15 @@ description: "The attach command description and usage"
 keywords: ["attach, running, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # attach
 
 ```markdown

docs/reference/commandline/build.md

@@ -4,6 +4,15 @@ description: "The build command description and usage"
 keywords: ["build, docker, image"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # build
 
 ```markdown

docs/reference/commandline/cli.md

@@ -4,6 +4,15 @@ description: "Docker's CLI command description and usage"
 keywords: ["Docker, Docker documentation, CLI,  command line"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # Use the Docker command line
 
 To list available commands, either run `docker` with no parameters
@@ -147,6 +156,7 @@ list of supported formatting directives, see the
 
 Following is a sample `config.json` file:
 
+    {% raw %}
     {
       "HttpHeaders": {
         "MyHeader": "MyValue"
@@ -156,6 +166,7 @@ Following is a sample `config.json` file:
       "serviceInspectFormat": "pretty",
       "detachKeys": "ctrl-e,e"
     }
+    {% endraw %}
 
 ### Notary
 

docs/reference/commandline/commit.md

@@ -4,6 +4,15 @@ description: "The commit command description and usage"
 keywords: ["commit, file, changes"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # commit
 
 ```markdown
@@ -51,6 +60,7 @@ created.  Supported `Dockerfile` instructions:
 
 ## Commit a container with new configurations
 
+    {% raw %}
     $ docker ps
     ID                  IMAGE               COMMAND             CREATED             STATUS              PORTS
     c3f279d17e0a        ubuntu:12.04        /bin/bash           7 days ago          Up 25 hours
@@ -61,6 +71,7 @@ created.  Supported `Dockerfile` instructions:
     f5283438590d
     $ docker inspect -f "{{ .Config.Env }}" f5283438590d
     [HOME=/ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin DEBUG=true]
+    {% endraw %}
 
 ## Commit a container with new `CMD` and `EXPOSE` instructions
 

docs/reference/commandline/container_prune.md

@@ -4,6 +4,15 @@ description: "Remove all stopped containers"
 keywords: [container, prune, delete, remove]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # container prune
 
 ```markdown

docs/reference/commandline/cp.md

@@ -4,6 +4,15 @@ description: "The cp command description and usage"
 keywords: ["copy, container, files, folders"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # cp
 
 ```markdown

docs/reference/commandline/create.md

@@ -4,6 +4,15 @@ description: "The create command description and usage"
 keywords: ["docker, create, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # create
 
 Creates a new container.

docs/reference/commandline/deploy.md

@@ -5,6 +5,15 @@ keywords: ["stack, deploy"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stack deploy (experimental)
 
 ```markdown

docs/reference/commandline/diff.md

@@ -4,6 +4,15 @@ description: "The diff command description and usage"
 keywords: ["list, changed, files, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # diff
 
 ```markdown

docs/reference/commandline/dockerd.md

@@ -5,6 +5,15 @@ description: "The daemon command description and usage"
 keywords: ["container, daemon, runtime"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # daemon
 
 ```markdown
@@ -324,7 +333,6 @@ options for `zfs` start with `zfs` and options for `btrfs` start with `btrfs`.
     $ sudo dockerd --storage-opt dm.basesize=50G
     ```
 
-
     This will increase the base device size to 50G. The Docker daemon will throw an
     error if existing base device size is larger than 50G. A user can use
     this option to expand the base device size however shrinking is not permitted.
@@ -631,7 +639,7 @@ options for `zfs` start with `zfs` and options for `btrfs` start with `btrfs`.
 
 *   `btrfs.min_space`
 
-    Specifies the mininum size to use when creating the subvolume which is used
+    Specifies the minimum size to use when creating the subvolume which is used
     for containers. If user uses disk quota for btrfs when creating or running
     a container with **--storage-opt size** option, docker should ensure the
     **size** cannot be smaller than **btrfs.min_space**.
@@ -672,6 +680,7 @@ Runtimes can be registered with the daemon either via the
 configuration file or using the `--add-runtime` command line argument.
 
 The following is an example adding 2 runtimes via the configuration:
+
 ```json
 "default-runtime": "runc",
 "runtimes": {

docs/reference/commandline/events.md

@@ -4,6 +4,15 @@ description: "The events command description and usage"
 keywords: ["events, container, report"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # events
 
 ```markdown

docs/reference/commandline/exec.md

@@ -4,6 +4,15 @@ description: "The exec command description and usage"
 keywords: ["command, container, run, execute"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # exec
 
 ```markdown

docs/reference/commandline/export.md

@@ -4,6 +4,15 @@ description: "The export command description and usage"
 keywords: ["export, file, system, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # export
 
 ```markdown

docs/reference/commandline/history.md

@@ -4,6 +4,15 @@ description: "The history command description and usage"
 keywords: ["docker, image, history"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # history
 
 ```markdown

docs/reference/commandline/image_prune.md

@@ -4,6 +4,15 @@ description: "Remove all stopped images"
 keywords: [image, prune, delete, remove]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # image prune
 
 ```markdown

docs/reference/commandline/images.md

@@ -4,6 +4,15 @@ description: "The images command description and usage"
 keywords: ["list, docker, images"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # images
 
 ```markdown
@@ -245,6 +254,7 @@ output the data exactly as the template declares or, when using the
 The following example uses a template without headers and outputs the
 `ID` and `Repository` entries separated by a colon for all images:
 
+    {% raw %}
     $ docker images --format "{{.ID}}: {{.Repository}}"
     77af4d6b9913: <none>
     b6fa739cedf5: committ
@@ -255,10 +265,12 @@ The following example uses a template without headers and outputs the
     746b819f315e: postgres
     746b819f315e: postgres
     746b819f315e: postgres
+    {% endraw %}
 
 To list all images with their repository and tag in a table format you
 can use:
 
+    {% raw %}
     $ docker images --format "table {{.ID}}\t{{.Repository}}\t{{.Tag}}"
     IMAGE ID            REPOSITORY                TAG
     77af4d6b9913        <none>                    <none>
@@ -270,3 +282,4 @@ can use:
     746b819f315e        postgres                  9.3
     746b819f315e        postgres                  9.3.5
     746b819f315e        postgres                  latest
+    {% endraw %}

docs/reference/commandline/import.md

@@ -4,6 +4,15 @@ description: "The import command description and usage"
 keywords: ["import, file, system, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # import
 
 ```markdown

docs/reference/commandline/index.md

@@ -5,7 +5,14 @@ keywords: ["Docker, Docker documentation, CLI,  command line"]
 identifier: "smn_cli_guide"
 ---
 
-
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
 
 # The Docker commands
 

docs/reference/commandline/info.md

@@ -4,6 +4,15 @@ description: "The info command description and usage"
 keywords: ["display, docker, information"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # info
 
 ```markdown

docs/reference/commandline/inspect.md

@@ -4,6 +4,15 @@ description: "The inspect command description and usage"
 keywords: ["inspect, container, json"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # inspect
 
 ```markdown
@@ -34,29 +43,39 @@ describes all the details of the format.
 For the most part, you can pick out any field from the JSON in a fairly
 straightforward manner.
 
+    {% raw %}
     $ docker inspect --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $INSTANCE_ID
+    {% endraw %}
 
 **Get an instance's MAC address:**
 
 For the most part, you can pick out any field from the JSON in a fairly
 straightforward manner.
 
+    {% raw %}
     $ docker inspect --format='{{range .NetworkSettings.Networks}}{{.MacAddress}}{{end}}' $INSTANCE_ID
+    {% endraw %}
 
 **Get an instance's log path:**
 
+    {% raw %}
     $ docker inspect --format='{{.LogPath}}' $INSTANCE_ID
+    {% endraw %}
 
 **Get a Task's image name:**
 
+    {% raw %}
     $ docker inspect --format='{{.Container.Spec.Image}}' $INSTANCE_ID
+    {% endraw %}
 
 **List all port bindings:**
 
 One can loop over arrays and maps in the results to produce simple text
 output:
 
+    {% raw %}
     $ docker inspect --format='{{range $p, $conf := .NetworkSettings.Ports}} {{$p}} -> {{(index $conf 0).HostPort}} {{end}}' $INSTANCE_ID
+    {% endraw %}
 
 **Find a specific port mapping:**
 
@@ -68,7 +87,9 @@ numeric public port, you use `index` to find the specific port map, and
 then `index` 0 contains the first object inside of that. Then we ask for
 the `HostPort` field to get the public address.
 
+    {% raw %}
     $ docker inspect --format='{{(index (index .NetworkSettings.Ports "8787/tcp") 0).HostPort}}' $INSTANCE_ID
+    {% endraw %}
 
 **Get a subsection in JSON format:**
 
@@ -77,4 +98,6 @@ fields, by default you get a Go-style dump of the inner values.
 Docker adds a template function, `json`, which can be applied to get
 results in JSON format.
 
+    {% raw %}
     $ docker inspect --format='{{json .Config}}' $INSTANCE_ID
+    {% endraw %}

docs/reference/commandline/kill.md

@@ -4,6 +4,15 @@ description: "The kill command description and usage"
 keywords: ["container, kill, signal"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # kill
 
 ```markdown

docs/reference/commandline/load.md

@@ -4,6 +4,15 @@ description: "The load command description and usage"
 keywords: ["stdin, tarred, repository"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # load
 
 ```markdown

docs/reference/commandline/login.md

@@ -4,6 +4,15 @@ description: "The login command description and usage"
 keywords: ["registry, login, image"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # login
 
 ```markdown
@@ -48,12 +57,12 @@ This is the list of currently available credentials helpers and where
 you can download them from:
 
 - D-Bus Secret Service: https://github.com/docker/docker-credential-helpers/releases
-- Apple OS X keychain: https://github.com/docker/docker-credential-helpers/releases
+- Apple macOS keychain: https://github.com/docker/docker-credential-helpers/releases
 - Microsoft Windows Credential Manager: https://github.com/docker/docker-credential-helpers/releases
 
 ### Usage
 
-You need to speficy the credentials store in `$HOME/.docker/config.json`
+You need to specify the credentials store in `$HOME/.docker/config.json`
 to tell the docker engine to use it:
 
 ```json

docs/reference/commandline/logout.md

@@ -4,6 +4,15 @@ description: "The logout command description and usage"
 keywords: ["logout, docker, registry"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # logout
 
 ```markdown

docs/reference/commandline/logs.md

@@ -4,6 +4,15 @@ description: "The logs command description and usage"
 keywords: ["logs, retrieve, docker"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # logs
 
 ```markdown

docs/reference/commandline/menu.md

@@ -5,7 +5,14 @@ keywords: ["Docker, Docker documentation, CLI,  command line"]
 identifier:  "smn_cli"
 ---
 
-
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
 
 # The Docker commands
 

docs/reference/commandline/network_connect.md

@@ -4,6 +4,15 @@ description: "The network connect command description and usage"
 keywords: ["network, connect, user-defined"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # network connect
 
 ```markdown

docs/reference/commandline/network_create.md

@@ -4,6 +4,15 @@ description: "The network create command description and usage"
 keywords: ["network, create"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # network create
 
 ```markdown

docs/reference/commandline/network_disconnect.md

@@ -4,6 +4,15 @@ description: "The network disconnect command description and usage"
 keywords: ["network, disconnect, user-defined"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # network disconnect
 
 ```markdown

docs/reference/commandline/network_inspect.md

@@ -4,6 +4,15 @@ description: "The network inspect command description and usage"
 keywords: ["network, inspect, user-defined"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # network inspect
 
 ```markdown

docs/reference/commandline/network_ls.md

@@ -4,6 +4,15 @@ description: "The network ls command description and usage"
 keywords: ["network, list, user-defined"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # docker network ls
 
 ```markdown

docs/reference/commandline/network_rm.md

@@ -4,6 +4,15 @@ description: "the network rm command description and usage"
 keywords: ["network, rm, user-defined"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # network rm
 
 ```markdown

docs/reference/commandline/node_demote.md

@@ -4,6 +4,15 @@ description: "The node demote command description and usage"
 keywords: ["node, demote"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # node demote
 
 ```markdown

docs/reference/commandline/node_inspect.md

@@ -4,6 +4,15 @@ description: "The node inspect command description and usage"
 keywords: ["node, inspect"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # node inspect
 
 ```markdown
@@ -89,8 +98,10 @@ Example output:
     }
     ]
 
+    {% raw %}
     $ docker node inspect --format '{{ .ManagerStatus.Leader }}' self
     false
+    {% endraw %}
 
     $ docker node inspect --pretty self
     ID:                     e216jshn25ckzbvmwlnh5jr3g

docs/reference/commandline/node_ls.md

@@ -4,6 +4,15 @@ description: "The node ls command description and usage"
 keywords: ["node, list"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # node ls
 
 ```markdown

docs/reference/commandline/node_promote.md

@@ -4,6 +4,15 @@ description: "The node promote command description and usage"
 keywords: ["node, promote"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # node promote
 
 ```markdown

docs/reference/commandline/node_ps.md

@@ -5,6 +5,15 @@ keywords: ["node, tasks", "ps"]
 aliases: ["/engine/reference/commandline/node_tasks/"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # node ps
 
 ```markdown

docs/reference/commandline/node_rm.md

@@ -4,6 +4,15 @@ description: "The node rm command description and usage"
 keywords: ["node, remove"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # node rm
 
 ```markdown

docs/reference/commandline/node_update.md

@@ -4,6 +4,15 @@ description: "The node update command description and usage"
 keywords: ["resources, update, dynamically"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 ## update
 
 ```markdown

docs/reference/commandline/pause.md

@@ -4,6 +4,15 @@ description: "The pause command description and usage"
 keywords: ["cgroups, container, suspend, SIGSTOP"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # pause
 
 ```markdown

docs/reference/commandline/plugin_disable.md

@@ -5,6 +5,15 @@ keywords: ["plugin, disable"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # plugin disable (experimental)
 
 ```markdown

docs/reference/commandline/plugin_enable.md

@@ -5,6 +5,15 @@ keywords: ["plugin, enable"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # plugin enable (experimental)
 
 ```markdown

docs/reference/commandline/plugin_inspect.md

@@ -5,6 +5,15 @@ keywords: ["plugin, inspect"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # plugin inspect (experimental)
 
 ```markdown

docs/reference/commandline/plugin_install.md

@@ -5,6 +5,15 @@ keywords: ["plugin, install"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # plugin install (experimental)
 
 ```markdown

docs/reference/commandline/plugin_ls.md

@@ -5,6 +5,15 @@ keywords: ["plugin, list"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # plugin ls (experimental)
 
 ```markdown

docs/reference/commandline/plugin_rm.md

@@ -5,6 +5,15 @@ keywords: ["plugin, rm"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # plugin rm (experimental)
 
 ```markdown

docs/reference/commandline/port.md

@@ -4,6 +4,15 @@ description: "The port command description and usage"
 keywords: ["port, mapping, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # port
 
 ```markdown

docs/reference/commandline/ps.md

@@ -4,6 +4,15 @@ description: "The ps command description and usage"
 keywords: ["container, running, list"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # ps
 
 ```markdown
@@ -145,6 +154,7 @@ $ docker ps -a --filter 'exited=137'
 CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS                       PORTS               NAMES
 b3e1c0ed5bfe        ubuntu:latest       "sleep 1000"           12 seconds ago      Exited (137) 5 seconds ago                       grave_kowalevski
 a2eb5558d669        redis:latest        "/entrypoint.sh redi   2 hours ago         Exited (137) 2 hours ago                         sharp_lalande
+```
 
 Any of these events result in a `137` status:
 
@@ -271,7 +281,7 @@ CONTAINER ID        IMAGE       COMMAND       CREATED             STATUS
 The `volume` filter shows only containers that mount a specific volume or have
 a volume mounted in a specific path:
 
-```bash
+```bash{% raw %}
 $ docker ps --filter volume=remote-volume --format "table {{.ID}}\t{{.Mounts}}"
 CONTAINER ID        MOUNTS
 9c3527ed70ce        remote-volume
@@ -279,7 +289,7 @@ CONTAINER ID        MOUNTS
 $ docker ps --filter volume=/data --format "table {{.ID}}\t{{.Mounts}}"
 CONTAINER ID        MOUNTS
 9c3527ed70ce        remote-volume
-```
+{% endraw %}```
 
 #### Network
 
@@ -304,7 +314,9 @@ example shows all containers that are attached to the `net1` network, using
 the network id as a filter;
 
 ```bash
+{% raw %}
 $ docker network inspect --format "{{.ID}}" net1
+{% endraw %}
 
 8c0b4110ae930dbe26b258de9bc34a03f98056ed6f27f991d32919bfe401d7c5
 
@@ -333,7 +345,7 @@ Placeholder   | Description
 `.Size`       | Container disk size.
 `.Names`      | Container names.
 `.Labels`     | All labels assigned to the container.
-`.Label`      | Value of a specific label for this container. For example `'{{.Label "com.docker.swarm.cpu"}}'`
+`.Label`      | Value of a specific label for this container. For example `'{% raw %}{{.Label "com.docker.swarm.cpu"}}{% endraw %}'`
 `.Mounts`     | Names of the volumes mounted in this container.
 
 When using the `--format` option, the `ps` command will either output the data
@@ -344,7 +356,9 @@ The following example uses a template without headers and outputs the `ID` and
 `Command` entries separated by a colon for all running containers:
 
 ```bash
+{% raw %}
 $ docker ps --format "{{.ID}}: {{.Command}}"
+{% endraw %}
 
 a87ecb4f327c: /bin/sh -c #(nop) MA
 01946d9d34d8: /bin/sh -c #(nop) MA
@@ -355,7 +369,9 @@ c1d3b0166030: /bin/sh -c yum -y up
 To list all running containers with their labels in a table format you can use:
 
 ```bash
+{% raw %}
 $ docker ps --format "table {{.ID}}\t{{.Labels}}"
+{% endraw %}
 
 CONTAINER ID        LABELS
 a87ecb4f327c        com.docker.swarm.node=ubuntu,com.docker.swarm.storage=ssd

docs/reference/commandline/pull.md

@@ -4,6 +4,15 @@ description: "The pull command description and usage"
 keywords: ["pull, image, hub, docker"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # pull
 
 ```markdown

docs/reference/commandline/push.md

@@ -4,6 +4,15 @@ description: "The push command description and usage"
 keywords: ["share, push, image"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # push
 
 ```markdown

docs/reference/commandline/rename.md

@@ -4,6 +4,15 @@ description: "The rename command description and usage"
 keywords: ["rename, docker, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # rename
 
 ```markdown

docs/reference/commandline/restart.md

@@ -4,6 +4,15 @@ description: "The restart command description and usage"
 keywords: ["restart, container, Docker"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # restart
 
 ```markdown

docs/reference/commandline/rm.md

@@ -4,6 +4,15 @@ description: "The rm command description and usage"
 keywords: ["remove, Docker, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # rm
 
 ```markdown

docs/reference/commandline/rmi.md

@@ -4,6 +4,15 @@ description: "The rmi command description and usage"
 keywords: ["remove, image, Docker"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # rmi
 
 ```markdown

docs/reference/commandline/run.md

@@ -4,6 +4,15 @@ description: "The run command description and usage"
 keywords: ["run, command, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # run
 
 ```markdown

docs/reference/commandline/save.md

@@ -4,6 +4,15 @@ description: "The save command description and usage"
 keywords: ["tarred, repository, backup"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # save
 
 ```markdown

docs/reference/commandline/search.md

@@ -4,6 +4,15 @@ description: "The search command description and usage"
 keywords: ["search, hub, images"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # search
 
 ```markdown
@@ -76,7 +85,7 @@ at least 3 stars and the description isn't truncated in the output:
 
 ## Limit search results (--limit)
 
-The flag `--limit` is the maximium number of results returned by a search. This value could
+The flag `--limit` is the maximum number of results returned by a search. This value could
 be in the range between 1 and 100. The default value of `--limit` is 25.
 
 

docs/reference/commandline/service_create.md

@@ -4,6 +4,15 @@ description: "The service create command description and usage"
 keywords: ["service, create"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # service create
 
 ```Markdown

docs/reference/commandline/service_inspect.md

@@ -4,6 +4,15 @@ description: "The service inspect command description and usage"
 keywords: ["service, inspect"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # service inspect
 
 ```Markdown
@@ -136,10 +145,10 @@ The `--format` option can be used to obtain specific information about a
 service. For example, the following command outputs the number of replicas
 of the "redis" service.
 
-```bash
+```bash{% raw %}
 $ docker service inspect --format='{{.Spec.Mode.Replicated.Replicas}}' redis
 10
-```
+{% endraw %}```
 
 
 ## Related information

docs/reference/commandline/service_ls.md

@@ -4,6 +4,15 @@ description: "The service ls command description and usage"
 keywords: ["service, ls"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # service ls
 
 ```Markdown

docs/reference/commandline/service_ps.md

@@ -5,6 +5,15 @@ keywords: ["service, tasks", "ps"]
 aliases: ["/engine/reference/commandline/service_tasks/"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # service ps
 
 ```Markdown

docs/reference/commandline/service_rm.md

@@ -4,6 +4,15 @@ description: "The service rm command description and usage"
 keywords: ["service, rm"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # service rm
 
 ```Markdown

docs/reference/commandline/service_scale.md

@@ -4,6 +4,15 @@ description: "The service scale command description and usage"
 keywords: ["service, scale"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # service scale
 
 ```markdown
@@ -19,8 +28,10 @@ Options:
 
 ### Scale a service
 
-If you scale a service, you set the *desired* number of replicas. Even though
-the command returns directly, actual scaling of the service may take some time.
+The scale command enables you to scale one or more services either up or down to
+the desired number of replicas. The command will return immediately, but the
+actual scaling of the service may take some time. To stop all replicas of a
+service while keeping the service active in the swarm you can set the scale to 0.
 
 For example, the following command scales the "frontend" service to 50 tasks.
 
@@ -30,7 +41,7 @@ frontend scaled to 50
 ```
 
 Directly afterwards, run `docker service ls`, to see the actual number of
-replicas
+replicas.
 
 ```bash
 $ docker service ls --filter name=frontend
@@ -40,7 +51,7 @@ ID            NAME      REPLICAS  IMAGE         COMMAND
 ```
 
 You can also scale a service using the [`docker service update`](service_update.md)
-command. The following commands are therefore equivalent:
+command. The following commands are equivalent:
 
 ```bash
 $ docker service scale frontend=50

docs/reference/commandline/service_update.md

@@ -4,6 +4,15 @@ description: "The service update command description and usage"
 keywords: ["service, update"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # service update
 
 ```Markdown

docs/reference/commandline/stack_config.md

@@ -5,6 +5,15 @@ keywords: ["stack, config"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stack config (experimental)
 
 ```markdown

docs/reference/commandline/stack_deploy.md

@@ -5,6 +5,15 @@ keywords: ["stack, deploy, up"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stack deploy (experimental)
 
 ```markdown

docs/reference/commandline/stack_ls.md

@@ -5,6 +5,15 @@ keywords: ["stack, ls"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stack ls (experimental)
 
 ```markdown

docs/reference/commandline/stack_ps.md

@@ -5,6 +5,15 @@ keywords: ["stack, ps"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stack ps (experimental)
 
 ```markdown

docs/reference/commandline/stack_rm.md

@@ -3,10 +3,17 @@ title: "stack rm"
 description: "The stack rm command description and usage"
 keywords: ["stack, rm, remove, down"]
 advisory: "experimental"
-
-
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stack rm (experimental)
 
 ```markdown

docs/reference/commandline/stack_services.md

@@ -5,6 +5,15 @@ keywords: ["stack, services"]
 advisory: "experimental"
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stack services (experimental)
 
 ```markdown

docs/reference/commandline/start.md

@@ -4,6 +4,15 @@ description: "The start command description and usage"
 keywords: ["Start, container, stopped"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # start
 
 ```markdown

docs/reference/commandline/stats.md

@@ -4,6 +4,15 @@ description: "The stats command description and usage"
 keywords: ["container, resource, statistics"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stats
 
 ```markdown

docs/reference/commandline/stop.md

@@ -4,6 +4,15 @@ description: "The stop command description and usage"
 keywords: ["stop, SIGKILL, SIGTERM"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # stop
 
 ```markdown

docs/reference/commandline/swarm_init.md

@@ -4,6 +4,15 @@ description: "The swarm init command description and usage"
 keywords: ["swarm, init"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # swarm init
 
 ```markdown

docs/reference/commandline/swarm_join.md

@@ -4,6 +4,15 @@ description: "The swarm join command description and usage"
 keywords: ["swarm, join"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # swarm join
 
 ```markdown

docs/reference/commandline/swarm_join_token.md

@@ -4,6 +4,15 @@ description: "The swarm join-token command description and usage"
 keywords: ["swarm, join-token"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # swarm join-token
 
 ```markdown

docs/reference/commandline/swarm_leave.md

@@ -4,6 +4,15 @@ description: "The swarm leave command description and usage"
 keywords: ["swarm, leave"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # swarm leave
 
 ```markdown

docs/reference/commandline/swarm_update.md

@@ -4,6 +4,15 @@ description: "The swarm update command description and usage"
 keywords: ["swarm, update"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # swarm update
 
 ```markdown

docs/reference/commandline/system_df.md

@@ -4,6 +4,15 @@ description: "The system df command description and usage"
 keywords: [system, data, usage, disk]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # system df
 
 ```markdown

docs/reference/commandline/system_prune.md

@@ -4,6 +4,15 @@ description: "Remove unused data"
 keywords: [system, prune, delete, remove]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # system prune
 
 ```markdown

docs/reference/commandline/tag.md

@@ -4,6 +4,15 @@ description: "The tag command description and usage"
 keywords: ["tag, name, image"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # tag
 
 ```markdown

docs/reference/commandline/top.md

@@ -4,6 +4,15 @@ description: "The top command description and usage"
 keywords: ["container, running, processes"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # top
 
 ```markdown

docs/reference/commandline/unpause.md

@@ -4,6 +4,15 @@ description: "The unpause command description and usage"
 keywords: ["cgroups, suspend, container"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # unpause
 
 ```markdown

docs/reference/commandline/update.md

@@ -4,6 +4,15 @@ description: "The update command description and usage"
 keywords: ["resources, update, dynamically"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 ## update
 
 ```markdown

docs/reference/commandline/version.md

@@ -4,6 +4,15 @@ description: "The version command description and usage"
 keywords: ["version, architecture, api"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # version
 
 ```markdown
@@ -45,10 +54,14 @@ describes all the details of the format.
 
 **Get server version:**
 
+    {% raw %}
     $ docker version --format '{{.Server.Version}}'
 	1.8.0
+    {% endraw %}
 
 **Dump raw data:**
 
+    {% raw %}
     $ docker version --format '{{json .}}'
     {"Client":{"Version":"1.8.0","ApiVersion":"1.20","GitCommit":"f5bae0a","GoVersion":"go1.4.2","Os":"linux","Arch":"amd64","BuildTime":"Tue Jun 23 17:56:00 UTC 2015"},"ServerOK":true,"Server":{"Version":"1.8.0","ApiVersion":"1.20","GitCommit":"f5bae0a","GoVersion":"go1.4.2","Os":"linux","Arch":"amd64","KernelVersion":"3.13.2-gentoo","BuildTime":"Tue Jun 23 17:56:00 UTC 2015"}}
+    {% endraw %}

docs/reference/commandline/volume_create.md

@@ -4,6 +4,15 @@ description: "The volume create command description and usage"
 keywords: ["volume, create"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # volume create
 
 ```markdown

docs/reference/commandline/volume_inspect.md

@@ -4,6 +4,15 @@ description: "The volume inspect command description and usage"
 keywords: ["volume, inspect"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # volume inspect
 
 ```markdown
@@ -36,8 +45,10 @@ Example output:
       }
     ]
 
+    {% raw %}
     $ docker volume inspect --format '{{ .Mountpoint }}' 85bffb0677236974f93955d8ecc4df55ef5070117b0e53333cc1b443777be24d
     /var/lib/docker/volumes/85bffb0677236974f93955d8ecc4df55ef5070117b0e53333cc1b443777be24d/_data
+    {% endraw %}
 
 ## Related information
 

docs/reference/commandline/volume_ls.md

@@ -4,6 +4,15 @@ description: "The volume ls command description and usage"
 keywords: ["volume, list"]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # volume ls
 
 ```markdown

docs/reference/commandline/volume_prune.md

@@ -4,6 +4,15 @@ description: "Remove unused volumes"
 keywords: [volume, prune, delete]
 ---
 
+<!-- This file is maintained within the docker/docker Github
+     repository at https://github.com/docker/docker/. Make all
+     pull requests against that repo. If you see this file in
+     another repository, consider it read-only there, as it will
+     periodically be overwritten by the definitive file. Pull
+     requests which include edits to this file in other repositories
+     will be rejected.
+-->
+
 # volume prune
 
 ```markdown