Navigate to

glenn-rodgers-sf · glenn-rodgers-sf · commit a25159c73398 · 2023-06-07T11:22:16.000-05:00
diff --git a/modules/ROOT/pages/_partials/task-configure-proxy.adoc b/modules/ROOT/pages/_partials/task-configure-proxy.adoc
@@ -12,7 +12,7 @@
 [[select_proxy_type]]
 = Select a Proxy Type
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . In *API Administration*, click *Add API* and select *Add new API*.
 . Select *Mule Gateway* as your runtime.
 . Select *Deploy a proxy application* for *Proxy type*.
diff --git a/modules/ROOT/pages/access-developer-portal-task.adoc b/modules/ROOT/pages/access-developer-portal-task.adoc
@@ -14,7 +14,7 @@ Before you access an asset portal, ensure that you meet one of the following con
 
 To access an asset portal:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the name of the API instance that you want to access.
 . Click *Actions* and select *View API in Exchange*.
 +
diff --git a/modules/ROOT/pages/add-api-alert-task.adoc b/modules/ROOT/pages/add-api-alert-task.adoc
@@ -15,7 +15,7 @@ NOTE: This tutorial is for Mule Gateway and Service Mesh runtimes. To add alerts
 == Add API Alerts for Mule Gateway or Service Mesh
 To add an API alert to a Mule Gateway or Service Mesh API:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the API instance to which to add an alert.
 . Click *Alerts* > *Add alert*.
 . Specify the alert options:
diff --git a/modules/ROOT/pages/api-groups-add-sla-tiers.adoc b/modules/ROOT/pages/api-groups-add-sla-tiers.adoc
@@ -8,7 +8,7 @@ You can add multiple SLA tiers to an API Group instance.
 
 To add an SLA tier:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . Click *API Groups*.
 . Expand the *API Group* list and click the API Group instance to which you want to add the SLA tier.
 . Click *SLA Tiers* and then click *Add SLA tier* on the details page.
diff --git a/modules/ROOT/pages/api-groups-creating-groups.adoc b/modules/ROOT/pages/api-groups-creating-groups.adoc
@@ -35,7 +35,7 @@ You create an API Group at the organization level.
 
 To create API Groups:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . Click *API Groups* > *Create API Group*.
 . In the *API Group name* field, specify a name for the API Group that you want to create: for example, `Social Chatter`.
 . In the *API Group version* field, specify the version for the API Group: for example, `v1`.
diff --git a/modules/ROOT/pages/api-groups-deleting-groups.adoc b/modules/ROOT/pages/api-groups-deleting-groups.adoc
@@ -12,7 +12,7 @@ Before you begin, ensure that you have the API Group Administrator permissions t
 
 To delete an API Group:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . Click *API Groups*.
 . Select the version of the API Group that you want to delete.
 . Click *...* > *Delete*.
diff --git a/modules/ROOT/pages/api-groups-deprecating-groups.adoc b/modules/ROOT/pages/api-groups-deprecating-groups.adoc
@@ -13,7 +13,7 @@ Before you begin, ensure that you have the API Group Administrator permissions t
 
 To deprecate an API Group:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . Click *API Groups*.
 . Select the version of the API Group that you want to deprecate.
 . Click *...* > *Deprecate*.
diff --git a/modules/ROOT/pages/api-groups-manage-api-group-instance-contracts.adoc b/modules/ROOT/pages/api-groups-manage-api-group-instance-contracts.adoc
@@ -57,7 +57,7 @@ Note that a contract is applied for an API but not for an API Group instance. Fo
 
 To view API Group instance contracts:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . Click *API Groups*.
 . From the API Group instance details page, click the `version:instance` link for the API Group instance.
 . Click *Contracts* and expand the instance for which you want to view the contract information:
diff --git a/modules/ROOT/pages/api-groups-modifying-groups.adoc b/modules/ROOT/pages/api-groups-modifying-groups.adoc
@@ -48,7 +48,7 @@ You might want to add API instances to an existing API Group to widen the busine
 
 To add API instances to an existing API Group:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . Click *API Groups*.
 . On the API Groups details page, expand the API Group to view its available versions.
 . Click *Add group instance* for the version of the API Group that you want to add the API instance to.
@@ -71,7 +71,7 @@ If your business requirements change, you might want to modify an API Group by r
 
 To remove an API instance from an API Group:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . Click *API Groups*.
 . On the API Groups page, expand the API Group to view its available versions.
 . Expand the API Group version to view its available instances.
