-
Notifications
You must be signed in to change notification settings - Fork 509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spelling (and make links accessible) #3615
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jsoref The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @jsoref. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|x|[v0.5.0](https://github.com/nginx/nginx-gateway-fabric/releases/tag/v0.5.0)|x|[link](./v1.1.0-report.yaml)| | ||
|x|[v0.5.0](https://github.com/nginx/nginx-gateway-fabric/releases/tag/v0.5.0)|x|[v0.5.0 report](./v0.5.0-report.yaml)| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is notable, the link was bad...
|x|[2.4.1](https://github.com/kumahq/kuma/releases/tag/2.4.1)|x|[link](./2.4.1-report.yaml)| | ||
|x|[2.4.1](https://github.com/kumahq/kuma/releases/tag/2.4.1)|x|[v2.4.1 report](./2.4.1-report.yaml)| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fwiw, I'd be inclined to change the Implementation version
to consistently use a v
prefix, it's probably 1/3 without the v, but I decided that was too far out of scope to do here. (As is, I half expect to split the accessibility changes into a distinct PR.)
|experimental|[v1.27.3](https://github.com/projectcontour/contour/releases/tag/v1.27.3)|x|[v1.27.3 report](./v1.27.3-report.yaml)| | ||
|experimental|[v1.27.4](https://github.com/projectcontour/contour/releases/tag/v1.27.4)|x|[v1.27.4 report](./experimental-v1.27.4-default-report.yaml)| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm aware that the file names sometimes hint at experimental
, and sometimes don't, but the things clearly don't think we care about that specific detail.
|standard|1.30.3-gke.1211000|gke-l7-global-external-managed|[v1.30.3 gxlb report](./standard-1.30.3-gxlb-report.yaml)| | ||
|standard|1.30.3-gke.1211000|gke-l7-regional-external-managed|[v1.30.3 rxlb report](./standard-1.30.3-rxlb-report.yaml)| | ||
|standard|1.30.3-gke.1211000|gke-l7-rilb|[v1.30.3 rilb report](./standard-1.30.3-rilb-report.yaml)| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've generally avoided adding any additional words beyond report
, but as these are actually distinct reports, it's really important for accessibility agents to be able to distinguish them.
@@ -4,7 +4,7 @@ | |||
|
|||
| API channel | Implementation version | Mode | Report | | |||
|--------------|-------------------------------------------------------------------------------------|-------------|-------------------------------------------------------| | |||
| standard | [v1.4.0](https://github.com/Kong/gateway-operator/releases/tag/v1.4.0) | expressions | [link](./standard-v1.4.0-expressions-report.yaml) | | |||
| standard | [v1.4.0](https://github.com/Kong/gateway-operator/releases/tag/v1.4.0) | expressions | [v1.4.0 expressions report](./standard-v1.4.0-expressions-report.yaml) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've generally avoided including things other than report
in the link title, but it feels like expressions
is significantly different from the default report.
@@ -195,7 +195,7 @@ other signal that makes the failure sufficiently clear to the requester without | |||
based on established security requirements. | |||
|
|||
All policy resources must include `TargetRefs` with the fields specified | |||
[here](https://github.com/kubernetes-sigs/gateway-api/blob/a33a934af9ec6997b34fd9b00d2ecd13d143e48b/apis/v1alpha2/policy_types.go#L24-L41). | |||
in [PolicyTargetReference](https://github.com/kubernetes-sigs/gateway-api/blob/a33a934af9ec6997b34fd9b00d2ecd13d143e48b/apis/v1alpha2/policy_types.go#L24-L41). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Picking names for things is hard, it's possible someone will have a better suggestion...
@@ -6,18 +6,18 @@ Gateway API has tooling to facilitate interacting with the resources. | |||
|
|||
Interested in seeing what your ingress resources will look like in Gateway API? `ingress2gateway` provides an easy manner to translate provider-specific resources to Gateway API resources. Managed by the Gateway API SIG-Network subproject. | |||
|
|||
Get started [here](https://github.com/kubernetes-sigs/ingress2gateway?tab=readme-ov-file#installation)! | |||
Get started with [kubernetes-sigs/ingress2gateway: installation](https://github.com/kubernetes-sigs/ingress2gateway?tab=readme-ov-file#installation)! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added : installation
to distinguish from the cases where links are to the general readme...
|
||
## Third-Party Tooling | ||
|
||
### `policy-machinery` | ||
|
||
Machinery for implementing Gateway API policies and policy controllers. | ||
|
||
Get started [here](https://github.com/Kuadrant/policy-machinery/tree/main) | ||
Get started with [Kuadrant/policy-machinery](https://github.com/Kuadrant/policy-machinery/tree/main) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally, this would be a link to https://github.com/Kuadrant/policy-machinery
or https://github.com/Kuadrant/policy-machinery/
, I'm not sure why someone included /tree/main
, but it's outside the scope of this PR.
@@ -251,7 +251,7 @@ In contrast, Gateway API specifies how to merge rules and resolve conflicts: | |||
* A Gateway implementation must merge the routing rules from all HTTPRoutes | |||
attached to a listener. | |||
* Conflicts must be handled as | |||
prescribed [here](/concepts/guidelines/#conflicts). For example, more specific | |||
prescribed in [API Design Guide: Conflicts](/guides/api-design/#conflicts). For example, more specific |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link appeared to redirect, so I've updated it, and then tried to pick a title based on the resolved page...
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
((See status definitions [here](/geps/overview/#gep-states).) | ||
(See [status definitions](/geps/overview/#gep-states).) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The stray (
is notable
((See status definitions [here](/geps/overview/#gep-states).) | ||
(See [status definitions](/geps/overview/#gep-states).) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
((See status definitions [here](/geps/overview/#gep-states).) | ||
(See [status definitions](/geps/overview/#gep-states).) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto
((See status definitions [here](/geps/overview/#gep-states).) | ||
(See [status definitions](/geps/overview/#gep-states).) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto
((See status definitions [here](/geps/overview/#gep-states).) | ||
(See [status definitions](/geps/overview/#gep-states).) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at https://github.com/jsoref/gateway-api/actions/runs/13315074066#summary-37186971636
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/gateway-api/actions/runs/13315074182#summary-37186971624
Which issue(s) this PR fixes:
The last series of commits address this accessibility complaint (see "Forbidden patterns 🙅 (6)" in https://github.com/jsoref/gateway-api/actions/runs/13315074066#summary-37186971636):
Do not use
(click) here
linksFor more information, see:
Does this PR introduce a user-facing change?: