Update limitations (#2657)

* Update limitations

* Update embedded-overview.mdx

* docs edit

---------

Co-authored-by: Paige Calvert <[email protected]>

Author: ajp-io

docs/vendor/embedded-overview.mdx

@@ -43,13 +43,11 @@ As shown in the diagram above, the Embedded Cluster Config is included in the ap
 
 Embedded Cluster has the following limitations:
 
-* **No migration from kURL**: There is not a supported path to migrate an existing kURL instance to Embedded Cluster.
+* **No automated migration from kURL**: There is no automated migration from an existing kURL instance to Embedded Cluster. For a manual migration procedure, reach out to Alex Parker at [email protected].
 
 * **Multi-node support is in alpha**: Support for multi-node embedded clusters is in alpha. Only single-node embedded clusters are in beta. For more information, see [Enable High Availability for Multi-Node Clusters (Alpha)](#ha) below.
 
-* **Air gap support is in beta**: Support for air gap installations with Embedded Cluster is a beta feature. For more information, see [Air Gap Installation with Embedded Cluster (Beta)](/enterprise/installing-embedded-air-gap).
-
-* **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)
+* **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).
 
 * **Rollbacks not supported**: The [`allowRollback`](/reference/custom-resource-application#allowrollback) field in the KOTS Application custom resource is not supported for Embedded Cluster installations. In Embedded Cluster installations, the application and the cluster are installed and updated together as a single appliance. Because of this, users cannot roll back (downgrade) the application to an earlier version.