Merge pull request #1 from mendix/yl-remove-or-update-Mendix-10-instances

Remove or update Mendix/Studio Pro 10 instances

Author: MariaShaposhnikova

content/en/docs/appstore/use-content/platform-supported-content/modules/SAML/_index.md

@@ -153,6 +153,8 @@ There are different versions of the SAML module, depending on which version of M
 
         Mendix 10 does not support the 2.0 version of the Atlas UI, so you should never use the even-numbered (Atlas 2.0-compatible) SAML patch releases with your Mendix 10 app.
 
+    {{% todo %}} Do we need to add anything here for Mendix 11? {{% /todo %}}
+
 3. To download the required release, in the **Releases** tab, find the release that is compatible with your app per the guidelines in the **Documentation** tab, and then click the **Download** button by the number of the release.
 4. Follow the instructions in [How to Use Marketplace Content](/appstore/use-content/) to import the SAML module into your app.
 
@@ -175,6 +177,7 @@ By default, the SAML module will be installed as the **SAML20** module in your a
             Only use this setting if you are using SAML on a hybrid mobile app. Note that this functionality also requires mobile authentication tokens to be enabled in your IdP Configuration as well as changes to the hybrid app package as described in [How To Implement SSO on a Hybrid App with Mendix and SAML](/howto8/mobile/implement-sso-on-a-hybrid-app-with-mendix-and-saml/).
 
         {{% alert color="warning" %}}Hybrid mobile apps are not available in Mendix 10.{{% /alert %}}
+        {{% todo %}} How about in Mendix 11? {{% /todo %}}
 
 5. Sign in to the application and configure the SAML module as described in the [Configuration SAML Module](#config) section.
 

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/appstore/use-content/platform-supported-content/modules/oidc.md

@@ -15,9 +15,11 @@ OIDC is an extension of OAuth2 that propagates the end-user's identity to your a
 {{% alert color="warning" %}}
 This OIDC SSO module works with Mendix 9.0 and above. If you are using a previous version of Mendix, you can use the community-supported module [OpenIDConnect Single Sign-on (OIDC, OAuth2, SSO)](https://marketplace.mendix.com/link/component/117529).
 
-If you are using Mendix 9.20 and above, ensure you are using version 2.0.0 or above of the OIDC SSO module. For Mendix 10.0 and above, you need to use version 2.2.0 or above of the OIDC SSO module.
+If you are using Mendix versions from 9.20 to 9.24, ensure you are using version 2.0.0 or above of the OIDC SSO module. For all versions of Mendix 10.0, you need to use version 2.2.0 or above of the OIDC SSO module.
 {{% /alert %}}
 
+{{% todo %}} The team will update the above warning for Mendix 11 when more information is available. {{% /todo %}}
+
 {{% alert color="warning" %}}
 If you are migrating to the OIDC module version 3.0.0 and above, include the [UserCommons](https://marketplace.mendix.com/link/component/223053) module as a dependency and configure the `OIDC.Startup` microflow as part of after-startup Microflow. In the module version 3.1.0 and above, `OIDC.Startup` has been renamed to `OIDC.ASU_OIDC_Startup`. For more details, see the [Upgrading the OIDC SSO Module](#upgrade) section below.
 {{% /alert %}}

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

@@ -8,7 +8,7 @@ weight: 10
 
 ## 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 (design time). For Mendix apps that use Snowflake as their database, the External Database connector is the recommended integration option for Mendix 10.
+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 (design time). For Mendix apps that work with Snowflake data, the External Database connector is the recommended integration option for Mendix 10 and above.
 
 This how-to describes the steps required to enable your app to use the External Database connector with Snowflake, and to model several common use cases.
 

content/en/docs/catalog/manage/security.md

@@ -16,7 +16,7 @@ Security for a Mendix app can be defined at the app-level, module-level, and ent
 
 This security level determines which end-users of the apps will have access to the data represented by the exposed dataset. For further information, see the [Security](/refguide/published-odata-services/#security) section in *Published OData Services*.
 
-Access to data is determined by the identification protocols of the organization and applied to all access to the data via Mendix apps. For an example of custom HTTP header validation, see the [custom HTTP header validation](/refguide/security-shared-datasets/#http-header-validation) section of *Security and Shared Datasets* in the Studio Pro 10 guide.
+Access to data is determined by the identification protocols of the organization and applied to all access to the data via Mendix apps. For an example of custom HTTP header validation, see the [custom HTTP header validation](/refguide/security-shared-datasets/#http-header-validation) section of *Security and Shared Datasets*.
 
 ## Access Level of Registered Services {#access-level}
 

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" %}}

content/en/docs/developerportal/global-navigation.md

@@ -77,7 +77,7 @@ To use Maia Chat, you need to be signed in to Mendix and have an internet connec
 Maia Chat does not use any project, customer, or company information. It only uses the data that you have entered in the Chat. Please do not enter any personal or sensitive data!
 {{% /alert %}}
 
-Maia Chat  is a built-in chat interface in the Mendix Platform powered by Generative AI. Developers can ask questions about all aspects of Mendix, including how to apply concepts, best practices, governance tools, and development patterns.
+Maia Chat is a built-in chat interface in the Mendix Platform powered by Generative AI. Developers can ask questions about all aspects of Mendix, including how to apply concepts, best practices, governance tools, and development patterns.
 
 Maia Chat is also available in Studio Pro 10.12.0 and above. See [Maia Chat](/refguide/maia-chat/) for more information.