Deployed a22464c to dev with MkDocs 1.6.0 and mike 2.1.2

dev/guides/node-management/drain/index.html

@@ -1063,7 +1063,7 @@ <h2 id="draining-a-node">Draining a node</h2>
 as described in
 <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/">Taints and Tolerations</a>.</p>
 <p>This would be used only after the WLM jobs have been removed from that Rabbit (preferably) and there is some reason to also remove the NNF software from it. This might be used before a Rabbit is powered off and pulled out of the cabinet, for example, to avoid leaving pods in "Terminating" state (harmless, but it's noise).</p>
-<p>If an admin used this taint before power-off it would mean there wouldn't be "Terminating" pods laying around for that Rabbit. After a new/same Rabbit is put back in its place, the NNF software won't jump back on it while the taint is present. The taint can be removed at any time, from immediately after the node is powered off up to some time after the new/same Rabbit is powered back on.</p>
+<p>If an admin used this taint before power-off it would mean there wouldn't be "Terminating" pods lying around for that Rabbit. After a new/same Rabbit is put back in its place, the NNF software won't jump back on it while the taint is present. The taint can be removed at any time, from immediately after the node is powered off up to some time after the new/same Rabbit is powered back on.</p>
 <h3 id="drain-nnf-pods-from-a-rabbit-node">Drain NNF pods from a rabbit node</h3>
 <p>Drain the NNF software from a node by applying the <code>cray.nnf.node.drain</code> taint.
 The CSI driver pods will remain on the node to satisfy any unmount requests from k8s