From fff9e7498147a24d833cd3b1a46424981ea2266a Mon Sep 17 00:00:00 2001 From: Art Date: Fri, 10 May 2024 15:46:30 -0400 Subject: [PATCH] Update docs/content/introduction/faq.md Co-authored-by: Rachael Graham --- docs/content/introduction/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/introduction/faq.md b/docs/content/introduction/faq.md index 558715b7c0c..a0682dd77ad 100644 --- a/docs/content/introduction/faq.md +++ b/docs/content/introduction/faq.md @@ -151,7 +151,7 @@ If you create a VirtualService and assign it TLS/SSL configuration, it will be b ### How can I associate a specific VirtualService to a specific gateway listener? -In the event you have multiple gateways or listeners on gateway or you want more fine-grained control over how a VirtualService gets associated with a Gateway, you can explicitly add the VirtualService name to the Gateway resource like this: +In the event you have multiple gateways or multiple listeners on a gateway, or you want more fine-grained control over how a VirtualService gets associated with a Gateway, you can explicitly add the VirtualService name to the Gateway resource like this: {{< highlight yaml "hl_lines=9-12" >}} apiVersion: gateway.solo.io/v1