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

@@ -158,7 +158,7 @@ Once a HTTPRoute with path matches and rules are defined, the nginx.conf is upda
 
 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.
 2. A simple `coffee` application with hostname `cafe.example.com` and referenced to the Gateway we created.
-3. A HTTPRoute to expose `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 redirect requests as needed.
+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.
 
 For example, this `coffee` route matches requests with path `/coffee` and type `prefix`. Lets see how the `nginx.conf` is modified.