Merge pull request #3266 from replicatedhq/anchor-links

fix anchor links

Author: paigecalvert

docs/enterprise/embedded-manage-nodes.mdx

@@ -8,7 +8,7 @@ This topic describes managing nodes in clusters created with Replicated Embedded
 
 Multi-node clusters with Embedded Cluster have the following limitations:
 
-* Setting node roles with the Embedded Cluster Config [roles](/reference/embedded-config#roles) key is Beta.
+* Setting node roles with the Embedded Cluster Config [roles](/reference/embedded-config#roles-beta) 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.
 

docs/vendor/customer-reporting.md

@@ -14,9 +14,9 @@ As shown in the image above, the **Reporting** page has the following main secti
 * [Manage Customer](#manage-customer)
 * [Time to Install](#time-to-install)
 * [Download Portal](#download-portal)
-* [Enterprise Portal](#enterprise-portal)
+* [Enterprise Portal](#enterprise-portal-alpha)
 * [Instances](#instances)
-* [Install Attempts](#install-attempts)
+* [Install Attempts](#install-attempts-alpha)
 
 ### Manage Customer
 

docs/vendor/embedded-using.mdx

@@ -235,7 +235,7 @@ Using the NVIDIA GPU Operator with Embedded Cluster requires configuring the con
 When the containerd options are configured as shown above, the NVIDIA GPU Operator automatically creates the required configurations in the `/etc/k0s/containerd.d/nvidia.toml` file. It is not necessary to create this file manually, or modify any other configuration on the hosts.
 
 :::note
-If you include the NVIDIA GPU Operator as a Helm extension, remove any existing containerd services that are running on the host (such as those deployed by Docker) before attempting to install the release with Embedded Cluster. If there are any containerd services on the host, the NVIDIA GPU Operator will generate an invalid containerd config, causing the installation to fail. For more information, see [Installation failure when NVIDIA GPU Operator is included as Helm extension](#nvidia) in _Troubleshooting Embedded Cluster_.
+If you include the NVIDIA GPU Operator as a Helm extension, remove any existing containerd services that are running on the host (such as those deployed by Docker) before attempting to install the release with Embedded Cluster. If there are any containerd services on the host, the NVIDIA GPU Operator will generate an invalid containerd config, causing the installation to fail. For more information, see [Installation failure when NVIDIA GPU Operator is included as Helm extension](#nvidia-gpu-operator) in _Troubleshooting Embedded Cluster_.
 
 This is the result of a known issue with v24.9.x of the NVIDIA GPU Operator. For more information about the known issue, see [container-toolkit does not modify the containerd config correctly when there are multiple instances of the containerd binary](https://github.com/NVIDIA/nvidia-container-toolkit/issues/982) in the nvidia-container-toolkit repository in GitHub.
 :::

docs/vendor/enterprise-portal-about.mdx

@@ -56,9 +56,9 @@ The Enterprise Portal provides insights to end users about their active and inac
 
 ### Customer Reporting
 
-The Enterprise Portal sends insights back to the Vendor Portal, which are surfaced on the **Customer Reporting** page. For more information, see [Enterprise Portal](/vendor/customer-reporting#enterprise-portal) in _Customer Reporting_.
+The Enterprise Portal sends insights back to the Vendor Portal, which are surfaced on the **Customer Reporting** page. For more information, see [Enterprise Portal](/vendor/customer-reporting#enterprise-portal-alpha) in _Customer Reporting_.
 
-These insights include details about the customer's install attempts. The Enterprise Portal tracks and reports on install attempts by creating unique, _just-in-time_ service accounts. These service accounts allow the Enterprise Portal to send data back to the Vendor Portal when the user starts and completes the installation or takes other actions that are specific to the installation type. The service accounts also provide realtime feedback to the user on their installation progress using checkboxes and status indicators, and allow users to pause and return to an installation attempt. For more information, see [Install Attempts](/vendor/customer-reporting#install-attempts) in _Customer Reporting_.
+These insights include details about the customer's install attempts. The Enterprise Portal tracks and reports on install attempts by creating unique, _just-in-time_ service accounts. These service accounts allow the Enterprise Portal to send data back to the Vendor Portal when the user starts and completes the installation or takes other actions that are specific to the installation type. The service accounts also provide realtime feedback to the user on their installation progress using checkboxes and status indicators, and allow users to pause and return to an installation attempt. For more information, see [Install Attempts](/vendor/customer-reporting#install-attempts-alpha) in _Customer Reporting_.
 
 The following shows an example of the **Install Attempts** section:
 

docs/vendor/replicated-onboarding.mdx

@@ -490,7 +490,7 @@ To add support for air gap installations:
 
 The Embedded Cluster Config supports roles for multi-node clusters. One or more roles can be selected and assigned to a node when it is joined to the cluster. Node roles can be used to determine which nodes run the Kubernetes control plane, and to assign application workloads to particular nodes.
 
-For more information, see [roles](/reference/embedded-config#roles) in _Embedded Cluster Config_.
+For more information, see [roles](/reference/embedded-config#roles-beta) in _Embedded Cluster Config_.
 
 ### Add and Map License Entitlements