# changes ssl_keys_https.md (#1448)

* suggested changes
* sentence style capitalization on all headings
* change "we" and "our" to "you" and "your" where appropriate
* replace conjunctions with words
* remove passive voice
* add <kbd></kbd> tags for the ENTER commands

Author: sspencerwire

docs/guides/security/ssl_keys_https.md

@@ -9,88 +9,87 @@ tags:
   - openssl
 ---
 
-# Generating SSL Keys
+# Generating SSL/TLS keys
 
 ## Prerequisites
 
-* A workstation and a server running Rocky Linux (OK, Linux, but really, you want Rocky Linux, right?)
-* _OpenSSL_ installed on the machine that you are going to be generating the private key and CSR, as well as on the server where you will eventually be installing your key and certificates
+* A workstation and a server running Rocky Linux 
+* _OpenSSL_ installed on the machine that you are going to be generating the private key and CSR (Certificate Signing Request), and on the server where you will eventually be installing your key and certificates
 * Able to run commands comfortably from the command-line
-* Helpful: knowledge of SSL and OpenSSL commands
+* Helpful: knowledge of SSL/TLS and OpenSSL commands
 
 
 ## Introduction
 
-Nearly every web site today _should_ be running with an SSL (secure socket layer) certificate. This procedure will guide you through generating the private key for your web site and then from this, generating the CSR (certificate signing request) that you will use to purchase your new certificate.
+Nearly every web site today _should_ be running with an SSL/TLS (secure socket layer) certificate. This procedure will guide you through generating the private key for your web site and then generating the CSR (certificate signing request) that you will use to purchase your certificate.
 
-## Generate The Private Key
+## Generate the private key
 
-For the uninitiated, SSL private keys can have different sizes, measured in bits, which basically determines how hard they are to crack.
+For the uninitiated, SSL/TLS private keys can have different sizes, measured in bits, determining how hard they are to crack.
 
-As of 2021, the recommended private key size for a web site is still 2048 bits. You can go higher, but doubling the key size from 2048 bits to 4096 bits is only about 16% more secure, takes more space to store the key, and causes higher CPU loads when the key is processed.
+As of 2021, a website's recommended private key size is still 2048 bits. You can go higher, but doubling the key size from 2048 bits to 4096 bits is only about 16% more secure, takes more space to store the key, and causes higher CPU loads when processing the key.
 
-This slows down your web site performance without gaining any significant security. Stick with the 2048 key size for now and always keep tabs on what is currently recommended.
-
-To start with, let's make sure that OpenSSL is installed on both your workstation and server:
+This slows down your web site performance without gaining any significant security. Stick with the 2048 key size and always keep tabs on what is currently recommend
+To start with, ensure the installation of OpenSSL on your workstation and server:
 
 `dnf install openssl`
 
 If it is not installed, your system will install it and any needed dependencies.
 
-Our example domain is example.com. Keep in mind that you would need to purchase and register your domain ahead of time. You can purchase domains through a number of "Registrars".
+The example domain is "example.com." Remember that you will need to purchase and register your domain beforehand. You can purchase domains through several "Registrars".
 
 If you are not running your own DNS (Domain Name System), you can often use the same providers for DNS hosting. DNS translates your named domain, to numbers (IP addresses, either IPv4 or IPv6) that the Internet can understand. These IP addresses will be where the web site is actually hosted.
 
-Let's generate the key using openssl:
+Generate the key using `openssl`:
 
 `openssl genrsa -des3 -out example.com.key.pass 2048`
 
-Note that we named the key, with a .pass extension. That's because as soon as we execute this command, it requests that you enter a passphrase. Enter a simple passphrase that you can remember as we are going to be removing this shortly:
+Note that you named the key, with a *.pass* extension. That is because when you run this command, it requests that you enter a passphrase. Enter a simplistic passphrase that you can remember as you are going to be removing this shortly:
 
 ```
 Enter pass phrase for example.com.key.pass:
 Verifying - Enter pass phrase for example.com.key.pass:
 ```
 
-Next, let's remove that passphrase. The reason for this is that if you don't remove it, each time your web server restarts and loads up your key, you will need to enter that passphrase.
+Next, remove that passphrase. This is because if you do not remove it, you will need to enter that passphrase each time your website restarts and loads up your key.
 
-You might not even be around to enter it, or worse, might not have a console at the ready to enter it. Remove it now to avoid all of that:
+You might not even be around to enter it, or worse, might not have a console available. Remove it now to avoid all of that:
 
 `openssl rsa -in example.com.key.pass -out example.com.key`
 
 This will request that passphrase once again to remove the passphrase from the key:
 
 `Enter pass phrase for example.com.key.pass:`
 
