Merge branch 'v2.x' into W-11764425-CH2-simplified-deployment-LDS

Author: luanamulesoft

modules/ROOT/pages/api-groups-manage-api-group-instance-contracts.adoc

@@ -20,15 +20,12 @@ When an application has multiple contracts with the same API instance, only one
 .The screen capture displays the contract levels and the contract status for the API instance contracts.
 image:api-groups-instance-contracts.png[API Group Instance Contracts,95%,100%]
 
-<1> The contracts for an API instance at the instance-level
-
-<2> The API Group for which the contracts are displayed
-
-<3> The applications that currently have a contract with the API instance
-
-<4> The contract that is currently active
-
-<5> The contracts for an API instance at the API Group-level
+[calloutlist]
+. The contracts for an API instance at the instance-level
+. The API Group for which the contracts are displayed
+. The applications that currently have a contract with the API instance
+. The contract that is currently active
+. The contracts for an API instance at the API Group-level
 
 An application can have multiple contracts with the different APIs in an API Group. You can view the API instance contracts at the API Group level. The contracts are sorted by the applications that are in contract with the API Group. The contract that is currently active within an API Group is displayed as `Applied`.
 

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

@@ -63,7 +63,7 @@ outbound.truststore.password_281324
 
 The `281324` suffix in this case is API Instance ID of your API Proxy.
 
-If you inspect your API Proxy's XML, you can see these properites being used in your trustore/keystore configurations:
+If you inspect your API Proxy's XML, you can see these properties being used in your trustore/keystore configurations:
 
 [source,xml,linenums]
 ----

modules/ROOT/pages/configure-api-task.adoc

@@ -18,7 +18,7 @@ Not all options are available depending on the runtime as well as the API.
 | *Base path* | Specifies the URL prefix for all API paths, relative to the host root. It must start with a leading slash /. | No | 
 | **Advanced Options** |  |  |
 | *Scheme* | Specifies whether to use HTTP or HTTPS. | Yes | If you select HTTPS, specify a TLS context for inbound traffic.
-| *Port* | Specifies the number to use if the displayed port is incorrect. | No | 
+| *Port* | Specifies the number to use if the displayed port is incorrect. | No | Port can be shared between API instances over the same Target as long as the Base paths are different. Only available on Flex 1.2.0+.
 |===
 
 == Configure an API Instance on Service Mesh Options

modules/ROOT/pages/datagraph-managing-contracts.adoc

@@ -13,8 +13,9 @@ In API Manager, the DataGraph *Contracts* page lists client applications that ha
 
 image::datagraph-contracts.png[The DataGraph contracts page]
 
-<1> To get additional information about a client application, click the *>* icon next to the application's name.
-<2> To revoke an application's access, click *Revoke*.
+[calloutlist]
+. To get additional information about a client application, click the *>* icon next to the application's name.
+. To revoke an application's access, click *Revoke*.
 +
 To restore access, click *Restore*.
 

modules/ROOT/pages/datagraph-settings.adoc

@@ -7,13 +7,11 @@ On the DataGraph Administration settings page, you can select environments, view
 
 image::datagraph-settings.png[The illustration shows the Anypoint DataGraph Administration page]
 
-<1> *Switch Environment* control. Click the control to see a list of environments you have added to your organization. Select an environment to switch.
-
-<1> *Consumer endpoint* edit options. To edit the current endpoint, click the *Edit consumer endpoint* icon. To revert to the system-generated endpoint, click the *Revert* icon.
-
-<1> *DataGraph Policies* configuration options. You can choose to restrict requests to your unified schema from registered client applications only, set SLA-based rate limiting for requests, or allow requests from anyone with access to the unified schema's endpoint.
-
-<1> *DataGraph external client providers* control. To see a list of external client providers previously configured by your organization administrators, click the control. Select a provider from the list. To run queries in Anypoint DataGraph, obtain proper credentials from the external client provider.
+[calloutlist]
+. *Switch Environment* control. Click the control to see a list of environments you have added to your organization. Select an environment to switch.
+. *Consumer endpoint* edit options. To edit the current endpoint, click the *Edit consumer endpoint* icon. To revert to the system-generated endpoint, click the *Revert* icon.
+. *DataGraph Policies* configuration options. You can choose to restrict requests to your unified schema from registered client applications only, set SLA-based rate limiting for requests, or allow requests from anyone with access to the unified schema's endpoint.
+. *DataGraph external client providers* control. To see a list of external client providers previously configured by your organization administrators, click the control. Select a provider from the list. To run queries in Anypoint DataGraph, obtain proper credentials from the external client provider.
 +
 If your administrators haven't configured any external client providers, this item is not available.
 

