Add information on impact of change in Mendix versioning

content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md

@@ -138,6 +138,10 @@ You can install and run the Mendix Operator in either Global or Standard mode. I
 * [Running the Mendix Operator in Global Mode](/developerportal/deploy/global-operator/)
 * [Running the Mendix Operator in Standard Mode](/developerportal/deploy/standard-operator/)
 
+{{% alert color="info" %}}
+For Mendix version 11.5.0 and above, you will need to install Mendix Operator version 2.24 or above.
+{{% /alert %}}
+
 ### Licensing the Application with Private Cloud License Manager
 
 You can license the Operator and Runtime of your application by configuring the Operator configuration with License Manager details. In order to start using Private Cloud License Manager, you need to first download the PCLM executable available in the Installation page. For more information, see [Private Cloud License Manager](/developerportal/deploy/private-cloud/private-cloud-license-manager/). The PCLM executable is available for download from this page.

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md

@@ -15,6 +15,10 @@ It is essential to ensure that each namespace is exclusively managed by a single
 
 Global Operator installation is supported officially from Operator version v2.20.0 and above.
 
+{{% alert color="info" %}}
+For Mendix version 11.5.0 and above, you will need to install Mendix Operator version 2.24 or above.
+{{% /alert %}}
+
 ## Installing the Global Operator
 
 While installing the Mendix Operator in Global mode, you must first deploy the Mendix Operator and Agent within the *Global Operator namespace*. A Global Operator namespace comprises the Operator itself, the Agent, and the configuration that instructs the Operator on the namespaces it should oversee.

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-standard-operator.md

@@ -13,6 +13,10 @@ When running the Mendix Operator in Standard mode, you must install it separatel
 It is essential to ensure that each namespace is exclusively managed by a single Operator. The deployment of two Operators, particularly with distinct versions, to manage the same namespace, may lead to conflicts, resulting in the cancellation and rollback of each operator's modifications.
 {{% /alert %}}
 
+{{% alert color="info" %}}
+For Mendix version 11.5.0 and above, you will need to install Mendix Operator version 2.24 or above.
+{{% /alert %}}
+
 ## Downloading the Configuration Tool {#download-configuration-tool}
 
 Before you can use the Mendix Operator in your namespace you need to install it and configure the services your app will use. Mendix provides you with a **Configuration Tool** which guides you through the process.

content/en/docs/refguide/general/mxbuild.md

@@ -15,19 +15,16 @@ The table below can help you find the correct MxBuild. Copy a URL from the corre
 
 | Operating System | Mendix Version               | URL                                                          |
 | ---------------- | ---------------------------- | ------------------------------------------------------------ |
-| Linux (x64)      | All versions                 | `https://cdn.mendix.com/runtime/mxbuild-{mxversion}.tar.gz`  |
-| Windows (x64)    | All version of Studio Pro 11 | `https://cdn.mendix.com/runtime/win-mxbuild-{mxversion}.tar.gz` |
+| Linux (x64)      | All                          | `https://cdn.mendix.com/runtime/mxbuild-{mxversion}.tar.gz`  |
+| Windows (x64)    | 11                           | `https://cdn.mendix.com/runtime/win-mxbuild-{mxversion}.tar.gz` |
 
 {{% alert color="info" %}}
+In Mendix version 11.5.0 and above, `{mxversion}` follows a SemVer pattern `major.minor.patch` with the occasional pre-release suffix (for example, `11.5.0` or `11.6.0-beta.1` for planned pre-releases).
 
-A build number is included in the version, which has to be included in the link path mentioned above (for example, `11.0.0.9976` is the 9976 build of the 11.0.0 Studio Pro release).
-
-You can find the build number in path of your Mendix installation (for example, if your installation looks like this `C:\Program Files\Mendix\11.0.0.9976`, use this URL to get your files: [https://cdn.mendix.com/runtime/mxbuild-11.0.0.9976.tar.gz](https://cdn.mendix.com/runtime/mxbuild-11.0.0.9976.tar.gz)).
+In Mendix versions below 11.5.0, a build number is included in the version, which has to be included in `{mxversion}` in the link path mentioned above (for example, `11.0.0.73100` is the 73100 build of the 11.0.0 Studio Pro release). You can find the build number in the path of your Mendix installation (for example, if your installation looks like this `C:\Program Files\Mendix\11.0.0.73100`, use this URL to get your files: [https://cdn.mendix.com/runtime/mxbuild-11.0.0.73100.tar.gz](https://cdn.mendix.com/runtime/mxbuild-11.0.0.73100.tar.gz)).
 
 Any public version of Studio Pro in this [Studio Pro Releases List](https://marketplace.mendix.com/link/studiopro/) will allow you to download MxBuild files. If you experience trouble downloading files, make sure your build is listed there.
 
-As of Studio Pro 11.5.0, Mendix introduced a change in the versioning schema by dropping the fourth element, known as the build number. Versions now follow a SemVer pattern `major.minor.patch` with the occasional pre-release suffix (for example, `11.5.0` or `11.6.0-beta.1` for planned pre-releases).
-
 {{% /alert %}}
 
 You can extract the files using an archival tool, such as [7-Zip](https://www.7-zip.org/).