Skip to content

Commit c9af91d

Browse files
shaneuttTim Bannister
andauthored
Apply suggestions from code review
Co-authored-by: Tim Bannister <[email protected]>
1 parent 2614af6 commit c9af91d

File tree

1 file changed

+3
-3
lines changed
  • content/en/blog/_posts/2023-10-31-Gateway-API-GA

1 file changed

+3
-3
lines changed

content/en/blog/_posts/2023-10-31-Gateway-API-GA/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ slug: gateway-api-ga
77

88
***Authors:*** Shane Utt (Kong), Nick Young (Isovalent), Rob Scott (Google)
99

10-
We are pleased to announce the v1.0 release of [Gateway
10+
On behalf of Kubernetes SIG Network, we are pleased to announce the v1.0 release of [Gateway
1111
API](https://gateway-api.sigs.k8s.io/)! This release marks a huge milestone for
1212
this project. Several key APIs are graduating to GA (generally available), while
1313
other significant features have been added to the Experimental channel.
@@ -112,7 +112,7 @@ We've also been working towards moving
112112
a built-in Kubernetes API that can be used for more than just Gateway API.
113113
Within Gateway API, we've used this resource to safely enable cross-namespace
114114
references, and that concept is now being adopted by other SIGs. The new version
115-
of this API will be owned by SIG-Auth and will likely include at least some
115+
of this API will be owned by SIG Auth and will likely include at least some
116116
modifications as it migrates to a built-in Kubernetes API.
117117

118118
### Gateway API at KubeCon + CloudNativeCon
@@ -142,7 +142,7 @@ you'd like to discuss or brainstorm any related topics. To get the latest
142142
updates on these sessions, join the `#sig-network-gateway-api` channel on
143143
[Kubernetes Slack](https://slack.kubernetes.io/).
144144

145-
## Get Involved
145+
## Get involved
146146

147147
We've only barely scratched the surface of what's in flight with Gateway API.
148148
There are lots of opportunities to get involved and help define the future of

0 commit comments

Comments
 (0)