Merge pull request #54886 from mletalie/GH-53709

mburke5678 · web-flow · commit 5b527554fa40 · 2023-01-19T11:32:31.000-05:00
Adding 'you' per request/typo.
diff --git a/modules/nw-cluster-mtu-change.adoc b/modules/nw-cluster-mtu-change.adoc
@@ -344,7 +344,7 @@ ExecStart=/usr/local/bin/mtu-migration.sh
 
 . Update the underlying network interface MTU value:
 
-** If are specifying the new MTU with a NetworkManager connection configuration, enter the following command. The MachineConfig Operator automatically performs a rolling reboot of the nodes in your cluster.
+** If you are specifying the new MTU with a NetworkManager connection configuration, enter the following command. The MachineConfig Operator automatically performs a rolling reboot of the nodes in your cluster.
 +
 [source,terminal]
 ----
@@ -353,7 +353,7 @@ $ for manifest in control-plane-interface worker-interface; do
   done
 ----
 
-** If are specifying the new MTU with a DHCP server option or a kernel command line and PXE, make the necessary changes for your infrastructure.
+** If you are specifying the new MTU with a DHCP server option or a kernel command line and PXE, make the necessary changes for your infrastructure.
 
 . As the MCO updates machines in each machine config pool, it reboots each node one by one. You must wait until all the nodes are updated. Check the machine config pool status by entering the following command:
 +

Original file line number	Diff line number	Diff line change
`@@ -344,7 +344,7 @@ ExecStart=/usr/local/bin/mtu-migration.sh`
`344`	`344`
`345`	`345`	`. Update the underlying network interface MTU value:`
`346`	`346`
`347`		`-** If are specifying the new MTU with a NetworkManager connection configuration, enter the following command. The MachineConfig Operator automatically performs a rolling reboot of the nodes in your cluster.`
	`347`	`+** If you are specifying the new MTU with a NetworkManager connection configuration, enter the following command. The MachineConfig Operator automatically performs a rolling reboot of the nodes in your cluster.`
`348`	`348`	`+`
`349`	`349`	`[source,terminal]`
`350`	`350`	`----`
`@@ -353,7 +353,7 @@ $ for manifest in control-plane-interface worker-interface; do`
`353`	`353`	`done`
`354`	`354`	`----`
`355`	`355`
`356`		`-** If are specifying the new MTU with a DHCP server option or a kernel command line and PXE, make the necessary changes for your infrastructure.`
	`356`	`+** If you are specifying the new MTU with a DHCP server option or a kernel command line and PXE, make the necessary changes for your infrastructure.`
`357`	`357`
`358`	`358`	`. As the MCO updates machines in each machine config pool, it reboots each node one by one. You must wait until all the nodes are updated. Check the machine config pool status by entering the following command:`
`359`	`359`	`+`