diff --git a/reference/fleet/upgrade-elastic-agent.md b/reference/fleet/upgrade-elastic-agent.md
index 23580c9ac5..fafc932167 100644
--- a/reference/fleet/upgrade-elastic-agent.md
+++ b/reference/fleet/upgrade-elastic-agent.md
@@ -37,7 +37,7 @@ For a detailed view of the {{agent}} upgrade process and the interactions betwee
 
 Note the following restrictions with upgrading an {{agent}}:
 
-* {{agent}} cannot be upgraded to a version higher than the highest currently installed version of {{fleet-server}}. When you upgrade a set of {{agents}} that are currently at the same version, you should first upgrade any agents that are acting as {{fleet-server}} (any agents that have a {{fleet-server}} policy associated with them).
+* {{agent}} cannot be upgraded to a minor version higher than the currently installed minor version of {{fleet-server}}. For example, you can enroll 9.1.5 {{agents}} with a 9.1.0 {{fleet-server}}, but not 9.2.0 {{agents}}. So while you can install newer maintenance releases, you cannot install newer minor versions. Before you upgrade {{agents}} to a newer minor version, you should first upgrade any agents that are acting as a [{{fleet-server}}](/reference/fleet/fleet-server.md) (any agents associated with a {{fleet-server}} policy).
 * To be upgradeable, {{agent}} must not be running inside a container.
 * To be upgradeable in a Linux environment, {{agent}} must be running as a service. The Linux Tar install instructions for {{agent}} provided in {{fleet}} include the commands to run it as a service. {{agent}} RPM and DEB system packages cannot be upgraded through {{fleet}}.