From 3c86f88de465c67b5e49e4c49b18a3b8158248b0 Mon Sep 17 00:00:00 2001 From: Matthieu Maquevice Date: Wed, 5 Sep 2018 06:09:46 +0200 Subject: [PATCH] wording (#2519) --- content/docs/tasks/traffic-management/ingress/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/tasks/traffic-management/ingress/index.md b/content/docs/tasks/traffic-management/ingress/index.md index 61bf974fef..b2f2aaa6c1 100644 --- a/content/docs/tasks/traffic-management/ingress/index.md +++ b/content/docs/tasks/traffic-management/ingress/index.md @@ -222,7 +222,7 @@ Let's see how you can configure a `Gateway` on port 80 for HTTP traffic. Entering the `httpbin` service URL in a browser won't work because you can't tell the browser to pretend to be accessing `httpbin.example.com` like with `curl`. In a real world situation, this is not a problem because because you configure the requested host properly and DNS resolvable. Thus, you use the host's domain name in the URL, for example, `https://httpbin.example.com/status/200`. -To work around this problem for simple tests and demos, use a wildcard `*` value for the host in the `Gateway` and `VirutualService` configurations. For example, if you change your ingress configuration to the following: +To work around this problem for simple tests and demos, use a wildcard `*` value for the host in the `Gateway` and `VirtualService` configurations. For example, if you change your ingress configuration to the following: {{< text bash >}} $ cat <