@@ -90,7 +90,7 @@ If you modify an API Group to add a new API or delete an existing API based on c
 
 To create additional versions of an API Group:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . Click *API Groups*.
 . Click *Add group version* for the API Group.
 . In the *API Group Version* field, specify the version number that you want to create: for example, `v1.1` or `v2.0`.
diff --git a/modules/ROOT/pages/api-groups-promote-api-instance.adoc b/modules/ROOT/pages/api-groups-promote-api-instance.adoc
@@ -19,7 +19,7 @@ For example, if the API Group instance that you want to promote contains the Fac
 
 To promote an API Group instance:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . Click *API Groups* > *Promote from environment*.
 . From the *Source Environment* list, select the environment of the API you want to promote.
 . From the *API Group* list, select the API Group to which the API instance belongs.
diff --git a/modules/ROOT/pages/api-groups-publishing-to-exchange.adoc b/modules/ROOT/pages/api-groups-publishing-to-exchange.adoc
@@ -12,7 +12,7 @@ Before you begin, ensure that you have permissions to all the assets in the API
 
 === To publish API Groups to Exchange:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . Click *API Groups*.
 . From the API Groups details page, click the *API Group version* that you want to publish and click the *API Group instance*.
 +
diff --git a/modules/ROOT/pages/api-groups-remove-sla-tier.adoc b/modules/ROOT/pages/api-groups-remove-sla-tier.adoc
@@ -7,7 +7,7 @@ You can remove an SLA tier from an API Group instance if you no longer need it.
 
 To remove an SLA tier:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . Click *API Groups*.
 . Expand the API Group list and click the API Group instance to which you want to add the SLA tier.
 . Click *SLA Tiers*:
diff --git a/modules/ROOT/pages/classify-api-task.adoc b/modules/ROOT/pages/classify-api-task.adoc
@@ -100,12 +100,12 @@ Anypoint Platform assigns the unique and immutable Organization ID and Environme
 Deployed in CloudHub:
 
 . Get the environment client ID and secret.
-. Go to Access Manager.
+. Navigate to Access Manager.
 . Click  Environments.
 . Click the environment name that you want to use.
 . Copy the Client ID and Client Secret.
 . Update the application in CloudHub:
-. Go to the proxy application in Runtime Manager.
+. Navigate to the proxy application in Runtime Manager.
 . Click Settings > Properties.
 . Change the values of the following properties to the values from the Environment:
 +
@@ -125,14 +125,14 @@ Deployed in standalone Mule Runtime:
 Perform these steps to prepare Mule Runtime to use API environments without updating the agent or registering the server with Runtime Manager.
 
 . Get the environment client ID and secret.
-. Go to Access Manager.
+. Navigate to Access Manager.
 . Click  Environments.
 . Click the environment name that you want to use.
 . Copy the Client ID and Client Secret.
 
 Updating an application in CloudHub:
 
-. Go to the proxy application in Runtime Manager.
+. Navigate to the proxy application in Runtime Manager.
 . Click Settings > Properties.
 . Change the values of the following properties to the values from the Environment:
 +
@@ -192,14 +192,14 @@ To update an existing server:
 
 If your API was deployed in Runtime Manager:
 
-. Go to Access Manager.
+. Navigate to Access Manager.
 . Click Environments.
 . Click the environment name you want to use.
 . Copy the Client ID and Client Secret.
 
 To update an application in Runtime Manager:
 
-. Go to the proxy application in Runtime Manager.
+. Navigate to the proxy application in Runtime Manager.
 . Click Settings.
 . Click Properties.
 . Change the values of the following properties to the values from the Environment:
@@ -222,14 +222,14 @@ This section explains the manual steps needed to prepare Mule Runtime to use API
 
 Getting the environment client ID and secret:
 
-. Go to Access Manager.
+. Navigate to Access Manager.
 . Click  Environments.
 . Click the environment name that you want to use.
 . Copy the Client ID and Client Secret.
 
 Updating an application in Runtime Manager:
 
-. Go to the proxy application in Runtime Manager.
+. Navigate to the proxy application in Runtime Manager.
 . Click Settings.
 . Click Properties.
 . Change the values of the following properties to the values from the environment:
