Fix some typos, plus various small wording and punctuation tweaks

Author: waldyrious

_authentication.md

@@ -1,6 +1,6 @@
 # Authentication
 
-Uphold is an OAuth 2.0 compliant service.
+Uphold is an [OAuth 2.0](https://oauth.net/2/)-compliant service.
 
 Partners looking to integrate with our API must [register an application](#registering-an-application).
 Applications that implement a user-facing web interface, to provide custom functionality for multiple Uphold users, should use the [Web Application Flow](#web-application-flow).
@@ -20,12 +20,18 @@ Or for sandbox applications:
 
 `https://sandbox.uphold.com/authorize/<client_id>`
 
+> Example of an authorization request URL:
+
+```
+https://uphold.com/authorize/<client_id>?state=<state_string>&scope=accounts:read%20cards:read
+```
+
 Supported query parameters:
 
 Parameter | Required | Description
---------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------
-intention | no       | Unauthenticated users will be redirected to the `login` page, this behavior can be changed by sending `signup` as the `intention` value.
-scope     | yes      | Permissions to request from the user.
+--------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------
+intention | no       | By default, unauthenticated users will be redirected to the `login` page. This behavior can be changed by sending `signup` as the `intention` value.
+scope     | yes      | Permissions to request from the user. Multiple scopes [should be](https://tools.ietf.org/html/rfc6749#section-3.3) separated by spaces.
 state     | yes      | An unguessable, cryptographically secure random string used to protect against cross-site request forgery attacks.
 
 ### Step 2 - Requesting a Token
@@ -92,15 +98,15 @@ Once you have obtained an access token you may call any protected API method on
 <aside class="notice">
   <strong>Security Notice</strong>: No other method of authentication is supported. For security reasons only the "Authorization" header will be processed.
 
-  This prevents attackers from stealing tokens from the user's browser history, logs, referer headers and other unsecure locations when credentials are sent via query URLs.
+  This prevents attackers from stealing tokens from the user's browser history, logs, referrer headers and other insecure locations when credentials are sent via query URLs.
 </aside>
 
 ## Client Credentials Flow
 
 Ideal for backend integrations that do not require access to other Uphold user accounts.
 
 For **business usage only** you may choose to use client credentials authentication.
-This requires manual approval from Uphold.
+This requires [manual approval](#support) from Uphold.
 
 ### Creating a Token
 
@@ -146,7 +152,7 @@ Once you have obtained a client credentials token you may call any protected API
 <aside class="notice">
   <strong>Security Notice</strong>: No other method of authentication is supported.
   For security reasons only the "Authorization" header will be processed.
-  This prevents attackers from stealing tokens from the user's browser history, logs, referer headers and other unsecure locations when credentials are sent via query URLs.
+  This prevents attackers from stealing tokens from the user's browser history, logs, referrer headers and other insecure locations when credentials are sent via query URLs.
 </aside>
 
 ## Personal Access Tokens (PAT)
@@ -270,5 +276,5 @@ curl https://api.uphold.com/v0/me \
 
 You can use Basic Authentication by providing your email and password combination.
 
-If OTP (One-Time Password, also known as Two-Factor Authentication) is required, then you will get a [401 HTTP error](#errors), along with the HTTP headers `OTP-Token: Required` and `OTP-Method-Id: Required`.
-In which case, execute the command above again, this time passing your OTP verification code and method id as a headers, like so: `OTP-Token: <OTP-Token>` and `OTP-Method-Id: <OTP-Method-Id>`.
+If OTP (One-Time Password, also known as Two-Factor Authentication) is required, then you will get a [401 HTTP error](#errors), along with the HTTP header `OTP-Token: Required` and/or `OTP-Method-Id: Required`.
+In which case, execute the command above again, this time passing your OTP verification code and method id as headers, like so: `OTP-Token: <OTP-Token>` and `OTP-Method-Id: <OTP-Method-Id>`.

_entities.md

@@ -134,7 +134,7 @@ name      | The display name of the contact created by joining the first and las
 }
 ```
 
-A currency pair is the combination of two currencies, encoded as two currency codes, e.g. USD, GBP, EUR, concatenated together to represent the current status of converting the first currency into the second.
+A currency pair is the combination of two currencies, encoded as two [currency codes](#currencies) concatenated together to represent the current status of converting the first currency into the second.
 For example, the currency pair "BTCUSD" represents moving from bitcoin to US dollars.
 
 Each currency pair has four properties:

_tickers.md

@@ -1,6 +1,6 @@
 # Tickers
 
-Developers can query at any time the rates we utilize when exchanging one form of value for another.
+At any time, you can query the rates we utilize when exchanging one form of value for another.
 These are expressed in [currency pairs](#currency-pair-object).
 
 ## Get Tickers for Currency
@@ -446,7 +446,7 @@ curl https://api.uphold.com/v0/ticker/USD
 }]
 ```
 
-This method allows developers to find all exchanges rates relative to a given currency.
+Lists all exchange rates relative to a given currency.
 
 ### Request
 
@@ -487,7 +487,7 @@ curl https://api.uphold.com/v0/ticker/EUR-USD
 }
 ```
 
-This method allows developers to find the exchange rate of a currency relative to any other currency.
+Retrieves the exchange rate of a currency relative to any other currency.
 
 <aside class="notice">
 The order of the currencies in the pair affects the output.

_transactions.md

@@ -126,11 +126,11 @@ The first step is to prepare the transaction by specifying:
 
 The following table describes the types of transactions currently supported:
 
-Type       | Origin                             | Destination
----------- | ---------------------------------- | --------------------------------------------------------
-deposit    | _ACH_, _CARD_ or _SEPA_ account id | Uphold card id
-withdrawal | Uphold card id                     | _ACH_, _SEPA_ or _Bitcoin_ address
-transfer   | Uphold card id                     | An email address, an application id or an Uphold card id
+Type       | Origin                              | Destination
+---------- | ----------------------------------- | --------------------------------------------------------
+deposit    | ACH, credit card or SEPA account id | Uphold card id
+withdrawal | Uphold card id                      | ACH or SEPA account id, or cryptocurrency address
+transfer   | Uphold card id                      | Email address, Application id or Uphold card id
 
 Upon preparing a transaction, a [Transaction Object](#transaction-object) will be returned with a newly-generated `id`, and a status of `pending`.
 
@@ -777,7 +777,7 @@ This endpoint supports [Pagination](#pagination).
 Returns an array of [Transaction Objects](#transaction-object).
 
 <aside class="notice">
-  Be advised that this method has the potential to return a great deal of data.
+  Be advised that this method can potentially return a large amount of data.
 </aside>
 
 ## Get Transaction (Public)

_transparency.md

@@ -254,7 +254,7 @@ curl https://api.uphold.com/v0/reserve/statistics
 ```
 
 To assist developers with tracking the overall status of our Reserve, we provide a summary of all the obligations and assets within it.
-Then for convenience's sake we compute the value of each our holdings in all of the currencies we support, making it easy for example to display our total US dollar liabilities, but expressed in Euros.
+Then, for convenience's sake, we compute the value of each our holdings in all of the currencies we support, making it easy for example to display our total US dollar liabilities, but expressed in Euros.
 For example, a request to fetch a summary will return an array of assets with the following properties:
 
 Property | Description
@@ -354,7 +354,7 @@ Instead, Uphold owes them the $507.51 they exchanged for that bitcoin.
 </code></pre>
 
 This transfer of value affects our liabilities immediately and in real-time, and thus is reflected in real-time in the ledger.
-But when our obligations to our members change a possible imbalance in our Reserve is introduced.
+But when our obligations to our members change, a possible imbalance in our Reserve is introduced.
 To compensate for this, we must make changes to the assets as well.
 These changes to our assets may or may not happen in real-time.
 This would therefore be recorded in our ledger at some point in the future as follows:
@@ -469,7 +469,7 @@ By following these transactions you walk backwards down different paths of the R
 ### Security and Privacy
 
 All transactions are made public, but specific details about the transaction may be withheld from parties who were not a party to said transaction.
-To control this we would require developers to authenticate prior to retrieving privileged information relating to a transaction.
+To control this, we require developers to authenticate prior to retrieving privileged information relating to a transaction.
 
 ### Deposits
 

_users.md

@@ -91,7 +91,7 @@ Returns the data associated with the current user.
 See the [user object](#user-object) documentation for details about the format of the response.
 
 <aside class="notice">
-  Be advised that this method has the potential to return a great deal of data.
+  Be advised that this method can potentially return a large amount of data.
 </aside>
 
 ### Cards

_webhooks.md

@@ -1,12 +1,12 @@
 # Webhooks
 
 For **business usage only** you may choose to use webhooks to get updates in real time instead of having to poll the API.
-This requires manual approval from Uphold.
+This requires [manual approval](#support) from Uphold.
 
 A webhooks integration requires the following details:
 
 * **Subscription URL:** the URL for Uphold to send webhook requests to;
-* **Secret:** the secret for Uphold to use to sign all requests and prove they have not been tampered
+* **Secret:** the secret for Uphold to use to sign all requests and prove they have not been tampered with
   (not the same as the client secret that is used for Uphold's API).
 
 Each webhook uses the following format:
@@ -26,7 +26,7 @@ userId    | Unique identifier of the Uphold user that owns the resource.
 sha512=040518ad86dd4bea08ba6d23240f53a9f35175bcb3c548e83f33acc792aabcafe29954f92b0e1d6ede9192c851b3ba0768f760f516e168c7b318a17d2714bf52
 ```
 
-In addition, the request also includes a signature header, that can be used to verify the request body has not been tampered.
+In addition, the request also includes a signature header, that can be used to verify the request body has not been tampered with.
 That header is built by signing the request body with the previously provided secret, using the SHA512 algorithm.
 
 ## Card Updated