fix: correct branding references, typos, and formatting issues across documentation

en/docs/devant-concepts/data-planes.md

@@ -7,11 +7,11 @@ description: Understand the architecture of Devant data planes, including cloud
 
 Devant's architecture comprises two key components: the control plane and the data plane. The control plane handles essential tasks such as administering organizations, users, and projects. In addition, it also governs the entire journey of integration development, from the initial stages of creation, progressing to deployment, including measures to enforce governance and the provision for observability. The Devant control plane is a SaaS that manages all cloud data planes and private data planes. It caters to diverse user personas, including CIOs, architects, and developers, as well as DevOps, and platform engineers.
 
-The data plane is the environment where user integrations are deployed based on configurations set in the control plane. The integrations can be built in [Ballerina](https://ballerina.io/) and [Wso2 Micro Integrator](https://wso2.com/integrator/micro-integrator/) which are optimized for building integrations or using the Devant Cloud Editor. Importantly, all traffic related to the runtime of user integrations are restricted to the Devant data plane, ensuring strict containment of user data within its boundaries.
+The data plane is the environment where user integrations are deployed based on configurations set in the control plane. The integrations can be built in [Ballerina](https://ballerina.io/) and [WSO2 Micro Integrator](https://wso2.com/integrator/micro-integrator/) which are optimized for building integrations or using the Devant Cloud Editor. Importantly, all traffic related to the runtime of user integrations is restricted to the Devant data plane, ensuring strict containment of user data within its boundaries.
 
 Devant's architecture features two distinct data plane types: cloud data planes and private data planes. A cloud data plane utilizes a multi-tenanted infrastructure model for deploying user integrations, creating a shared yet secure environment for integration runtime. In contrast, a private data plane(PDP) provides dedicated infrastructure for a single organization to run its user integrations. This ensures an added layer of privacy and control for organizations with specific requirements.
 
-![Choreo high-level view](../assets/img/devant-concepts/high-level-view.png)
+![Devant high-level view](../assets/img/devant-concepts/high-level-view.png)
 
 ## Private data planes
 
@@ -131,7 +131,7 @@ The following diagram depicts the architecture overview of Devant's in-data-plan
 
 ![Observability architecture](../assets/img/devant-concepts/observability-architecture.png){width=700 height=500}
 
-The private data plane observability architecture is centered around a strong commitment to data privacy and compliance. This is achieved through a strategic decision to retain logs and observability data within the data planes itself. Key aspects of this architecture include:
+The private data plane observability architecture is centered around a strong commitment to data privacy and compliance. This is achieved through a strategic decision to retain logs and observability data within the data plane itself. Key aspects of this architecture include:
 
 - **Data storage at source**: Logs and observability data are stored within the data plane itself, enhancing security, simplifying access, and ensuring compliance.
 - **Direct browser-to-data-plane interaction**: The Devant Console in the user's browser directly interacts with APIs in the data plane, reducing potential data routing complexities and ensuring a more secure, direct flow of information.

en/docs/devant-concepts/deployment-tracks.md

@@ -41,7 +41,7 @@ You can follow the approach given below when you version APIs in Devant:
 
 One of the primary concerns when dealing with SaaS APIs is to minimize disruption for API consumers while continuously developing and deploying updates.
 
-In compliance with SemVer, changes that don't introduce breaking or additive modifications to the API are categorized as patch updates. Hover, from the perspective of API consumers, these changes should ideally not disrupt their API clients. Typically, API consumers are most concerned with major API version alterations, but there might be instances where minor version changes are communicated to them.
+In compliance with SemVer, changes that don't introduce breaking or additive modifications to the API are categorized as patch updates. However, from the perspective of API consumers, these changes should ideally not disrupt their API clients. Typically, API consumers are most concerned with major API version alterations, but there might be instances where minor version changes are communicated to them.
 
 Therefore, in the context of deployment tracks, API developers only need to specify the major and minor versions being delivered from a particular deployment track. This information is treated as the API version attribute of a deployment track. If the publisher requires versioning for internal tracking purposes, this can be accomplished in Git through the use of Git tags, GitHub with GitHub releases, and so forth.
 

en/docs/devant-concepts/organization.md

@@ -5,7 +5,7 @@ description: Learn about Organizations in Devant and how to manage them.
 
 # Organization
 
-An organization in Devant is a logical grouping of users and user resources. A first-time user must create an organization and be a member of it when signing in to Devant. Users and resources in an organization cannot access resources in another organization unless an admin of the other organization invites them and adds them as member of that organization. A user cannot create more than one organization.
+An organization in Devant is a logical grouping of users and user resources. A first-time user must create an organization and be a member of it when signing in to Devant. Users and resources in an organization cannot access resources in another organization unless an admin of the other organization invites them and adds them as a member of that organization. A user cannot create more than one organization.
 
 ## Switch organizations
 

en/docs/devops-and-ci-cd/manage-configurations-and-secrets.md

@@ -18,7 +18,7 @@ Devant treats all configurations and secrets as sensitive content, but lets you
 - **Secrets** are write-only. Once created, you cannot view or retrieve their content via Devant, but you can overwrite them at any time.
 - **Configurations** can be read and updated via Devant after creation.
 
-    !!!info "Note"
+    !!! info "Note"
         For sensitive data such as database passwords, cloud credentials, or service accounts, it is recommended to use secrets rather than configurations.
 
 ## Managing environment variables and file mounts on Devant
@@ -43,7 +43,7 @@ To add environment variables:
 3. Select **Environment Variables** in the **Create a Config or Secret** pane.
 4. Select **Mark as a Secret** if the values contain sensitive information.
 
-    !!!info "Note"
+    !!! info "Note"
         Secret environment variables cannot be read after creation, but you can overwrite them at any time.
 
 5. Enter a **Display Name** to identify this configuration.

en/docs/manage-databases-and-caches/devant-managed-caches.md

@@ -85,7 +85,7 @@ For example, on a server with 4GB memory (4,096 MB), the simultaneous connection
 4 x 4096 = 16384 // 16k connections
 ```
 
-This number is estimated by the exact available memory so it can vary between different plans and cloud providers. To see the exact maximum connections allowed, use the \* redis-cli and info command as follows:
+This number is estimated by the exact available memory so it can vary between different plans and cloud providers. To see the exact maximum connections allowed, use the redis-cli and info command as follows:
 
 ```
 echo "info" | redis-cli -u REDIS_URI | grep maxclients

en/docs/manage-databases-and-caches/devant-managed-databases-and-caches.md

@@ -12,7 +12,7 @@ These databases and caches can be seamlessly provisioned to offer persistence an
     - The capability to create Devant-managed databases, vector databases, and cache services is available only for paid Devant users.
     - Billing for these services will be included in your Devant subscription, with pricing varying based on the service plan of the resources you create. For more details, see [Devant Platform Services Billing](../references/devant-platform-services-billing-and-upgrades.md#platform-service-billing-information).
 
-!!!Tip "Explore the free trial"
+!!! tip "Explore the free trial"
     Devant provides a 7-day free trial for all database types on the 'Hobbyist' service plan, available to free-tier users.
 
 ## PostgreSQL on Devant