Clarify HTTPRouteMatch rules (#3741)

* docs: clarify HTTPRouteMatch rules

Signed-off-by: Vegard Hagen <[email protected]>

* docs: add missing criterion in HTTPRouteMatch rules

also try to use more clear language

Signed-off-by: Vegard Hagen <[email protected]>

---------

Signed-off-by: Vegard Hagen <[email protected]>
Signed-off-by: Vegard Hagen <[email protected]>

Author: vehagn

site-src/api-types/httproute.md

@@ -211,9 +211,16 @@ unspecified, the rule performs no forwarding. If unspecified and no filters
 are specified that would result in a response being sent, a 404 error code
 is returned.
 
-The following example forwards HTTP requests for prefix `/bar` to service
-"my-service1" on port `8080` and HTTP requests for prefix `/some/thing` with
-header `magic: foo` to service "my-service2" on port `8080`:
+The following example forwards HTTP requests for path prefix `/bar` to service
+"my-service1" on port `8080`, and HTTP requests fulfilling _all_ four of the 
+following criteria
+
+- header `magic: foo` 
+- query param `great: example`
+- path prefix `/some/thing`
+- method `GET`
+
+to service "my-service2" on port `8080`:
 ```yaml
 {% include 'standard/basic-http.yaml' %}
 ```