diff --git a/docs/docs-content/clusters/cluster-management/cluster-updates.md b/docs/docs-content/clusters/cluster-management/cluster-updates.md
index 5f4207b212..8c940d7bac 100644
--- a/docs/docs-content/clusters/cluster-management/cluster-updates.md
+++ b/docs/docs-content/clusters/cluster-management/cluster-updates.md
@@ -43,7 +43,7 @@ upgrading, you review the information provided in the
   - For PXK and PXK-E, refer to
     [Upgrade Kubeadm Clusters](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/).
   - For K3s, refer to [K3s Upgrades](https://docs.k3s.io/upgrades#version-specific-caveats)
-  - For RKE2, refer to [RKE2 Manual Upgrades](https://docs.rke2.io/upgrade/manual_upgrade)
+  - For RKE2, refer to [RKE2 Manual Upgrades](https://docs.rke2.io/upgrades/manual_upgrade)
 
 ## Prerequisites
 
diff --git a/docs/docs-content/clusters/data-center/maas/create-manage-maas-clusters.md b/docs/docs-content/clusters/data-center/maas/create-manage-maas-clusters.md
index 8769293120..5b374686d6 100644
--- a/docs/docs-content/clusters/data-center/maas/create-manage-maas-clusters.md
+++ b/docs/docs-content/clusters/data-center/maas/create-manage-maas-clusters.md
@@ -94,8 +94,8 @@ section of the pack Additional Guidance for further information.
         servers to only those that have at least the amount of CPU and Memory selected.
 
       - Tags: Specify the MAAS machine tags so that Palette can deploy nodes onto the MAAS machines that match the
-        provided tags. To learn more about MAAS tags, refer to the [MAAS Tags](https://maas.io/docs/how-to-tag-machines)
-        documentation.
+        provided tags. To learn more about MAAS tags, refer to the
+        [MAAS Tags](https://maas.io/docs/how-to-use-group-machines#p-19384-tags-and-annotations) documentation.
 
 12. You can configure the following cluster management features now if needed, or you can do it later:
 
diff --git a/docs/docs-content/clusters/edge/site-deployment/deploy-custom-registries/webhook-disable.md b/docs/docs-content/clusters/edge/site-deployment/deploy-custom-registries/webhook-disable.md
index 1f3d33c660..9875a246a5 100644
--- a/docs/docs-content/clusters/edge/site-deployment/deploy-custom-registries/webhook-disable.md
+++ b/docs/docs-content/clusters/edge/site-deployment/deploy-custom-registries/webhook-disable.md
@@ -173,10 +173,9 @@ If you are using public registries that do not require authentication, you can s
 If your registries require authentication, you will need to provide credentials to enable image pulls. This example uses
 an open source generic Kubernetes credentials provider to provide the resources. There are other resources that you can
 take advantage of to provide registry credentials, including using a `registry.yaml` file in
-[K3s](https://docs.k3s.io/installation/private-registry) or
-[RKE2](https://docs.rke2.io/install/containerd_registry_configuration). However, the advantage of the approach used in
-this example is that after installation, you will not need to restart your cluster services to update the registry paths
-or the registry credentials.
+[K3s](https://docs.k3s.io/installation/private-registry) or [RKE2](https://docs.rke2.io/install/private_registry).
+However, the advantage of the approach used in this example is that after installation, you will not need to restart
+your cluster services to update the registry paths or the registry credentials.
 
 :::info