[DOC-1047] xCluster DR version and automatic mode updates

docs/content/stable/yugabyte-platform/back-up-restore-universes/disaster-recovery/_index.md

@@ -86,7 +86,7 @@ Automatic mode is recommended for all new DR configurations. When possible, you
 
 Automatic mode is used for any xCluster DR configuration when the following pre-requisites are met at setup time:
 
-- Both DR primary and replica are running YugabyteDB {{<release "2025.1.0">}} or later.
+- Both DR primary and replica are running YugabyteDB {{<release "2025.1.1">}} or later.
 - Automatic mode is enabled. While in {{<tags/feature/ea idea="2089">}}, the feature is not enabled by default. To enable it, set the **Automatic mode for xCluster** Global runtime configuration option (config key `yb.xcluster.db_scoped.automatic_ddl.creationEnabled`) to true. Refer to [Manage runtime configuration settings](../../administer-yugabyte-platform/manage-runtime-config/). Note that only a Super Admin user can modify Global runtime configuration settings.
 - Semi-automatic mode is enabled. Semi-automatic mode is enabled by default, and set using the **DB scoped xCluster replication creation** Global Runtime Configuration option (config key `yb.xcluster.db_scoped.creationEnabled`).
 

docs/content/stable/yugabyte-platform/back-up-restore-universes/disaster-recovery/disaster-recovery-tables.md

@@ -34,10 +34,20 @@ For each DDL statement:
 
 After both steps are complete, the YugabyteDB Anywhere UI should reflect any added/removed tables in the Tables listing for this DR configuration.
 
+In addition, keep in mind the following:
+
+- If you are using Colocated tables, you CREATE TABLE on DR primary, then CREATE TABLE on DR replica making sure that you force the Colocation ID to be identical to that on DR primary.
+- If you try to make a DDL change on DR primary and it fails, you must also make the same attempt on DR replica and get the same failure.
+- TRUNCATE TABLE is not supported. To truncate a table, pause replication, truncate the table on both primary and standby, and resume replication.
+
   {{% /tab %}}
 
   {{% tab header="Manual mode" lang="manual-mode" %}}
 
+{{< warning title="Warning" >}}
+Fully Manual xCluster replication is deprecated and not recommended due to the operational complexity involved.
+{{< /warning >}}
+
 You should perform these actions in a specific order, depending on whether performing a CREATE, DROP, ALTER, and so forth, as indicated by the sequence number of the operation in the table below.
 
 | DDL | Step 1 | Step 2 | Step 3 |
@@ -51,17 +61,17 @@ You should perform these actions in a specific order, depending on whether perfo
 | ALTER TABLE<br>ADD CONSTRAINT UNIQUE | Execute on Primary | Execute on Replica | [Reconcile configuration](#reconcile-configuration) |
 | ALTER TABLE<br>DROP CONSTRAINT<br>(unique constraints only) | Execute on Replica | Execute on Primary | [Reconcile configuration](#reconcile-configuration) |
 
-  {{% /tab %}}
-
-{{</tabpane >}}
-
 In addition, keep in mind the following:
 
 - If you are using Colocated tables, you CREATE TABLE on DR primary, then CREATE TABLE on DR replica making sure that you force the Colocation ID to be identical to that on DR primary.
 - If you try to make a DDL change on DR primary and it fails, you must also make the same attempt on DR replica and get the same failure.
 - TRUNCATE TABLE is not supported. To truncate a table, pause replication, truncate the table on both primary and standby, and resume replication.
 
-Use the following guidance when managing tables and indexes in universes with DR configured.
+  {{% /tab %}}
+
+{{</tabpane >}}
+
+Use the following guidance when managing tables and indexes in universes when DR is configured in Manual mode.
 
 ## Tables