diff --git a/modules/ROOT/pages/create-instance-task.adoc b/modules/ROOT/pages/create-instance-task.adoc
@@ -18,7 +18,7 @@ when you add a new API instance, you need to xref:configure-api-task.adoc[config
 
 == Add a New API
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click *Add API* and select *Add new API*.
 . Select and configure your runtime from the following options:
 Flex Gateway:: Select Flex Gateway for any APIs that need a flexible and performant API gateway
@@ -59,7 +59,7 @@ include::partial$task-configure-proxy.adoc[tags=mid-steps;asset-type-options;con
 
 == Promote API from Environment
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . In *API Administration*, click **Add API** and select **Promote API from environment**.
 . Select the **Source Environment**.
 . Select the **API** by entering the name of the API into the search field.
@@ -71,7 +71,7 @@ include::partial$task-configure-proxy.adoc[tags=mid-steps;asset-type-options;con
 
 == Import API from Zip File
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . From *API Administration*, click **Add API** and select **Import API from zip file**.
 . Click **Choose file** and select your API instance configuration zip file.
 . Click **Next**.
diff --git a/modules/ROOT/pages/datagraph-adding-sla-tiers.adoc b/modules/ROOT/pages/datagraph-adding-sla-tiers.adoc
@@ -7,7 +7,7 @@ Add multiple SLA tiers to an Anypoint DataGraph instance to control user access
 
 To add an SLA tier:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . Click *DataGraph Administration* > *SLA Tiers*:
 . From the DataGraph SLA Tiers page, click *Add SLA tier*:
 +
diff --git a/modules/ROOT/pages/delete-api-task.adoc b/modules/ROOT/pages/delete-api-task.adoc
@@ -10,7 +10,7 @@ You cannot delete an API specification that is currently used in one or more API
 
 To delete API instances from API Manager:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the name of the API instance you want to delete. 
 . Select *Actions* > *Delete API*.
 . Click *Delete* to confirm. 
diff --git a/modules/ROOT/pages/deprecate-api-latest-task.adoc b/modules/ROOT/pages/deprecate-api-latest-task.adoc
@@ -5,7 +5,7 @@ endif::[]
 
 While transitioning consumers of your API to an updated instance, you can prevent developers from signing up for access to your old API instance. As an API administrator, you mark an API as deprecated to remove the invitation for developers to request access from the portal page. Existing application contracts remain active but no new contracts can be created for that API instance. Deprecated APIs have an indicator in any location where they appear showing they are deprecated. A badge in search results indicates that the instance is deprecated.
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the name of the API instance you want to deprecate. 
 . Select *Actions* > *Deprecate API*.
 . Click *Ok*. 
diff --git a/modules/ROOT/pages/download-proxy-task.adoc b/modules/ROOT/pages/download-proxy-task.adoc
@@ -9,7 +9,7 @@ NOTE: You must have View APIs Configuration permission to download a proxy.
 
 You can download a proxy that you generated in API Manager by following this procedure.
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the API instance whose proxy you want to download.
 . Click *Actions* and select *Download Proxy*.
 // when Mule 4 is released, will this dialog list it, or will u download some other way?
diff --git a/modules/ROOT/pages/edit-api-endpoint-task.adoc b/modules/ROOT/pages/edit-api-endpoint-task.adoc
@@ -9,7 +9,7 @@ For more information about the API endpoint configuration fields, see the releva
 
 To edit an API instance's endpoint:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the name of the API instance whose endpoint you want to edit. 
 . Click *Settings*.
 . Edit the desired endpoint configuration fields.
diff --git a/modules/ROOT/pages/edit-enable-disable-alerts-task.adoc b/modules/ROOT/pages/edit-enable-disable-alerts-task.adoc
@@ -5,7 +5,7 @@ endif::[]
 
 When creating an alert, you can select if the alert will be enabled or disabled. You can also edit an existing alert and enable or disable the alert.
 
-. Go to *Anypoint Platform* > *API Manager*..
+. Navigate to *Anypoint Platform* > *API Manager*..
 . In *API Administration*, click the API instance whose alert you want to edit.
 . Click *Alerts*.
 . Click the *Edit* button on the alert you want to edit.
diff --git a/modules/ROOT/pages/export-api-latest-task.adoc b/modules/ROOT/pages/export-api-latest-task.adoc
@@ -21,7 +21,7 @@ The following information is not exported with the API instance:
 
 To export an API instance:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the name of the API you want to export. 
 . Click *Actions* and select *Export API*.
 +
diff --git a/modules/ROOT/pages/find-api-id-task.adoc b/modules/ROOT/pages/find-api-id-task.adoc
@@ -7,7 +7,7 @@ API Manager generates the `apiId` of new API instances managed by API Manager an
 
 To find the API instance ID:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the name of the API instance whose ID you want.
 +
 The API instance ID is displayed under *API Instance ID*.
diff --git a/modules/ROOT/pages/manage-client-apps-latest-task.adoc b/modules/ROOT/pages/manage-client-apps-latest-task.adoc
@@ -18,7 +18,7 @@ To manually approve or reject requests, you must have:
 
 To approve or reject requests to access your API:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . In *API Administration*, click the name of the API instance to which you are requesting access. 
 . Click *Contracts*. 
 +
diff --git a/modules/ROOT/pages/manage-exchange-api-task.adoc b/modules/ROOT/pages/manage-exchange-api-task.adoc
@@ -12,7 +12,7 @@ If you are running an API on a self-managed server, you have two options for add
 
 To manage an API instance from Exchange:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click **Add API** and select **Add new API**.
 . Select **Mule Gateway** as your runtime.
 . Select **Deploy a proxy application** for **Proxy type**.
@@ -58,7 +58,7 @@ For example, if an API is defined with the `Implementation URI` set to `http://j
 
 To create a new API instance and configure the endpoint:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click **Add API** and select **Add new API**.
 . Select **Mule Gateway** as your runtime.
 . Select **Deploy a proxy application** for **Proxy type**.
diff --git a/modules/ROOT/pages/manage-versions-instances-concept.adoc b/modules/ROOT/pages/manage-versions-instances-concept.adoc
@@ -9,7 +9,7 @@ After you publish new version details for an API definition to Exchange, you mus
 
 To change the asset version of an API instance:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the name of the API instance whose version you want to manage.
 . Select *Actions* > *Change API specification*.
 . In *Asset version*, Select *latest*. 
diff --git a/modules/ROOT/pages/promote-api-task.adoc b/modules/ROOT/pages/promote-api-task.adoc
@@ -7,7 +7,7 @@ A tight integration of Anypoint Platform components extends the use of environme
 
 You must have `Manage APIs Configuration` permission to promote an API and `Access Management` permission to set permissions for viewing and managing an entity. You can only promote an entity (Policies, Alerts, and so forth) if you have permission to view the source and permission to manage the destination over each entity. Typical view permissions are `View API Configuration` and `View Policies`, as explained in xref:environment-permission-task.adoc[To Grant Permission to Access Environments]. Set the permissions as needed before proceeding.
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . In *API Administration*lick *Add API* and select *Promote API from environment*.
 . For *Source Environment*, select the environment of the API to promote.
 . For *API*, enter the name of the API and then select it from the APIs in the source environment.
diff --git a/modules/ROOT/pages/remove-client-app-latest-task.adoc b/modules/ROOT/pages/remove-client-app-latest-task.adoc
@@ -9,7 +9,7 @@ Deleting a contract deletes the approved contract from Anypoint Exchange. Revoki
 
 To delete a contract with an application:
 
-. Go to *Anypoint Platform* > *API Manager*. 
+. Navigate to *Anypoint Platform* > *API Manager*. 
 . In *API Administration*, click the name of the API instance for which you want to revoke access.
 . Click the `<api version>:<api instance or label>` link, for example, `v1:16046365`. 
 . Click *Contracts*.
diff --git a/modules/ROOT/pages/view-api-contracts.adoc b/modules/ROOT/pages/view-api-contracts.adoc
@@ -8,7 +8,7 @@ From API Manager, you can view the contracts created for your API instance when
 
 To view your API instance contracts:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . In *API Administration*, click the name of the API instance you want to configure.
 . Click *Contracts*. +
 A tab displays the contract information for your API instance.
diff --git a/modules/ROOT/pages/viewing-api-analytics.adoc b/modules/ROOT/pages/viewing-api-analytics.adoc
@@ -8,7 +8,7 @@ You can view your Mule API Analytics data from both API Manager and Anypoint Mon
 
 To view Mule API Analytics Data in API Manager:
 
-. Go to *Anypoint Platform* > *API Manager*.
+. Navigate to *Anypoint Platform* > *API Manager*.
 . Click *Mule API Analytics*.
 
 From the dashboard, you can navigate to the analytics about your APIs gathered by Anypoint Platform.

Original file line number	Diff line number	Diff line change
`@@ -14,7 +14,7 @@ Before you access an asset portal, ensure that you meet one of the following con`
`14`	`14`
`15`	`15`	`To access an asset portal:`
`16`	`16`
`17`		`-. Go to Anypoint Platform > API Manager.`
	`17`	`+. Navigate to Anypoint Platform > API Manager.`
`18`	`18`	`. In API Administration, click the name of the API instance that you want to access.`
`19`	`19`	`. Click Actions and select View API in Exchange.`
`20`	`20`	`+`