Merge pull request #78136 from JoeAldinger/OSDOCS-34559

OSDOCS-34559: updates procedure with xref to alternative option

Author: JoeAldinger

modules/nw-ovn-kubernetes-migration.adoc

@@ -85,9 +85,9 @@ where:
 +
 --
 * Maximum transmission unit (MTU). Consider the following before customizing the MTU for this optional step:
-** If you use the default MTU, and you want to keep the default MTU during migration, this step can be ignored. 
+** If you use the default MTU, and you want to keep the default MTU during migration, this step can be ignored.
 ** If you used a custom MTU, and you want to keep the custom MTU during migration, you must declare the custom MTU value in this step.
-** This step does not work if you want to change the MTU value during migration. Instead, you must first follow the instructions for "Changing the cluster MTU". You can then keep the custom MTU value by performing this procedure and declaring the custom MTU value in this step. 
+** This step does not work if you want to change the MTU value during migration. Instead, you must first follow the instructions for "Changing the cluster MTU". You can then keep the custom MTU value by performing this procedure and declaring the custom MTU value in this step.
 +
 [NOTE]
 ====
@@ -289,6 +289,12 @@ daemon set "multus" successfully rolled out
 
 . To complete changing the network plugin, reboot each node in your cluster. You can reboot the nodes in your cluster with either of the following approaches:
 
++
+[IMPORTANT]
+====
+The following scripts reboot all of the nodes in the cluster at the same time. This can cause your cluster to be unstable. Another option is to reboot your nodes manually one at a time. Rebooting nodes one-by-one causes considerable downtime in a cluster with many nodes.
+====
+
 ** With the `oc rsh` command, you can use a bash script similar to the following:
 +
 [source,bash]