Correct the dev corrected errors

en/docs/administer/key-managers/configure-custom-connector.md

@@ -461,4 +461,4 @@ When registering a third-party Identity Provider as a Key Manager in the Admin P
     !!! tip
         If you want to generate the tokens with scopes, make sure that those scopes are defined in the Authorization Server.
 
-6. You can now use the generated token to [invoke an API]({{base_path}}/en/docs/consume/invoke-apis/invoke-apis-using-tools/include-additional-headers-in-the-api-console.md).
+6. You can now use the generated token to [invoke an API]({{base_path}}/consume/invoke-apis/invoke-apis-using-tools/include-additional-headers-in-the-api-console/).

en/docs/install-and-setup/install/installing-the-product/installing-api-m-as-a-windows-service.md

@@ -20,7 +20,7 @@ The configuration file used for wrapping Java Applications by YAJSW is `wrapper.
 
 !!! info
 
-    If you want to set additional properties from an external registry at runtime, store sensitive information like usernames and passwords for connecting to the registry in a properties file and secure it with [secure vault]({{base_path}}/administer/product-security/General/logins-and-passwords/admin-carbon-secure-vault-implementation).
+    If you want to set additional properties from an external registry at runtime, store sensitive information like usernames and passwords for connecting to the registry in a properties file and secure it with [secure vault]({{base_path}}/install-and-setup/setup/security/logins-and-passwords/working-with-encrypted-passwords/).
 
 !!! note
 

en/docs/install-and-setup/setup/api-controller/advanced-topics/configuring-different-endpoint-types.md

@@ -225,7 +225,7 @@ The following is an example parameters file for this scenario. (Make sure to spe
     ```
 
 !!! tip
-    When importing an API, if you are specifying the endpoint type as `dynamic`, you can include a message mediation policy with a `To` header inside the `Sequences` directory of your API Project. (Refer [Adding Dynamic Endpoints]({{base_path}}/deploy-and-publish/deploy-on-gateway/api-gateway/message-mediation/adding-dynamic-endpoints/#adding-dynamic-endpoints) to learn more about Dynamic endpoints and message mediations associated with that.)
+    When importing an API, if you are specifying the endpoint type as `dynamic`, you can include a message mediation policy with a `To` header inside the `Sequences` directory of your API Project. (Refer [Adding Dynamic Endpoints]({{base_path}}/design/api-policies/regular-gateway-policies/adding-dynamic-endpoints//) to learn more about Dynamic endpoints and message mediations associated with that.)
 
 ### AWS Lambda Endpoints
 

en/docs/install-and-setup/setup/si-setup/production-checklist.md

@@ -38,7 +38,7 @@ If you want to allow business users with limited coding knowledge to write busin
 
 ## Monitoring the Streaming Integrator
 
-To monitor the performance of your Streaming Integrator setup, configure WSO2 SI to publish its statistics in Dashboards as described in [Configuring Grafana Dashboards]({{base_path}}/install-and-setup/setup/si-setup/setting-up-grafana-dashboards).
+To monitor the performance of your Streaming Integrator setup, configure WSO2 SI to publish its statistics in Dashboards as described in [Configuring Grafana Dashboards]({{base_path}}/https://observe/streaming-integrator/setting-up-si-statistics-dashboards/)
 
 
 

en/docs/reference/connectors/develop-connectors.md

@@ -785,7 +785,7 @@ Connection timeout is an environment dependent configuration. Developers may def
 **Handle errors meaningfully. Use ERROR CODES**
 Sometimes it is required to handle errors within the connector. Sometimes it is required to let the calling template handle the error. Sometimes it is required to forward the error message back to the connector operation invoker as it is. It is good to analyze use cases, and then design which errors need to be handled at which instance. However, it is a good practice to define and use error codes. 
 
-Please read the [WSO2 Error Code guide]({{base_path}}/reference/error_handling/). 
+Please read the [WSO2 Error Code guide]({{base_path}}/troubleshooting/error-handling/#error-codes). 
 
 **Write test cases**
 

en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md

@@ -1,4 +1,4 @@
-# Get Credentials for Google Spreadsheet
+the next screen# Get Credentials for Google Spreadsheet
 
 To obtain the Access Token, Client Id, Client Secret and Refresh Token, we need to follow the below steps. 
 
@@ -11,16 +11,13 @@ To obtain the Access Token, Client Id, Client Secret and Refresh Token, we need
 
 4. Click **Configure consent screen** in the next screen.
 
-  <img src="{{base_path}}/assets/img/integrate/connectors/consent-screen.png" title="Consent Screen" width="800" alt="Consent Screen" />
-
+  <img src="{{base_path}}/assets/img/integrate/connectors/consent-screen.jpg" title="Consent Screen" width="800" alt="Consent Screen" /><br>
 5. Provide the Application Name as `SpreadsheetConnector` in the Consent Screen.
 
-  <img src="{{base_path}}/assets/img/integrate/connectors/consent-screen2.png" title="Consent Screen" width="800" alt="Consent Screen" />
-
+  <img src="{{base_path}}/assets/img/integrate/connectors/consent-screen2.jpg" title="Consent Screen" width="800" alt="Consent Screen" /><br>
 6. Click Create credentials and click OAuth client ID.
 
-  <img src="{{base_path}}/assets/img/integrate/connectors/create-credentials.png" title="Create Credentials" width="800" alt="Create Credentials" />
-
+  <img src="{{base_path}}/assets/img/integrate/connectors/create-credentials.png" title="Create Credentials" width="800" alt="Create Credentials" /><br>
 7. Enter the following details in the Create OAuth client ID screen and click Create.
 
   | Type                        | Name                                             | 
@@ -29,12 +26,12 @@ To obtain the Access Token, Client Id, Client Secret and Refresh Token, we need
   | Name                        | SpreadsheetConnector                                   |
   | Authorized redirect URIs    | https://developers.google.com/oauthplayground    |
 
-
+<br>  
 8. A Client ID and a Client Secret are provided. Keep them saved.
   <img src="{{base_path}}/assets/img/integrate/connectors/credentials.png" title="Credentials" width="800" alt="Credentials" />
-
+<br>
 9. Click Library on the side menu, search for **Google Sheets API** and click on it.
-
+<br>
 10. Click **Enable** to enable the Google Sheets API.
   <img src="{{base_path}}/assets/img/integrate/connectors/sheetsapi.png" title="Enable Google Sheets API" width="800" alt="Enable Google Sheets API" />
 

en/docs/reference/connectors/redis-connector/redis-connector-overview.md

@@ -20,7 +20,7 @@ For older versions, see the details in the connector store.
 
 ## Redis Connector documentation
 
-* **[Setting up the Redis Environment]({{base_path}}/reference/connectors/redis-connector/redis-connector-configuration/)**: This involves setting up the Redis server and a backend to test the flow.
+* **[Setting up the Redis Environment]({{base_path}}/reference/connectors/redis-connector/2.4.x/redis-connector-reference/)**: This involves setting up the Redis server and a backend to test the flow.
 
 * **[Redis Connector Example]({{base_path}}/reference/connectors/redis-connector/redis-connector-example/)**: This example demonstrates how to work with the Redis Connector and access the Redis server using Redis commands. 
 

en/docs/reference/connectors/salesforce-connectors/salesforcebulk-connector-example.md

@@ -42,7 +42,7 @@ Now follow the steps below to add configurations to the `insertEmployeeBulkRecor
 
 1. Initialize the connector.
 
-    1. Follow these steps to [generate the Access Tokens for Salesforce]({{base_path}}/reference/connectors/salesforce-connectors/salesforcebulk-connector-configuration) and obtain the Client Id, Client Secret, Access Token, and Refresh Token.
+    1. Follow these steps to [generate the Access Tokens for Salesforce]({{base_path}}/includes/reference/connectors/salesforce-connectors/sf-access-token-generation) and obtain the Client Id, Client Secret, Access Token, and Refresh Token.
 
     2. Navigate into the **Palette** pane and select the graphical operations icons listed under **Salesforcebulk Connector** section. Then drag and drop the `init` operation into the Design pane.
 

en/docs/reference/connectors/salesforcebulk-connector/salesforcebulk-connector-example.md

@@ -42,7 +42,7 @@ Now follow the steps below to add configurations to the `insertEmployeeBulkRecor
 
 1. Initialize the connector.
 
-    1. Follow these steps to [generate the Access Tokens for Salesforce](salesforcebulk-connector-configuration/) and obtain the Client Id, Client Secret, Access Token, and Refresh Token.
+    1. Follow these steps to [generate the Access Tokens for Salesforce]({{base_path}}/includes/reference/connectors/salesforce-connectors/sf-access-token-generation/) and obtain the Client Id, Client Secret, Access Token, and Refresh Token.
 
     2. Navigate into the **Palette** pane and select the graphical operations icons listed under **Salesforcebulk Connector** section. Then drag and drop the `init` operation into the Design pane.
 

en/docs/reference/customize-product/customizations/adding-internationalization.md

@@ -182,7 +182,7 @@ Follow the instructions below to change the direction of the UI:
     ```
 
     !!! tip
-    Learn more about [Tenant theming]({{base_path}}/consume/customizations/customizing-the-developer-portal/overriding-developer-portal-theme/#uploading-via-the-admin-portal-tenants-only).
+    Learn more about [Tenant theming]({{base_path}}/reference/customize-product/customizations/customizing-the-developer-portal/overriding-developer-portal-theme/#uploading-devportal-theme-via-the-admin-portal-tenants-only).
 
 
 ## Enabling the language switch

en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md

@@ -6,7 +6,7 @@ An API's gateway configuration file(Synapse configuration) content contains API
 
 ## Engaging a custom handler based on API Properties
 
-In API Manager, you can implement and engage custom handlers to customize the default mediation flow of API requests. See [Writing a custom handler]() for more information. The [API properties]({base_path}/learn/design-api/create-api/adding-custom-properties-to-apis/) can be used to conditionally engage these custom handlers for APIs.
+In API Manager, you can implement and engage custom handlers to customize the default mediation flow of API requests. See [Writing a custom handler]() for more information. The [API properties]({{base_path}}/design/create-api/adding-custom-properties-to-apis/) can be used to conditionally engage these custom handlers for APIs.
 
 Following steps illustrate how you can enable a custom handler for a selected set of APIs which are having a particular property value. 
 
@@ -74,7 +74,7 @@ Following steps illustrate how you can enable a custom handler for a selected se
      
  3. Save the changes.
  
- 4. Add `custom_authentication=true` as an [additional property]({base_path}/learn/design-api/create-api/adding-custom-properties-to-apis/) for those APIs which you need to enable the custom handler.
+ 4. Add `custom_authentication=true` as an [additional property]({{base_path}}/design/create-api/adding-custom-properties-to-apis/) for those APIs which you need to enable the custom handler.
  
     <a href="{{base_path}}/assets/img/develop/extensions/custom_properties.png" ><img src="{{base_path}}/assets/img/develop/extensions/custom_properties.png" alt="Add Custom Property" 
            title="Add Custom Property" width="80%" /></a>

en/docs/reference/synapse-properties/data-services/datasource-configuration-parameters.md

@@ -7,7 +7,7 @@ The datasource configuration in a data service specifies how the service connect
 Shown below is the synapse configuration of an RDBMS datasource in a data service. See the complete list of [JDBC connection pool parameters](http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html) and the [DBCP configuration guide](http://commons.apache.org/proper/commons-dbcp/configuration.html) for more details.
 
 !!! Note
-      The default values of the following parameters might not be optimal for the specific hardware/server configurations in your environment. We recommend that you carry out load tests in your environment to tune them accordingly. See [Tuning Datasource Configuration Parameters]({{base_path}}/install-and-setup/performance_tuning/jdbc_tuning) for information on how you can select the best values for these parameters.
+      The default values of the following parameters might not be optimal for the specific hardware/server configurations in your environment. We recommend that you carry out load tests in your environment to tune them accordingly. See [Tuning Datasource Configuration Parameters](/install-and-setup/setup/mi-setup/performance_tuning/jdbc_tuning/) for information on how you can select the best values for these parameters.
 
 ```toml
 <data name="RDBMSDataService" serviceStatus="inactive" transports="http https local">

en/docs/reference/synapse-properties/transport-parameters/rabbitmq-transport-parameters.md

@@ -3,7 +3,7 @@
 When you implement an integration use case that requires a RabbitMQ connection, you can use the following RabbitMQ parameters in your [proxy service]({{base_path}}/integrate/develop/creating-artifacts/creating-a-proxy-service) artifact.
 
 !!! Info
-      The Micro Integrator can listen to a RabbitMQ instance or send messages to a RabbitMQ instance only if the RabbitMQ transport listener and sender are enabled and configured at the server level. Read about the [RabbitMQ transport]({{base_path}}/install-and-setup/brokers/configure-with-rabbitMQ).
+      The Micro Integrator can listen to a RabbitMQ instance or send messages to a RabbitMQ instance only if the RabbitMQ transport listener and sender are enabled and configured at the server level. Read about the [RabbitMQ transport]({{base_path}}/install-and-setup/setup/mi-setup/performance_tuning/rabbitmq_transport_tuning/).
 
 ## Service-Level Parameters (Receiving Messages)