fix broken links.

Author: dushaniw

en/docs/api-design-manage/deploy-and-publish/deploy-on-gateway/api-gateway/api-gateways-with-dedicated-backends.md

@@ -1,6 +1,6 @@
 # Gateways with Dedicated Backends
 
-We can extend the [multiple gateway environments]({{base_path}}/manage-apis/deploy-and-publish/api-gateway/maintaining-separate-production-and-sandbox-gateways) feature by utilizing parameterized endpoint capabilities of WSO2 API Manager to have each gateway point to a different back-end endpoint. Universal Gateway is the actual runtime of the APIs that are developed and published from the API Publisher. WSO2 API Manager is capable of publishing APIs to different Gateways where API users connect to those Universal Gateways in order to do the actual API calls through the applications to which they are subscribed.
+We can extend the [multiple gateway environments]({{base_path}}/api-gateway/maintaining-separate-production-and-sandbox-gateways) feature by utilizing parameterized endpoint capabilities of WSO2 API Manager to have each gateway point to a different back-end endpoint. Universal Gateway is the actual runtime of the APIs that are developed and published from the API Publisher. WSO2 API Manager is capable of publishing APIs to different Gateways where API users connect to those Universal Gateways in order to do the actual API calls through the applications to which they are subscribed.
 
 However, the API Publisher can only provide a single static endpoint for an API in the implementation. Therefore, the API call is directed to a single endpoint in whichever Gateway the API is deployed in, as depicted in the diagram below.
 
@@ -18,7 +18,7 @@ Follow the steps below to configure a parameterized endpoint as the API endpoint
 
     [![Dedicated backend definition]({{base_path}}/assets/img/learn/dedicated-backend-def.png)]({{base_path}}/assets/img/learn/dedicated-backend-def.png)
 
-3.  Save and [publish]({{base_path}}/manage-apis/deploy-and-publish/publish-on-dev-portal/publish-an-api) the API.
+3.  Save and [publish]({{base_path}}/api-design-manage/deploy-and-publish/publish-on-dev-portal/publish-an-api) the API.
 
 4.  Navigate to the `<API-M_HOME>/repository/deployment/server/synapse-configs/default/sequences` directory of each Gateway and create the following sequence.
 

en/docs/api-design-manage/deploy-and-publish/deploy-on-gateway/api-gateway/gateway-policies.md

@@ -55,7 +55,7 @@ Follow the instructions provided below to create a gateway policy:
         [![Save individual policy data]({{base_path}}/assets/img/deploy/gateway/global-polices-add-header-policy.png){: style="width:90%"}]({{base_path}}/assets/img/deploy/gateway/global-polices-add-header-policy.png)
 
         !!!note
-            All the policies listed for addition as global policies are [common policies]({{base_path}}/manage-apis/design/api-policies/create-policy/).
+            All the policies listed for addition as global policies are [common policies]({{base_path}}/api-design-manage/design/api-policies/create-policy/).
 
     5. After saving the dropped policy, you should now be able to view the associated **Add Header** policy indicated by the initials **AH**.
 
@@ -95,4 +95,4 @@ To undeploy a global policy from any gateway environment, simply click on the cl
 
 You can engage policies with APIs and their resources:
 
-[Attaching API Policies]({{base_path}}/manage-apis/design/api-policies/attach-policy/)
+[Attaching API Policies]({{base_path}}/api-design-manage/design/api-policies/attach-policy/)

en/docs/api-design-manage/deploy-and-publish/deploy-on-gateway/api-gateway/mutual-ssl-between-api-gateway-and-backend.md

@@ -110,7 +110,7 @@ Now both the backend service and API Manager are configured to use default key s
 
 You can do the following to test your mutual SSL configurations
 
-1.  [Create an API]({{base_path}}/manage-apis/design/create-api/create-rest-api/create-a-rest-api)
-2.  [Publish the API]({{base_path}}/manage-apis/deploy-and-publish/publish-on-dev-portal/publish-an-api)
-3.  [Subscribe to the API]({{base_path}}/consume/manage-subscription/subscribe-to-an-api)
-4.  [Invoke the API]({{base_path}}/consume/invoke-apis/invoke-apis-using-tools/invoke-an-api-using-the-integrated-api-console)
+1.  [Create an API]({{base_path}}/api-design-manage/design/create-api/create-rest-api/create-a-rest-api)
+2.  [Publish the API]({{base_path}}/api-design-manage/deploy-and-publish/publish-on-dev-portal/publish-an-api)
+3.  [Subscribe to the API]({{base_path}}/api-developer-portal/manage-subscription/subscribe-to-an-api)
+4.  [Invoke the API]({{base_path}}/api-developer-portal/invoke-apis/invoke-apis-using-tools/invoke-an-api-using-the-integrated-api-console)

