diff --git a/doc/source/dist_cloud/kubernetes/deploy-software-releases-using-the-cli-1ea02eb230e5.rst b/doc/source/dist_cloud/kubernetes/deploy-software-releases-using-the-cli-1ea02eb230e5.rst
index 3a82cf098..6d3e6e81d 100644
--- a/doc/source/dist_cloud/kubernetes/deploy-software-releases-using-the-cli-1ea02eb230e5.rst
+++ b/doc/source/dist_cloud/kubernetes/deploy-software-releases-using-the-cli-1ea02eb230e5.rst
@@ -31,14 +31,15 @@ The System Controller is now ready for new subcloud deployment.
 .. note::
 
     Starting release |prod-ver|, low-latency configuration via remote install
-	is no longer supported.
-    
+    is no longer supported.
+
     For new subcloud deployments that involve remote install using Redfish,
-	avoid using ``install_type`` of 4 and 5 in ``install-values.yaml``. 
-    
+    avoid using ``install_type`` of 4 and 5 in ``install-values.yaml``.
+
     For existing subclouds that were originally deployed with remote install,
-	use :command:`dcmanager subcloud update --install-values` to update the
-	``install_type`` so they can be restored in the future.
+    use :command:`dcmanager subcloud update --install-values` to update
+    ``install_type`` so they can be restored in the future. Ensure that the
+    software version in ``install_values`` matches the new version.
 
 Orchestrate the Deployment of a Software Release Across the Subclouds
 ---------------------------------------------------------------------
@@ -340,4 +341,4 @@ If a failure occurs, follow the general steps below:
 #.  Resolve the condition that caused the failure.
 
 #.  Retry the orchestration by deleting the failed strategy and create a new
-    one for the failed subcloud(s).
\ No newline at end of file
+    one for the failed subcloud(s).