merge conflicts

Author: paigecalvert

docs/enterprise/installing-embedded-air-gap.mdx

@@ -125,7 +125,7 @@ To install with Embedded Cluster in an air gap environment:
 
 1. On the **Nodes** page, you can view details about the machine where you installed, including its node role, status, CPU, and memory. 
 
-     Optionally, add nodes to the cluster before deploying the application. For more information about joining nodes, see [Adding and Managing Nodes with Embedded Cluster](/enterprise/embedded-manage-nodes). Click **Continue**.
+     Optionally, add nodes to the cluster before deploying the application. For more information about joining nodes, see [Managing Multi-Node Clusters with Embedded Cluster](/enterprise/embedded-manage-nodes). Click **Continue**.
 
 1. On the **Configure [App Name]** screen, complete the fields for the application configuration options. Click **Continue**.
 

docs/enterprise/installing-embedded.mdx

@@ -87,7 +87,7 @@ To install an application with Embedded Cluster:
 
 1. On the **Nodes** page, you can view details about the machine where you installed, including its node role, status, CPU, and memory. 
 
-     Optionally, add nodes to the cluster before deploying the application. For more information about joining nodes, see [Adding and Managing Nodes with Embedded Cluster](/enterprise/embedded-manage-nodes). Click **Continue**.
+     Optionally, add nodes to the cluster before deploying the application. For more information about joining nodes, see [Managing Multi-Node Clusters with Embedded Cluster](/enterprise/embedded-manage-nodes). Click **Continue**.
 
 1. On the **Configure [App Name]** screen, complete the fields for the application configuration options. Click **Continue**.
 

docs/vendor/embedded-overview.mdx

@@ -266,20 +266,6 @@ To access the cluster and use other included binaries:
      If you encounter a typical workflow where your customers have to use the Embedded Cluster shell, reach out to Alex Parker at [email protected]. These workflows might be candidates for additional Admin Console functionality.
      :::
 
-## Troubleshoot
-
-From the shell, you can generate a support bundle for Replicated Embedded Cluster installations to help with troubleshooting.
-
-The default support bundle spec for Embedded Cluster collects host-level information to troubleshoot failures related to host configuration like DNS, networking, or storage problems.
-
-It also collects cluster-level information about the components provided by Replicated, such as the Admin Console and Embedded Cluster operator that manage install and upgrade operations. If the cluster has not installed successfully and cluster-level information is not available, it will be excluded from the bundle.
-
-When generating the default host bundle for Embedded Cluster installations, you can also use the `--load-cluster-specs` flag to automatically discover all support bundle specs that are defined in Secrets or ConfigMaps in the cluster. This ensures that any application-specific specs are included in the bundle. For more information, see [Discover Cluster Specs](https://troubleshoot.sh/docs/support-bundle/discover-cluster-specs/) in the Troubleshoot documentation.
-
-<EmbeddedClusterSupportBundle/>
-
-You can then use the support bundle for troubleshooting or provide it to Replicated for assistance.
-
 ## Reset a Node
 
 Resetting a node removes the cluster and your application from that node. This is useful for iteration, development, and when mistakes are made, so you can reset a machine and reuse it instead of having to procure another machine.

sidebars.js

@@ -240,6 +240,7 @@ const sidebars = {
             'reference/embedded-cluster-install',
           ],
         },
+        'enterprise/embedded-manage-nodes',
         'enterprise/updating-embedded',
         'vendor/embedded-disaster-recovery',
       ],