Fix order of steps for cluster node replacement (#60782)

Author: andrba

content/admin/monitoring-and-managing-your-instance/configuring-clustering/replacing-a-cluster-node.md

@@ -223,11 +223,11 @@ If you need to allocate more resources to your primary MySQL (or MySQL and MSSQL
 
    > [!NOTE] The previous snippet does not assume {% data variables.product.prodname_actions %} is enabled in the cluster.
 
-1. Check the status of the MySQL(or MySQL and MSSQL) replication from any node in the cluster by running `ghe-cluster-status -v`.
 1. If {% data variables.product.prodname_actions %} is enabled in the cluster, run the following command from the new MySQL and MSSQL node.
 
    ```shell copy
    /usr/local/share/enterprise/ghe-repl-post-failover-mssql
    ```
 
+1. Check the status of the MySQL(or MySQL and MSSQL) replication from any node in the cluster by running `ghe-cluster-status -v`.
 1. When the MySQL(or MySQL and MSSQL) replication is finished, from any node in the cluster, disable maintenance mode. See [AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode#enabling-or-disabling-maintenance-mode-for-all-nodes-in-a-cluster-via-the-cli).