From 705e3d1c4bb776f1fbc25d070186145aa544ed5a Mon Sep 17 00:00:00 2001 From: nsymms Date: Fri, 12 Aug 2016 09:04:18 -0500 Subject: [PATCH 1/2] Simple grammar fixes --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 0f6d63c1..c8768d53 100644 --- a/README.md +++ b/README.md @@ -485,7 +485,7 @@ Please refer the [Available Configuration Parameters](#available-configuration-p ### SSL -Access to the gitlab application can be secured using SSL so as to prevent unauthorized access to the data in your repositories. While a CA certified SSL certificate allows for verification of trust via the CA, a self signed certificates can also provide an equal level of trust verification as long as each client takes some additional steps to verify the identity of your website. I will provide instructions on achieving this towards the end of this section. +Access to the gitlab application can be secured using SSL so as to prevent unauthorized access to the data in your repositories. While a CA certified SSL certificate allows for verification of trust via the CA, a self signed certificate can also provide an equal level of trust verification as long as each client takes some additional steps to verify the identity of your website. I will provide instructions on achieving this towards the end of this section. Jump to the [Using HTTPS with a load balancer](#using-https-with-a-load-balancer) section if you are using a load balancer such as hipache, haproxy or nginx. @@ -495,9 +495,9 @@ To secure your application via SSL you basically need two things: When using CA certified certificates, these files are provided to you by the CA. When using self-signed certificates you need to generate these files yourself. Skip to [Strengthening the server security](#strengthening-the-server-security) section if you are armed with CA certified SSL certificates. -#### Generation of Self Signed Certificate +#### Generation of a Self Signed Certificate -Generation of self-signed SSL certificate involves a simple 3-step procedure: +Generation of a self-signed SSL certificate involves a simple 3-step procedure: **STEP 1**: Create the server private key @@ -517,7 +517,7 @@ openssl req -new -key gitlab.key -out gitlab.csr openssl x509 -req -days 3650 -in gitlab.csr -signkey gitlab.key -out gitlab.crt ``` -Congratulations! You now a self-signed SSL certificate valid for 10 years. +Congratulations! You now have a self-signed SSL certificate valid for 10 years. #### Strengthening the server security From 9a4708e05cbc11497f48231e2163b8a0583c6a03 Mon Sep 17 00:00:00 2001 From: nsymms Date: Fri, 12 Aug 2016 10:09:03 -0500 Subject: [PATCH 2/2] Fix TOC in Readme.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c8768d53..74b0b6ac 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ - [Mail](#mail) - [Reply by email](#reply-by-email) - [SSL](#ssl) - - [Generation of Self Signed Certificate](#generation-of-self-signed-certificate) + - [Generation of a Self Signed Certificate](#generation-of-a-self-signed-certificate) - [Strengthening the server security](#strengthening-the-server-security) - [Installation of the SSL Certificates](#installation-of-the-ssl-certificates) - [Enabling HTTPS support](#enabling-https-support)