From aa3e262ee107abc9d6e9b9115cddf1073bb1b720 Mon Sep 17 00:00:00 2001
From: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
Date: Fri, 12 May 2023 09:28:07 -0700
Subject: [PATCH] Update website/content/docs/k8s/annotations-and-labels.mdx

Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>
---
 website/content/docs/k8s/annotations-and-labels.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/k8s/annotations-and-labels.mdx b/website/content/docs/k8s/annotations-and-labels.mdx
index 8c13b274949e..d34a56f97120 100644
--- a/website/content/docs/k8s/annotations-and-labels.mdx
+++ b/website/content/docs/k8s/annotations-and-labels.mdx
@@ -80,7 +80,7 @@ The following Kubernetes resource annotations could be used on a pod to control
        Use the unlabeled annotation format to specify a service name, Consul Enterprise namespaces and partitions, and
        datacenters. 
 
-      - Service name: Place the service name at the beginning of the annotation to specify the upstream service. You also have the option to append the datacenter where the service is deployed.
+      - Service name: Place the service name at the beginning of the annotation to specify the upstream service. You also have the option to append the WAN federated datacenter where the service is deployed.
    
         ```yaml
         annotations: