Skip to content

Commit d217da8

Browse files
SvenDowideitArnaud Porterie
authored andcommitted
Spelling mistake in dockerlinks
Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
1 parent d74d6d9 commit d217da8

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/sources/reference/commandline/cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ for un-encrypted, and port `2376` for encrypted communication with the daemon.
139139
> for security reasons.
140140
141141
On Systemd based systems, you can communicate with the daemon via
142-
[systemd socket activation](http://0pointer.de/blog/projects/socket-activation.html), use
142+
[Systemd socket activation](http://0pointer.de/blog/projects/socket-activation.html), use
143143
`docker -d -H fd://`. Using `fd://` will work perfectly for most setups but
144144
you can also specify individual sockets: `docker -d -H fd://3`. If the
145145
specified socket activated files aren't found, then Docker will exit. You

docs/sources/userguide/dockerlinks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -233,7 +233,7 @@ command to list the specified container's environment variables.
233233
> will scrub them when spawning shells for connection.
234234
235235
> **Note**:
236-
> Unlike host entries in the [`/ets/hosts` file](#updating-the-etchosts-file),
236+
> Unlike host entries in the [`/etc/hosts` file](#updating-the-etchosts-file),
237237
> IP addresses stored in the environment variables are not automatically updated
238238
> if the source container is restarted. We recommend using the host entries in
239239
> `/etc/hosts` to resolve the IP address of linked containers.

0 commit comments

Comments
 (0)