Updated release notes and migration guide

Author: mariadb-mmontes

release-notes/enterprise-operator/25.10.md

@@ -10,9 +10,9 @@ If you're upgrading from previous versions, __please follow the [UPGRADE GUIDE](
 
 The operator now supports provisioning and operating MariaDB clusters using asynchronous replication as a high availability topology, providing an alternative to the existing synchronous multi-master topology based on Galera. In a replication setup, one primary server handles all write operations while one or more replica servers replicate data from the primary, being able to handle read operations. More precisely, the primary has a binary log and the replicas asynchronously replicate the binary log events over the network. 
 
-Operations and the full lifecycle of the replication cluster are fully managed by the operator, including provisioning, scaling, replica recovery and disaster recovery. For the primary failover/switchover, we recommend using MaxScale 25.10, currently supported by this version.
+Operations and the lifecycle of the replication cluster are fully managed by the operator, including provisioning, scaling, replica recovery and disaster recovery. For the primary switchover and  failover operations, we recommend using MaxScale 25.10, currently supported by this version.
 
-Please refer to the [replication](https://mariadb.com/docs/tools/mariadb-enterprise-operator/topologies/replication) for more details about this topology.
+Please refer to the [replication documentation](https://mariadb.com/docs/tools/mariadb-enterprise-operator/topologies/replication) for more details about this topology.
 
 ### LTS releases
 
@@ -27,9 +27,9 @@ The current release has been tested with the following versions:
 | Platform/Component        | Version  |
 | ------------------------- | -------- |
 | Kubernetes                | 1.34     |
-| OpenShift                 | 4.18.6, 4.16.4 |
+| OpenShift                 | 4.18.6   |
 | MariaDB Enterprise Server | 11.8.3-1 |
-| MaxScale                  | 25.10.0 |
+| MaxScale                  | 25.10.0  |
 
 {% include "https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/~/reusable/pNHZQXPP5OEz2TgvhFva/" %}
 

tools/mariadb-enterprise-operator/migrations/migrate-25.10.md

@@ -3,10 +3,7 @@
 This guide illustrates, step by step, how to migrate to `25.10.0` from previous versions. 
 
 
-- The Galera data-plane must be updated to the `25.10.0` version. 
-
-
-If you want the operator to automatically update the data-plane (i.e. init and agent containers), you can set `updateStrategy.autoUpdateDataPlane=true` in your `MariaDB` resources:
+- The Galera data-plane must be updated to the `25.10.0` version. You must set `updateStrategy.autoUpdateDataPlane=true` in your `MariaDB` resources before updating the operator. Then, once updated, the operator will also be updating the data-plane based on its version:
 ```diff
 apiVersion: enterprise.mariadb.com/v1alpha1
 kind: MariaDB
@@ -17,23 +14,6 @@ spec:
 +   autoUpdateDataPlane: true
 ```
 
-Alternatively, you can also do this manually:
-
-```diff
-apiVersion: enterprise.mariadb.com/v1alpha1
-kind: MariaDB
-metadata:
-  name: mariadb-galera
-spec:
-  galera:
-    agent:
--      image: docker.mariadb.com/mariadb-enterprise-operator:1.0.0
-+      image: docker.mariadb.com/mariadb-enterprise-operator:25.10.0
-    initContainer:
--      image: docker.mariadb.com/mariadb-enterprise-operator:1.0.0
-+      image: docker.mariadb.com/mariadb-enterprise-operator:25.10.0
-```
-
 - Then, you may proceeed to update the operator. If you are using __Helm__:
 
 Upgrade `mariadb-enterprise-operator-crds` to `25.10.0`:
@@ -85,7 +65,7 @@ spec:
   sourceNamespace: openshift-marketplace
 ``` 
 
-- If you previously set `updateStrategy.autoUpdateDataPlane=true`, you may consider reverting the changes once the upgrades have finished to avoid unexpected updates:
+- Consider reverting `updateStrategy.autoUpdateDataPlane` back to `false` to avoid unexpected updates:
 
 ```diff
 apiVersion: enterprise.mariadb.com/v1alpha1