From 43a1cb05a4a1776572fa507d3d17221d76fe278b Mon Sep 17 00:00:00 2001
From: L-Hudson <44844738+L-Hudson@users.noreply.github.com>
Date: Fri, 7 Dec 2018 15:39:01 -0500
Subject: [PATCH] Update https.md

editorial crx
---
 engine/security/https.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/engine/security/https.md b/engine/security/https.md
index e0d4ed7132..18376b4a93 100644
--- a/engine/security/https.md
+++ b/engine/security/https.md
@@ -7,10 +7,10 @@ redirect_from:
 title: Protect the Docker daemon socket
 ---
 
-By default, Docker runs via a non-networked Unix socket. It can also
+By default, Docker runs through a non-networked UNIX socket. It can also
 optionally communicate using an HTTP socket.
 
-If you need Docker to be reachable via the network in a safe manner, you can
+If you need Docker to be reachable through the network in a safe manner, you can
 enable TLS by specifying the `tlsverify` flag and pointing Docker's
 `tlscacert` flag to a trusted CA certificate.
 
@@ -73,7 +73,7 @@ to connect to Docker:
 
 Next, we're going to sign the public key with our CA:
 
-Since TLS connections can be made via IP address as well as DNS name, the IP addresses
+Since TLS connections can be made through IP address as well as DNS name, the IP addresses
 need to be specified when creating the certificate. For example, to allow connections
 using `10.10.10.20` and `127.0.0.1`:
 
@@ -180,7 +180,7 @@ certificates and trusted CA:
 ## Secure by default
 
 If you want to secure your Docker client connections by default, you can move
-the files to the `.docker` directory in your home directory -- and set the
+the files to the `.docker` directory in your home directory --- and set the
 `DOCKER_HOST` and `DOCKER_TLS_VERIFY` variables as well (instead of passing
 `-H=tcp://$HOST:2376` and `--tlsverify` on every call).