mirror of https://github.com/docker/cli.git
Additional typo corrections
Signed-off-by: Iain MacDonald <ijmacd@gmail.com> Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
This commit is contained in:
parent
a84536eb4a
commit
64c20f3013
|
@ -46,7 +46,7 @@ The `until` filter 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 daemon machine’s time. Supported formats for date
|
relative to the daemon machine’s time. Supported formats for date
|
||||||
formatted 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-02T07:00`, and `2006-01-02`. The local
|
||||||
timezone on the daemon will be used if you do not provide either a `Z` or a
|
timezone on the daemon 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
|
||||||
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
||||||
|
|
|
@ -69,7 +69,7 @@ The `until` filter 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 daemon machine’s time. Supported formats for date
|
relative to the daemon machine’s time. Supported formats for date
|
||||||
formatted 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-02T07:00`, and `2006-01-02`. The local
|
||||||
timezone on the daemon will be used if you do not provide either a `Z` or a
|
timezone on the daemon 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
|
||||||
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
||||||
|
|
|
@ -44,7 +44,7 @@ The `until` filter 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 daemon machine’s time. Supported formats for date
|
relative to the daemon machine’s time. Supported formats for date
|
||||||
formatted 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-02T07:00`, and `2006-01-02`. The local
|
||||||
timezone on the daemon will be used if you do not provide either a `Z` or a
|
timezone on the daemon 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
|
||||||
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
||||||
|
|
|
@ -63,7 +63,7 @@ The `--since` option shows only the service logs generated after
|
||||||
a given date. You can specify the date as an RFC 3339 date, a UNIX
|
a given date. You can specify the date as an RFC 3339 date, a UNIX
|
||||||
timestamp, or a Go duration string (e.g. `1m30s`, `3h`). Besides RFC3339 date
|
timestamp, or a Go duration string (e.g. `1m30s`, `3h`). Besides RFC3339 date
|
||||||
format you may also use RFC3339Nano, `2006-01-02T15:04:05`,
|
format you may also use RFC3339Nano, `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-02T07: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
|
||||||
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
||||||
|
|
|
@ -148,7 +148,7 @@ 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
|
||||||
formatted 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-02T07: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
|
||||||
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
||||||
|
|
|
@ -24,7 +24,7 @@ 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
|
||||||
formatted 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-02T07: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
|
||||||
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
|
||||||
|
|
Loading…
Reference in New Issue