From a51554988e615b317e95125f5612a28c3bff8e8a Mon Sep 17 00:00:00 2001 From: Lorenz Leutgeb Date: Thu, 22 Jan 2015 21:46:01 +0100 Subject: [PATCH] Fix inconsistent formatting Colon was bold, but regular at other occurences. Blame cf27b310c4fc8d2c13ba181398a628d03e1e3c58 Signed-off-by: Lorenz Leutgeb --- docs/sources/articles/https.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sources/articles/https.md b/docs/sources/articles/https.md index 775573ec33..8fb0bb869c 100644 --- a/docs/sources/articles/https.md +++ b/docs/sources/articles/https.md @@ -26,7 +26,7 @@ it will only connect to servers with a certificate signed by that CA. ## Create a CA, server and client keys with OpenSSL -> **Note:** replace all instances of `$HOST` in the following example with the +> **Note**: replace all instances of `$HOST` in the following example with the > DNS name of your Docker daemon's host. First generate CA private and public keys: @@ -59,7 +59,7 @@ Now that we have a CA, you can create a server key and certificate signing request (CSR). Make sure that "Common Name" (i.e., server FQDN or YOUR name) matches the hostname you will use to connect to Docker: -> **Note:** replace all instances of `$HOST` in the following example with the +> **Note**: replace all instances of `$HOST` in the following example with the > DNS name of your Docker daemon's host. $ openssl genrsa -out server-key.pem 2048 @@ -129,7 +129,7 @@ providing a certificate trusted by our CA: To be able to connect to Docker and validate its certificate, you now need to provide your client keys, certificates and trusted CA: -> **Note:** replace all instances of `$HOST` in the following example with the +> **Note**: replace all instances of `$HOST` in the following example with the > DNS name of your Docker daemon's host. $ docker --tlsverify --tlscacert=ca.pem --tlscert=cert.pem --tlskey=key.pem \