From efcb466e38e70a52f0239231ba559d8bbfb6701e Mon Sep 17 00:00:00 2001 From: boruszak Date: Wed, 28 Sep 2022 16:09:23 -0500 Subject: [PATCH] Typo fix --- .../docs/connect/cluster-peering/create-manage-peering.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx index 7f82c2c326..2dedce8fe4 100644 --- a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx +++ b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx @@ -375,7 +375,7 @@ Next to the name of the peer, click **More** (three horizontal dots) and then ** -## Traffic nanagement between peers +## Traffic management between peers As of Consul v1.14, you can use [dynamic traffic management](/consul/docs/connect/l7-traffic) to configure your service mesh so that services automatically failover and redirect between peers. The following examples updates the [ServiceResolver config entry](/docs/connect/config-entries/) in `cluster-01` so that Consul redirects traffic intended for the `frontend` service to a backup instance in peer `cluster-02` when it detects multiple connection failures.