Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typos found across repository 

Signed-off-by: Justas Brazauskas <brazauskasjustas@gmail.com>
This commit is contained in:
Justas Brazauskas 2015-12-13 18:00:39 +02:00 committed by Tibor Vass
parent 53c1cb81c0
commit b91f98d9f1
5 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/commandline/events.md
View File

@ -27,11 +27,11 @@ and Docker images will report:
delete, import, pull, push, tag, untag delete, import, pull, push, tag, untag
The `--since` and `--until` parameters can be Unix timestamps, date formated The `--since` and `--until` parameters can be Unix timestamps, date formatted
timestamps, or Go duration strings (e.g. `10m`, `1h30m`) computed timestamps, or Go duration strings (e.g. `10m`, `1h30m`) computed
relative to the client machine’s time. If you do not provide the --since option, relative to the client machine’s time. If you do not provide the --since option,
the command returns only new and/or live events. Supported formats for date the command returns only new and/or live events. Supported formats for date
formated time stamps include RFC3339Nano, RFC3339, `2006-01-02T15:04:05`, formatted time stamps include RFC3339Nano, RFC3339, `2006-01-02T15:04:05`,
`2006-01-02T15:04:05.999999999`, `2006-01-02Z07:00`, and `2006-01-02`. The local `2006-01-02T15:04:05.999999999`, `2006-01-02Z07:00`, and `2006-01-02`. The local
timezone on the client will be used if you do not provide either a `Z` or a timezone on the client will be used if you do not provide either a `Z` or a
`+-00:00` timezone offset at the end of the timestamp. When providing Unix `+-00:00` timezone offset at the end of the timestamp. When providing Unix

2
experimental/plugins_graphdriver.md
View File

@ -204,7 +204,7 @@ Respond with a string error if an error occurred.
{} {}
``` ```
Perform neccessary tasks to release resources help by the plugin, for example Perform necessary tasks to release resources help by the plugin, for example
unmounting all the layered file systems. unmounting all the layered file systems.
**Response**: **Response**:

14
experimental/userns.md
View File

@ -12,13 +12,13 @@ In this experimental phase, the Docker daemon creates a single daemon-wide mappi
for all containers running on the same engine instance. The mappings will for all containers running on the same engine instance. The mappings will
utilize the existing subordinate user and group ID feature available on all modern utilize the existing subordinate user and group ID feature available on all modern
Linux distributions. Linux distributions.
The [`/etc/subuid`](http://man7.org/linux/man-pages/man5/subuid.5.html) and The [`/etc/subuid`](http://man7.org/linux/man-pages/man5/subuid.5.html) and
[`/etc/subgid`](http://man7.org/linux/man-pages/man5/subgid.5.html) files will be [`/etc/subgid`](http://man7.org/linux/man-pages/man5/subgid.5.html) files will be
read for the user, and optional group, specified to the `--userns-remap` read for the user, and optional group, specified to the `--userns-remap`
parameter. If you do not wish to specify your own user and/or group, you can parameter. If you do not wish to specify your own user and/or group, you can
provide `default` as the value to this flag, and a user will be created on your behalf provide `default` as the value to this flag, and a user will be created on your behalf
and provided subordinate uid and gid ranges. This default user will be named and provided subordinate uid and gid ranges. This default user will be named
`dockremap`, and entries will be created for it in `/etc/passwd` and `dockremap`, and entries will be created for it in `/etc/passwd` and
`/etc/group` using your distro's standard user and group creation tools. `/etc/group` using your distro's standard user and group creation tools.
> **Note**: The single mapping per-daemon restriction exists for this experimental > **Note**: The single mapping per-daemon restriction exists for this experimental
@ -43,7 +43,7 @@ values in the following formats:
If numeric IDs are provided, translation back to valid user or group names If numeric IDs are provided, translation back to valid user or group names
will occur so that the subordinate uid and gid information can be read, given will occur so that the subordinate uid and gid information can be read, given
these resources are name-based, not id-based. If the numeric ID information these resources are name-based, not id-based. If the numeric ID information
provided does not exist as entries in `/etc/passwd` or `/etc/group`, dameon provided does not exist as entries in `/etc/passwd` or `/etc/group`, daemon
startup will fail with an error message. startup will fail with an error message.
*An example: starting with default Docker user management:* *An example: starting with default Docker user management:*
@ -67,7 +67,7 @@ create the following range, based on an existing user already having the first
> **Note:** On a fresh Fedora install, we found that we had to `touch` the > **Note:** On a fresh Fedora install, we found that we had to `touch` the
> `/etc/subuid` and `/etc/subgid` files to have ranges assigned when users > `/etc/subuid` and `/etc/subgid` files to have ranges assigned when users
> were created. Once these files existed, range assigment on user creation > were created. Once these files existed, range assignment on user creation
> worked properly. > worked properly.
If you have a preferred/self-managed user with subordinate ID mappings already If you have a preferred/self-managed user with subordinate ID mappings already
@ -84,7 +84,7 @@ current experimental user namespace support.
The simplest case exists where only one contiguous range is defined for the The simplest case exists where only one contiguous range is defined for the
provided user or group. In this case, Docker will use that entire contiguous provided user or group. In this case, Docker will use that entire contiguous
range for the mapping of host uids and gids to the container process. This range for the mapping of host uids and gids to the container process. This
means that the first ID in the range will be the remapped root user, and the means that the first ID in the range will be the remapped root user, and the
IDs above that initial ID will map host ID 1 through the end of the range. IDs above that initial ID will map host ID 1 through the end of the range.

6
man/docker-events.1.md
View File

@ -37,11 +37,11 @@ and Docker images will report:
**--until**="" **--until**=""
Stream events until this timestamp Stream events until this timestamp
The `--since` and `--until` parameters can be Unix timestamps, date formated The `--since` and `--until` parameters can be Unix timestamps, date formatted
timestamps, or Go duration strings (e.g. `10m`, `1h30m`) computed timestamps, or Go duration strings (e.g. `10m`, `1h30m`) computed
relative to the client machine’s time. If you do not provide the --since option, relative to the client machine’s time. If you do not provide the --since option,
the command returns only new and/or live events. Supported formats for date the command returns only new and/or live events. Supported formats for date
formated time stamps include RFC3339Nano, RFC3339, `2006-01-02T15:04:05`, formatted time stamps include RFC3339Nano, RFC3339, `2006-01-02T15:04:05`,
`2006-01-02T15:04:05.999999999`, `2006-01-02Z07:00`, and `2006-01-02`. The local `2006-01-02T15:04:05.999999999`, `2006-01-02Z07:00`, and `2006-01-02`. The local
timezone on the client will be used if you do not provide either a `Z` or a timezone on the client will be used if you do not provide either a `Z` or a
`+-00:00` timezone offset at the end of the timestamp. When providing Unix `+-00:00` timezone offset at the end of the timestamp. When providing Unix
@ -49,7 +49,7 @@ timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap
seconds (aka Unix epoch or Unix time), and the optional .nanoseconds field is a seconds (aka Unix epoch or Unix time), and the optional .nanoseconds field is a
fraction of a second no more than nine digits long. fraction of a second no more than nine digits long.
# EXAMPLES # EXAMPLES
## Listening for Docker events ## Listening for Docker events

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

@ -48,7 +48,7 @@ the running containers.
.Ports - Exposed ports. .Ports - Exposed ports.
.Status - Container status. .Status - Container status.
.Size - Container disk size. .Size - Container disk size.
.Labels - All labels asigned to the container. .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 `{{.Label "com.docker.swarm.cpu"}}`
**--help** **--help**