remove alpha and beta warnings

Author: paigecalvert

docs/enterprise/embedded-manage-nodes.mdx

@@ -8,19 +8,15 @@ This topic describes managing nodes in clusters created with Replicated Embedded
 
 Multi-node clusters with Embedded Cluster have the following limitations:
 
-* Support for multi-node clusters with Embedded Cluster is Beta. Only single-node embedded clusters are Generally Available (GA).
-
-* High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. For more information about this feature, reach out to Alex Parker at [alexp@replicated.com](mailto:alexp@replicated.com).
+* Setting node roles with the Embedded Cluster Config [roles](/reference/embedded-config#roles) key is Beta.
 
 * The same Embedded Cluster data directory used at installation is used for all nodes joined to the cluster. This is either the default `/var/lib/embedded-cluster` directory or the directory set with the [`--data-dir`](/reference/embedded-cluster-install#flags) flag. You cannot choose a different data directory for Embedded Cluster when joining nodes.
 
 * More than one controller node should not be joined at the same time. When joining a controller node, a warning is printed that explains that the user should not attempt to join another node until the controller node joins successfully.
 
-* Setting node roles with the Embedded Cluster Config [roles](/reference/embedded-config#roles) key is Beta.
+* The `join print-command` command always returns the commands for joining a node with the controller role. It does not support printing the join command for any custom node roles defined in the Embedded Cluster Config `roles` key. See [Automate Controller Node Joins](#automate-node-joins) below.
 
-* The `join print-command` command always returns the commands for joining a node with the controller role. It does not support printing the join command for any custom node roles defined in the Embedded Cluster Config `roles` key. See [Automate Controller Node Joins (Beta)](#automate-node-joins) below.
-
-## Add Nodes to a Cluster (Beta) {#add-nodes}
+## Add Nodes to a Cluster {#add-nodes}
 
 This section describes how to add nodes to a cluster with Embedded Cluster.
 
@@ -60,7 +56,7 @@ To add a node to a cluster with Embedded Cluster:
 
 1. Repeat these steps for each node you want to add.
 
-## Automate Controller Node Joins (Beta) {#automate-node-joins}
+## Automate Controller Node Joins {#automate-node-joins}
 
 With Embedded Cluster, you can use the command line to get the commands for joining controller nodes, rather than having to log into the Admin Console UI to get the commands. This is especially useful when testing multi-node Embedded Cluster installations where you need to automate the process of joining controller nodes to a cluster.
 
@@ -100,11 +96,7 @@ To automate controller node joins with Embedded Cluster:
 
 1. On the node that you want to join as a controller, run each of the commands provided in the `join print-command` output to download the Embedded Cluster binary, extract the binary, and join the node to the cluster.
 
-## High Availability for Multi-Node Clusters (Alpha) {#ha}
-
-:::important
-High availability for Embedded Cluster in an Alpha feature. This feature is subject to change, including breaking changes. For more information about this feature, reach out to Alex Parker at [alexp@replicated.com](mailto:alexp@replicated.com).
-:::
+## High Availability for Multi-Node Clusters {#ha}
 
 Multi-node clusters are not highly available by default. The first node of the cluster holds important data for Kubernetes and KOTS, such that the loss of this node would be catastrophic for the cluster. Enabling high availability requires that at least three controller nodes are present in the cluster.