Description of problem:

Clarify how many times the worker nodes needs to reboot     

Additional info:

Currently, in a "Control Plane only update" documentation, we do have below statement

However, administrators who want to update between two even-numbered minor versions can do so incurring only a single reboot of non-control plane hosts

I would like an further clarification that, even if the upgrade path include some intermediate patch upgrade, there is still only one time of non-control plane hosts reboot needed.

For example: From 4.14.13 to 4.16.14, the path requires the cluster to first upgrade to 4.14.37 as an intermediate version, then going to 4.15.z and 4.16.z.  The clarification should be clear that, this intermediate patch release upgrade still do not require worker nodes unpause and reboot, hence that the entire progress only need one time of worker nodes reboot, which will be performed as the last step of upgrade.

Business value: by clarifying that the additional reboot/disrupt of worker nodes is not necessary, customer can greatly reduce the maintenance windows and shorten the upgrade schedule.