diff --git a/docs/reference/custom-resource-application.mdx b/docs/reference/custom-resource-application.mdx
index e6027b9a6..82596df65 100644
--- a/docs/reference/custom-resource-application.mdx
+++ b/docs/reference/custom-resource-application.mdx
@@ -148,7 +148,7 @@ spec:
   </tr>
   <tr>
     <th>Supported for <a href="/vendor/embedded-overview">Embedded Cluster</a>?</th>
-    <td>No. <code>allowRollback</code> is not supported because Embedded Cluster does not support rolling back or downgrading.</td>
+    <td>Embedded Cluster 1.17.0 and later supports partial rollbacks of the application version. Partial rollbacks are supported only when rolling back to a version where there is no change to the [Embedded Cluster Config](/reference/embedded-config) compared to the currently-installed version. For example, users can roll back to release version 1.0.0 after upgrading to 1.1.0 only if both 1.0.0 and 1.1.0 use the same Embedded Cluster Config.</td>
   </tr>    
 </table>
 
diff --git a/docs/release-notes/rn-embedded-cluster.md b/docs/release-notes/rn-embedded-cluster.md
index 3d8dcb0fb..6e72e3798 100644
--- a/docs/release-notes/rn-embedded-cluster.md
+++ b/docs/release-notes/rn-embedded-cluster.md
@@ -95,7 +95,7 @@ Released on November 4, 2024
 </table>
 
 ### New Features {#new-features-1-17-0}
-* Adds partial rollback support where you can roll back from one version to another as long as the Embedded Cluster Config doesn't change between the two.
+* Adds support for partial rollbacks. Partial rollbacks are supported only when rolling back to a version where there is no change to the Embedded Cluster Config compared to the currently-installed version. For example, users can roll back to release version 1.0.0 after upgrading to 1.1.0 only if both 1.0.0 and 1.1.0 use the same [Embedded Cluster Config](/reference/embedded-config). For more information about how to enable rollbacks for your application in the KOTS Application custom resource, see [allowRollback](/reference/custom-resource-application#allowrollback) in _Application_.
 * Introduces a new landing page and guided installation workflow for the Admin Console.
 
 ### Improvements {#improvements-1-17-0}
diff --git a/docs/vendor/embedded-overview.mdx b/docs/vendor/embedded-overview.mdx
index 884798c94..e5100c74a 100644
--- a/docs/vendor/embedded-overview.mdx
+++ b/docs/vendor/embedded-overview.mdx
@@ -51,7 +51,7 @@ Embedded Cluster has the following limitations:
 
 * **Disaster recovery is in alpha**: Disaster Recovery for Embedded Cluster installations is in alpha. For more information, see [Disaster Recovery for Embedded Cluster (Alpha)](/vendor/embedded-disaster-recovery).
 
-* **Partial rollback support**: Rollbacks for Embedded Cluster installations are supported only when rolling back to a version where there is no change to the [Embedded Cluster Config](https://docs.replicated.com/reference/embedded-config) compared to the currently-installed version. For example, users can roll back to release version 1.0.0 after upgrading to 1.1.0 only if both 1.0.0 and 1.1.0 use the same Embedded Cluster Config.
+* **Partial rollback support**: In Embedded Cluster 1.17.0 and later, rollbacks are supported only when rolling back to a version where there is no change to the [Embedded Cluster Config](/reference/embedded-config) compared to the currently-installed version. For example, users can roll back to release version 1.0.0 after upgrading to 1.1.0 only if both 1.0.0 and 1.1.0 use the same Embedded Cluster Config. For more information about how to enable rollbacks for your application in the KOTS Application custom resource, see [allowRollback](/reference/custom-resource-application#allowrollback) in _Application_.
 
 * **Changing node hostnames is not supported**: After a host is added to a Kubernetes cluster, Kubernetes assumes that the hostname and IP address of the host will not change. If you need to change the hostname or IP address of a node, you must first remove the node from the cluster. For more information about the requirements for naming nodes, see [Node name uniqueness](https://kubernetes.io/docs/concepts/architecture/nodes/#node-name-uniqueness) in the Kubernetes documentation.