Fix typo in Gateway API compatibility doc (#1606)

Problem: The compatibility doc states that URLRewrite 
and RequestHeaderModifier filters are incompatible 
but should be URLRewrite and RequestRedirect.

Solution: Update the doc to state that URLRewrite 
and RequestRedirect filters are incompatible.

Author: kate-osborn

site/content/overview/gateway-api-compatibility.md

@@ -154,9 +154,9 @@ See the [static-mode]({{< relref "/reference/cli-help.md#static-mode">}}) comman
       - `method`: Supported.
     - `filters`
       - `type`: Supported.
-      - `requestRedirect`: Supported except for the experimental `path` field. If multiple filters are configured, NGINX Gateway Fabric will choose the first and ignore the rest.
-      - `requestHeaderModifier`: Supported. If multiple filters are configured, NGINX Gateway Fabric will choose the first and ignore the rest. Incompatible with `urlRewrite`.
-      - `urlRewrite`: Supported. If multiple filters are configured, NGINX Gateway Fabric will choose the first and ignore the rest. Incompatible with `requestHeaderModifier`.
+      - `requestRedirect`: Supported except for the experimental `path` field. If multiple filters are configured, NGINX Gateway Fabric will choose the first and ignore the rest. Incompatible with `urlRewrite`.
+      - `requestHeaderModifier`: Supported. If multiple filters are configured, NGINX Gateway Fabric will choose the first and ignore the rest.
+      - `urlRewrite`: Supported. If multiple filters are configured, NGINX Gateway Fabric will choose the first and ignore the rest. Incompatible with `requestRedirect`.
       - `responseHeaderModifier`, `requestMirror`, `extensionRef`: Not supported.
     - `backendRefs`: Partially supported. Backend ref `filters` are not supported.
 - `status`