docs/reference: explain "colon"

Colon may not be something non-native English readers
know about, so explain the symbol in the running text.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

docs/reference/commandline/build.md

@@ -84,7 +84,7 @@ user credentials, VPN's, and so forth.
 > the repository and its submodules using a `git clone --recursive` command.
 
 Git URLs accept context configuration in their fragment section, separated by a
-colon `:`.  The first part represents the reference that Git will check out,
+colon (`:`).  The first part represents the reference that Git will check out,
 and can be either a branch, a tag, or a remote reference. The second part
 represents a subdirectory inside the repository that will be used as a build
 context.

docs/reference/commandline/history.md

@@ -68,7 +68,8 @@ output the data exactly as the template declares or, when using the
 `table` directive, will include column headers as well.
 
 The following example uses a template without headers and outputs the
-`ID` and `CreatedSince` entries separated by a colon for the `busybox` image:
+`ID` and `CreatedSince` entries separated by a colon (`:`) for the `busybox`
+image:
 
 ```bash
 $ docker history --format "{{.ID}}: {{.CreatedSince}}" busybox

docs/reference/commandline/images.md

@@ -308,7 +308,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, will include column headers as well.
 
 The following example uses a template without headers and outputs the
-`ID` and `Repository` entries separated by a colon for all images:
+`ID` and `Repository` entries separated by a colon (`:`) for all images:
 
 ```bash
 $ docker images --format "{{.ID}}: {{.Repository}}"

docs/reference/commandline/network_ls.md

@@ -221,7 +221,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`ID` and `Driver` entries separated by a colon for all networks:
+`ID` and `Driver` entries separated by a colon (`:`) for all networks:
 
 ```bash
 $ docker network ls --format "{{.ID}}: {{.Driver}}"

docs/reference/commandline/node_ls.md

@@ -152,7 +152,8 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`ID`, `Hostname`, and `TLS Status` entries separated by a colon for all nodes:
+`ID`, `Hostname`, and `TLS Status` entries separated by a colon (`:`) for all
+nodes:
 
 ```bash
 $ docker node ls --format "{{.ID}}: {{.Hostname}} {{.TLSStatus}}"

docs/reference/commandline/node_ps.md

@@ -130,7 +130,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`Name` and `Image` entries separated by a colon for all tasks:
+`Name` and `Image` entries separated by a colon (`:`) for all tasks:
 
 ```bash
 $ docker node ps --format "{{.Name}}: {{.Image}}"

docs/reference/commandline/plugin_ls.md

@@ -88,7 +88,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`ID` and `Name` entries separated by a colon for all plugins:
+`ID` and `Name` entries separated by a colon (`:`) for all plugins:
 
 ```bash
 $ docker plugin ls --format "{{.ID}}: {{.Name}}"

docs/reference/commandline/ps.md

@@ -421,7 +421,7 @@ exactly as the template declares or, when using the `table` directive, includes
 column headers as well.
 
 The following example uses a template without headers and outputs the `ID` and
-`Command` entries separated by a colon for all running containers:
+`Command` entries separated by a colon (`:`) for all running containers:
 
 ```bash
 $ docker ps --format "{{.ID}}: {{.Command}}"

docs/reference/commandline/search.md

@@ -152,7 +152,7 @@ output the data exactly as the template declares. If you use the
 `table` directive, column headers are included as well.
 
 The following example uses a template without headers and outputs the
-`Name` and `StarCount` entries separated by a colon for all images:
+`Name` and `StarCount` entries separated by a colon (`:`) for all images:
 
 ```bash
 $ docker search --format "{{.Name}}: {{.StarCount}}" nginx

docs/reference/commandline/secret_ls.md

@@ -126,7 +126,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, will include column headers as well.
 
 The following example uses a template without headers and outputs the
-`ID` and `Name` entries separated by a colon for all images:
+`ID` and `Name` entries separated by a colon (`:`) for all images:
 
 ```bash
 $ docker secret ls --format "{{.ID}}: {{.Name}}"

docs/reference/commandline/service_create.md

@@ -926,7 +926,7 @@ Long form syntax of `--network` allows to specify list of aliases and driver opt
 You can publish service ports to make them available externally to the swarm
 using the `--publish` flag. The `--publish` flag can take two different styles
 of arguments. The short version is positional, and allows you to specify the
-published port and target port separated by a colon.
+published port and target port separated by a colon (`:`).
 
 ```bash
 $ docker service create --name my_web --replicas 3 --publish 8080:80 nginx

docs/reference/commandline/service_ls.md

@@ -141,7 +141,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`ID`, `Mode`, and `Replicas` entries separated by a colon for all services:
+`ID`, `Mode`, and `Replicas` entries separated by a colon (`:`) for all services:
 
 ```bash
 $ docker service ls --format "{{.ID}}: {{.Mode}} {{.Replicas}}"

docs/reference/commandline/service_ps.md

@@ -171,7 +171,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`Name` and `Image` entries separated by a colon for all tasks:
+`Name` and `Image` entries separated by a colon (`:`) for all tasks:
 
 ```bash
 $ docker service ps --format "{{.Name}}: {{.Image}}" top

docs/reference/commandline/stack_ls.md

@@ -63,7 +63,7 @@ the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`Name` and `Services` entries separated by a colon for all stacks:
+`Name` and `Services` entries separated by a colon (`:`) for all stacks:
 
 ```bash
 $ docker stack ls --format "{{.Name}}: {{.Services}}"

docs/reference/commandline/stack_ps.md

@@ -140,7 +140,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`Name` and `Image` entries separated by a colon for all tasks:
+`Name` and `Image` entries separated by a colon (`:`) for all tasks:
 
 ```bash
 $ docker stack ps --format "{{.Name}}: {{.Image}}" voting

docs/reference/commandline/stack_services.md

@@ -101,7 +101,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`ID`, `Mode`, and `Replicas` entries separated by a colon for all services:
+`ID`, `Mode`, and `Replicas` entries separated by a colon (`:`) for all services:
 
 ```bash
 $ docker stack services --format "{{.ID}}: {{.Mode}} {{.Replicas}}"

docs/reference/commandline/stats.md

@@ -149,7 +149,7 @@ outputs the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`Container` and `CPUPerc` entries separated by a colon for all images:
+`Container` and `CPUPerc` entries separated by a colon (`:`) for all images:
 
 ```bash
 $ docker stats --format "{{.Container}}: {{.CPUPerc}}"

docs/reference/commandline/system_df.md

@@ -99,7 +99,7 @@ the data exactly as the template declares or, when using the
 `table` directive, will include column headers as well.
 
 The following example uses a template without headers and outputs the
-`Type` and `TotalCount` entries separated by a colon:
+`Type` and `TotalCount` entries separated by a colon (`:`):
 
 ```bash
 $ docker system df --format "{{.Type}}: {{.TotalCount}}"

docs/reference/commandline/volume_ls.md

@@ -171,7 +171,7 @@ output the data exactly as the template declares or, when using the
 `table` directive, includes column headers as well.
 
 The following example uses a template without headers and outputs the
-`Name` and `Driver` entries separated by a colon for all volumes:
+`Name` and `Driver` entries separated by a colon (`:`) for all volumes:
 
 ```bash
 $ docker volume ls --format "{{.Name}}: {{.Driver}}"