Merged paul-porter:patch-1 into master

Original author: https://github.com/paul-porter
Original branch: https://github.com/paul-porter/aws-mfa/tree/patch-1
Original PR: broamski#38

Author: Andrew Wheal

README.md

@@ -5,7 +5,7 @@ aws-mfa: Easily manage your AWS Security Credentials when using Multi-Factor Aut
 
 The concept behind **aws-mfa** is that there are 2 types of credentials:
 
-* `long-term` - Your typcial AWS access keys, consisting of an `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`
+* `long-term` - Your typical AWS access keys, consisting of an `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`
 
 * `short-term` - A temporary set of credentials that are generated by AWS STS using your `long-term` credentials in combination with your MFA device serial number (either a hardware device serial number or virtual device ARN) and one time token code. Your short term credentials are the credentials that are actively utilized by the AWS SDK in use.
 
@@ -31,7 +31,7 @@ Credentials File Setup
 
 In a typical AWS credentials file (located at `~/.aws/credentials`), credentials are stored in sections, denoted by a pair of brackets: `[]`. The `[default]` section stores your default credentials. You can store multiple sets of credentials using different profile names. If no profile is specified, the `[default]` section is always used.
 
-By default long term credential sections are identified by the convention `[<profile_name>-long-term]` and short term credentials are identified by the typical convention: `[<profile_name>]`. The following illustrates how you would configure you credentials file using **aws-mfa** with your default credentials:
+By default, long term credential sections are identified by the convention `[<profile_name>-long-term]` and short term credentials are identified by the typical convention: `[<profile_name>]`. The following illustrates how you would configure your credentials file using **aws-mfa** with your default credentials:
 
 ```ini
 [default-long-term]
@@ -286,4 +286,4 @@ INFO - Success! Your credentials will expire in 3600 seconds at: 2017-07-10 07:1
 $> aws s3 list-objects —bucket my-production-bucket —profile myorganization-production
 
 $> aws s3 list-objects —bucket my-staging-bucket —profile myorganization-staging
-```
+```