diff --git a/Containers/Kubernetes/Rancher RKE2/AWX Operator/RKE2 Ansible AWX.md b/Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible Operator.md
similarity index 92%
rename from Containers/Kubernetes/Rancher RKE2/AWX Operator/RKE2 Ansible AWX.md
rename to Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible Operator.md
index b8ebacb..934dd38 100644
--- a/Containers/Kubernetes/Rancher RKE2/AWX Operator/RKE2 Ansible AWX.md	
+++ b/Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible Operator.md	
@@ -7,8 +7,7 @@ Deploying a Rancher RKE2 Cluster-based Ansible AWX Operator server.  This can sc
 ![Ansible AWX WebUI](awx.png)
 
 ## Deploy Rancher RKE2 Cluster
-You will need to follow the [Rancher RKE2 Cluster Deployment](https://docs.cyberstrawberry.net/Container%20Documentation/Kubernetes/Rancher%20RKE2/Rancher%20RKE2%20Cluster)
- guide in order to initially set up the cluster itself.  After this phase, you can focus on the Ansible AWX-specific aspects of the deployment.  If you are only deploying AWX in a small environment, a single ControlPlane node is all you need to set up AWX.
+You will need to deploy a [Rancher RKE2 Cluster](https://docs.bunny-lab.io/Containers/Kubernetes/Rancher%20RKE2/Rancher%20RKE2%20Cluster/) on an Ubuntu Server-based virtual machine. After this phase, you can focus on the Ansible AWX-specific deployment. A single ControlPlane node is all you need to set up AWX, additional infrastructure can be added after-the-fact.
 :::tip
 
 If this is a virtual machine, after deploying the RKE2 cluster and validating it functions, now would be the best time to take a checkpoint / snapshot of the VM before moving forward, in case you need to perform rollbacks of the server(s) if you accidentally misconfigure something.