From 86722af89f550c9e0a774222f3f440055e2270a3 Mon Sep 17 00:00:00 2001 From: Nathan Coleman Date: Tue, 4 Oct 2022 18:05:03 -0400 Subject: [PATCH] Update website/content/docs/consul-vs-other/api-gateway-compare.mdx Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> --- website/content/docs/consul-vs-other/api-gateway-compare.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/consul-vs-other/api-gateway-compare.mdx b/website/content/docs/consul-vs-other/api-gateway-compare.mdx index cc0eb6fcaf..57eccde06d 100644 --- a/website/content/docs/consul-vs-other/api-gateway-compare.mdx +++ b/website/content/docs/consul-vs-other/api-gateway-compare.mdx @@ -9,7 +9,7 @@ description: >- **Examples**: Kong Gateway, Apigee, Mulesoft, Gravitee -The Consul API Gateway ([documentation](/docs/api-gateway)) is an implementation of the [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/). Traditionally, API gateways are used for two things: _Client Traffic Management_ and _API Lifecycle Management_. +The [Consul API Gateway](/docs/api-gateway) is an implementation of the [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/). Traditionally, API gateways are used for two things: _Client Traffic Management_ and _API Lifecycle Management_. Client traffic management refers to an API gateway's role in controlling the point of entry for public traffic into a given environment, also known as _managing north-south traffic_. The Consul API Gateway is deployed alongside Consul service mesh and is responsible for routing inbound client requests to the mesh based on defined routes. For a full list of supported traffic management features, refer to the [Consul API Gateway documentation](/docs/api-gateway).