Re-arranging steps for oc adm wait-for-stable-cluster

oc adm wait-for-stable-cluster this needs to be run after all required cluster operator force rollout.

Update modules/dr-restoring-cluster-state.adoc

changing `Platform` to 'platform'

Co-authored-by: Servesha Dudhgaonkar <49194531+xenolinux@users.noreply.github.com>

Author: vsolanki12

modules/dr-restoring-cluster-state.adoc

@@ -530,15 +530,6 @@ The `etcd` redeployment starts.
 +
 When the `etcd` cluster Operator performs a redeployment, the existing nodes are started with new pods similar to the initial bootstrap scale up.
 
-. Monitor the `etcd` instances by running:
-+
-[source,terminal]
-----
-$ oc adm wait-for-stable-cluster
-----
-+
-This process can take up to 15 minutes.
-
 . Turn the quorum guard back on by entering:
 +
 [source,terminal]
@@ -652,6 +643,15 @@ AllNodesAtLatestRevision
 +
 If the output includes multiple revision numbers, such as `2 nodes are at revision 6; 1 nodes are at revision 7`, this means that the update is still in progress. Wait a few minutes and try again.
 
+. Monitor the platform Operators by running:
++
+[source,terminal]
+----
+$ oc adm wait-for-stable-cluster
+----
++
+This process can take up to 15 minutes.
+
 . Verify that all control plane hosts have started and joined the cluster.
 +
 In a terminal that has access to the cluster as a `cluster-admin` user, run the following command: