From 2f77c0318d47940ef24fa0e10f07f831006ca2ab Mon Sep 17 00:00:00 2001 From: Frank Budinsky Date: Fri, 1 Mar 2024 13:53:35 -0500 Subject: [PATCH] Minor wording fixes to egress gateway doc (#14672) --- .../traffic-management/egress/egress-gateway/index.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md b/content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md index f17d99c5d8..9b2b0f5d6b 100644 --- a/content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md +++ b/content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md @@ -168,8 +168,7 @@ First create a `ServiceEntry` to allow direct traffic to an external service. [TLS Origination for Egress Traffic](/docs/tasks/traffic-management/egress/egress-tls-origination/) example, without TLS origination. -1. Create an egress `Gateway` for _edition.cnn.com_, port 80, and a destination rule for - traffic directed to the egress gateway. +1. Create a `Gateway` for egress traffic to _edition.cnn.com_ port 80. {{< tabset category-name="config-api" >}} @@ -467,8 +466,8 @@ You need to specify port 443 with protocol `TLS` in a corresponding `ServiceEntr ... {{< /text >}} -1. Create an egress `Gateway` for _edition.cnn.com_, a destination rule and a virtual service - to direct the traffic through the egress gateway and from the egress gateway to the external service. +1. Create an egress `Gateway` for _edition.cnn.com_ and route rules to direct the traffic + through the egress gateway and from the egress gateway to the external service. {{< tabset category-name="config-api" >}}