From 402ddd6dcdd7e2aa890d63bc0430348ea977f83c Mon Sep 17 00:00:00 2001 From: Jeff Apple <79924108+Jeff-Apple@users.noreply.github.com> Date: Thu, 8 Sep 2022 12:54:02 -0700 Subject: [PATCH] Update website/content/docs/api-gateway/tech-specs.mdx Co-authored-by: Nathan Coleman --- website/content/docs/api-gateway/tech-specs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/api-gateway/tech-specs.mdx b/website/content/docs/api-gateway/tech-specs.mdx index f62458eb86..f74b42b38b 100644 --- a/website/content/docs/api-gateway/tech-specs.mdx +++ b/website/content/docs/api-gateway/tech-specs.mdx @@ -49,7 +49,7 @@ The following table lists API Gateway limitations related to specific Consul fea | Consul Feature | Limitation | | -------------- | ---------- | | Admin Partitions | API Gateway can deployed only in the default Admin Partition. | -| Data Center Federation | When multiple Consul Data Centers are fererated together, API gateway can only be deployed in the Priary Data Center. | +| Datacenter Federation | When multiple Consul datacenters are federated together, API Gateway can only be deployed in the primary datacenter. | | Routing between Data Centers | When multiple Consul Data Centers are fererated together, API gateway can route traffic only to Services in the local Data Center. Howeve, API Gateway can route to Services in othe Kubernetes clusters when they are in the same Consul Data Center. See [Single Consul Datacenter in Multiple Kubernetes Clusters](https://www.consul.io/docs/k8s/deployment-configurations/single-dc-multi-k8s) for more details. | ## Deployment Environments