modules/ROOT/pages/datagraph-viewing-application-contracts.adoc

@@ -9,9 +9,10 @@ To view or manage client applications with Anypoint DataGraph contracts, click *
 
 image::datagraph-view-contracts.png[The illustration shows the Client Applications page]
 
-<1> Filter applications based on contract types. Select *Clients with DataGraph Contracts* to view only applications with DataGraph contracts.
-<2> Choose a client applications to see its contract details.
-<3> View the contract options for a selected client application.
+[calloutlist]
+. Filter applications based on contract types. Select *Clients with DataGraph Contracts* to view only applications with DataGraph contracts.
+. Choose a client applications to see its contract details.
+. View the contract options for a selected client application.
 +
 From this view, you can reset a client secret, revoke a client contract, delete an application, or remove the application owner.
 

modules/ROOT/pages/delete-sla-tier-task.adoc

@@ -9,7 +9,7 @@ endif::[]
 * Set up and add the new SLA Tier.
 . Notify application owners of the new tier name and ask them to re-request access to the API using the new tier.
 . After all application owners sign up for a new tier and you approve their move to the new tier, delete the old tier:
-* On the API dashbaord, select SLA Tiers.
+* On the API dashboard, select SLA Tiers.
 * Click Delete.
 
 == See Also

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

@@ -22,9 +22,9 @@ To access API Manager, log in to Anypoint Platform and select *API Manager* from
 
 image::api-manager-ui-overview.png["API Manager page navigation shown with callouts.",97%,97%]
 
-<1> The environment selector. Anypoint Platform enables you to create and manage separate deployment environments for APIs and applications. API Manager displays all environments except design environments. For details, see xref:switch-environment-task.adoc[Switching Environments].
-
-<2> Navigation menu:
+[calloutlist]
+. The environment selector. Anypoint Platform enables you to create and manage separate deployment environments for APIs and applications. API Manager displays all environments except design environments. For details, see xref:switch-environment-task.adoc[Switching Environments].
+. Navigation menu:
 * *API Groups*
 +
 An _API group_ is an API asset that enables organizations to publish a group of API instances as a single unit. For details, see xref:api-groups-landing-page.adoc[API Groups].
@@ -44,19 +44,19 @@ Anypoint DataGraph enables you to unify all the data within your application net
 +
 API analytics provide insight into how your APIs are being used and how they are performing. For details, see xref:viewing-api-analytics.adoc[Reviewing Analytics Usage].
 
-<3> The *Add API* button. Enables you to add a new API instance, to promote an API from any environment to the current environment, or to import a configuration ZIP file that was exported from API Manager. For details, see xref:getting-started-proxy.adoc[Getting Started with Managing an API].
+. The *Add API* button. Enables you to add a new API instance, to promote an API from any environment to the current environment, or to import a configuration ZIP file that was exported from API Manager. For details, see xref:getting-started-proxy.adoc[Getting Started with Managing an API].
 
-<4> The *Environment information* button, available only to administrator users. Enables administrators to display a dialog with information about the current environment, such as environment credentials. Use environment credentials to provision the Anypoint Service Mesh adapter or to configure Studio to sync with your environment.
+. The *Environment information* button, available only to administrator users. Enables administrators to display a dialog with information about the current environment, such as environment credentials. Use environment credentials to provision the Anypoint Service Mesh adapter or to configure Studio to sync with your environment.
 