en/docs/api-design-manage/deploy-and-publish/deploy-on-gateway/api-gateway/response-caching.md

@@ -8,7 +8,7 @@ You need to enable response caching when creating a new API or editing an existi
 
 Please follow below steps to enable response caching for an API.
 
-1.  [Create an API]({{base_path}}/manage-apis/design/create-api/create-rest-api/create-a-rest-api/).
+1.  [Create an API]({{base_path}}/api-design-manage/design/create-api/create-rest-api/create-a-rest-api/).
 
 2.  Navigate to the **Runtime** tab under **API Configurations** where you find the response caching configuration. Then turn on Response caching and give a timeout value. This enables the default response caching settings.
 

en/docs/api-design-manage/deploy-and-publish/deploy-on-gateway/deploy-api/deploy-through-multiple-api-gateways.md

@@ -162,7 +162,7 @@ Carry out the following instructions in the **second** and the **third** instanc
 
 4.  Enable JSON Web Token (JWT) if required.
 
-     For instructions, see [Generating JSON Web Token]({{base_path}}/manage-apis/deploy-and-publish/deploy-on-gateway/api-gateway/passing-enduser-attributes-to-the-backend-via-api-gateway/).   
+     For instructions, see [Generating JSON Web Token]({{base_path}}/api-gateway/passing-enduser-attributes-to-the-backend-via-api-gateway/).   
 
 5.  Add the public certificate of the private key (that is used for signing the tokens) to the truststore under the `"gateway_certificate_alias"` alias. 
 

en/docs/api-design-manage/deploy-and-publish/deploy-on-gateway/federated-gateways/overview.md

@@ -29,7 +29,7 @@ Deploy and manage APIs on Amazon Web Services API Gateway. WSO2 API Manager come
 - OAuth 2.0 security via Lambda Authorizer
 - Centralized management through WSO2 API Manager
 
-[Learn more about AWS API Gateway deployment]({{base_path}}/manage-apis/deploy-and-publish/federated-gateways/aws/deploy-on-aws-api-gateway/)
+[Learn more about AWS API Gateway deployment]({{base_path}}/api-design-manage/deploy-and-publish/federated-gateways/aws/deploy-on-aws-api-gateway/)
 
 ### Azure API Gateway
 Deploy and manage APIs on Microsoft Azure API Management Service. The built-in Azure gateway connector facilitates deployment and discovery of APIs on Azure infrastructure.
@@ -51,7 +51,7 @@ Discover and manage APIs deployed on Kong Gateway. WSO2 API Manager supports bot
 - Support for Kong Kubernetes and Standalone modes
 - Unified management through WSO2 API Manager Control Plane
 
-[Learn more about Kong Gateway integration]({{base_path}}/manage-apis/deploy-and-publish/federated-gateways/kong/kong-standalone/discover-apis-on-kong-gateway/)
+[Learn more about Kong Gateway integration]({{base_path}}/api-design-manage/deploy-and-publish/federated-gateways/kong/kong-standalone/discover-apis-on-kong-gateway/)
 
 ### Envoy Gateway
 Discover and manage APIs deployed on Envoy Gateway in Kubernetes environments. 
@@ -61,7 +61,7 @@ Discover and manage APIs deployed on Envoy Gateway in Kubernetes environments.
 - Kubernetes-native integration
 - Centralized API governance
 
-[Learn more about Envoy Gateway integration]({{base_path}}/manage-apis/deploy-and-publish/federated-gateways/EnvoyGateway/eg-k8s/discover-apis-on-eg-gateway-in-kubernetes/)
+[Learn more about Envoy Gateway integration]({{base_path}}/api-design-manage/deploy-and-publish/federated-gateways/EnvoyGateway/eg-k8s/discover-apis-on-eg-gateway-in-kubernetes/)
 
 ## Gateway Modes
 
@@ -75,7 +75,7 @@ Federated gateways can operate in different modes depending on your requirements
 
 If you need to integrate with a third-party gateway that is not supported out-of-the-box, WSO2 API Manager provides the flexibility to create custom gateway agents. This allows you to extend the federated gateway capabilities to any external gateway.
 
