API edits

Author: glenn-rodgers-sf

modules/ROOT/nav.adoc

@@ -56,8 +56,8 @@
 * xref:analytics-landing-page.adoc[View Mule API Analytics]
  ** xref:viewing-api-analytics.adoc[Review Mule API Analytics Usage]
  ** xref:analytics-chart.adoc[Review Mule API Analytics Charts Usage]
- ** xref:analytics-event-api.adoc[Review Mule API Analytics Event API]
- ** xref:analytics-event-forward.adoc[Review Mule API Analytics Event Forwarding]
+ ** xref:analytics-event-api.adoc[Review API Analytics Event API]
+ ** xref:analytics-event-forward.adoc[Review API Analytics Event Forwarding]
 * xref:mule-oauth-provider-landing-page.adoc[Mule OAuth 2.0 Provider]
  ** xref:about-configure-api-for-oauth.adoc[OAuth 2.0 Policy Prerequisites]
  ** xref:external-oauth-2.0-token-validation-policy.adoc[OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider]

modules/ROOT/pages/analytics-event-api.adoc

@@ -1,12 +1,12 @@
-= Reviewing Mule API Analytics Event API
+= Reviewing API Analytics Event API
 ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 :keywords: analytics, api, reports
 
 //Rename topic to Generating Analytics Reports for APIs
 
-API Manager gathers analytics data for each Mule API that you manage.  You can generate this data in reports and charts, using the Mule API Analytics Event API. You can create reports for a specific environment or for multiple APIs, and you can create different reports for the same API.
+API Manager gathers analytics data for each Mule API that you manage. You can generate this data in reports and charts, using the API Analytics Event API. You can create reports for a specific environment or for multiple APIs, and you can create different reports for the same API.
 
 == Requirements and Restrictions
 
@@ -240,8 +240,8 @@ Your report can query data for one or more of the available data fields:
 In your query, if the `Content-Length` header is:
 
 * Present: `Response Size` is set to that value. 
-* Not present and the payload is a String: Analytics calculates the length of the String and reports that value. 
-* Not present and the payload is not a String: Analytics reports the response size as -1. 
+* Not present and the payload is a String: Mule API Analytics calculates the length of the String and reports that value. 
+* Not present and the payload is not a String: Mule API Analytics reports the response size as -1. 
 +
 For example, if the output returned is a DataWeave stream and the `Content-Length` header is not present, the Analytics Event API does not report a response size because the value is not a String. However if your application performs a String conversion, the response size is listed.
 

modules/ROOT/pages/analytics-event-forward.adoc

@@ -3,21 +3,21 @@ ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 
-Sometimes you need to forward the Anypoint API Analytics events to a third-party system. An example of this could be integrating with ELK or other analytics system.
+Sometimes you need to forward the Mule API Analytics events to a third-party system. An example of this could be integrating with ELK or other analytics system.
 
 There are three ways to export events:
 
 * Use the API Analytics Report API to pull the data. One consideration with this method is that the API has limit on the number and frequency of events that can be reported. Additionally, events may have delays of up to 10 minutes from the time the event is generated to the moment it is available for query.
 
-* Forward API Analytics events from the Gateway to configured HTTP endpoint. To configure this on CloudHub, configure the `anypoint.platform.analytics_base_uri` gateway property from the Settings tab of Runtime Manager.
+* Forward Mule API Analytics events from the Gateway to configured HTTP endpoint. To configure this on CloudHub, configure the `anypoint.platform.analytics_base_uri` gateway property from the Settings tab of Runtime Manager.
 +
 Setting this property configures the base URL where the events are posted.
 
 image::analytics-event-forwarding.png[Event Forwarding]
 
 In the example shown above, the events are published to `+http://<your-address-here>/v2/analytics/events+` using the POST method and GZIP for compression.
 
-The disadvantage of this approach is that events are not published to Anypoint Platform and neither API Analytics nor API Manager display information about API calls.
+The disadvantage of this approach is that events are not published to Anypoint Platform and neither Mule API Analytics nor API Manager display information about API calls.
 
 * Use Runtime Manager to xref:runtime-manager::sending-data-from-arm-to-external-analytics-software.adoc[Export Data to External Analytics Tools]