diff --git a/Docker & Kubernetes/Servers/AWX/AWX Operator/Ansible AWX Operator.md b/Docker & Kubernetes/Servers/AWX/AWX Operator/Ansible AWX Operator.md
index e462e02..ce6fcdd 100644
--- a/Docker & Kubernetes/Servers/AWX/AWX Operator/Ansible AWX Operator.md	
+++ b/Docker & Kubernetes/Servers/AWX/AWX Operator/Ansible AWX Operator.md	
@@ -124,7 +124,7 @@ kubectl apply -k .
 !!! warning "Be Patient - Wait 20 Minutes"
     The process may take a while to spin up AWX, postgresql, redis, and other workloads necessary for AWX to function.  Depending on the speed of the server, it may take between 5 and 20 minutes for AWX to be ready to connect to.  You can watch the progress via the CLI commands listed above, or directly on Rancher's WebUI at https://rancher.bunny-lab.io.  
 
-## Add Kerberos Authentication (Windows)
+## Add Kerberos Execution Environment
 You may find that you need to be able to remotely control domain-joined Windows devices using Kerberos.  You need to go through some extra steps to set this up after you have successfully deployed AWX Operator into Kubernetes.
 
 ### Create Kerberos Keytab File