-Now that you have entered the passphrase a third time, it has been removed from the key file and saved as example.com.key
+Your password is now removed from the key now that you have entered the passphrase a third time, and saved as *example.com.key*
 
 ## Generate the CSR
 
-Next, we need to generate the CSR (certificate signing request) that we will use to purchase our certificate.
+Next, you need to generate the CSR (certificate signing request) that you will use to purchase your certificate.
 
-During the generation of the CSR, you will be prompted for several pieces of information. These are the X.509 attributes of the certificate.
+Prompting for several pieces of information occurs during the generation of the CSR. These are the X.509 attributes of the certificate.
 
-One of the prompts will be for "Common Name (e.g., YOUR name)". It is important that this field be filled in with the fully qualified domain name of the server to be protected by SSL. If the website to be protected will be https://www.example.com, then enter www.example.com at this prompt:
+One of the prompts will be for "Common Name (e.g., YOUR domain name)". This field must have the fully qualified domain name of the server that the SSL/TLS is protecting. If the website to be protected will be https://www.example.com, then enter www.example.com at this prompt:
 
 `openssl req -new -key example.com.key -out example.com.csr`
 
 This opens up a dialog:
 
-`Country Name (2 letter code) [XX]:` enter the two character country code where your site resides, example "US"
+`Country Name (2 letter code) [XX]:` enter the two character country code where your site resides, for example "US"
 
-`State or Province Name (full name) []:` enter the full official name of your state or province, example "Nebraska"
+`State or Province Name (full name) []:` enter the full official name of your state or province, for example "Nebraska"
 
-`Locality Name (eg, city) [Default City]:` enter the full city name, example "Omaha"
+`Locality Name (eg, city) [Default City]:` enter the full city name, for example "Omaha"
 
-`Organization Name (eg, company) [Default Company Ltd]:` If you want, you can enter an organization that this domain is a part of, or just hit 'Enter' to skip.
+`Organization Name (eg, company) [Default Company Ltd]:` If you want, you can enter an organization that this domain is a part of, or just hit <kbd>ENTER</kbd> to skip.
 
-`Organizational Unit Name (eg, section) []:` This would describe the division of the organization that your domain falls under. Again, you can just hit 'Enter' to skip.
+`Organizational Unit Name (eg, section) []:` This would describe the division of the organization that your domain falls under. Again, you can just hit <kbd>ENTER</kbd> to skip.
 
-`Common Name (eg, your name or your server's hostname) []:` Here, we have to enter our site hostname, example "www.example.com"
+`Common Name (eg, your name or your server's hostname) []:` Here, you have to enter your site hostname, example "www.example.com"
 
-`Email Address []:` This field is optional, you can decide to fill it out or just hit 'Enter' to skip.
+`Email Address []:` This field is optional, you can decide to fill it out or just hit <kbd>ENTER</kbd> to skip.
 
-Next, you will be asked to enter extra attributes which can be skipped by hitting 'Enter' through both:
+Next, the procedure prompts you to enter extra attributes. Skipping these is possible by hitting <kbd>ENTER</kbd>:
 
 ```
 Please enter the following 'extra' attributes
@@ -99,11 +98,11 @@ A challenge password []:
 An optional company name []:
 ```
 
-Now you should have generated your CSR.
+Generating of your CSR is complete.
 
-## Purchasing The Certificate
+## Purchasing the certificate
 
-Each certificate vendor will have basically the same procedure. You purchase the SSL and term (1 or 2 years, etc.) and then you submit your CSR. To do this, you will need to use the `more` command, and then copy the contents of your CSR file.
+Each certificate vendor will have basically the same procedure. You purchase the SSL/TLS and term (1 or 2 years, etc.) and then you submit your CSR. To do this, you will need to use the `more` command, and then copy the contents of your CSR file.
 
 `more example.com.csr`
 
@@ -131,8 +130,9 @@ HFOltYOnfvz6tOEP39T/wMo=
 
 You want to copy everything including the "BEGIN CERTIFICATE REQUEST" and "END CERTIFICATE REQUEST" lines. Then paste these into the CSR field on the web site where you are purchasing the certificate.
 
-You may have to perform other verification steps, depending on ownership of the domain, the registrar you are using, etc., before your certificate is issued. When it is issued, it should be issued along with an intermediate certificate from the provider, which you will use in the configuration as well.
+Before issuing your certificate, You may have to perform other verification steps depending on domain ownership, the registrar you are using, etc. When issued, it will include an intermediate certificate from the provider, which you will also use in the configuration.
 
 ## Conclusion
 
-Generating all of the bits and pieces for the purchase of a web site certificate is not terribly difficult and can be performed by the systems administrator or web site administrator using the above procedure.
+Generating all of the bits and pieces for purchasing a web site certificate is not difficult using this procedure.
+