Merge pull request #77676 from skopacz1/OSDOCS-10958

OSDOCS-10958: removing 60 day update requirement from EUS doc

Author: skopacz1

updating/updating_a_cluster/eus-eus-update.adoc

@@ -26,7 +26,6 @@ There are a number of caveats to consider when attempting an EUS-to-EUS update.
 * EUS-to-EUS updates are only offered after updates between all versions involved have been made available in `stable` channels.
 * If you encounter issues during or after updating to the odd-numbered minor version but before updating to the next even-numbered version, then remediation of those issues may require that non-control plane hosts complete the update to the odd-numbered version before moving forward.
 * You can do a partial update by updating the worker or custom pool nodes to accommodate the time it takes for maintenance.
-* You can complete the update process during multiple maintenance windows by pausing at intermediate steps. However, plan to complete the entire update within 60 days. This is critical to ensure that normal cluster automation processes are completed.
 
 * Until the machine config pools are unpaused and the update is complete, some features and bugs fixes in <4.y+1> and <4.y+2> of {product-title} are not available.