Update site/content/how-to/monitoring/troubleshooting.md

Co-authored-by: Kate Osborn <50597707+kate-osborn@users.noreply.github.com>

Author: salonichf5

site/content/how-to/monitoring/troubleshooting.md

@@ -156,7 +156,7 @@ server {
 
 Once a HTTPRoute with path matches and rules are defined, the nginx.conf is updated accordingly to determine which location block will manage incoming requests. To demonstrate how `nginx.conf` is changed, let's create some resources:
 
-1. A Gateway with single listener on port 80. The hostname specified is `*.example.com`, so all incoming requests matching that wildcard is accepted by this Gateway.
+1. A Gateway with single listener with the hostname `*.example.com` on port 80. 
 2. A simple `coffee` application with hostname `cafe.example.com` and referenced to the Gateway we created.
 3. An HTTPRoute that exposes the `coffee` application outside the cluster using the listener created in step 1. The path and rule matches create different location blocks in `nginx.conf` to route requests as needed.