edits

Author: glenn-rodgers-sf

modules/ROOT/pages/_partials/task-configure-proxy.adoc

@@ -96,7 +96,7 @@ NOTE: After adding the API on Anypoint Platform, you will need to bind it to a s
 
 ** **REST API:** Select this option if you have a RAML or OAS API definition file you want to include for your asset.
 +
-Upload either a RAML or OAS file for your REST API.
+Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are the recommended versions for OAS or RAML specs, because these versions add native OAS support. If you upload an OAS API specification to an API proxy version 1.0 or earlier, your API specification is translated to RAML.
 ** **HTTP API:** Select this option if you do not have an API definition file you want to include for your asset.
 ** **SOAP API:** Select this option if you have a WSDL API definition file or an external link to the file.
 +
@@ -108,7 +108,7 @@ This option is not available for Flex Gateway runtime at this time.
 //end::asset-type-options[]
 //tag::raml-oas[]
 .. Select **REST API** as the **Asset type**.
-.. Upload either a RAML or OAS file for your REST API.
+.. Upload either a RAML or OAS file for your REST API. 
 +
 NOTE: Anypoint API Manager supports OpenAPI Specification (OAS) 3.0, with the exception of the callback feature. To work around this issue, handle the callback outside of the Mule runtime engine domain or use an OAS 3.0 specification that does not use callbacks.
 
@@ -134,14 +134,14 @@ You should now see the *Inbound TLS* field enabled.
 . Enter the *Port* number for your API proxy.
 . Enter the *Base path*.
 . Click *Advanced Options*.
-. Select optional down stream configuration settings. For more configuration settings, see xref:create-instance-task-service-mesh.adoc[].
+. Select optional down stream configuration settings. For more configuration settings, see xref:create-instance-task-mule.adoc[].
 . In *Proxy Version*, select *latest*. +
 This value ensures that your API proxy uses the latest released proxy version.
 If a new proxy version is available in Anypoint platform, return to this step to reconfigure your proxy to the latest version.
 . Click *Next*.
 . Enter your *Upstream URL*. This is the URL to access the proxy or the API. For example, you can use the URL of your API asset in Exchange. +
 This is the only required field. For further details on the optional fields, see xref:configure-api-task.adoc[Configure an API Endpoint].
-. Click *Add TLS Context* for *Outbound TLS*.
+. Click *Add TLS Context* for *Outbound TLS*. This is required for API instances using HTTPs communication.
 .. Select the secret group where you hosted your TLS Context from the *Secret Group* drop-down list.
 .. Select your TLS Context for your HTTPS API Proxy from the *TLS Context* drop-down.
 +
@@ -152,8 +152,8 @@ If you can't see a context, check that you have the right permissions, as mentio
 //end::mid-steps2[]
 //tag::raml-oas-version[]
 +
-Versions 2.0.0 and later are the recommended versions for OAS or RAML specs, because these versions add native OAS support. +
-If you upload an OAS API specification to an API proxy version 1.0 or earlier, your API specification will be translated to RAML.
+Versions 2.0.0 and later are the recommended versions for OAS or RAML specs, because these versions add native OAS support.
+If you upload an OAS API specification to an API proxy version 1.0 or earlier, your API specification is translated to RAML.
 +
 //end::raml-oas-version[]
 //tag::tls[]

modules/ROOT/pages/building-soap-proxy.adoc

@@ -46,7 +46,7 @@ With SOAP proxy v2.1.0, you can retrieve a WSDL from a remote location using the
 
 Configure your SOAP proxy by completing the following tasks:
 
-include::partial$task-configure-proxy.adoc[tags=intro;first-steps;target-type;mid-steps;soap;mid-steps2;tls;last-steps,leveloffset=+2]
+include::partial$task-configure-proxy.adoc[tags=intro;first-steps;target-type;mid-steps;soap;mid-steps2;last-steps,leveloffset=+2]
 
 
 == Troubleshooting SOAP Proxies for Missing Imports on XSD Files

modules/ROOT/pages/proxy-deploy-raml-oas-proxy.adoc

@@ -6,7 +6,7 @@ API Manager 2.x enables you to use a RAML or OAS type of API Proxy, for all your
 
 Configure your RAML or OAS API proxy by completing the following tasks:
 
-include::partial$task-configure-proxy.adoc[tags=intro;first-steps;target-type;mid-steps;raml-oas;mid-steps2;raml-oas-version;tls;last-steps,leveloffset=+2]
+include::partial$task-configure-proxy.adoc[tags=intro;first-steps;target-type;mid-steps;raml-oas;mid-steps2;last-steps,leveloffset=+2]
 
 
 == See Also

modules/ROOT/pages/proxy-domain-support.adoc

@@ -42,7 +42,7 @@ For HTTP listener configuration defined in the domain, the listener setup on the
 
 Configure the domain used by an API proxy by completing the following tasks:
 
-include::partial$task-configure-proxy.adoc[tags=intro;first-steps;hybrid;mid-steps;asset-type-options;mid-steps2;raml-oas-version;tls;last-steps,leveloffset=+2]
+include::partial$task-configure-proxy.adoc[tags=intro;first-steps;hybrid;mid-steps;asset-type-options;mid-steps2;last-steps,leveloffset=+2]
 . After saving the API proxy configuration, perform one of the following steps:
 
 * Deploy the API proxy to the selected target (*Settings*, under *Deployment Configuration*).

modules/ROOT/pages/proxy-latest-concept.adoc

@@ -27,7 +27,7 @@ For Mule versions 3.8 and later, use Mule Agent 1.9.0. For Mule 4.x, use the Mul
 
 Deploy your proxy by completing the following tasks:
 
-include::partial$task-configure-proxy.adoc[tags=intro;first-steps;target-type;mid-steps;asset-type-options;mid-steps2;raml-oas-version;tls;last-steps,leveloffset=+2]
+include::partial$task-configure-proxy.adoc[tags=intro;first-steps;target-type;mid-steps;asset-type-options;mid-steps2;last-steps,leveloffset=+2]
 
 If you are deploying your API to a Mule 4 environment and want to enable the proxy to support HTTPS requests, first xref:building-https-proxy.adoc[build HTTPS API proxies].