kubernetes-sigs · k8s-ci-robot · May 10, 2024 · May 9, 2024 · May 10, 2024
diff --git a/site-src/api-types/backendtlspolicy.md b/site-src/api-types/backendtlspolicy.md
@@ -2,7 +2,8 @@
 
 ??? example "Experimental Channel in v1.0.0+"
 
-    The `BackendTLSPolicy` resource is Alpha and part of the Experimental Channel in `v1.0.0+`.
+    The `BackendTLSPolicy` resource is Alpha and has been part of
+    the Experimental Channel since `v1.0.0`.
 
 [BackendTLSPolicy][backendtlspolicy] is a Gateway API type for specifying the TLS configuration
 of the connection from the Gateway to a backend pod/s via the Service API object.

diff --git a/site-src/api-types/gateway.md b/site-src/api-types/gateway.md
@@ -2,7 +2,9 @@
 
 ??? success "Standard Channel in v0.5.0+"
 
-    The `Gateway` resource is Beta and part of the Standard Channel in `v0.5.0+`.
+    The `Gateway` resource is GA and has been part of the Standard Channel since
+    `v0.5.0`. For more information on release channels, refer to the [related
+    documentation](/concepts/versioning).
 
 A `Gateway` is 1:1 with the lifecycle of the configuration of infrastructure.
 When a user creates a `Gateway`, some load balancing infrastructure is

diff --git a/site-src/api-types/gatewayclass.md b/site-src/api-types/gatewayclass.md
@@ -1,8 +1,10 @@
 # GatewayClass
 
 ??? success "Standard Channel in v0.5.0+"
-
-    The `GatewayClass` resource is Beta and part of the Standard Channel in `v0.5.0+`.
+
+    The `GatewayClass` resource is GA and has been part of the Standard Channel since
+    `v0.5.0`. For more information on release channels, refer to the [related
+    documentation](/concepts/versioning).
 
 [GatewayClass][gatewayclass] is cluster-scoped resource defined by the
 infrastructure provider. This resource represents a class of Gateways that can

diff --git a/site-src/api-types/grpcroute.md b/site-src/api-types/grpcroute.md
@@ -1,9 +1,9 @@
 # GRPCRoute
 
-??? example "Experimental Channel in v0.6.0+"
+??? success "Standard Channel in v1.1.0+"
 
