Correct readme typographic errors

Author: leschan

1-Create_S3_Bucket/README.md

@@ -2,7 +2,7 @@
 
 In this step you will stage a private Amazon S3 bucket with a sample HTML file.
 
-**Note**: Amazon S3 routes any virtual hosted–style requests to the US East (N. Virginia) region by default if you use the US East (N. Virginia) endpoint (s3.amazonaws.com), When you create a new bucket, in any region, Amazon S3 updates DNS to reroute the request to the correct region, which might take time when using Amazon CloudFront for distribution in later section. For the purpose of this exercise, you will create a new bucket in AWS **region** `us-east-1`. Detailed explanation of **AWS Virtual hosting of buckets** is provided in [AWS User Guide](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html).
+**Note**: Amazon S3 routes any virtual hosted–style requests to the US East (N. Virginia) region by default if you use the US East (N. Virginia) endpoint (s3.amazonaws.com). When you create a new bucket, in any region, Amazon S3 updates DNS to reroute the request to the correct region, which might take time when using Amazon CloudFront for distribution in later section. For the purpose of this exercise, you will create a new bucket in AWS **region** `us-east-1`. Detailed explanation of **AWS Virtual hosting of buckets** is provided in [AWS User Guide](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html).
 
 ### Create S3 Bucket
 1. Log into your AWS account and navigate to the [Amazon S3 Management Console](https://s3.console.aws.amazon.com/).
@@ -17,6 +17,6 @@ In this step you will stage a private Amazon S3 bucket with a sample HTML file.
 10. Choose the included sample file `sample.html` from your local drive.
 11. Choose **Upload** to upload the file.
 
-You successfully created an Amazon S3 bucket and uploaded a sample HTML file. However if you try to access the sample HTML file using the S3 object URL, like `https://yourbucket.s3-us-west-2.amazonaws.com/sample.html`, in your browser you will get an access denied message. This is exactly what you want. You want to keep your S3 contents private and will only distribute them using an Amazon CloudFront distribution.
+You successfully created an Amazon S3 bucket and uploaded a sample HTML file. However if you try to access the sample HTML file using the S3 object URL, like `https://yourbucket.s3-us-east-1.amazonaws.com/sample.html`, in your browser you will get an access denied message. This is exactly what you want. You want to keep your S3 contents private and will only distribute them using an Amazon CloudFront distribution.
 
 In [Step 2](../2-Create_CloudFront_Distribution/README.md), you will create the Amazon CloudFront Distribution.

3-Create_CloudFront_Key_Groups/README.md

@@ -7,7 +7,7 @@ In this step you will create a trusted [CloudFront key group](https://docs.aws.a
 
 
 ### Create Key Pair
-The following steps use OpenSSL as an example of one way to create a key pair. There are many other ways to create an RSA key pair.
+There are different ways to create an RSA key pair. The following steps use OpenSSL to create a key pair.
 1. The following example command uses OpenSSL to generate an RSA key pair with a length of 2048 bits and save to the file named `private_key.pem`.
 ```
 $ openssl genrsa -out private_key.pem 2048
@@ -21,12 +21,10 @@ $ openssl rsa -pubout -in private_key.pem -out public_key.pem
 1. On [Amazon CloudFront Management Console](https://console.aws.amazon.com/cloudfront)
 2. In the navigation menu, choose **Public keys**.
 3. Choose **Add public key**.
-4. In the **Add public key** window, do the following:
+4. In the **Add public key** window, complete the following and choose **Add**.
   - For **Key name**, type a name to identify the public key.
   - For **Key value**, copy and paste the contents of the public key. If you followed the steps in the preceding procedure, the public key is in the file named `public_key.pem`.
   - (Optional) For **Comment**, add a comment to describe the public key.  
-
-  When finished, choose **Add**.
 5. Record the public key ID. You will use it later section.
 
 ### Create Key group

6-Create_CloudFront_SignedURL_Custom/README.md

@@ -65,7 +65,7 @@ Since the newly created Lambda role does **NOT** have permission to access **AWS
 6. In the browser, replace `"*"` with `"sample.html"` and hit enter. The webpage should render correctly now.
 7. Let's do another test by uploading a new file `"newsample.html"` to your Amazon S3 bucket.
 8. In the browser, replace `"sample.html"` with `"newsample.html"` and hit enter. The new webpage should render correctly as well.
-9. Try changing the date or IP address and see how it affect the access.
+9. Try changing the date or IP address and see how it affects the access.
 
 With a custom policy using a wildcard `*`, you can use the signed URL with multiple files based on matching pattern. In the example above where we used an URL `"https://d1xxxxxxxxxxxx.cloudfront.net/*"`, any of the URLs below would work: