Minor bug fixes and small additions

* Removed mention of Azure metrics being supported via API
* Added Container Cost History report as queryable
* Removed mention of CUR as supported through AWS Accounts API

_account/aws-account-add.md

@@ -29,11 +29,11 @@ parameters:
         content: External ID generated by CloudHealth. See [How to get External ID](#accountexternal-id-get).
   - name: billing
     required: no
-    content: JSON field that specifies the location of the AWS Detailed Billing Record (DBR) or the AWS Cost and Usage Report (CUR).
+    content: JSON field that specifies the location of the AWS Detailed Billing Record (DBR).
     sub-fields:
       - name: bucket
         required: yes
-        content: Name of S3 bucket containing the DBR and CUR
+        content: Name of S3 bucket containing the DBR
   - name: cloudtrail
     required: no
     content: JSON field that specifies whether CloudHealth should collect CloudTrail Trails and the location of Trail files.

_metrics/about-metrics-api.md

@@ -6,7 +6,7 @@ parameters:
   - name:
     content:
 content_markdown: |-
-  The Metrics API allows REST-based access to performance metrics, such as CPU, Memory, and Disk for AWS and Azure assets.
+  The Metrics API allows REST-based access to performance metrics, such as CPU, Memory, and Disk for AWS assets.
 
   The Metrics API allows you to read and write various performance metrics at this endpoint.
   ```

_reporting/intro-to-reporting-api.md

@@ -12,7 +12,7 @@ content_markdown: |-
 
   #### Which Reports are Queryable
   You can only retrieve data presented in OLAP reports. These are reports that are:
-  * available at the `/olap_reports` endpoint, and
+  * available at the `/olap_reports` endpoint (including the Container Cost History report), and
   * present data visually through charts and graphs
 
   #### Reporting Terminology