OCPBUGS-17933: Clarify steps

- https://issues.redhat.com/browse/OCPBUGS-17933

Author: jab-rh

modules/nw-cluster-mtu-change.adoc

@@ -72,6 +72,11 @@ Status:
 
 ifndef::local-zone,wavelength-zone,post-aws-zones,outposts[]
 . Prepare your configuration for the hardware MTU:
++
+[IMPORTANT]
+====
+There are many ways to configure the hardware MTU for your cluster nodes. The following examples show only the most common methods. You must verify that your infrastructure MTU is correct and that your preferred method for configuring your hardware MTU in the cluster nodes is in effect before proceeding.
+====
 
 ** If your hardware MTU is specified with DHCP, update your DHCP configuration such as with the following dnsmasq configuration:
 +
@@ -91,7 +96,6 @@ where:
 ** If your hardware MTU is specified in a NetworkManager connection configuration, complete the following steps. This approach is the default for {product-title} if you do not explicitly specify your network configuration with DHCP, a kernel command line, or some other method. Your cluster nodes must all use the same underlying network configuration for the following procedure to work unmodified.
 
 ... Find the primary network interface by entering the following command:
-
 +
 [source,terminal]
 ----
@@ -389,7 +393,7 @@ $ oc get nodes
 +
 [source,terminal]
 ----
-$ oc debug node/<node> -- chroot /host ip address show <interface>
+$ oc adm node-logs <node> -u ovs-configuration | grep configure-ovs.sh | grep mtu | grep <interface> | head -1
 ----
 +
 where: