Wrap some long lines

This makes it easier to review changes, since diffs will be more localized.

See <https://rhodesmill.org/brandon/2012/one-sentence-per-line/> for context and motivation.

Author: waldyrious

_applications.md

@@ -2,7 +2,8 @@
 
 ## Registering an application
 
-Developers will need to [register their application](https://support.uphold.com/hc/en-us/articles/217210266) before getting started. A registered application will be assigned a unique _Client Id_ and _Client Secret_.
+Developers will need to [register their application](https://support.uphold.com/hc/en-us/articles/217210266) before getting started.
+A registered application will be assigned a unique _Client Id_ and _Client Secret_.
 
 <aside class="notice">
   <strong>Security Notice</strong>: Your <i>Client Secret</i> should never be shared, must be kept secret at all times and should only be used from your server-side application.
@@ -20,7 +21,8 @@ Developers will need to [register their application](https://support.uphold.com/
 
 ## Permissions
 
-When requesting authorization from a user the application must specify the level of access needed. These _scopes_ are displayed to the user on the authorization form and currently the user cannot opt-out of individual scopes.
+When requesting authorization from a user the application must specify the level of access needed.
+These _scopes_ are displayed to the user on the authorization form and currently the user cannot opt-out of individual scopes.
 
 The API supports the following _scopes_:
 

_authentication.md

@@ -2,7 +2,9 @@
 
 Uphold is an OAuth 2.0 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). Applications that implement a backend interface for a corporate partner (and therefore represent an Uphold user themselves) should use the [Client Credentials Flow](#client-credentials-flow).
+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).
+Applications that implement a backend interface for a corporate partner (and therefore represent an Uphold user themselves) should use the [Client Credentials Flow](#client-credentials-flow).
 
 ## Web Application Flow
 
@@ -97,7 +99,8 @@ Once you have obtained an access token you may call any protected API method on
 
 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.
+For **business usage only** you may choose to use client credentials authentication.
+This requires manual approval from Uphold.
 
 ### Creating a Token
 
@@ -141,16 +144,19 @@ Once you have obtained a client credentials token you may call any protected API
 `Authorization: Bearer <token>`
 
 <aside class="notice">
-  <strong>Security Notice</strong>: No other method of authentication is supported. For security reasons only the "Authorization" header will be processed.
-
+  <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.
 </aside>
 
 ## Personal Access Tokens (PAT)
 
 Ideal for scripts, automated tools and command-line programs which remain under your control.
 
-For **personal usage only** you may choose to use a PAT. This token establishes who you are, provides full access to your user account and bypasses Two Factor Authentication, if enabled. For this reason it should be treated just like your email/password combination, i.e. remain secret and never shared with third parties. PATs can be issued and revoked individually.
+For **personal usage only** you may choose to use a PAT.
+This token establishes who you are, provides full access to your user account and bypasses Two Factor Authentication, if enabled.
+For this reason it should be treated just like your email/password combination, i.e. remain secret and never shared with third parties.
+PATs can be issued and revoked individually.
 
 ### Listing PATs
 

_currencies.md

@@ -1,13 +1,18 @@
 # Currencies
 
-Uphold [supports](https://uphold.com/en/transparency) multiple financial assets, including traditional currencies, cryptocurrencies, stablecoins, precious metals, U.S. equities, and more.
+Uphold [supports](https://uphold.com/en/transparency) multiple financial assets,
+ including traditional currencies, cryptocurrencies, stablecoins, precious metals, U.S. equities, and more.
 
 <aside class="notice">
   For brevity and convenience, we may refer to any such asset simply as "currency" throughout the API documentation.
   In cases that only apply to specific classes of assets, we will clarify accordingly.
 </aside>
 
-In Uphold's API, various endpoints include currencies in their input or output. We represent all such currencies by an abbreviation **code** of variable length, typically containing uppercase letters (for example, a currency's [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) code, an equity's [ticker symbol](https://en.wikipedia.org/wiki/Ticker_symbol), or other similar well-known representation).
+In Uphold's API, various endpoints include currencies in their input or output.
+We represent all such currencies by an abbreviation **code** of variable length, typically containing uppercase letters
+(for example, a currency's [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) code,
+an equity's [ticker symbol](https://en.wikipedia.org/wiki/Ticker_symbol),
+or other similar well-known representation).
 
 ## List Supported Assets
 

_entities.md

@@ -134,7 +134,8 @@ 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. For example, the currency pair "BTCUSD" represents moving from bitcoin to US dollars.
+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.
+For example, the currency pair "BTCUSD" represents moving from bitcoin to US dollars.
 
 Each currency pair has four properties:
 
@@ -265,7 +266,8 @@ verified            | A boolean indicating if this phone number has been verifie
 }
 ```
 
-Transactions record the movement of value into, within and out of the Uphold network. Transactions have the following properties:
+Transactions record the movement of value into, within and out of the Uphold network.
+Transactions have the following properties:
 
 <aside class="notice">
   There are two views of a transaction: public and private.
@@ -312,7 +314,8 @@ rate     | The quoted rate for converting between the denominated currency and t
 
 ### Fees
 
-The `fees` property contains an array of fees that were applied to the transaction. Each object in the array contains the following properties:
+The `fees` property contains an array of fees that were applied to the transaction.
+Each object in the array contains the following properties:
 
 Property   | Description
 ---------- | ---------------------------------------------------------------------------------
@@ -528,17 +531,22 @@ memberAt | The date when the user became a [verified member](https://support.uph
 
 ### User Status
 
-We communicate a number of different user statuses through our API. At a high-level users can be in one of four statuses:
+We communicate a number of different user statuses through our API.
+At a high-level users can be in one of four statuses:
 
-- **pending** - This status applies to a user that is in the process of creating an account; it means the signup process is not yet finalized.
-- **restricted** - This status means the user is allowed to login to the application, deposit or receive money, and perform trades, but they are not permitted to withdraw nor send money to other users. This status exists to allow users to satisfy additional data requirements.
-- **blocked** - This status is present when a user has violated our terms of service. In this status users are unable to login or access the product.
+- **pending** - This status applies to a user that is in the process of creating an account;
+  it means the signup process is not yet finalized.
+- **restricted** - This status means the user is allowed to login to the application, deposit or receive money, and perform trades, but they are not permitted to withdraw nor send money to other users.
+  This status exists to allow users to satisfy additional data requirements.
+- **blocked** - This status is present when a user has violated our terms of service.
+  In this status users are unable to login or access the product.
 - **ok** - Everything is ay-ok.
 
 ### User Verifications
 
 The `verifications` field can help communicate the reasons for a given user status, or what's missing to complete the membership process.
-These verifications have permissible values and in some cases, an associated reason. Here is an overview of the verifications field:
+These verifications have permissible values and in some cases, an associated reason.
+Here is an overview of the verifications field:
 
 Flag      | Permissible Values               | Reason         | Description
 --------- | -------------------------------- | -------------- | --------------------------------------------------------------------------------------

_introduction.md

@@ -1,6 +1,8 @@
 # Introduction
 
-Welcome to the Uphold API — we're glad to have you! Here you can find all the documentation you need to help you create custom and revolutionary new services powered by the Uphold Platform. Together, with your ingenuity, we can serve the needs of individuals and organizations across the globe and change the financial services ecosystem forever.
+Welcome to the Uphold API — we're glad to have you!
+Here you can find all the documentation you need to help you create custom and revolutionary new services powered by the Uphold Platform.
+Together, with your ingenuity, we can serve the needs of individuals and organizations across the globe and change the financial services ecosystem forever.
 
 ## API code samples
 

_pagination.md

@@ -5,7 +5,8 @@ Collection endpoints with large dataset supports [Range Pagination Headers](http
 ## Request
 
 You can provide the `Range` header in your request to specify how many items you want to retrieve.
-The maximum number of items per page is 50. That is also the default value if you leave it unspecified.
+The maximum number of items per page is 50.
+That is also the default value if you leave it unspecified.
 
 > For example, here's how you'd fetch the five most recent transactions associated with the current user.
 > Note that the items are indexed from zero:

_ratelimits.md

@@ -1,10 +1,17 @@
 # Rate Limits
 
-The API applies rate limits based on the number of requests per a predefined interval (i.e. a time-window). We currently do not differentiate between authenticated and unauthenticated requests. The global rate limit takes into account the remote client IP only.
+The API applies rate limits based on the number of requests per a predefined interval (i.e. a time-window).
+We currently do not differentiate between authenticated and unauthenticated requests.
+The global rate limit takes into account the remote client IP only.
 
-We plan on changing this policy in the future to one that limits on an account-by-account basis. For now, please be advised that those operating from corporate networks may hit their limit faster given that everyone may present the same IP address to our network.
+We plan on changing this policy in the future to one that limits on an account-by-account basis.
+For now, please be advised that those operating from corporate networks may hit their limit faster,
+given that everyone may present the same IP address to our network.
 
-Some endpoints have stricter rules as it relates to rate limits. These endpoints may additionally take into consideration the user's account or email address. For example, there can be 10 requests per 10 minute time period per IP to the `/password/forgot` endpoint; but multiple IPs can only make 3 requests per 5 minute time period per user account (e.g. `foo@bar.com`).
+Some endpoints have stricter rules as it relates to rate limits.
+These endpoints may additionally take into consideration the user's account or email address.
+For example, there can be 10 requests per 10 minute time period per IP to the `/password/forgot` endpoint;
+but multiple IPs can only make 3 requests per 5 minute time period per user account (e.g. `foo@bar.com`).
 
 The following table indicates the current rate limits:
 
@@ -22,7 +29,9 @@ POST /users                               |         10 / 10-min window |
 
 ## Response Headers
 
-The current rate limit in effect is explained via custom HTTP headers as described in the table below. Additionally, the standard HTTP `Retry-After` header field will be appended when the rate limit is exhausted and indicates, in delta-seconds, how long until the rate limit window is reset.
+The current rate limit in effect is explained via custom HTTP headers as described in the table below.
+Additionally, the standard HTTP `Retry-After` header field will be appended when the rate limit is exhausted,
+and indicates, in delta-seconds, how long until the rate limit window is reset.
 
 Header               | Description
 -------------------- | ----------------------------------------------------------------------------------------------------------------------

_tickers.md

@@ -1,6 +1,7 @@
 # Tickers
 
-Developers can query at any time the rates we utilize when exchanging one form of value for another. These are expressed in [currency pairs](#currency-pair-object).
+Developers can query at any time 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
 
@@ -453,7 +454,8 @@ This method allows developers to find all exchanges rates relative to a given cu
 
 ### Response
 
-Returns an associative array containing the current rates Uphold has on record for the currency specified. If no currency is specified on the endpoint, USD currency pair will be returned by default.
+Returns an associative array containing the current rates Uphold has on record for the currency specified.
+If no currency is specified on the endpoint, USD currency pair will be returned by default.
 
 ## Get Tickers for Currency Pair
 

_totp.md

@@ -1,6 +1,7 @@
 # One-Time Password
 
-Uphold provides a TOTP (Time-Based One-Time Password) mechanism to secure user accounts. Adopting and adhering to this mechanism is recommended for safety reasons.
+Uphold provides a TOTP (Time-Based One-Time Password) mechanism to secure user accounts.
+Adopting and adhering to this mechanism is recommended for safety reasons.
 The following section documents how the Authentication Methods API works to provide support for this security mechanism.
 
 ## List Authentication Methods