From 13161a1722e6a7fb9af17296a1fc8cbd2927a211 Mon Sep 17 00:00:00 2001
From: wemeya <1013939285@qq.com>
Date: Thu, 7 Apr 2016 19:35:04 +0800
Subject: [PATCH] Update how to use your own certificate in harbor.md

edit the file
---
 ...w to use your own certificate in harbor.md | 29 ++++++++++---------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/docs/how to use your own certificate in harbor.md b/docs/how to use your own certificate in harbor.md
index 329b3c12e..978e6a685 100644
--- a/docs/how to use your own certificate in harbor.md	
+++ b/docs/how to use your own certificate in harbor.md	
@@ -1,17 +1,19 @@
 #How to use your own certificate in harbor?
 
-1.  If you already have a certificate, go to step 3.
+1.If you already have a certificate, go to step 3.
 
-2.  If not, you can generate a self-signed certificate using openSSL with following commands
+2.If not, you can generate a self-signed certificate using openSSL with following commands
     
-    1)	Generate a private key:
+    1)Generate a private key:
 
 ```sh
     openssl genrsa -out prvtkey.pem 2048    
 ```
+   
     you can call it prvtkey.pem or other names you like.
     
-    2)	Generate a certificate:
+   
+    2)Generate a certificate:
 
 ```sh
     openssl req -new -x509 -key prvtkey.pem -out cacert.pem -days 1095
@@ -19,24 +21,25 @@
    
     prvtkey.pem is what you generated in the first step, if you change the name, you should change it in the command. Also you can name cacert.pem what you like.
 
-3.  Clone harbor to your local position. Then open Deploy, and edit the harbor.cfg, make necessary configuration changes such as hostname, admin password and mail server. Refer to Installation Guide for more info. then execute ./prepare . Here, harbor generates several config files. We need to replace the original private key and certificate with your own key and certificate.
+3.Clone harbor to your local position. Then open Deploy, and edit the harbor.cfg, make necessary configuration changes such as hostname, admin password and mail server. Refer to Installation Guide for more info. then execute ./prepare . Here, harbor generates several config files. We need to replace the original private key and certificate with your own key and certificate.
 
-4.  Following are what you should do:
+4.Following are what you should do:
  
-    a. edit docker-compose.yml, find private_key.pem replace it with your own private key as following:
+    a.edit docker-compose.yml, find private_key.pem replace it with your own private key as following:
+
 
 ![edit docker-compose.yml](img/edit_docker-compose-yml.png)
 
 
-    b. cd config/ui, you will see private_key.pem.
+    b.cd config/ui, you will see private_key.pem.
     
-    c. replace private_key.pem with your private key.
+    c.replace private_key.pem with your private key.
     
-    d. cd ../registry, you will see root.crt. Replace it with your certificate.
+    d.cd ../registry, you will see root.crt. Replace it with your certificate.
  
-    e. at the same directory, you will see config.yml. We need to modify it, open it and find root.crt, then change it to your certificate.
+    e.at the same directory, you will see config.yml. We need to modify it, open it and find root.crt, then change it to your certificate.
 
-5.  After these, go back to harbor directory, execute:
+5.After these, go back to harbor directory, execute:
 
 ```sh
        docker-compose build
@@ -45,6 +48,6 @@
        docker-compose up –d  
 ```
 
-6.  Then you can push/pull images to see if your own certificate works. Please refer [User Guide](https://github.com/vmware/harbor/blob/master/docs/user_guide.md)
+6.Then you can push/pull images to see if your own certificate works. Please refer [User Guide](https://github.com/vmware/harbor/blob/master/docs/user_guide.md)