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

salonichf5 · sjberman · web-flow · commit f5cb59947632 · 2024-06-28T11:23:11.000-06:00
Co-authored-by: Saylor Berman &lt;s.berman@f5.com&gt;
diff --git a/site/content/how-to/monitoring/troubleshooting.md b/site/content/how-to/monitoring/troubleshooting.md
@@ -226,7 +226,7 @@ server {
 }
 ```
 
-Once 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:
+Once an 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.
 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
`@@ -226,7 +226,7 @@ server {`
`226`	`226`	`}`
`227`	`227`	```
`228`	`228`
`229`		-Once 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:
	`229`	+Once an 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:
`230`	`230`
`231`	`231`	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.
`232`	`232`	2. A simple `coffee` application with hostname `cafe.example.com` and referenced to the Gateway we created.