docs: Run *.md documents through Grammer.ly (#757)

Author: danimart1991

CHANGELOG.md

@@ -215,11 +215,11 @@ All notable changes to this project will be documented in this file.
 - [PR #518](https://github.com/sendgrid/sendgrid-csharp/pull/518) README improvements. Big thanks to [Matt Bernier](https://github.com/mbernier) for the PR!
 
 ## Fixed
-- [PR #735](https://github.com/sendgrid/sendgrid-csharp/pull/735) Fix #418 groupsToDisplay shold be optional.
-- [PR #719](https://github.com/sendgrid/sendgrid-csharp/pull/719) Update travis config to use relative path. Big thanks to [Maxim Rubis](https://github.com/siburny) for the PR!
+- [PR #735](https://github.com/sendgrid/sendgrid-csharp/pull/735) Fix #418 groupsToDisplay should be optional.
+- [PR #719](https://github.com/sendgrid/sendgrid-csharp/pull/719) Update travis config to use a relative path. Big thanks to [Maxim Rubis](https://github.com/siburny) for the PR!
 - [PR #702](https://github.com/sendgrid/sendgrid-csharp/pull/702) Fixed virtual bug. Big thanks to [Phil](https://github.com/psboies) for the PR!
 - [PR #700](https://github.com/sendgrid/sendgrid-csharp/pull/700) Add default value for SubstitutionTag parameter. Big thanks to [Vedant Koditkar](https://github.com/KoditkarVedant) for the PR!
-- [PR #688](https://github.com/sendgrid/sendgrid-csharp/pull/688) Fix mixup of Response.Body and Response.Header summarie. Big thanks to [Ryan David Sheasb](https://github.com/ryan27968) for the PR!
+- [PR #688](https://github.com/sendgrid/sendgrid-csharp/pull/688) Fix mixup of Response.Body and Response.Header summary. Big thanks to [Ryan David Sheasb](https://github.com/ryan27968) for the PR!
 - [PR #635](https://github.com/sendgrid/sendgrid-csharp/pull/635) Fixed "Variable assigned but never used" issue. Big thanks to [Unlocked](https://github.com/TheUnlocked) for the PR!
 - [PR #615](https://github.com/sendgrid/sendgrid-csharp/pull/615) Update USAGE.md - fix typo. Big thanks to [Anvesh Chaturvedi](https://github.com/anveshc05) for the PR!
 - [PR #613](https://github.com/sendgrid/sendgrid-csharp/pull/613) Update CONTRIBUTING.md - fix typo. Big thanks to [thepriefy](https://github.com/thepriefy) for the PR!

CONTRIBUTING.md

@@ -13,7 +13,7 @@ All third party contributors acknowledge that any contributions they provide wil
 - [Code Reviews](#code-reviews)
 
 <a name="roadmap"></a>
-We use [GitHub Projects](https://github.com/sendgrid/sendgrid-csharp/projects) to help define current roadmaps, please feel free to grab an issue from our [GitHub Issues](https://github.com/sendgrid/sendgrid-csharp/issues). Please indicate that you have begun work on it to avoid collisions. Once a PR is made, community review, comments, suggestions and additional PRs are welcomed and encouraged.
+We use [GitHub Projects](https://github.com/sendgrid/sendgrid-csharp/projects) to help define current roadmaps, please feel free to grab an issue from our [GitHub Issues](https://github.com/sendgrid/sendgrid-csharp/issues). Please indicate that you have begun work on it to avoid collisions. Once a PR is made, community review, comments, suggestions, and additional PRs are welcomed and encouraged.
 
 There are a few ways to contribute, which we'll enumerate below:
 
@@ -36,8 +36,8 @@ A software bug is a demonstrable issue in the code base. In order for us to diag
 
 Before you decide to create a new issue, please try the following:
 
-1. Check the Github issues tab if the identified issue has already been reported, if so, please add a +1 to the existing post.
-2. Update to the latest version of this code and check if issue has already been fixed
+1. Check the GitHub issues tab if the identified issue has already been reported, if so, please add a +1 to the existing post.
+2. Update to the latest version of this code and check if the issue has already been fixed
 3. Copy and fill in the Bug Report Template we have provided below
 
 ### Please use our Bug Report Template
@@ -132,7 +132,7 @@ Generally, we follow the style guidelines as suggested by the official language.
    git pull upstream <dev-branch>
    ```
 
-3. Create a new topic branch off the `development` branch to
+3. Create a new topic branch (off the main project development branch) to
    contain your feature, change, or fix:
 
    ```bash
@@ -167,4 +167,4 @@ Generally, we follow the style guidelines as suggested by the official language.
 <a name="code-reviews"></a>
 ## Code Reviews
 
-If you can, please look at open PRs and review them. Give feedback and help us merge these PRs much faster! If you don't know how, Github has some great information on how to review a Pull Request.
+If you can, please look at open PRs and review them. Give feedback and help us merge these PRs much faster! If you don't know how GitHub has some great information on how to review a Pull Request.

ExampleNet45ASPNetProject/README.md

@@ -1,4 +1,4 @@
-**The Twilio SendGrid C# .NET library provide an easy way to send emails. This example application shows how to integrate with an ASP.NET application.**
+**The Twilio SendGrid C# .NET library provides an easy way to send emails. This example application shows how to integrate with an ASP.NET application.**
 
 # Installation
 
@@ -7,20 +7,20 @@
 - .NET version 4.5.2 and higher
 - Visual Studio 2015
 
-##  Setup Environment Variables
+## Setup Environment Variables
 
 Update the "SendGridApiKey" appSettings variable within the web.config file.
 
 ## Steps
 
 1. Open SendGrid.ASPSamples.sln
-2. Switch to one of the example project (right click on a project -> "Set as StartUp project")
-2. Build and run the project
+2. Switch to one of the example project (right-click on a project -> "Set as StartUp project")
+3. Build and run the project
 
-You may need to download the latest Nuget executable and run `nuget.exe restore`
+    You may need to download the latest Nuget executable and run `nuget.exe restore`
 
-3. When you run the project, a web form will launch in your browser that will send an email.
+4. When you run the project, a web form will launch in your browser that will send an email.
 
 ## Happy coding
 
-Big thanks to [paritosh baghel](https://github.com/paritoshmmmec) for contributing this example code!
+Big thanks to [paritosh baghel](https://github.com/paritoshmmmec) for contributing this example code!

README.md

@@ -73,14 +73,14 @@ Setup Environment Variables using the UI:
 1. Press Win+R and run SystemPropertiesAdvanced
 2. Click on Environment Variables
 3. Click New in user variables section
-4. Type SENDGRID_API_KEY in the name. (Make sure this name matches the name of key in your code)
+4. Type SENDGRID_API_KEY in the name. (Make sure this name matches the name of the key in your code)
 5. Type actual API Key in the value
 6. Restart the IDE and you're done!
 
 Setup Environment Variables using CMD:
 
 1. Run CMD as administrator
-2. setx SENDGRID_API_KEY "YOUR_API_KEY"
+2. set SENDGRID_API_KEY "YOUR_API_KEY"
 
 Here are a few examples to get and set API Keys programmatically:
 

TROUBLESHOOTING.md

@@ -1,4 +1,4 @@
-If you have an issue logging into your Twilio SendGrid account, please read this [document](https://sendgrid.com/docs/ui/account-and-settings/troubleshooting-login/). For any questions regarding login issues, please contact our [support team](https://support.sendgrid.com).
+If you have an issue logging into your Twilio SendGrid account, please read this [document](https://sendgrid.com/docs/ui/account-and-settings/troubleshooting-login/). For any questions regarding login issues, please contact our [support team](https://support.sendgrid.com).
 
 If you have a non-library Twilio SendGrid issue, please contact our [support team](https://support.sendgrid.com).
 
@@ -48,7 +48,7 @@ becomes
 
 `string apiKey = "SENDGRID_API_KEY";`
 
-In the first case SENDGRID_API_KEY is in reference to the name of the environment variable, while the second case references the actual Twilio SendGrid API Key.
+In the first case, SENDGRID_API_KEY is in reference to the name of the environment variable, while the second case references the actual Twilio SendGrid API Key.
 
 <a name="error"></a>
 ## Error Messages
@@ -171,7 +171,7 @@ In most cases we recommend you download the latest version of the library, but i
 <a name="versioning"></a>
 ## Versioning Convention
 
-We follow the MAJOR.MINOR.PATCH versioning scheme as described by [SemVer.org](http://semver.org). Therefore, we recommend that you always pin (or vendor) the particular version you are working with to your code and never auto-update to the latest version. Especially when there is a MAJOR point release, since that is guaranteed to be a breaking change. Changes are documented in the [CHANGELOG](CHANGELOG.md) and [releases](https://github.com/sendgrid/sendgrid-csharp/releases) section.
+We follow the MAJOR.MINOR.PATCH versioning scheme as described by [SemVer.org](http://semver.org). Therefore, we recommend that you always pin (or vendor) the particular version you are working with your code and never auto-update to the latest version. Especially when there is a MAJOR point release since that is guaranteed to be a breaking change. Changes are documented in the [CHANGELOG](CHANGELOG.md) and [releases](https://github.com/sendgrid/sendgrid-csharp/releases) section.
 
 <a name="request-body"></a>
 ## Viewing the Request Body
@@ -187,7 +187,7 @@ Console.WriteLine(msg.Serialize());
 <a name="ui-requests"></a>
 ## UI Requests are Failing / Deadlocks
 
-If your UI based requests are failing, it may be due to a little known issue where the UI only has a single thread. The answer here is to use `ConfigureAwait(false)` on the end of your request call, so that the thread does not reset back to request context and stays in capture context. Normally, async the request thread would "let go" of the capture context and reset to request context. With the UI, there is only a single thread, so you have to force the thread to switch to capture context, using `ConfigureAwait(false)`. For more information, please see a better summary that is linked to a longer article [in StackOverflow](https://stackoverflow.com/a/13494570).
+If your UI based requests are failing, it may be due to a little known issue where the UI only has a single thread. The answer here is to use `ConfigureAwait(false)` on the end of your request call so that the thread does not reset back to request context and stays in capture context. Normally, async the request thread would "let go" of the capture context and reset to request context. With the UI, there is only a single thread, so you have to force the thread to switch to capture context, using `ConfigureAwait(false)`. For more information, please see a better summary that is linked to a longer article [in StackOverflow](https://stackoverflow.com/a/13494570).
 
 In our example code, you would change:
 
@@ -203,4 +203,4 @@ var response = await client.SendEmailAsync(msg).ConfigureAwait(false);
 
 If you are running a newer versions of .NET you can turn on a couple different Roslyn based analyzers that will trigger build errors if you're not calling `.ConfigureAwait(false)` on your async methods.
 
-`Roslynator.Analyzers` can be installed through NuGet or as a VS plugin, but if you use the plugin then the analyzers won't run on build servers and trigger build errors like the NuGet package would. (thanks to [xt0rted](https://github.com/xt0rted) for this tip!)
+`Roslynator.Analyzers` can be installed through NuGet or as a VS plugin, but if you use the plugin then the analyzers won't run on build servers and trigger build errors as the NuGet package would. (thanks to [xt0rted](https://github.com/xt0rted) for this tip!)