Leave link titles blank to pull titles from linked docs

Author: marinasasso

.vscode/settings.json

@@ -1 +1,18 @@
-{}
+{
+    "files.exclude": {
+        "**/.git": true,
+        "**/.svn": true,
+        "**/.hg": true,
+        "**/CVS": true,
+        "**/.DS_Store": true,
+        "**/Thumbs.db": true,
+        "**/.apivcs": true,
+        "**/.gitignore": true,
+        "**/.designer.json": true,
+        "**/.exchange.xml": true,
+        "**/.vscode": true,
+        "**/.mvn": true,
+        "**/.exchange_modules_tmp": true,
+        ".mule": true
+    }
+}

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

@@ -35,28 +35,28 @@ To access API Manager, log in to Anypoint Platform and select *API Manager*:
 image::api-manager-ui-overview.png["API Manager page navigation shown with callouts.",97%,97%]
 
 [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].
+. 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[].
 . Sidebar:
 * *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].
+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[].
 * *Automated Policies* 
 +
-Policy automation enables security architects and administrators to secure and govern every API running in an environment. For details, see xref:policies::policies-automated-overview.adoc[Automated Policies].
+Policy automation enables security architects and administrators to secure and govern every API running in an environment. For details, see xref:policies::policies-automated-overview.adoc[].
 * *Client Applications*
 +
-_Applications_ are external services that consume APIs. For details about applications and their related contracts, see xref:view-api-contracts.adoc[View API Instance Contracts].
+_Applications_ are external services that consume APIs. For details about applications and their related contracts, see xref:view-api-contracts.adoc[].
 * *Custom Policies*
 +
-_Custom policies_ are policies that anyone can develop and apply to their APIs, with the intention of extending existing functionality or defining new functionality. For details, see xref:policies::policies-custom-overview.adoc[Custom Policies].
+_Custom policies_ are policies that anyone can develop and apply to their APIs, with the intention of extending existing functionality or defining new functionality. For details, see xref:policies::policies-custom-overview.adoc[].
 * *DataGraph Administration*
 +
-Anypoint DataGraph enables you to unify all the data within your application network in a unified schema. For details, see xref:datagraph::index.adoc[Anypoint DataGraph Overview]. *DataGraph Administration* is only visible after you configure a DataGraph unified schema.
+Anypoint DataGraph enables you to unify all the data within your application network in a unified schema. For details, see xref:datagraph::index.adoc[]. *DataGraph Administration* is only visible after you configure a DataGraph unified schema.
 * *Mule API Analytics*
 +
-Mule API Analytics provide insight into how your Mule APIs are being used and how they are performing. For details, see xref:viewing-api-analytics.adoc[Reviewing Mule API Analytics Usage].
+Mule API Analytics provide insight into how your Mule APIs are being used and how they are performing. For details, see xref:viewing-api-analytics.adoc[].
 
-. 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[].
 
 . 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.
 
@@ -79,10 +79,10 @@ For details, see xref:api-instance-landing-page.adoc[].
 For details, see xref:using-api-alerts.adoc[].
 ** *Contracts*
 +
-For details, see xref:api-contracts-landing-page.adoc[Client Applications and Contracts].
+For details, see xref:api-contracts-landing-page.adoc[].
 ** *Policies*
 +
-For details, see xref:policies-landing-page.adoc[Policies].
+For details, see xref:policies-landing-page.adoc[].
 ** *SLA Tiers*
 +
 For details, see xref:defining-sla-tiers.adoc[].
@@ -95,14 +95,14 @@ For details, see xref:govern-api-instances.adoc[].
 
 . 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[Anypoint Monitoring Quick Start].
+If "No Data" is displayed, automatic monitoring has not been enabled for the API. For details, see xref:monitoring::quick-start.adoc[].
 
 . 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[Anypoint Monitoring Quick Start].
+If "No Data" is displayed, automatic monitoring has not been enabled for the API. For details, see xref:monitoring::quick-start.adoc[].
 
 . The number of contracted client applications for each API. For details,
-see xref:api-contracts-landing-page.adoc[Client Applications and Contracts].
+see xref:api-contracts-landing-page.adoc[].
 
 
 == API Manager Components, Concepts, and Features
@@ -115,7 +115,7 @@ The API Summary shows key information about a deployed API instance:
 
 image::api-instance-summary.png[API Summary page]
 
-For details, see xref:api-instance-landing-page.adoc[API Instance].
+For details, see xref:api-instance-landing-page.adoc[].
 
 === API Alerts
 
@@ -128,7 +128,7 @@ An _API alert_ (different from a Runtime Manager alert) is an alarm that flags o
 
 API Manager triggers alerts when states change from desirable to undesirable or vice versa. When an alert is triggered, API Manager sends an email notification to you and to anyone else you specify in the configuration.
 
-For details, see xref:using-api-alerts.adoc[Reviewing Alerts Concepts].
+For details, see xref:using-api-alerts.adoc[].
 
 === Contracts
 
@@ -139,7 +139,7 @@ Contracts are enforced with either of the following:
 * SLA enforcement policies
 * Client enforcement policies
 