-<5> Search. Enables you to search for managed APIs using the API search field. Searches are case-insensitive. Filter search results by selecting *Active*.
+. Search. Enables you to search for managed APIs using the API search field. Searches are case-insensitive. Filter search results by selecting *Active*.
 
-<6> The tracking registration status of each API: *Active*, *Inactive*, or *Unregistered*.  
+. The tracking registration status of each API: *Active*, *Inactive*, or *Unregistered*.  
 +
 A status of *Unregistered* means that Anypoint Platform has never tracked the endpoint for this API version. Either you have entered a URL for an API or proxy that hasn't yet communicated with the platform, or you have declared an endpoint that is hosted somewhere other than an API gateway and need to proxy that endpoint so that the platform can track it.
 +
 The endpoint must have a tracking registration status of *Active* for governance policies and SLA tiers to function.
 
-<7> The name of each API. Clicking the API name navigates you to the API *Settings* view, where you manage the following:
+. The name of each API. Clicking the API name navigates you to the API *Settings* view, where you manage the following:
 +
 ** *Alerts*
 +
@@ -71,15 +71,15 @@ For details, see xref:policies-landing-page.adoc[Policies].
 +
 For details, see xref:defining-sla-tiers.adoc[Reviewing SLA Tiers Concepts].
 
-<8> The percentage of API requests that resulted in errors (in the past 24 hours).
+. The percentage of API requests that resulted in errors (in the past 24 hours).
 +
 If "No Data" is displayed, automatic monitoring has not been enabled for the API. For details, see xref:monitoring::quick-start.adoc[Monitoring Quick Start].
 
-<9> The total number of API requests (in the past 24 hours).
+. The total number of API requests (in the past 24 hours).
 +
 If "No Data" is displayed, automatic monitoring has not been enabled for the API. For details, see xref:monitoring::quick-start.adoc[Monitoring Quick Start].
 
-<10> The number of contracted client applications for each API. For details,
+. The number of contracted client applications for each API. For details,
 see xref:api-contracts-landing-page.adoc[Client Applications and Contracts].
 
 

modules/ROOT/pages/rate-limit-1.2.0-task.adoc

@@ -60,7 +60,7 @@ Possible identifiers must extract the result from the request using DataWeave, b
 
 As one algorithm must exist for every identifier, carefully create the DataWeave expression not to return an unbounded co-domain (or a very large one), as it will require hosting the same amount of algorithms in memory (if there is at least a request for every possible identifier). For example, suppose the DataWeave expression uses the ip as the identifier in a runtime that is public to the Internet. If every public IPv4 IP in the internet makes a request to this runtime, there will be 3,706,452,992 algorithms running in a single runtime. On an average of 250 bytes per algorithm, this would be approximately 1 terabyte in rate limit algorithms.
 
-MuleSoft recommends using a DatatWeave expression that resolves to a finite number of identifiers, and to keep the resulting set as small as possible.
+MuleSoft recommends using a DataWeave expression that resolves to a finite number of identifiers, and to keep the resulting set as small as possible.
 
 === Rate Limiting for Anypoint Service Mesh
 

modules/ROOT/pages/troubleshooting-config-properties-apiid-error.adoc

@@ -12,7 +12,7 @@ org.mule.runtime.deployment.model.api.DeploymentException: Failed to deploy arti
 Caused by: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.deployment.model.api.DeploymentInitException: PropertyNotFoundException: Couldn't find configuration property 
 value for key ${apiId} from properties provider Domain properties - within 
 resolver Deployment properties trying to process key apiId - within 
-esolver global-properties configuration attributes trying to process key apiId - within resolver environment properties provider trying to process key apiId - within resolver Deployment properties trying to process key apiId - within resolver External files trying to process key apiId - within resolver Deployment properties trying to process key apiId
+resolver global-properties configuration attributes trying to process key apiId - within resolver environment properties provider trying to process key apiId - within resolver Deployment properties trying to process key apiId - within resolver External files trying to process key apiId - within resolver Deployment properties trying to process key apiId
 ----
 
 == Cause