Merge pull request #477 from mulesoft/W-10587060-add-configure-instuctions-gr

W 10587060 add configure instuctions gr

Author: glenn-rodgers-sf

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

@@ -127,6 +127,7 @@ You should now see the **TLS Context for Inbound Traffic** field enabled.
 . Click *Advanced Options*.
 . 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 *Add TLS Context* for *TLS Context for Outbound traffic*.
 .. 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.

modules/ROOT/pages/manage-versions-instances-concept.adoc

@@ -1,13 +1,19 @@
-= Managing API Versions
+= Managing API Instance Versions
 ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 
-After you create an API in Anypoint Platform, you configure the version details for the API and then publish it to Anypoint Exchange (Exchange). The API version resides in Exchange, and not in API Manager. However, you then manage this API version from API Manager.
+In Anypoint Exchange (Exchange), you can add, delete, and deprecate API versions, also known as _Exchange assets_. An API version in Exchange can have its own RAML file, API portal, and URL. For more information on how to manage API versions in Exchange, see xref:exchange::manage-versions.adoc[Manage Versions].
 
-After setting up an API version for management, you repeat the process to create another instance. Attempting to configure the same version creates another instance of the version. You can create multiple instances and expand the version information to view details about them.
+After you publish new version details for an API definition to Exchange, you must change the version of your API instance in API Manager if you want the instance to reflect the latest version. For more information on API instances, see xref:api-instance-landing-page.adoc[API Instance].
 
-You can add, delete, and deprecate API versions, also known as _Exchange assets_, in Exchange. An API version in Exchange can have its own RAML file, API portal, and URL. See xref:exchange::manage-versions.adoc[Manage Versions] for more information.
+To change the asset version of an API instance:
+
+. Go to *Anypoint Platform* > *API Manager*.
+. In *API Administration*, click the name of the API whose version you want to manage.
+. Select *Actions* > *Change API specification*.
+. In *Asset version*, Select *latest*. 
+. Click *Change*.
 
 == See Also