Fix endpoint

Author: glenn-rodgers-sf

modules/ROOT/pages/_partials/task-add-api-instance.adoc

@@ -145,32 +145,23 @@ NOTE: Anypoint API Manager supports OpenAPI Specification (OAS) 3.0, with the ex
 . Click *Next*.
 //end::soap[]
 
-//tag::mid-steps2[]
-. If you want to enable TSL for inbound traffic:
-** Select *HTTPS* for the *Scheme*. +
-You should now see the *Inbound TLS* field enabled.
-** Select *Add TLS Context*.
-*** Select the secret group where you hosted your TLS context from the *Secret group* drop-down.
-*** Select your TLS context for your HTTPS API Proxy from the *TLS Context* drop-down.
-. Enter the *Port* number for your API proxy.
-. Enter the *Base path*.
-. Click *Advanced Options*.
-. Select optional downstream 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.
+//tag::proxy-endpoints[]
+. Configure the downstream configuration settings:
+.Expand for configuration settings.
+[%collapsible]
+====
+include::partial$api-configuration-tables.adoc[tags=mule-proxy-downstream]
+====
 . 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*. 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.
+. Configure the upstream configuration settings:
 +
-[NOTE]
-If you can't see a context, check that you have the right permissions, as mentioned in <<Before You Begin>>.
-
+.Expand for configuration settings.
+[%collapsible]
+====
+include::partial$api-configuration-tables.adoc[tags=mule-proxy-upstream]
+====
 . Click *Next*.
-//end::mid-steps2[]
+//end::proxy-endpoints[]
 
 //tag::last-steps[]
 

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 steps:
 
-include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;soap;mid-steps2;last-steps]
+include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;soap;proxy-endpoints;last-steps]
 
 
 == 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 steps:
 
-include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;raml-oas;mid-steps2;last-steps]
+include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;raml-oas;proxy-endpoints;last-steps]
 
 
 == 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
 
 To configure the API proxy domain by completing the following steps:
 
-include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;hybrid;mid-steps;asset-type-options;mid-steps2;last-steps]
+include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;hybrid;mid-steps;asset-type-options;proxy-endpoints;last-steps]
 
 . After saving the API proxy configuration, perform one of the following steps:
 

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 steps:
 
-include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;asset-type-options;mid-steps2;last-steps]
+include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;asset-type-options;proxy-endpoints;last-steps]
 
 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].