Apply suggestions from code review from @mikeyMJCO

Updates the changes as suggested by Mikey

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

docs/api/index.md

@@ -2,9 +2,9 @@
 
 CiviCRM has a stable comprehensive **API** (Application Programming Interface) that can be used to access and manage data in CiviCRM. The API is the recommended way for any CiviCRM extension, CMS module, or external program to interact with CiviCRM.
 
-Utilizing the API is superior to accessing core functions directly (e.g.calling raw SQL, or calling functions within the BAO files) because the API offers a consistent interface to CiviCRM's features. It is designed to function predictably with every new release so as to preserve backwards compatibility of the API for several versions of CiviCRM. If you decide to use other ways to collect data (like your own SQL statements), you risk running into future problems when changes to the schema andBAO arguments inevitably occur.
+Utilizing the API is superior to accessing core functions directly (e.g.calling raw SQL, or calling functions within the BAO files) because the API offers a consistent interface to CiviCRM's features. It is designed to function predictably with every new release so as to preserve backwards compatibility of the API for several versions of CiviCRM. If you decide to use other ways to collect data (like your own SQL statements), you risk running into future problems when changes to the schema and BAO arguments inevitably occur.
 
-The best place to begin working with the API is your own ***test*** install of CiviCRM, using the API explorer and the API parameter list.
+The best place to begin working with the API is your own *test* install of CiviCRM, using the API explorer and the API parameter list.
 
 For help creating your own API custom calls, see [civix generate:api](/extensions/civix.md#generate-api)
 
@@ -12,13 +12,13 @@ For help creating your own API custom calls, see [civix generate:api](/extension
 
 The API explorer is a powerful GUI tool for building and executing API calls.
 
-To access the APIv3 explorer:
+### Access the APIv3 explorer:
 
 1. Go to any CiviCRM site
     * This can even be the [demo site](http://dmaster.demo.civicrm.org/).
 1. Within the CivCRM menu, go to **Support > Developer > APIv3 Explorer** or go to the URL `/civicrm/api`.
 
-To access the APIv4 explorer:
+### Access the APIv4 explorer:
 
 1. Go to any CiviCRM site
     * This can even be the [demo site](http://dmaster.demo.civicrm.org/).
@@ -27,7 +27,7 @@ To access the APIv4 explorer:
 !!! warning
     The API explorer actually executes real API calls. It can modify data! So if you execute a `Contact` `delete` call, it will really delete the contact. As such, any experimenting is best done within a test site.
 
-You can select the entity you want to use, for example `Contact` and the action you want to perform, for example `Get`. The API explorer will show you the specific code necessary to execute the API call you have been testing.
+You can select the entity you want to use, for example `Contact` and the action you want to perform, for example `Get`. The API explorer will show you the specific code necessary to execute the API call you have been testing using the various API interfaces available.
 
 ## API parameter documentation
 

docs/api/interfaces.md

@@ -12,7 +12,7 @@ The AJAX interface is one of the more common interfaces used within CiviCRM code
 
 #### CRM.api3 / CRM.api4
 
-`CRM.api3` and `CRM.api4` is a javascript method produced by CiviCRM as a thin wrapper around a call to `http://example.org/civicrm/ajax/rest`. The standard format of such an API call can be found under the relevant usage sub chapter of this docuemtation
+`CRM.api3` and `CRM.api4` is a javascript method produced by CiviCRM as a thin wrapper around a call to `http://example.org/civicrm/ajax/rest`. The standard format of such an API call can be found under the relevant usage sub-chapter of this documentation
 
 #### Tests
 

docs/api/v3/usage.md

@@ -161,7 +161,7 @@ For more details, see [REST interface](/api/interfaces.md#rest).
 CRM.api3('entity', 'action', [params], [statusMessage]);
 ```
 
-If you pass `true` in as the `StatusMessage` param, it will display the default status Message. This is useful when doing things such as adding tags to contacts or similar. If you wish to do further work based on the result of the API call (e.g use the results from a GET call) you will need to use the [done method](http://api.jquery.com/deferred.done/) to listen for the event. For example:
+If you pass `true` in as the `StatusMessage` param, it will display the default status message. This is useful when doing things such as adding tags to contacts or similar. If you wish to do further work based on the result of the API call (e.g use the results from a GET call) you will need to use the [done method](http://api.jquery.com/deferred.done/) to listen for the event. For example:
 
 ```javascript
 CRM.api3('entity_tag', 'create', {contact_id:123, tag_id:42})
@@ -185,7 +185,7 @@ CRM.api3(params).done(function(result) {
 
 You can also use associative objects in your API call as follows:
 
-```
+``` javascript
 var params = {
   one: ['email', 'getoptions', {field: 'location_type_id'}],
   two: ['phone', 'getoptions', {field: 'phone_type_id', sequential: 1}],
@@ -198,11 +198,11 @@ CRM.api3(params).done(function(result) {
 });
 ```
 
-The AJAX interface is automatically available for web-pages generated through CiviCRM (such as standard CiviCRM web-pages, CiviCRM extensions, and custom CiviCRM templates).
+The AJAX interface is automatically available for web-pages generated through CiviCRM (such as standard CiviCRM web-pages, CiviCRM extensions and custom CiviCRM templates).
 
-The AJAX interface could be made available to other parts of the same website (e.g. a drupal module or wordpress widget) by calling `CRM_Core_Resources::singleton()->addCoreResources()`
+The AJAX interface could be made available to other parts of the same website (e.g. a Drupal module or WordPress widget) by calling `CRM_Core_Resources::singleton()->addCoreResources()`
 from php. Please note that the AJAX interface is subject to [API Security](/security/permissions.md#api-permissions)
-and [Same Origin Policy](http://en.wikipedia.org/wiki/Same_origin_policy). To use it from an external site or application, see REST interface documentation.
+and [Same Origin Policy](http://en.wikipedia.org/wiki/Same_origin_policy). To use it from an external site or application, see the REST interface documentation.
 
 ## Smarty
 

docs/api/v4/usage.md

@@ -25,7 +25,7 @@ The result of a successful API call typically looks like this:
 
 ```php
 [
- { /* DAO Object */
+ { /* DAO Object */ }
 ]
 ```
 
@@ -44,9 +44,9 @@ array(
 
 ## PHP
 
-This is the most common way to call the API. There are 2 formats of API calls a proceedural approach and the more traditional approach
+This is the most common way to call the API. There are 2 formats of API calls a procedural approach and the more traditional approach
 
-Object Oriented Proceedural approach:
+Object Oriented Procedural approach:
 
 ```php
 $contacts = \Civi\Api4\Contact::get()
@@ -78,9 +78,7 @@ This format matches canonical format almost exactly, with a few improvements for
 -  Errors are reported as PHP exceptions. You may catch the exceptions or (by default) allow them to bubble up.
 - You can immediately iterate over the contacts returned
 
-*Note*: If you're writing a Drupal module, a Joomla extension, a WordPress plugin, or a standalone script, then you may need to **bootstrap** CiviCRM before using the API.  See the examples in [Bootstrap Reference].
-
-[Bootstrap Reference](/framework/bootstrap.md)
+*Note*: If you're writing a Drupal module, a Joomla extension, a WordPress plugin, or a standalone script, then you may need to **bootstrap** CiviCRM before using the API.  See the examples in [Bootstrap Reference](/framework/bootstrap.md).
 
 ## REST
 
@@ -125,7 +123,7 @@ For more details, see [REST interface](/api/interfaces.md#rest).
 CRM.api4('entity', 'action', [params], [statusMessage]);
 ```
 
-If you pass `true` in as the `StatusMessage` param, it will display the default status Message. This is useful when doing things such as adding tags to contacts or similar. If you wish to do further work based on the result of the API call (e.g use the results from a GET call) you will need to use the [done method](http://api.jquery.com/deferred.done/) to listen for the event. For example:
+If you pass `true` in as the `StatusMessage` param, it will display the default Status Message. This is useful when doing things such as adding tags to contacts or similar. If you wish to do further work based on the result of the API call (e.g use the results from a GET call) you will need to use the [done method](http://api.jquery.com/deferred.done/) to listen for the event. For example:
 
 ```javascript
 CRM.api4('EntityTag', 'create', {
@@ -137,9 +135,9 @@ CRM.api4('EntityTag', 'create', {
 });
 ```
 
-The AJAX interface is automatically available for web-pages generated through CiviCRM (such as standard CiviCRM web-pages, CiviCRM extensions, and custom CiviCRM templates).
+The AJAX interface is automatically available for web-pages generated through CiviCRM (such as standard CiviCRM web-pages, CiviCRM extensions and custom CiviCRM templates).
 
-The AJAX interface could be made available to other parts of the same website (e.g. a drupal module or wordpress widget) by calling `CRM_Core_Resources::singleton()->addCoreResources()`
+The AJAX interface could be made available to other parts of the same website (e.g. a Drupal module or WordPress widget) by calling `CRM_Core_Resources::singleton()->addCoreResources()`
 from php. Please note that the AJAX interface is subject to [API Security](/security/permissions.md#api-permissions)
 and [Same Origin Policy](http://en.wikipedia.org/wiki/Same_origin_policy). To use it from an external site or application, see REST interface documentation.
 
@@ -157,7 +155,7 @@ For more details, see
 [Smarty API interface](/api/interfaces.md#smarty-api-interface).
 
 ## Scheduled jobs
-Any API call can be configured to be run as a scheduled job. These can be configured in the UI under Administer->System Settings->Scheduled jobs. Usually API calls run this way are written with the intent that they be run as scheduled jobs - e.g those with the Job entity or provided by payment processors to run recurring payments.
+Any API call can be configured to be run as a scheduled job. These can be configured in the UI under **Administer -> System Settings -> Scheduled Jobs**. Usually API calls run this way are written with the intent that they be run as scheduled jobs - e.g those with the Job entity or provided by payment processors to run recurring payments.