Fix docs typos (#4328)

Author: nurzhan-zhanuzak

site-src/api-types/httproute.md

@@ -307,7 +307,7 @@ RouteStatus defines the observed state that is required across all route types.
 
 Parents define a list of the Gateways (or other parent resources) that are
 associated with the HTTPRoute, and the status of the HTTPRoute with respect to
-each of these Gateways. When a HTTPRoute adds a reference to a Gateway in
+each of these Gateways. When an HTTPRoute adds a reference to a Gateway in
 parentRefs, the controller that manages the Gateway should add an entry to this
 list when the controller first sees the route and should update the entry as
 appropriate when the route is modified.

site-src/api-types/referencegrant.md

@@ -39,7 +39,7 @@ in the `to` list because a ReferenceGrant can only be used to allow references
 to resources in the same namespace as the ReferenceGrant.
 
 ## Example
-The following example shows how a HTTPRoute in namespace `foo` can reference a
+The following example shows how an HTTPRoute in namespace `foo` can reference a
 Service in namespace `bar`. In this example a ReferenceGrant in the `bar`
 namespace explicitly allows references to Services from HTTPRoutes in the `foo`
 namespace.

site-src/guides/api-design.md

@@ -75,7 +75,7 @@ installed in the cluster are supported.
     removed in v1.1.0. With that said, all of this guidance will still apply for
     implementations as long as they support v1.0.0 or older releases of the API.
 
-CRD and webhook validation is not the final validation i.e. webhook is "nice UX"
+CRD and webhook validation is not the final validation, i.e. webhook is "nice UX"
 but not schema enforcement. This validation is intended to provide immediate
 feedback to users when they provide an invalid configuration. Write code
 defensively with the assumption that at least some invalid input (Gateway API

site-src/guides/http-header-modifier.md

@@ -13,7 +13,7 @@ HTTP header modification is the process of adding, removing, or modifying HTTP h
 
 To configure HTTP header modification, define a Gateway object with one or more HTTP filters. Each filter specifies a specific modification to make to incoming requests, such as adding a custom header or modifying an existing header.
 
-To add a header to a HTTP request, use a filter of the type `RequestHeaderModifier`, with the `add` action and the name and value of the header:
+To add a header to an HTTP request, use a filter of the type `RequestHeaderModifier`, with the `add` action and the name and value of the header:
 
 ```yaml
 {% include 'standard/http-request-header-add.yaml' %}

site-src/guides/http-redirect-rewrite.md

@@ -78,15 +78,15 @@ and HTTPS listeners.
 There are multiple ways to secure a Gateway. In this example, it is secured
 using a Kubernetes Secret(`redirect-example` in the `certificateRefs` section).
 
-You need a HTTPRoute that attaches to the HTTP listener and does the redirect
+You need an HTTPRoute that attaches to the HTTP listener and does the redirect
 to HTTPS. Here we set `sectionName` to be `http` so it only selects the
 listener named `http`.
 
 ```yaml
 {% include 'standard/http-redirect-rewrite/httproute-redirect-http.yaml' %}
 ```
 
-You also need a HTTPRoute that attaches to the HTTPS listener that forwards
+You also need an HTTPRoute that attaches to the HTTPS listener that forwards
 HTTPS traffic to application backends.
 
 ```yaml

site-src/guides/http-request-mirroring.md

@@ -10,7 +10,7 @@ requests to another backend using
 [filters](../api-types/httproute.md#filters-optional). This guide shows how to use
 this feature.
 
-Mirrored requests will must only be sent to one single destination endpoint
+Mirrored requests will only be sent to one single destination endpoint
 within this backendRef, and responses from this backend MUST be ignored by
 the Gateway.