-[Learn more about configuring custom gateway agents]({{base_path}}/manage-apis/deploy-and-publish/federated-gateways/configure-custom-gateway-agent/)
+[Learn more about configuring custom gateway agents]({{base_path}}/api-design-manage/deploy-and-publish/federated-gateways/configure-custom-gateway-agent/)
 
 ## Architecture Benefits
 

en/docs/api-design-manage/deploy-and-publish/federated-gateways/aws/deploy-on-aws-api-gateway.md

@@ -43,7 +43,7 @@ Follow the instructions given below to configure AWS API Gateway as a Federated
 
     `https://localhost:9443/admin`
 
-2. Register a third party KM following instructions in WSO2 documentation. In this guide we will setup Auth0 as the KM following the guide [Configure Auth0 as a Key Manager]({{base_path}}/administer/key-managers/configure-auth0-connector/).
+2. Register a third party KM following instructions in WSO2 documentation. In this guide we will setup Auth0 as the KM following the guide [Configure Auth0 as a Key Manager]({{base_path}}/api-security/key-management/third-party-key-managers/configure-auth0-connector/).
 
 ## Step 4 : Create and Design API
 

en/docs/api-design-manage/deploy-and-publish/publish-on-dev-portal/publish-an-api.md

@@ -4,9 +4,9 @@
 
 Follow the steps below to publish an API using WSO2 API Manager.
 
-1.  Sign in to the API Publisher `https://<hostname>:9443/publisher` (e.g., `https://localhost:9443/publisher` ). Upon signing in, the list of APIs in the API Publisher is listed. Please refer [create an API guide]({{base_path}}/manage-apis/design/create-api/create-rest-api/create-a-rest-api/) to create a new API. 
+1.  Sign in to the API Publisher `https://<hostname>:9443/publisher` (e.g., `https://localhost:9443/publisher` ). Upon signing in, the list of APIs in the API Publisher is listed. Please refer [create an API guide]({{base_path}}/api-design-manage/design/create-api/create-rest-api/create-a-rest-api/) to create a new API. 
 
-     The list of APIs in the API Publisher appears. If there are no APIs created, [create an API]({{base_path}}/manage-apis/design/create-api/create-rest-api/create-a-rest-api/) before starting.
+     The list of APIs in the API Publisher appears. If there are no APIs created, [create an API]({{base_path}}/api-design-manage/design/create-api/create-rest-api/create-a-rest-api/) before starting.
 
 2.  Click on an API that is in the **CREATED** state.
 

en/docs/api-design-manage/deploy-and-publish/publish-on-dev-portal/publish-to-multiple-external-api-stores.md

@@ -188,7 +188,7 @@ In this guide, let's use two separate instances of WSO2 API Manager, and let's p
 
 8.  Click **Save Content**.
 
-9.  Sign in to the Publisher of the first instance as `admin`/`admin` and if you do not have any APIs that are in the published state created, [create an API]({{base_path}}/manage-apis/design/create-api/create-rest-api/create-a-rest-api/).
+9.  Sign in to the Publisher of the first instance as `admin`/`admin` and if you do not have any APIs that are in the published state created, [create an API]({{base_path}}/api-design-manage/design/create-api/create-rest-api/create-a-rest-api/).
 
     !!! tip
             In a multi-tenant environment, sign in to the API Publisher using your tenant's credentials.

en/docs/api-design-manage/deploy-and-publish/publish-on-dev-portal/third-party-api-support.md

@@ -2,7 +2,7 @@
 
 WSO2 API Manager provides the capability to publish APIs that are deployed in an external gateway. Since these APIs are not deployed in the WSO2 API gateway, the API will not be proxied through the gateway.
 
-In previous versions of API Manager, third-party APIs were available when importing APIs from [AWS API Gateway]({{base_path}}/manage-apis/deploy-and-publish/publish-on-dev-portal/publish-aws-apis-in-the-dev-portal/) and when [publishing through external developer portals]({{base_path}}/manage-apis/deploy-and-publish//publish-on-dev-portal/publish-to-multiple-external-api-stores/).
+In previous versions of API Manager, third-party APIs were available when importing APIs from [AWS API Gateway]({{base_path}}/api-design-manage/deploy-and-publish/publish-on-dev-portal/publish-aws-apis-in-the-dev-portal/) and when [publishing through external developer portals]({{base_path}}/api-design-manage/deploy-and-publish/publish-on-dev-portal/publish-to-multiple-external-api-stores/).
 
 
 ## Creating a Third-party API