chore: fix typo (#4958)

fix typo

Signed-off-by: Huabing Zhao <[email protected]>

site/content/en/docs/tasks/extensibility/envoy-patch-policy.md

@@ -299,7 +299,7 @@ spec:
         op: add
         # Every virtual_host that ends with 'www_example_com' (using RegEx Filter)
         jsonPath: "..virtual_hosts[?match(@.name, '.*www_example_com')]"
-        # If the property does not exists, it can not be selected with jsonPath 
+        # If the property does not exists, it can not be selected with jsonPath
         # Therefore the new property must be set in path
         path: "include_attempt_count_in_response"
         value: true
@@ -331,7 +331,7 @@ spec:
         op: add
         # Every virtual_host that ends with 'www_example_com' (using RegEx Filter)
         jsonPath: "..virtual_hosts[?match(@.name, '.*www_example_com')]"
-        # If the property does not exists, it can not be selected with jsonPath 
+        # If the property does not exists, it can not be selected with jsonPath
         # Therefore the new property must be set in path
         path: "include_attempt_count_in_response"
         value: true
@@ -414,7 +414,7 @@ status:
 
 ## Caveats
 
-This API will always be an unstable API and the same outcome cannot be garunteed
+This API will always be an unstable API and the same outcome cannot be guaranteed
 across versions for these reasons
 * The Envoy Proxy API might deprecate and remove API fields
 * Envoy Gateway might alter the xDS translation creating a different xDS output

site/content/en/latest/tasks/extensibility/envoy-patch-policy.md

@@ -299,7 +299,7 @@ spec:
         op: add
         # Every virtual_host that ends with 'www_example_com' (using RegEx Filter)
         jsonPath: "..virtual_hosts[?match(@.name, '.*www_example_com')]"
-        # If the property does not exists, it can not be selected with jsonPath 
+        # If the property does not exists, it can not be selected with jsonPath
         # Therefore the new property must be set in path
         path: "include_attempt_count_in_response"
         value: true
@@ -331,7 +331,7 @@ spec:
         op: add
         # Every virtual_host that ends with 'www_example_com' (using RegEx Filter)
         jsonPath: "..virtual_hosts[?match(@.name, '.*www_example_com')]"
-        # If the property does not exists, it can not be selected with jsonPath 
+        # If the property does not exists, it can not be selected with jsonPath
         # Therefore the new property must be set in path
         path: "include_attempt_count_in_response"
         value: true
@@ -414,7 +414,7 @@ status:
 
 ## Caveats
 
-This API will always be an unstable API and the same outcome cannot be garunteed
+This API will always be an unstable API and the same outcome cannot be guaranteed
 across versions for these reasons
 * The Envoy Proxy API might deprecate and remove API fields
 * Envoy Gateway might alter the xDS translation creating a different xDS output

site/content/en/v0.5/user/envoy-patch-policy.md

@@ -10,7 +10,7 @@ is unstable and the outcome may change across versions. Use at your own risk.
 ## Introduction
 
 The [EnvoyPatchPolicy][] API allows user to modify the output [xDS][]
-configuration generated by Envoy Gateway intended for EnvoyProxy, 
+configuration generated by Envoy Gateway intended for EnvoyProxy,
 using [JSON Patch][] semantics.
 
 ## Motivation
@@ -30,7 +30,7 @@ Before proceeding, you should be able to query the example backend using HTTP.
 * By default EnvoyPatchPolicy][] is disabled. Lets enable it in the [EnvoyGateway][] startup configuration
 
 * The default installation of Envoy Gateway installs a default [EnvoyGateway][] configuration and attaches it
