Spelling (#3400)

* spelling: adding Signed-off-by: Josh Soref <[email protected]> * spelling: anymore Signed-off-by: Josh Soref <[email protected]> * spelling: approach Signed-off-by: Josh Soref <[email protected]> * spelling: attached Signed-off-by: Josh Soref <[email protected]> * spelling: because Signed-off-by: Josh Soref <[email protected]> * spelling: cannot Signed-off-by: Josh Soref <[email protected]> * spelling: case-insensitive Signed-off-by: Josh Soref <[email protected]> * spelling: case-sensitive Signed-off-by: Josh Soref <[email protected]> * spelling: certificate Signed-off-by: Josh Soref <[email protected]> * spelling: certificates Signed-off-by: Josh Soref <[email protected]> * spelling: criteria Signed-off-by: Josh Soref <[email protected]> * spelling: deterministically Signed-off-by: Josh Soref <[email protected]> * spelling: discoverability Signed-off-by: Josh Soref <[email protected]> * spelling: docs Signed-off-by: Josh Soref <[email protected]> * spelling: encapsulated Signed-off-by: Josh Soref <[email protected]> * spelling: feature Signed-off-by: Josh Soref <[email protected]> * spelling: filesystem Signed-off-by: Josh Soref <[email protected]> * spelling: format Signed-off-by: Josh Soref <[email protected]> * spelling: frankbu Signed-off-by: Josh Soref <[email protected]> * spelling: github Signed-off-by: Josh Soref <[email protected]> * spelling: grpc Signed-off-by: Josh Soref <[email protected]> * spelling: grpcroute Signed-off-by: Josh Soref <[email protected]> * spelling: has Signed-off-by: Josh Soref <[email protected]> * spelling: have Signed-off-by: Josh Soref <[email protected]> * spelling: http-route Signed-off-by: Josh Soref <[email protected]> * spelling: httpproxy Signed-off-by: Josh Soref <[email protected]> * spelling: httpredirect Signed-off-by: Josh Soref <[email protected]> * spelling: https Signed-off-by: Josh Soref <[email protected]> * spelling: implementation Signed-off-by: Josh Soref <[email protected]> * spelling: improvements Signed-off-by: Josh Soref <[email protected]> * spelling: in Signed-off-by: Josh Soref <[email protected]> * spelling: infrastructure Signed-off-by: Josh Soref <[email protected]> * spelling: into Signed-off-by: Josh Soref <[email protected]> * spelling: intuitive Signed-off-by: Josh Soref <[email protected]> * spelling: its Signed-off-by: Josh Soref <[email protected]> * spelling: linked Signed-off-by: Josh Soref <[email protected]> * spelling: maintainers Signed-off-by: Josh Soref <[email protected]> * spelling: maintenance Signed-off-by: Josh Soref <[email protected]> * spelling: maximum Signed-off-by: Josh Soref <[email protected]> * spelling: negotiated Signed-off-by: Josh Soref <[email protected]> * spelling: networking Signed-off-by: Josh Soref <[email protected]> * spelling: nonexistent Signed-off-by: Josh Soref <[email protected]> * spelling: or Signed-off-by: Josh Soref <[email protected]> * spelling: overridden Signed-off-by: Josh Soref <[email protected]> * spelling: possible Signed-off-by: Josh Soref <[email protected]> * spelling: preexisting Signed-off-by: Josh Soref <[email protected]> * spelling: prominence Signed-off-by: Josh Soref <[email protected]> * spelling: protocol Signed-off-by: Josh Soref <[email protected]> * spelling: recommend Signed-off-by: Josh Soref <[email protected]> * spelling: referent Signed-off-by: Josh Soref <[email protected]> * spelling: release Signed-off-by: Josh Soref <[email protected]> * spelling: route-override Signed-off-by: Josh Soref <[email protected]> * spelling: stabilizing Signed-off-by: Josh Soref <[email protected]> * spelling: substituted Signed-off-by: Josh Soref <[email protected]> * spelling: targeting Signed-off-by: Josh Soref <[email protected]> * spelling: the Signed-off-by: Josh Soref <[email protected]> * spelling: validationutil Signed-off-by: Josh Soref <[email protected]> * spelling: which Signed-off-by: Josh Soref <[email protected]> * Reword simplify prototyping description Signed-off-by: Josh Soref <[email protected]> --------- Signed-off-by: Josh Soref <[email protected]>
kubernetes-sigs · Feb 12, 2025 · d8f2a20 · d8f2a20
1 parent 663b32c
commit d8f2a20
Show file tree

Hide file tree

Showing 80 changed files with 225 additions and 225 deletions.
diff --git a/.openvex/templates/README.md b/.openvex/templates/README.md
@@ -14,7 +14,7 @@ vexctl add --in-place main.openvex.json pkg:oci/test CVE-2014-1234567 fixed
 That will add a new VEX statement expressing that the impact of
 CVE-2014-1234567 is under investigation in the test image. When
 cutting a new release, for `pkg:oci/test` the new file will be
-incorporated to the relase's VEX data.
+incorporated to the release's VEX data.
 
 ## Read more about OpenVEX
 

diff --git a/CHANGELOG/0.x-CHANGELOG.md b/CHANGELOG/0.x-CHANGELOG.md
@@ -226,7 +226,7 @@ For more information refer to
 
 - Added the missing ReferenceGrant resource the kustomization.yaml for the
   standard channel (#2084, @howardjohn)
-- Webhook validation now ensures that BackendRefs can not be specified in the
+- Webhook validation now ensures that BackendRefs cannot be specified in the
   same HTTPRoute rule as a Redirect filter (#2161, @slayer321)
 - GRPCRoute: The default match has been removed as it was invalid (it only
   specified a type of "Exact" without a corresponding Service or Method). Note
@@ -407,7 +407,7 @@ For more information, refer to
 
 - Added the missing ReferenceGrant resource the kustomization.yaml for the
   standard channel (#2084, @howardjohn)
-- Webhook validation now ensures that BackendRefs can not be specified in the
+- Webhook validation now ensures that BackendRefs cannot be specified in the
   same HTTPRoute rule as a Redirect filter (#2161, @slayer321)
 
 # v0.7.1
@@ -1089,7 +1089,7 @@ In this release, we've made two release channels available, `experimental` and
 `standard`.
 
 The `experimental` channel contains all resources and fields, while `standard`
-contains only resources that mave moved to beta status.
+contains only resources that have moved to beta status.
 
 We've also added a way to flag particular fields within a resource as
 experimental, and any fields marked in this way are only present in the
@@ -1274,7 +1274,7 @@ In this release, we've made two release channels available, `experimental` and
 `standard`.
 
 The `experimental` channel contains all resources and fields, while `standard`
-contains only resources that mave moved to beta status.
+contains only resources that have moved to beta status.
 
 We've also added a way to flag particular fields within a resource as
 experimental, and any fields marked in this way are only present in the

diff --git a/CHANGELOG/1.0-CHANGELOG.md b/CHANGELOG/1.0-CHANGELOG.md
@@ -142,7 +142,7 @@ Of course there's a lot more in this release:
 - The condition reason `GatewayReasonAddressNotUsable` for `Programmed` has been
   added to deal with situations where a static address has been provided for a
   Gateway which is of a supported type, and is syntactically valid, but for some
-  reason it can not be used for this Gateway (e.g. the address is already in use
+  reason it cannot be used for this Gateway (e.g. the address is already in use
   on the network).
   (#2412 @shaneutt)
 
@@ -332,7 +332,7 @@ Of course there's a lot more in this release:
 - The condition reason `GatewayReasonAddressNotUsable` for `Programmed` has been
   added to deal with situations where a static address has been provided for a
   Gateway which is of a supported type, and is syntactically valid, but for some
-  reason it can not be used for this Gateway (e.g. the address is already in use
+  reason it cannot be used for this Gateway (e.g. the address is already in use
   on the network).
   (#2412 @shaneutt)
 

diff --git a/CHANGELOG/1.2-CHANGELOG.md b/CHANGELOG/1.2-CHANGELOG.md
@@ -864,7 +864,7 @@ The Experimental `supportedFeatures` field in GatewayClass `status` has changed
 from being a list of strings to being a list of objects/structs with a `name`
 field.
 
-This is to allow addding in extra information to each entry at a later date.
+This is to allow adding in extra information to each entry at a later date.
 
 Relevant PRs:
 

diff --git a/CHANGELOG/1.2-TEAM.md b/CHANGELOG/1.2-TEAM.md
@@ -7,7 +7,7 @@
 | BackendProtocol Support | @dprotaso |
 | HTTPRoute Retries | @mikemorris |
 | Percentage-based request mirroring | @jakebennert |
-| Backend TLS Config improvments | @mkosieradzki, @LiorLieberman |
+| Backend TLS Config improvements | @mkosieradzki, @LiorLieberman |
 | Named Route Rules | @guicassolato, @howardjohn |
 | Conformance Profiles and Reports | @mlavacca, @shaneutt, @xtineskim |
 | Gateway API Maintainers | @mlavacca, @robscott, @shaneutt, @youngnick  |
diff --git a/Makefile b/Makefile
@@ -92,16 +92,16 @@ test.crds-validation:
 conformance:
 	go test ${GO_TEST_FLAGS} -v ./conformance -run TestConformance -args ${CONFORMANCE_FLAGS}
 
-# Install CRD's and example resources to a pre-existing cluster.
+# Install CRD's and example resources to a preexisting cluster.
 .PHONY: install
 install: crd example
 
-# Install the CRD's to a pre-existing cluster.
+# Install the CRD's to a preexisting cluster.
 .PHONY: crd
 crd:
 	kubectl kustomize config/crd | kubectl apply -f -
 
-# Install the example resources to a pre-existing cluster.
+# Install the example resources to a preexisting cluster.
 .PHONY: example
 example:
 	hack/install-examples.sh

diff --git a/RELEASE.md b/RELEASE.md
@@ -70,7 +70,7 @@ The following steps must be done by one of the [Gateway API maintainers][gateway
 - Run the `make build-install-yaml` command which will generate install files in the `release/` directory.
   Attach these files to the GitHub release.
 - Update the `README.md` and `site-src/guides/index.md` files to point links and examples to the new release.
-- Update the implementation table path (`nav.Implementations.Comparison`) in the nav of `mkdocs.yml` to point to the latest release file (for example Implementation Comparison points to `implmenetation-table-v1.2.0.md`). Add the now past version under `Past Version Comparisons`, and edit the text blurb in `mkdocs-generate-conformance.py` to also reflect the added past version.
+- Update the implementation table path (`nav.Implementations.Comparison`) in the nav of `mkdocs.yml` to point to the latest release file (for example Implementation Comparison points to `implementation-table-v1.2.0.md`). Add the now past version under `Past Version Comparisons`, and edit the text blurb in `mkdocs-generate-conformance.py` to also reflect the added past version.
 
 #### For an **RC** release:
 - Update `pkg/consts/consts.go` with the new semver tag (like `v1.2.0-rc1`) and any updates to the API review URL.

diff --git a/apis/v1/grpcroute_types.go b/apis/v1/grpcroute_types.go
@@ -230,7 +230,7 @@ type GRPCRouteRule struct {
 	// Specifying the same filter multiple times is not supported unless explicitly
 	// indicated in the filter.
 	//
-	// If an implementation can not support a combination of filters, it must clearly
+	// If an implementation cannot support a combination of filters, it must clearly
 	// document that limitation. In cases where incompatible or unsupported
 	// filters are specified and cause the `Accepted` condition to be set to status
 	// `False`, implementations may use the `IncompatibleFilters` reason to specify

diff --git a/apis/v1/httproute_types.go b/apis/v1/httproute_types.go
@@ -210,7 +210,7 @@ type HTTPRouteRule struct {
 	// they are specified.
 	//
 	// Implementations MAY choose to implement this ordering strictly, rejecting
-	// any combination or order of filters that can not be supported. If implementations
+	// any combination or order of filters that cannot be supported. If implementations
 	// choose a strict interpretation of filter ordering, they MUST clearly document
 	// that behavior.
 	//
@@ -232,7 +232,7 @@ type HTTPRouteRule struct {
 	//
 	// All filters are expected to be compatible with each other except for the
 	// URLRewrite and RequestRedirect filters, which may not be combined. If an
-	// implementation can not support other combinations of filters, they must clearly
+	// implementation cannot support other combinations of filters, they must clearly
 	// document that limitation. In cases where incompatible or unsupported
 	// filters are specified and cause the `Accepted` condition to be set to status
 	// `False`, implementations may use the `IncompatibleFilters` reason to specify
@@ -487,7 +487,7 @@ const (
 	PathMatchExact PathMatchType = "Exact"
 
 	// Matches based on a URL path prefix split by `/`. Matching is
-	// case sensitive and done on a path element by element basis. A
+	// case-sensitive and done on a path element by element basis. A
 	// path element refers to the list of labels in the path split by
 	// the `/` separator. When specified, a trailing `/` is ignored.
 	//
@@ -596,7 +596,7 @@ type HTTPHeaderMatch struct {
 	Type *HeaderMatchType `json:"type,omitempty"`
 
 	// Name is the name of the HTTP Header to be matched. Name matching MUST be
-	// case insensitive. (See https://tools.ietf.org/html/rfc7230#section-3.2).
+	// case-insensitive. (See https://tools.ietf.org/html/rfc7230#section-3.2).
 	//
 	// If multiple entries specify equivalent header names, only the first
 	// entry with an equivalent name MUST be considered for a match. Subsequent
@@ -947,7 +947,7 @@ const (
 // HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
 type HTTPHeader struct {
 	// Name is the name of the HTTP Header to be matched. Name matching MUST be
-	// case insensitive. (See https://tools.ietf.org/html/rfc7230#section-3.2).
+	// case-insensitive. (See https://tools.ietf.org/html/rfc7230#section-3.2).
 	//
 	// If multiple entries specify equivalent header names, the first entry with
 	// an equivalent name MUST be considered for a match. Subsequent entries

diff --git a/apis/v1/shared_types.go b/apis/v1/shared_types.go
@@ -469,7 +469,7 @@ type RouteParentStatus struct {
 	// There are a number of cases where the "Accepted" condition may not be set
 	// due to lack of controller visibility, that includes when:
 	//
-	// * The Route refers to a non-existent parent.
+	// * The Route refers to a nonexistent parent.
 	// * The Route is of a type that the controller does not support.
 	// * The Route is in a namespace the controller does not have access to.
 	//
@@ -675,7 +675,7 @@ type GatewayController string
 // Invalid values include:
 //
 // * example~ - "~" is an invalid character
-// * example.com. - can not start or end with "."
+// * example.com. - cannot start or end with "."
 //
 // +kubebuilder:validation:MinLength=1
 // +kubebuilder:validation:MaxLength=253
@@ -705,7 +705,7 @@ type AnnotationValue string
 // Invalid values include:
 //
 // * example~ - "~" is an invalid character
-// * example.com. - can not start or end with "."
+// * example.com. - cannot start or end with "."
 //
 // +kubebuilder:validation:MinLength=1
 // +kubebuilder:validation:MaxLength=253
@@ -771,7 +771,7 @@ const (
 	// (see [RFC 5952](https://tools.ietf.org/html/rfc5952)).
 	//
 	// This type is intended for specific addresses. Address ranges are not
-	// supported (e.g. you can not use a CIDR range like 127.0.0.0/24 as an
+	// supported (e.g. you cannot use a CIDR range like 127.0.0.0/24 as an
 	// IPAddress).
 	//
 	// Support: Extended

diff --git a/apis/v1/util/validation/gatewayclass_test.go b/apis/v1/util/validation/gatewayclass_test.go
@@ -20,7 +20,7 @@ import (
 	"testing"
 
 	gatewayv1 "sigs.k8s.io/gateway-api/apis/v1"
-	validationtutils "sigs.k8s.io/gateway-api/apis/v1beta1/util/validation"
+	validationutil "sigs.k8s.io/gateway-api/apis/v1beta1/util/validation"
 )
 
 func TestIsControllerNameValid(t *testing.T) {
@@ -58,7 +58,7 @@ func TestIsControllerNameValid(t *testing.T) {
 
 	for _, tc := range testCases {
 		t.Run(tc.name, func(t *testing.T) {
-			isValid := validationtutils.IsControllerNameValid(tc.controllerName)
+			isValid := validationutil.IsControllerNameValid(tc.controllerName)
 			if isValid != tc.isvalid {
 				t.Errorf("Expected validity %t, got %t", tc.isvalid, isValid)
 			}

diff --git a/apis/v1alpha2/shared_types.go b/apis/v1alpha2/shared_types.go
@@ -313,7 +313,7 @@ type GatewayController = v1.GatewayController
 // Invalid values include:
 //
 // * example~ - "~" is an invalid character
-// * example.com. - can not start or end with "."
+// * example.com. - cannot start or end with "."
 //
 // +kubebuilder:validation:MinLength=1
 // +kubebuilder:validation:MaxLength=253
@@ -360,7 +360,7 @@ const (
 	// (see [RFC 5952](https://tools.ietf.org/html/rfc5952)).
 	//
 	// This type is intended for specific addresses. Address ranges are not
-	// supported (e.g. you can not use a CIDR range like 127.0.0.0/24 as an
+	// supported (e.g. you cannot use a CIDR range like 127.0.0.0/24 as an
 	// IPAddress).
 	//
 	// Support: Extended

diff --git a/apis/v1alpha2/tcproute_types.go b/apis/v1alpha2/tcproute_types.go
@@ -67,7 +67,7 @@ type TCPRouteRule struct {
 	Name *SectionName `json:"name,omitempty"`
 
 	// BackendRefs defines the backend(s) where matching requests should be
-	// sent. If unspecified or invalid (refers to a non-existent resource or a
+	// sent. If unspecified or invalid (refers to a nonexistent resource or a
 	// Service with no endpoints), the underlying implementation MUST actively
 	// reject connection attempts to this backend. Connection rejections must
 	// respect weight; if an invalid backend is requested to have 80% of

diff --git a/apis/v1alpha2/tlsroute_types.go b/apis/v1alpha2/tlsroute_types.go
@@ -108,7 +108,7 @@ type TLSRouteRule struct {
 	Name *SectionName `json:"name,omitempty"`
 
 	// BackendRefs defines the backend(s) where matching requests should be
-	// sent. If unspecified or invalid (refers to a non-existent resource or
+	// sent. If unspecified or invalid (refers to a nonexistent resource or
 	// a Service with no endpoints), the rule performs no forwarding; if no
 	// filters are specified that would result in a response being sent, the
 	// underlying implementation must actively reject request attempts to this

diff --git a/apis/v1alpha2/udproute_types.go b/apis/v1alpha2/udproute_types.go
@@ -67,7 +67,7 @@ type UDPRouteRule struct {
 	Name *SectionName `json:"name,omitempty"`
 
 	// BackendRefs defines the backend(s) where matching requests should be
-	// sent. If unspecified or invalid (refers to a non-existent resource or a
+	// sent. If unspecified or invalid (refers to a nonexistent resource or a
 	// Service with no endpoints), the underlying implementation MUST actively
 	// reject connection attempts to this backend. Packet drops must
 	// respect weight; if an invalid backend is requested to have 80% of

diff --git a/apis/v1alpha3/backendtlspolicy_types.go b/apis/v1alpha3/backendtlspolicy_types.go
@@ -112,7 +112,7 @@ type BackendTLSPolicyValidation struct {
 	//
 	// If CACertificateRefs is empty or unspecified, then WellKnownCACertificates must be
 	// specified. Only one of CACertificateRefs or WellKnownCACertificates may be specified,
-	// not both. If CACertifcateRefs is empty or unspecified, the configuration for
+	// not both. If CACertificateRefs is empty or unspecified, the configuration for
 	// WellKnownCACertificates MUST be honored instead if supported by the implementation.
 	//
 	// References to a resource in a different namespace are invalid for the

diff --git a/apis/v1beta1/shared_types.go b/apis/v1beta1/shared_types.go
@@ -313,7 +313,7 @@ type GatewayController = v1.GatewayController
 // Invalid values include:
 //
 // * example~ - "~" is an invalid character
-// * example.com. - can not start or end with "."
+// * example.com. - cannot start or end with "."
 //
 // +kubebuilder:validation:MinLength=1
 // +kubebuilder:validation:MaxLength=253
@@ -360,7 +360,7 @@ const (
 	// (see [RFC 5952](https://tools.ietf.org/html/rfc5952)).
 	//
 	// This type is intended for specific addresses. Address ranges are not
-	// supported (e.g. you can not use a CIDR range like 127.0.0.0/24 as an
+	// supported (e.g. you cannot use a CIDR range like 127.0.0.0/24 as an
 	// IPAddress).
 	//
 	// Support: Extended

diff --git a/apis/v1beta1/util/validation/gatewayclass_test.go b/apis/v1beta1/util/validation/gatewayclass_test.go
@@ -20,7 +20,7 @@ import (
 	"testing"
 
 	gatewayv1b1 "sigs.k8s.io/gateway-api/apis/v1beta1"
-	validationtutils "sigs.k8s.io/gateway-api/apis/v1beta1/util/validation"
+	validationutil "sigs.k8s.io/gateway-api/apis/v1beta1/util/validation"
 )
 
 func TestIsControllerNameValid(t *testing.T) {
@@ -58,7 +58,7 @@ func TestIsControllerNameValid(t *testing.T) {
 
 	for _, tc := range testCases {
 		t.Run(tc.name, func(t *testing.T) {
-			isValid := validationtutils.IsControllerNameValid(tc.controllerName)
+			isValid := validationutil.IsControllerNameValid(tc.controllerName)
 			if isValid != tc.isvalid {
 				t.Errorf("Expected validity %t, got %t", tc.isvalid, isValid)
 			}

diff --git a/config/crd/experimental/gateway.networking.k8s.io_backendtlspolicies.yaml b/config/crd/experimental/gateway.networking.k8s.io_backendtlspolicies.yaml