From 86062d9592aab55d8ce204576ce0a9d798d0a41f Mon Sep 17 00:00:00 2001
From: timchenxiaoyu <837829664@qq.com>
Date: Tue, 16 May 2017 17:19:08 +0800
Subject: [PATCH] docs error

fix #1347
---
 docs/configure_https.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/configure_https.md b/docs/configure_https.md
index 0c3641066..220062e0f 100644
--- a/docs/configure_https.md
+++ b/docs/configure_https.md
@@ -83,8 +83,8 @@ After setting up HTTPS for Harbor, you can verify it by the following steps:
 
 1. Open a browser and enter the address: https://reg.yourdomain.com . It should display the user interface of Harbor.
 
-2. On a machine with Docker daemon, make sure the option "-insecure-registry" does not present, and you must copy ca.crt generated in the above step to /etc/docker/certs.d/yourdomain.com(or your registry host IP), if the directory does not exist, create it.
-If you mapped nginx port 443 to another port, then you should instead create the directory /etc/docker/certs.d/yourdomain.com:port(or your registry host IP:port). Then run any docker command to verify the setup, e.g. 
+2. On a machine with Docker daemon, make sure the option "-insecure-registry" does not present, and you must copy ca.crt generated in the above step to /etc/docker/certs.d/reg.yourdomain.com(or your registry host IP), if the directory does not exist, create it.
+If you mapped nginx port 443 to another port, then you should instead create the directory /etc/docker/certs.d/reg.yourdomain.com:port(or your registry host IP:port). Then run any docker command to verify the setup, e.g. 
 
 ```
   docker login reg.yourdomain.com