Update product_docs/docs/pgd/5.8/upgrades/upgrading_major_rolling.mdx

Author: djw-m

product_docs/docs/pgd/5.8/upgrades/upgrading_major_rolling.mdx

@@ -154,7 +154,7 @@ Using the [preliminary order](#prepare-the-upgrade), perform the following steps
 
 * **Update the extensions**
   * The upgrade process checks for extension updates and generates a script named `updated_extensions.sql` in the current directory if needed. 
-  This contains `ALTER EXTENSION` commands for any extensions that need updating after the upgrade. As these are DDL commands, if you have to run the script before all nodes are upgraded, you should turn off DDL replication temporarily to avoid issues with mixed major versions. If you can defer running the script until all nodes are upgraded, you can run it on each node after the upgrade of that node is complete.
+  This contains `ALTER EXTENSION` commands for any extensions that need updating after the upgrade. As these are DDL commands, if you have to run the script before all nodes are upgraded, you should [turn off DDL replication temporarily](https://www.enterprisedb.com/docs/pgd/latest/reference/pgd-settings/#bdrddl_replication) to avoid issues with mixed major versions. If you can defer running the script until all nodes are upgraded, you can run it on each node after the upgrade of that node is complete.
 
 * **Validate the new Postgres version**
   * Verify that your PostgreSQL instance is now upgraded: