+ Minor edits

Author: gnongsie

README.md

@@ -9,11 +9,11 @@
 * An Authorize.Net account (see _Registration & Configuration_ section below)
 
 ### Contribution  
-  - If you need information or clarification about any Authorize.Net features, please create an issue for it. Also you can search in the [Authorize.Net developer community](https://community.developer.authorize.net/).
+  - If you need information or clarification about Authorize.Net features, create an issue with your question. You can also search the [Authorize.Net developer community](https://community.developer.authorize.net/) for discussions related to your question.
   - Before creating pull requests, please read [the contributors guide](CONTRIBUTING.md).
 
 ### TLS 1.2
-The Authorize.Net APIs only support connections using the TLS 1.2 security protocol. It's important to make sure you have new enough versions of all required components to support TLS 1.2. Additionally, it's very important to keep these components up to date going forward to mitigate the risk of any security flaws that may be discovered in your system or any libraries it uses.
+The Authorize.Net APIs only support connections using the TLS 1.2 security protocol. Make sure to upgrade all required components to support TLS 1.2. Keep these components up to date to mitigate the risk of new security flaws.
 
 
 ## Installation
@@ -23,11 +23,11 @@ To install AuthorizeNet
 
 
 ## Registration & Configuration
-Use of this SDK and the Authorize.Net APIs requires having an account on our system. You can find these details in the Settings section.
-If you don't currently have a production Authorize.Net account and need a sandbox account for testing, you can easily sign up for one [here](https://developer.authorize.net/sandbox/).
+Use of this SDK and the Authorize.Net APIs requires having an account on the Authorize.Net system. You can find these details in the Settings section.
+If you don't currently have a production Authorize.Net account, [sign up for a sandbox account](https://developer.authorize.net/sandbox/).
 
 ### Authentication
-To authenticate with the Authorize.Net API you will need to use your account's API Login ID and Transaction Key. If you don't have these values, you can obtain them from our Merchant Interface site. Access the Merchant Interface for production accounts at (https://account.authorize.net/) or sandbox accounts at (https://sandbox.authorize.net).
+To authenticate with the Authorize.Net API, use your account's API Login ID and Transaction Key. If you don't have these credentials, you can obtain them from our Merchant Interface site. For production accounts, the Merchant Interface is located at (https://account.authorize.net/); and for sandbox accounts, at (https://sandbox.authorize.net).
 
 Once you have your keys simply load them into the appropriate variables in your code, as per the below sample code dealing with the authentication part of the API request. 
 
@@ -41,10 +41,10 @@ Once you have your keys simply load them into the appropriate variables in your
 An authentication test sample is provided and can be run with the following command:
 `node sample/test.js`  
 
-You should never include your Login ID and Transaction Key directly in a file that's in a publically accessible portion of your website. A better practice would be to define these in a constants file, and then reference those constants in the appropriate place in your code.
+Never include your Login ID and Transaction Key directly in a file that's in a publicly accessible portion of your website. As a best practice, define the API Login ID and Transaction Key in a constants file, and reference those constants in the appropriate place in your code.
 
 ### Switching between the sandbox environment and the production environment
-Authorize.Net maintains a complete sandbox environment for testing and development purposes. This sandbox environment is an exact duplicate of our production environment with the transaction authorization and settlement process simulated. By default, this SDK is configured to communicate with the sandbox environment. To switch to the production environment, call `setEnvironment` on the controller variable before execute. For example:
+Authorize.Net maintains a complete sandbox environment for testing and development purposes. The sandbox environment is an exact replica of our production environment, with simulated transaction authorization and settlement. By default, this SDK is configured to use with the sandbox environment. To switch to the production environment, call `setEnvironment` on the controller variable before execute. For example:
 ```javascript
 // For PRODUCTION use
 ctrl.setEnvironment(SDKConstants.endpoint.production);
@@ -54,27 +54,27 @@ API credentials are different for each environment, so be sure to switch to the
 
 
 ## SDK Usage Examples and Sample Code
-To get started using this SDK, it's highly recommended to download our sample code repository:
+When using this SDK, downloading the Authorize.Net sample code repository is recommended.
 * [Authorize.Net Node.js Sample Code Repository (on GitHub)](https://github.com/AuthorizeNet/sample-code-node)
 
-The respository contains comprehensive sample code for all common uses of our API:
+The repository contains comprehensive sample code for all common uses of the Authorize.Net API:
 
-Additionally, you can find details and examples of how our API is structured in our API Reference Guide:
+The API Reference contains details and examples of the structure and formatting of the Authorize.Net API.
 * [Developer Center API Reference](http://developer.authorize.net/api/reference/index.html)
 
-The API Reference Guide provides examples of what information is needed for a particular request and how that information would be formatted. Using those examples, you can easily determine what methods would be necessary to include that information in a request using this SDK.
+Use the examples in the API Reference to determine which methods and information to include in an API request using this SDK.
 
 ## Create a Chase Pay Transaction
 
 Use this method to authorize and capture a payment using a tokenized credit card number issued by Chase Pay. Chase Pay transactions are only available to merchants using the Paymentech processor.
 
 The following information is required in the request:
-- The **payment token**,
-- The **expiration date**,
-- The **cryptogram** received from the token provider,
-- The **tokenRequestorName**,
-- The **tokenRequestorId**, and
-- The **tokenRequestorEci**.
+- **payment token**
+- **expiration date**
+- **cryptogram** received from the token provider
+- **tokenRequestorName**
+- **tokenRequestorId**
+- **tokenRequestorEci**
 
 When using the SDK to submit Chase Pay transactions, consider the following points:
 - `tokenRequesterName` must be populated with **`”CHASE_PAY”`**