-using a `ConfigMap`. In the next step, we will update this resource to enable EnvoyPatchPolicy. 
+using a `ConfigMap`. In the next step, we will update this resource to enable EnvoyPatchPolicy.
 
 
 ```shell
@@ -188,7 +188,7 @@ status:
 
 ## Caveats
 
-This API will always be an unstable API and the same outcome cannot be garunteed
+This API will always be an unstable API and the same outcome cannot be guaranteed
 across versions for these reasons
 * The Envoy Proxy API might deprecate and remove API fields
 * Envoy Gateway might alter the xDS translation creating a different xDS output

site/content/en/v0.6/user/envoy-patch-policy.md

@@ -10,7 +10,7 @@ is unstable and the outcome may change across versions. Use at your own risk.
 ## Introduction
 
 The [EnvoyPatchPolicy][] API allows user to modify the output [xDS][]
-configuration generated by Envoy Gateway intended for EnvoyProxy, 
+configuration generated by Envoy Gateway intended for EnvoyProxy,
 using [JSON Patch][] semantics.
 
 ## Motivation
@@ -30,7 +30,7 @@ Before proceeding, you should be able to query the example backend using HTTP.
 * By default [EnvoyPatchPolicy][] is disabled. Lets enable it in the [EnvoyGateway][] startup configuration
 
 * The default installation of Envoy Gateway installs a default [EnvoyGateway][] configuration and attaches it
-using a `ConfigMap`. In the next step, we will update this resource to enable EnvoyPatchPolicy. 
+using a `ConfigMap`. In the next step, we will update this resource to enable EnvoyPatchPolicy.
 
 
 ```shell
@@ -188,7 +188,7 @@ status:
 
 ## Caveats
 
-This API will always be an unstable API and the same outcome cannot be garunteed
+This API will always be an unstable API and the same outcome cannot be guaranteed
 across versions for these reasons
 * The Envoy Proxy API might deprecate and remove API fields
 * Envoy Gateway might alter the xDS translation creating a different xDS output

site/content/en/v1.0/tasks/extensibility/envoy-patch-policy.md

@@ -227,7 +227,7 @@ status:
 
 ## Caveats
 
-This API will always be an unstable API and the same outcome cannot be garunteed
+This API will always be an unstable API and the same outcome cannot be guaranteed
 across versions for these reasons
 * The Envoy Proxy API might deprecate and remove API fields
 * Envoy Gateway might alter the xDS translation creating a different xDS output

site/content/en/v1.1/tasks/extensibility/envoy-patch-policy.md

@@ -340,7 +340,7 @@ status:
 
 ## Caveats
 
-This API will always be an unstable API and the same outcome cannot be garunteed
+This API will always be an unstable API and the same outcome cannot be guaranteed
 across versions for these reasons
 * The Envoy Proxy API might deprecate and remove API fields
 * Envoy Gateway might alter the xDS translation creating a different xDS output

site/content/en/v1.2/tasks/extensibility/envoy-patch-policy.md

@@ -299,7 +299,7 @@ spec:
         op: add
         # Every virtual_host that ends with 'www_example_com' (using RegEx Filter)
         jsonPath: "..virtual_hosts[?match(@.name, '.*www_example_com')]"
-        # If the property does not exists, it can not be selected with jsonPath 
+        # If the property does not exists, it can not be selected with jsonPath
         # Therefore the new property must be set in path
         path: "include_attempt_count_in_response"
         value: true
@@ -331,7 +331,7 @@ spec:
         op: add
         # Every virtual_host that ends with 'www_example_com' (using RegEx Filter)
         jsonPath: "..virtual_hosts[?match(@.name, '.*www_example_com')]"
-        # If the property does not exists, it can not be selected with jsonPath 
+        # If the property does not exists, it can not be selected with jsonPath
         # Therefore the new property must be set in path
         path: "include_attempt_count_in_response"
         value: true
@@ -414,7 +414,7 @@ status:
 
 ## Caveats
 
-This API will always be an unstable API and the same outcome cannot be garunteed
+This API will always be an unstable API and the same outcome cannot be guaranteed
 across versions for these reasons
 * The Envoy Proxy API might deprecate and remove API fields
 * Envoy Gateway might alter the xDS translation creating a different xDS output