MD formatting.

Author: bcomnes

CONTRIBUTING.md

@@ -1,7 +1,6 @@
 # CONTRIBUTING
 
-Contributions are always welcome, no matter how large or small. Before contributing,
-please read the [code of conduct](CODE_OF_CONDUCT.md).
+Contributions are always welcome, no matter how large or small. Before contributing, please read the [code of conduct](CODE_OF_CONDUCT.md).
 
 ## Setup
 
@@ -18,8 +17,7 @@ You can also use yarn.
 
 ## Testing
 
-This repo uses [ava](https://github.com/avajs/ava) for testing.  
-Any files in the `src` directory that have a `.test.js` file extension are automatically detected and run as tests.
+This repo uses [ava](https://github.com/avajs/ava) for testing. Any files in the `src` directory that have a `.test.js` file extension are automatically detected and run as tests.
 
 We also test for a few other variables:
 
@@ -30,11 +28,9 @@ We also test for a few other variables:
 
 ## Architecture
 
-We target Node.js LTS and stable environments, and aim for basic modern browser support when possible.  
-In order to facilitate simple contributions, we avoided any kind of build steps.
+We target Node.js LTS and stable environments, and aim for basic modern browser support when possible. In order to facilitate simple contributions, we avoided any kind of build steps.
 
-If you need to add new API routes, please add them to the [open-api](https://github.com/netlify/open-api) repo. 
-This client will automatically inherent the new routes from that module.
+If you need to add new API routes, please add them to the [open-api](https://github.com/netlify/open-api) repo. This client will automatically inherent the new routes from that module.
 
 Projects that depend heavily on this client that should be taken into consideration when making changes:
 

README.md

@@ -35,31 +35,25 @@ Create a new instance of the Netlify API client with the provided `accessToken`.
 
 ### `client.accessToken`
 
-A setter/getter that returns the `accessToken` that the client is configured to use.
-You can set this after the class is instantiated, and all subsequent calls will use the newly set `accessToken`.
+A setter/getter that returns the `accessToken` that the client is configured to use. You can set this after the class is instantiated, and all subsequent calls will use the newly set `accessToken`.
 
 ### `client.basePath`
 
 A getter that returns the formatted base URL of the endpoint the client is configured to use.
 
 ### Open API Client methods
 
-The client is dynamically generated from the [open-api](https://github.com/netlify/open-api) definition file.
-Each method is is named after the `operationId` name of each endpoint action.
-**To see list of available operations see the [open-api website](https://open-api.netlify.com/)**.
+The client is dynamically generated from the [open-api](https://github.com/netlify/open-api) definition file. Each method is is named after the `operationId` name of each endpoint action. **To see list of available operations see the [open-api website](https://open-api.netlify.com/)**.
 
 Every open-api method has the following signature:
 
 #### `promise(response) = client.operationId([params], [opts])`
 
-Perform a call to the given endpoint corresponding with the `operationId`.
-Returns promise that will resolve with the body of the response, or reject with an error with details about the request attached.
-Rejects if the `status` > 400.  
-Successful response objects have `status` and `statusText` properties on their prototype.
+Perform a call to the given endpoint corresponding with the `operationId`. Returns promise that will resolve with the body of the response, or reject with an error with details about the request attached. Rejects if the `status` > 400. Successful response objects have `status` and `statusText` properties on their prototype.
 
-`params` is an object that includes any of the required or optional endpoint parameters.  
-`params.body` should be an object which gets serialized to JSON automatically.  
-If the endpoint accepts `binary`, `params.body` can be a Node.js readable stream.
+- `params` is an object that includes any of the required or optional endpoint parameters.  
+- `params.body` should be an object which gets serialized to JSON automatically.  
+- If the endpoint accepts `binary`, `params.body` can be a Node.js readable stream.
 
 ```js
 // example params
@@ -72,8 +66,7 @@ If the endpoint accepts `binary`, `params.body` can be a Node.js readable stream
 }
 ```
 
-Optional `opts` can include any property you want passed to `node-fetch`.  
-The `headers` property is merged with some `defaultHeaders`.
+Optional `opts` can include any property you want passed to `node-fetch`. The `headers` property is merged with some `defaultHeaders`.
 
 ```js
 // example opts
@@ -102,18 +95,15 @@ async function getSomeData () {
 }
 ```
 
-If the request response includes `json` in the `contentType` header, fetch will deserialize the JSON body.  
-Otherwise the `text` of the response is returned.
+If the request response includes `json` in the `contentType` header, fetch will deserialize the JSON body. Otherwise the `text` of the response is returned.
 
 ### API Flow Methods
 
 Some methods have been added in addition to the open API methods that make certain actions simpler to perform.
 
 #### `promise(accessToken) = client.getAccessToken(ticket, [opts])`
 
-Pass in a [`ticket`](https://open-api.netlify.com/#model-ticket) and get back an `accessToken`.  
-Call this with the response from a `client.createTicket({ client_id })` call.  
-Automatically sets the `accessToken` to `this.accessToken` and returns `accessToken` for the consumer to save for later.
+Pass in a [`ticket`](https://open-api.netlify.com/#model-ticket) and get back an `accessToken`. Call this with the response from a `client.createTicket({ client_id })` call. Automatically sets the `accessToken` to `this.accessToken` and returns `accessToken` for the consumer to save for later.
 
 Optional `opts` include: