Fix some spelling mistakes

Author: oscr

RELEASE.md

@@ -43,7 +43,7 @@ For a major or minor release:
 For all releases:
 - Check out the `release-major.minor` branch locally
 - Update `pkg/generator/main.go` with the new semver tag and any updates to the API review URL.
-- Run the following commnand `BASE_REF=vmajor.minor.patch make generate` which will update generated docs
+- Run the following command `BASE_REF=vmajor.minor.patch make generate` which will update generated docs
   and webhook with the correct version info. Note that the YAMLs will not work until the tag is actually
   published in the next step.
 - Publish a new Git tag. This can  be done using the `git` CLI or Github's [release][release]

site-src/blog/2022/graduating-to-beta.md

@@ -16,7 +16,7 @@ description: >
 
 We are excited to announce the v0.5.0 release of Gateway API. For the first
 time, several of our most important Gateway API resources are graduating to
-beta. Additional, we are starting a new initiative to explore how Gateway API
+beta. Additionally, we are starting a new initiative to explore how Gateway API
 can be used for mesh and introducing new experimental concepts such as URL
 rewrites. We'll cover all of this and more below.
 

site-src/blog/index.md

@@ -9,7 +9,7 @@
 
 We are excited to announce the v0.5.0 release of Gateway API. For the first
 time, several of our most important Gateway API resources are graduating to
-beta. Additional, we are starting a new initiative to explore how Gateway API
+beta. Additionally, we are starting a new initiative to explore how Gateway API
 can be used for mesh and introducing new experimental concepts such as URL
 rewrites.
 

site-src/concepts/api-overview.md

@@ -302,7 +302,7 @@ Here is a summary of extension points in the API:
 - **HTTPRouteFilter**: This API type in HTTPRoute provides a way to hook into
 the request/response lifecycle of an HTTP request.
 - **Custom Routes**: If none of the above extensions points suffice for a use
-  case, Implementers can chose to create custom Route resources for protocols
+  case, Implementers can choose to create custom Route resources for protocols
   that are not currently supported in the API. Custom Route types need to share
   the same fields that core Route types do. These are contained within
   CommonRouteSpec and RouteStatus.

site-src/contributing/gamma.md

@@ -22,7 +22,7 @@ GAMMA meetings will occur weekly on Tuesdays for 1 hour, alternating between 3pm
 PT and 8am PT slots to try to be as time-zone inclusive as possible. Meetings
 will be moderated by the [GAMMA
 leads](https://github.com/kubernetes-sigs/gateway-api/blob/main/OWNERS_ALIASES#L23)
-with notes taken by a volunteer. Meeting occurences can be found on the
+with notes taken by a volunteer. Meeting occurrences can be found on the
 [sig-network calendar](/contributing/community/#meetings). Community members
 should feel free to attend both GAMMA and Gateway API meetings, but are by no
 means obligated to do so.

site-src/references/policy-attachment.md

@@ -196,7 +196,7 @@ used to set defaults and requirements for an entire GatewayClass.
 ### Targeting External Services
 In some cases (likely limited to mesh or egress) users may want to apply
 policies to requests to external services. To accomplish this, implementations
-can choose to support a refernce to a virtual resource type:
+can choose to support a reference to a virtual resource type:
 
 ```yaml
 apiVersion: networking.example.net/v1alpha1