diff --git a/docs/sources/reference/commandline/cli.md b/docs/sources/reference/commandline/cli.md
index d6b3824a86..73e6f5e789 100644
--- a/docs/sources/reference/commandline/cli.md
+++ b/docs/sources/reference/commandline/cli.md
@@ -139,7 +139,7 @@ for un-encrypted, and port `2376` for encrypted communication with the daemon.
 > for security reasons.
 
 On Systemd based systems, you can communicate with the daemon via
-[systemd socket activation](http://0pointer.de/blog/projects/socket-activation.html), use
+[Systemd socket activation](http://0pointer.de/blog/projects/socket-activation.html), use
 `docker -d -H fd://`. Using `fd://` will work perfectly for most setups but
 you can also specify individual sockets: `docker -d -H fd://3`. If the
 specified socket activated files aren't found, then Docker will exit. You
diff --git a/docs/sources/userguide/dockerlinks.md b/docs/sources/userguide/dockerlinks.md
index 0249e751dc..f35f61ecfc 100644
--- a/docs/sources/userguide/dockerlinks.md
+++ b/docs/sources/userguide/dockerlinks.md
@@ -233,7 +233,7 @@ command to list the specified container's environment variables.
 > will scrub them when spawning shells for connection.
 
 > **Note**:
-> Unlike host entries in the [`/ets/hosts` file](#updating-the-etchosts-file),
+> Unlike host entries in the [`/etc/hosts` file](#updating-the-etchosts-file),
 > IP addresses stored in the environment variables are not automatically updated
 > if the source container is restarted. We recommend using the host entries in
 > `/etc/hosts` to resolve the IP address of linked containers.