Small edits

Author: Yiyun333

content/en/docs/appstore/use-content/platform-supported-content/modules/databricks-edc.md

@@ -7,7 +7,7 @@ description: "Describes the steps required to use the Mendix External Database c
 
 ## Introduction
 
-The [External Database connector](/appstore/modules/external-database-connector/) allows you to connect to databases and select data to use in your app. You can use it to directly test connections and queries during configuration in Studio Pro at design time. For Mendix apps that use Databricks as their database, the External Database connector is the recommended integration option for Mendix 10.20.0 and up.
+The [External Database connector](/appstore/modules/external-database-connector/) allows you to connect to databases and select data to use in your app. You can use it to directly test connections and queries during configuration in Studio Pro at design time. For Mendix apps that use Databricks as their database, the External Database connector is the recommended integration option for Mendix 10.20.0 and above.
 
 This how-to describes the steps required to enable your app to use the External Database connector with Databricks.
 

content/en/docs/deployment/mx-azure/mx-azure-installation.md

@@ -22,7 +22,7 @@ Before starting the installation and implementation process, make sure that you
 {{< figure src="/attachments/deployment/mx-azure/coadmin-permission.png" class="no-border" >}}
 
 * Familiarize yourself with the [Private Cloud](https://docs.mendix.com/developerportal/deploy/private-cloud/) concepts.
-* Ensure that your Mendix Studio Pro is in version 10.10 or newer.
+* Ensure that your Mendix Studio Pro is in version 10.10 or above.
 * As an optional best practice, add multiple cluster manager to your clusters.
 
 ## Creating an Azure Cluster

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md

@@ -529,7 +529,7 @@ If the SQL Server instance is an Azure SQL database, you can use [managed identi
 
 SQL server databases are automated, on-demand databases. The **SQL Server** plan offers a good balance between automation, ease of use, and security when using Microsoft SQL Server or Azure SQL. If you would like to have more control over database configuration, consider using the [JDBC plan](#database-jdbc) instead.
 
-If your app is using Mendix 10.10 (or a later version) consider using the [Azure managed identity authentication](#database-sqlserver-azwi) instead, for additional security.
+If your app is using Mendix 10.10 (or above), consider using the [Azure managed identity authentication](#database-sqlserver-azwi) instead, for additional security.
 
 ##### Prerequisites
 
@@ -629,7 +629,7 @@ This section provides technical details on how managed identity authentication w
 
 ##### Limitations
 
-* To use this feature, your app needs to be upgraded to Mendix 10.10 (or later), and your namespace needs to use Mendix Operator version 2.17.0 (or later).
+* To use this feature, your app needs to be upgraded to Mendix 10.10 (or above), and your namespace needs to use Mendix Operator version 2.17.0 (or above).
 
 ##### Environment Isolation
 
@@ -1628,7 +1628,7 @@ In the Amazon S3 plan configuration, enter the following details:
 
 ### Azure Blob Storage {#blob-azure}
 
-If you would like to have Mendix Operator with automation, and have full isolation between environments, use the [Azure managed identity authentication](#blob-azure-azwi) option. This option works with apps using Mendix 10.10 (or a later version).
+If you would like to have Mendix Operator with automation, and have full isolation between environments, use the [Azure managed identity authentication](#blob-azure-azwi) option. This option works with apps using Mendix 10.10 (or above).
 
 If you would like to simply share a container between environments, or to manually create a container and account per environment, use the [static credentials](#blob-azure-static) option.
 
@@ -1651,7 +1651,7 @@ This section provides technical details on how managed identity authentication w
 
 ##### Limitations
 
-* To use this feature, your app needs to be upgraded to Mendix 10.10 (or later), and your namespace needs to use Mendix Operator version 2.17.0 (or later).
+* To use this feature, your app needs to be upgraded to Mendix 10.10 (or above), and your namespace needs to use Mendix Operator version 2.17.0 (or above).
 
 ##### Environment Isolation
 
@@ -1725,7 +1725,7 @@ Azure workload identities allow a Kubernetes Service Account to authenticate its
 
 This basic, on-demand option allows you to attach an existing Azure Blob Storage container and credentials (account name and secret key) to one or more environments. All apps (environments) will use the same Azure Blob Storage container and credentials.
 
-If your app is using Mendix 10.10 (or a later version) consider using the [Azure managed identity authentication](#blob-azure-azwi) instead, for additional security.
+If your app is using Mendix 10.10 (or above) consider using the [Azure managed identity authentication](#blob-azure-azwi) instead, for additional security.
 
 ##### Prerequisites
 
@@ -2148,7 +2148,7 @@ Azure recommends using [managed identity authentication](https://learn.microsoft
 This guide explains how to set up and use a database and blob file storage plan using Azure best practices.
 
 {{% alert color="warning" %}}
-This feature requires an Mendix app based on Mendix 10.10 (or later) and Mendix Operator version 2.17 (or later).
+This feature requires an Mendix app based on Mendix 10.10 (or above) and Mendix Operator version 2.17 (or above).
 {{% /alert %}}
 
 Before you begin, you need to create an AKS cluster and install Mendix for Private Cloud in that cluster.

content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md

@@ -262,7 +262,7 @@ Amazon and Azure SQL servers require additional firewall configuration to allow
 
 Some managed SQL Server databases might have restrictions or require additional configuration.
 
-As an alternative to static password authentication, Mendix Operator can use its Kubernetes Service Account to authenticate with Azure SQL databases. The Kubernetes Service Account is linked with a Managed Identity, and the Managed Identity replaces a static username/password. This feature requires Mendix Operator version 2.17 (or later) and Mendix 10.10 (or later).
+As an alternative to static password authentication, Mendix Operator can use its Kubernetes Service Account to authenticate with Azure SQL databases. The Kubernetes Service Account is linked with a Managed Identity, and the Managed Identity replaces a static username/password. This feature requires Mendix Operator version 2.17 (or above) and Mendix 10.10 (or above).
 
 {{% alert color="info" %}}
 To use a SQL Server database, the Mendix Operator requires Superuser account with permissions to create new users and databases.
@@ -333,7 +333,7 @@ configuration details.
 Mendix Operator can perform the following tasks:
 
 * Provide a static access key and other credentials to environments (a static config).
-* Handle the lifecycle of a storage container by creating a dedicated container and Azure Managed Identity for every new environment, and ensuring that an environment can only access its dedicated container (through the environment's Managed Identity); this feature works with Mendix 10.10 (or later versions).
+* Handle the lifecycle of a storage container by creating a dedicated container and Azure Managed Identity for every new environment, and ensuring that an environment can only access its dedicated container (through the environment's Managed Identity); this feature works with Mendix 10.10 and above.
 
 A complete list of supported Azure Blob Storage modes and their required role assignments (permissions) for each one is available in [storage plan](/developerportal/deploy/standard-operator/#storage-plan) configuration details.
 

content/en/docs/developerportal/general/team-server/migrate-to-git.md

@@ -20,6 +20,8 @@ If your main line is Studio Pro version 9.24.28 or above and your team role is S
 
 Mendix recommends to combine a migration to Git with an upgrade to Mendix 10, as the advantages of Git in Mendix 9 are limited. For more details on this recommendation, see the [Recommendation on Avoiding Git Issues](/refguide/troubleshoot-repository-size/#recommendation) section in *Troubleshooting Repository Size*.
 
+{{% todo %}} Do we need to mention anything about Mendix 11 here? {{% /todo %}}
+
 ## Apps Eligible for Migration
 
 {{% alert type="info" %}}