easy-rsa/b93d0a1.patch

From b93d0a16759137d68f6ffbf9fd41e9de23eacb71 Mon Sep 17 00:00:00 2001
From: Drew Anderson <d.anderson@beovista.com.au>
Date: Mon, 9 May 2016 10:24:02 +1000
Subject: [PATCH] spelling fixes and setence structure improvements

---
 doc/EasyRSA-Advanced.md      | 2 +-
 doc/EasyRSA-Readme.md        | 6 +++---
 doc/EasyRSA-Upgrade-Notes.md | 2 +-
 doc/Intro-To-PKI.md          | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/EasyRSA-Advanced.md b/doc/EasyRSA-Advanced.md
index 6406946..64b29ae 100644
--- a/doc/EasyRSA-Advanced.md
+++ b/doc/EasyRSA-Advanced.md
@@ -108,7 +108,7 @@ possible terse description is shown below:
     extensions
  *  `EASYRSA_REQ_CN` (CLI: `--req-cn`) - default CN, necessary to set in BATCH
     mode
- *  `EASYRSA_DIGEST` (CLI: `--digest`) - set a hash diget to use for req/cert
+ *  `EASYRSA_DIGEST` (CLI: `--digest`) - set a hash digest to use for req/cert
     signing
  *  `EASYRSA_BATCH` (CLI: `--batch`) - enable batch (no-prompt) mode; set
     env-var to non-zero string to enable (CLI takes no options)
diff --git a/doc/EasyRSA-Readme.md b/doc/EasyRSA-Readme.md
index 568c3a6..bece589 100644
--- a/doc/EasyRSA-Readme.md
+++ b/doc/EasyRSA-Readme.md
@@ -74,7 +74,7 @@ Obtaining and Using Easy-RSA
   General usage and command help can be shown with:
 
     ./easyrsa help [ command ]
-  
+
   When run without any command, general usage and a list of available commands
   are shown; when a command is supplied, detailed help output for that command
   is shown.
@@ -135,7 +135,7 @@ you need a more basic description of how a PKI works.
 
   When building a CA, a number of new files are created by a combination of
   Easy-RSA and (indirectly) openssl. The important CA files are:
-  
+
   * `ca.crt` - This is the CA certificate
   * `index.txt` - This is the "master database" of all issued certs
   * `serial` - Stores the next serial number (serial numbers increment)
@@ -224,7 +224,7 @@ Easy-RSA can generate a keypair and request with the following command:
     ./easyrsa gen-req nameOfRequest
 
 You will then be given a chance to modify the Subject details of your request.
-By default Easy-RSA uses the short name supplied on the command-line, though you
+Easy-RSA uses the short name supplied on the command-line by default, though you
 are free to change it if necessary. After providing a passphrase and Subject
 details, the keypair and request files will be shown.
 
diff --git a/doc/EasyRSA-Upgrade-Notes.md b/doc/EasyRSA-Upgrade-Notes.md
index f5c1514..6cc6df2 100644
--- a/doc/EasyRSA-Upgrade-Notes.md
+++ b/doc/EasyRSA-Upgrade-Notes.md
@@ -54,5 +54,5 @@ Easy-RSA 3 has some new concepts compared to the prior v2 series.
   generation as the requester doesn't need to know the CA's values in advance.
 
   Previously in v2, the Country, State, and Org values all had to match or a
-  request couldn't be signed. If you want the old behavior your can change the
+  request couldn't be signed. If you want the old behavior you can change the
   OpenSSL config to require it or simply look over the DN at signing time.
diff --git a/doc/Intro-To-PKI.md b/doc/Intro-To-PKI.md
index cd8217b..ea56629 100644
--- a/doc/Intro-To-PKI.md
+++ b/doc/Intro-To-PKI.md
@@ -37,7 +37,7 @@ PKI mixed in with one used to generate end-entity certificates, such as clients
 or servers (VPN or web servers.)
 
 To start a new PKI, the CA is first created on the secure environment.
-Depending on security needs, this could managed under a locked down account,
+Depending on security needs, this could be managed under a locked down account,
 dedicated system, or even a completely offline system or using removable media
 to improve security (after all, you can't suffer an online break-in if your
 system or PKI is not online.) The exact steps to create a CA are described in a