-For details about enforcement policies, see xref:api-contracts-landing-page.adoc[Client Applications and Contracts].
+For details about enforcement policies, see xref:api-contracts-landing-page.adoc[].
 
 === Policies
 
@@ -150,13 +150,13 @@ API Manager supports the following types of policies:
 * Default policies
 * Custom policies
 
-For details, see xref:policies-landing-page.adoc[Policies].
+For details, see xref:policies-landing-page.adoc[].
 
 === SLA Tiers
 
 _Service Level Access (SLA) tiers_ are categories of user access that you define for an API. The tier definition combined with an SLA-based policy determines whether access to the API at a certain level requires your approval. The tier definition also can limit the number of requests an application can make to the API. To enforce SLA tiers, you need to apply a rate-limiting or throttling policy that is SLA-based.
 
-For details, see xref:defining-sla-tiers.adoc[Reviewing SLA Tiers Concepts].
+For details, see xref:defining-sla-tiers.adoc[].
 
 === Settings
 
@@ -166,7 +166,7 @@ To add an API instance, see xref:add-api-instances.adoc[].
 
 After you create the API instance, you can edit the configuration settings from Settings.
 
-To edit an API instance, see xref:edit-api-endpoint-task.adoc[Edit an API Instance].
+To edit an API instance, see xref:edit-api-endpoint-task.adoc[].
 
 === Governance Report
 
@@ -176,14 +176,14 @@ API Governance tests API instances against rulesets to determine conformance iss
 
 You can view the governance validation report details to get the information you need to fix conformance issues. The validation report is available both in API Manager on the Governance Report page and in API Governance.
 
-To learn more about governing your API instances, see xref:govern-api-instances.adoc[Govern API Instances].
+To learn more about governing your API instances, see xref:govern-api-instances.adoc[].
 
 
 === Client Providers (Identity Providers)
 
 You use client providers to enforce security and regulations in your business organization. Client providers authorize client applications. 
 
-For details about using client providers, see xref:configure-multiple-credential-providers.adoc[Configure Multiple Client Providers for Client Management].
+For details about using client providers, see xref:configure-multiple-credential-providers.adoc[].
 
 === API Assets
 
@@ -197,20 +197,20 @@ API assets, published by Exchange, are the components that comprise applications
 * Modules
 * Connectors
 
-For details about sharing assets via a private Exchange or an Exchange public portal, see xref:exchange::about-sharing-assets.adoc[Share Assets].
+For details about sharing assets via a private Exchange or an Exchange public portal, see xref:exchange::about-sharing-assets.adoc[].
 
 === API Console
 
-When you create or edit APIs in API Manager, use xref:apikit::apikit-simulate.adoc[API Console] to expose and test your API specification. You can test RAML and OAS APIs when you manage the API as an endpoint with proxy. The console flow is already included and enabled (by default) in the API specification when you download an out-of-the-box proxy for your Mule application.
+When you create or edit APIs in API Manager, use xref:apikit::apikit-simulate.adoc[] to expose and test your API specification. You can test RAML and OAS APIs when you manage the API as an endpoint with proxy. The console flow is already included and enabled (by default) in the API specification when you download an out-of-the-box proxy for your Mule application.
 
-Starting with Mule 4, you can enable access to API Console and modify the API Console path from API Manager. API Console access from API Manager is disabled by default. For information about how to enable API Console access from API Manager, see xref:manage-exchange-api-task.adoc[Creating an API Instance by Importing from Exchange].
+Starting with Mule 4, you can enable access to API Console and modify the API Console path from API Manager. API Console access from API Manager is disabled by default. For information about how to enable API Console access from API Manager, see xref:manage-exchange-api-task.adoc[].
 
 
 === API Groups
 
 An _API group_ is a collection of API instances that act as a single unit, so that applications can access them using one client ID. API groups are created in API Manager and published to Exchange.
 
-For details, see xref:api-groups-landing-page.adoc[API Groups].
+For details, see xref:api-groups-landing-page.adoc[].
 
 === Autodiscovery Schemes
 
@@ -220,18 +220,18 @@ Through autodiscovery schemes, API Manager can track the API throughout the life
 
 A system administrator groups individuals within an organization into business groups. Each group has its own Exchange API assets and its own environments.
 
-For details, see xref:access-management::business-groups.adoc[Business Groups].
+For details, see xref:access-management::business-groups.adoc[].
 
 === Environments
 
 Anypoint Platform enables you to create and manage separate deployment environments for APIs and applications. These environments are independent from each other and enable you to test your applications under the same conditions as in your production environment.
 
 The support for environments in strategic components of Anypoint Platform eliminates the need to construct version names to reflect an environment. Restricting access to and managing environments is also simplified. Permissions to access APIs are environment-based.
 
-For details, see xref:access-management::environments.adoc[Environments].
+For details, see xref:access-management::environments.adoc[].
 
 == See Also
 
-* xref:general::api-led-overview.adoc[Tutorial: Build an API from Start to Finish]
-* xref:getting-started-proxy.adoc[Get Started with Managing an API]
-* xref:general::glossary.adoc[Anypoint Platform Glossary]
+* xref:general::api-led-overview.adoc[]
+* xref:getting-started-proxy.adoc[]
+* xref:general::glossary.adoc[]