diff --git a/content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md b/content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md
index 15759776283..2bfe608fa13 100644
--- a/content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md
+++ b/content/rancher/v2.x/en/deploy-across-clusters/fleet/_index.md
@@ -21,7 +21,8 @@ Fleet comes preinstalled in Rancher v2.5. To access it, go to the **Cluster Expl
 
 ### Windows Support
 
-Prior to Rancher v2.5.6, the `agent` would fail on downstream clusters with Windows nodes.
+Prior to Rancher v2.5.6, the `agent` did not have native Windows manifests on downstream clusters with Windows nodes.
+This would result in a failing `agent` pod for the cluster.
 If you are upgrading from an older version of Rancher to v2.5.6+, you can deploy a working `agent` with the following workflow *in the downstream cluster*:
 
 1. Cordon all Windows nodes.