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

salonichf5 · kate-osborn · web-flow · commit 00cab15a16b5 · 2024-06-26T09:58:18.000-06:00
Co-authored-by: Kate Osborn &lt;50597707+kate-osborn@users.noreply.github.com&gt;
diff --git a/site/content/how-to/monitoring/troubleshooting.md b/site/content/how-to/monitoring/troubleshooting.md
@@ -204,7 +204,7 @@ server {
 }
 ```
 
-Once routes 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, lets create some resources:
+Once routes 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.
 2. A simple `coffee` application with hostname `cafe.example.com` and referenced to the Gateway we created.

Original file line number	Diff line number	Diff line change
`@@ -204,7 +204,7 @@ server {`
`204`	`204`	`}`
`205`	`205`	```
`206`	`206`
`207`		-Once routes 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, lets create some resources:
	`207`	+Once routes 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:
`208`	`208`
`209`	`209`	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.
`210`	`210`	2. A simple `coffee` application with hostname `cafe.example.com` and referenced to the Gateway we created.