-    The `GRPCRoute` resource is Alpha and part of the Experimental Channel in
-    `v0.6.0+`. For more information on release channels, refer to the [related
+    The `GRPCRoute` resource is GA and has been part of the Stable Channel since
+    `v1.1.0`. For more information on release channels, refer to the [related
     documentation](/concepts/versioning).
 
 [GRPCRoute][grpcroute] is a Gateway API type for specifying routing behavior

diff --git a/site-src/api-types/httproute.md b/site-src/api-types/httproute.md
@@ -2,7 +2,9 @@
 
 ??? success "Standard Channel in v0.5.0+"
 
-    The `HTTPRoute` resource is Beta and part of the Standard Channel in `v0.5.0+`.
+    The `HTTPRoute` resource is GA and has been part of the Standard Channel since
+    `v0.5.0`. For more information on release channels, refer to the [related
+    documentation](/concepts/versioning).
 
 [HTTPRoute][httproute] is a Gateway API type for specifying routing behavior
 of HTTP requests from a Gateway listener to an API object, i.e. Service.
@@ -227,7 +229,7 @@ on `weight` and other fields.
 
 ??? example "Experimental Channel in v1.0.0+"
 
-    HTTPRoute timeouts are part of the Experimental Channel in `v1.0.0+`.
+    HTTPRoute timeouts have been part of the Experimental Channel since `v1.0.0`.
 
 HTTPRoute Rules include a `Timeouts` field. If unspecified, timeout behavior is implementation-specific.
 
@@ -252,7 +254,7 @@ Reference the [timeouts][timeouts] API documentation for additional details.
 
 ??? example "Experimental Channel in v1.0.0+"
 
-    This concept is part of the Experimental Channel in `v1.0.0+`.
+    This concept has been part of the Experimental Channel since `v1.0.0`.
 
 
 Some implementations may require the [backendRef][backendRef] to be labeled 

diff --git a/site-src/api-types/referencegrant.md b/site-src/api-types/referencegrant.md
@@ -2,7 +2,7 @@
 
 ??? success "Standard Channel in v0.6.0+"
 
-    The `ReferenceGrant` resource is Beta and part of the Standard Channel in `v0.6.0+`.
+    The `ReferenceGrant` resource is Beta and part of the Standard Channel since `v0.6.0`.
 
 !!! note
     This resource was originally named "ReferencePolicy". It was renamed

diff --git a/site-src/concepts/api-overview.md b/site-src/concepts/api-overview.md
@@ -32,8 +32,9 @@ the cluster.
 ### GatewayClass
 
 ??? success "Standard Channel in v0.5.0+"
-    The `GatewayClass` resource is GA and has been part of the Standard Channel in
-    `v0.5.0+`. For more information on release channels, refer to the [related
+
+    The `GatewayClass` resource is GA and has been part of the Standard Channel since
+    `v0.5.0`. For more information on release channels, refer to the [related
     documentation](/concepts/versioning).
 
 GatewayClass defines a set of Gateways that share a common configuration and
@@ -56,6 +57,7 @@ IngressClass object.
 ### Gateway
 
 ??? success "Standard Channel in v0.5.0+"
+
     The `Gateway` resource is GA and has been part of the Standard Channel since
     `v0.5.0`. For more information on release channels, refer to the [related
     documentation](/concepts/versioning).
@@ -95,8 +97,9 @@ types may be added to the API in future.
 #### HTTPRoute
 
 ??? success "Standard Channel in v0.5.0+"
-    The `HTTPRoute` resource is GA and has been part of the Standard Channel in
-    `v0.5.0+`. For more information on release channels, refer to the [related
+
+    The `HTTPRoute` resource is GA and has been part of the Standard Channel since
+    `v0.5.0`. For more information on release channels, refer to the [related
     documentation](/concepts/versioning).
 
 HTTPRoute is for multiplexing HTTP or terminated HTTPS connections. It's intended
@@ -109,7 +112,7 @@ modifying them in-flight.
 ??? example "Experimental Channel in v0.3.0+"
 
     The `TLSRoute` resource is Alpha and has been part of the Experimental
-    Channel since `v0.3.0+`. For more information on release channels, refer to
+    Channel since `v0.3.0`. For more information on release channels, refer to
     the [related documentation](/concepts/versioning).
 
 TLSRoute is for multiplexing TLS connections, discriminated via SNI. It's intended
@@ -135,11 +138,11 @@ is passed through to the backend.
 
 #### GRPCRoute
 
-??? example "Experimental Channel in v0.6.0+"
+??? success "Standard Channel in v1.1.0+"
 
-    The `GRPCRoute` resource is Alpha and has been part of the Experimental
-    Channel since `v0.6.0`. For more information on release channels, refer to
-    the [related documentation](/concepts/versioning).
+    The `GRPCRoute` resource is GA and has been part of the Stable Channel since
+    `v1.1.0`. For more information on release channels, refer to the [related
+    documentation](/concepts/versioning).
 
 GRPCRoute is for idiomatically routing gRPC traffic. Gateways supporting
 GRPCRoute are required to support HTTP/2 without an initial upgrade from HTTP/1,
@@ -213,6 +216,7 @@ The following is required for a Route to be attached to a Gateway:
 #### Referencing Gateways
 
 ??? example "Experimental Channel"
+
     The `Port` field described below is currently only included in the
     "Experimental" channel of Gateway API. For more information on release
     channels, refer to the [related documentation](/concepts/versioning/#adding-experimental-fields).

diff --git a/site-src/concepts/use-cases.md b/site-src/concepts/use-cases.md
@@ -33,7 +33,7 @@ separately.)
 ??? success "Standard Channel in v0.8.0+"
 
     The [north/south] use case is fully supported by the Standard Channel
-    in `v0.8.0+`.
+    since `v0.8.0`.
 
 Ana has created a microservice application which she wants to run in
 Kubernetes. Her application will be used by clients outside the cluster, and
@@ -91,7 +91,7 @@ rollouts](/guides/traffic-splitting)).
 ??? success "Standard Channel in v0.8.0+"
 
     The [north/south] use case is fully supported by the Standard Channel
-    in `v0.8.0+`.
+    since `v0.8.0`.
 
 This is remarkably similar to the [basic north/south use
 case](#basic-northsouth-use-case), but there are multiple application teams:

diff --git a/site-src/contributing/style-guide.md b/site-src/contributing/style-guide.md
@@ -21,13 +21,15 @@ feature is currently included in, and which version it was introduced to that
 channel. To accomplish that, we use admonitions that look like this:
 
 ??? success "Standard Channel in v0.5.0+"
+
     The `HTTPRoute` resource is GA and has been part of the Standard Channel
     since `v0.5.0`. For more information on release channels, refer to the
     [related documentation](/concepts/versioning).
 
-??? example "Experimental Channel in v0.6.0+"
-    The `GRPCRoute` resource is Alpha and has been part of the Experimental
-    Channel since `v0.6.0`. For more information on release channels, refer to
+??? example "Experimental Channel in v0.3.0+"
+
+    The `TLSRoute` resource is Alpha and has been part of the Experimental
+    Channel since `v0.3.0`. For more information on release channels, refer to
     the [related documentation](/concepts/versioning).
 
 ## Diagrams

diff --git a/site-src/guides/backend-protocol.md b/site-src/guides/backend-protocol.md
@@ -2,7 +2,7 @@
 
 ??? example "Experimental Channel in v1.0.0+"
 
-    This concept is part of the Experimental Channel in `v1.0.0+`.
+    This concept has been part of the Experimental Channel since `v1.0.0`.
 
 Not all implementations of Gateway API support automatic protocol selection. In some cases protocols are disabled without an explicit opt-in. 
 

diff --git a/site-src/index.md b/site-src/index.md
@@ -25,7 +25,7 @@ same configuration.
 
 ## Gateway API for Ingress <a name="for-ingress"></a>
 
-??? success "Standard in v0.5.0+"
+??? success "Standard Channel in v0.5.0+"
 
     Gateway, GatewayClass, and HTTPRoute have been part of the Standard Channel
     of Gateway API since v0.5.0 and are considered stable APIs. For more
@@ -54,10 +54,10 @@ resources), in the same cluster.
 
 ## Gateway API for Service Mesh (the [GAMMA initiative](/mesh/gamma)) <a name="for-service-mesh"></a>
 
-??? example "Standard in v1.2.0+"
+??? success "Standard Channel in v1.2.0+"
 
     The [GAMMA initiative](/mesh/gamma) work for supporting service mesh use cases
-    is part of the Standard Channel of Gateway API since v1.2.0 and are considered stable APIs. For more
+    is part of the Standard Channel since v1.2.0 and are considered stable APIs. For more
     information refer to our [versioning guide](/concepts/versioning).
 
 Things are a bit different when using Gateway API to manage a [service

diff --git a/site-src/mesh/index.md b/site-src/mesh/index.md
@@ -1,11 +1,11 @@
 
 # Gateway API for Service Mesh
 
-??? example "Experimental in v0.8.0+"
+??? success "Standard Channel in v1.2.0+"
 
-    Gateway API support for service mesh use cases is _experimental_ in `v0.8.0+`.
-    It is possible that it will change; we do not recommend it in production
-    at this point.
+    The [GAMMA initiative](/mesh/gamma) work for supporting service mesh use cases
+    is part of the Standard Channel since v1.2.0 and are considered stable APIs. For more
+    information refer to our [versioning guide](/concepts/versioning).
 
 The "[GAMMA initiative](/mesh/gamma)" refers to the group that is defining how
 Gateway API can be used for Service Mesh. To date, this group has been able to