diff --git a/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst b/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst
index a2077eed9..cd5befc73 100644
--- a/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst
+++ b/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst
@@ -40,11 +40,13 @@ meets the following conditions:
     Upgrade Orchestration Strategy* creation step will fail if there are no
     qualified hosts detected.
 
-    A Kubernetes version upgrade is a reboot required operation. Therefore, in
-    systems that have the |prefix|-openstack application applied with running
-    instances, if the migrate option is selected there must be spare
-    openstack-compute (worker) capacity to move instances off the
-    openstack-compute (worker) host\(s) being upgraded.
+    A Kubernetes version upgrade requires replacing kubelet on each node, which
+    requires the applications on each node to be disrupted. In the multi-node
+    clusters, a Kubernetes version upgrade also requires a host lock/unlock.
+    Therefore, in the multi-node systems that have the |prefix|-openstack application
+    applied with running instances, if the migrate option is selected, there
+    must be spare openstack-compute (worker) capacity to move instances off the
+    openstack-compute (worker) host(s) being upgraded.
 
 -   If you are using NetApp Trident in |prod| |prod-ver| and have upgraded from
     the |prod| previous version, ensure that your NetApp backend version is