toolshed/docker-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix a number of minor typos

Browse Source 
Fix 19 typos, grammatical errors and duplicated words.

These fixes have minimal impact on the code as these are either in the
doc files or in comments inside the code files.

Signed-off-by: Abdur Rehman <abdur_rehman@mentor.com>
This commit is contained in:
Abdur Rehman
2017-10-31 15:21:09 +05:00
parent 96b8d15bdd
commit c3fe9d85ef
18 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
man/docker-run.1.md
View File

@ -582,7 +582,7 @@ incompatible with any restart policy other than `none`.
This option is only available for the `devicemapper`, `btrfs`, `overlay2` and `zfs` graph drivers.
For the `devicemapper`, `btrfs` and `zfs` storage drivers, user cannot pass a size less than the Default BaseFS Size.
For the `overlay2` storage driver, the size option is only available if the backing fs is `xfs` and mounted with the `pquota` mount option.
Under these conditions, user can pass any size less then the backing fs size.
Under these conditions, user can pass any size less than the backing fs size.
**--stop-signal**=*SIGTERM*
Signal to stop a container. Default is SIGTERM.

2
man/dockerd.8.md
View File

@ -480,7 +480,7 @@ autoextend the available space [100 = disabled]
##### dm.thinp_autoextend_percent
Sets the value percentage value to increase the thin pool by when when `lvm`
Sets the value percentage value to increase the thin pool by when `lvm`
attempts to autoextend the available space [100 = disabled]
###### Example:

2
man/src/network/create.md
View File

@ -123,7 +123,7 @@ to create an externally isolated `overlay` network, you can specify the
You can create the network which will be used to provide the routing-mesh in the
swarm cluster. You do so by specifying `--ingress` when creating the network. Only
one ingress network can be created at the time. The network can be removed only
if no services depend on it. Any option available when creating a overlay network
if no services depend on it. Any option available when creating an overlay network
is also available when creating the ingress network, besides the `--attachable` option.
```bash

2
man/src/network/inspect.md
View File

@ -92,7 +92,7 @@ $ docker network inspect simple-network
details such as the service's VIP and port mappings. It also shows IPs of service tasks,
and the IPs of the nodes where the tasks are running.
Following is an example output for a overlay network `ov1` that has one service `s1`
Following is an example output for an overlay network `ov1` that has one service `s1`
attached to. service `s1` in this case has three replicas.
```bash