Update task-add-api-instance.adoc

Author: glenn-rodgers-sf

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

@@ -98,7 +98,7 @@ See xref:runtime-fabric::proxy-deploy-runtime-fabric.adoc[Deploying API Proxies
 * Click **Select API from Exchange** if you have an API shared with you through Exchange that you want to manage.
 [arabic]
 .. Click the API from the list under **Select API**. You can search for a specific API if needed.
-.. Update the *Asset type*, *API version*, and *Asset version* if needed.
+.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
 +
 For more information about how to Exchange versions, see xref:exchange::asset-versions.adoc[].
 .. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
@@ -117,7 +117,7 @@ For more information about how to Exchange versions, see xref:exchange::asset-ve
 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.
 
-.. Update the *Asset type*, *API version*, and *Asset version* if needed.
+.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
 +
 For more information about how to Exchange versions, see xref:exchange::asset-versions.adoc[].
 .. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
@@ -137,7 +137,7 @@ Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are
 Upload a WSDL file for your SOAP API or add the link to the file. +
 This option is not available for Flex Gateway runtime at this time.
 
-.. Update the *Asset type*, *API version*, and *Asset version* if needed.
+.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
 +
 For more information about how to Exchange versions, see xref:exchange::asset-versions.adoc[].
 .. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
@@ -151,7 +151,7 @@ For more information about how to Exchange versions, see xref:exchange::asset-ve
 +
 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.
 
-.. Update the *Asset type*, *API version*, and *Asset version* if needed.
+.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
 +
 For more information about how to Exchange versions, see xref:exchange::asset-versions.adoc[].
 .. View the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[]