diff --git a/site/content/en/latest/design/accesslog.md b/site/content/en/latest/design/accesslog.md
index cb72f05fe43..a229d5f6eff 100644
--- a/site/content/en/latest/design/accesslog.md
+++ b/site/content/en/latest/design/accesslog.md
@@ -6,17 +6,17 @@ title: "Observability: Accesslog"
 
 Envoy supports extensible accesslog to different sinks, File, gRPC etc. Envoy supports customizable access log formats using predefined fields as well as arbitrary HTTP request and response headers. Envoy supports several built-in access log filters and extension filters that are registered at runtime.
 
-Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since accesslog is not covered by `Core` or `Extended` APIs, EG should provide an easy to config access log formats and sinks per `EnvoyProxy`.
+Envoy Gateway leverages [Gateway API][] for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels][] for implementers such as Envoy Gateway to expose features. Since accesslog is not covered by `Core` or `Extended` APIs, EG should provide an easy to config access log formats and sinks per `EnvoyProxy`.
 
 ## Goals
 
 - Support send accesslog to `File` or `OpenTelemetry` backend
-- TODO: Support access log filters base on [CEL](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access_loggers/filters/cel/v3/cel.proto#extension-envoy-access-loggers-extension-filters-cel) expression
+- TODO: Support access log filters base on [CEL][] expression
 
 ## Non-Goals
 
 - Support non-CEL filters, e.g. `status_code_filter`, `response_flag_filter`
-- Support [HttpGrpcAccessLogConfig](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access_loggers/grpc/v3/als.proto#extensions-access-loggers-grpc-v3-httpgrpcaccesslogconfig) or [TcpGrpcAccessLogConfig](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access_loggers/grpc/v3/als.proto#extensions-access-loggers-grpc-v3-tcpgrpcaccesslogconfig)
+- Support [HttpGrpcAccessLogConfig][] or [TcpGrpcAccessLogConfig][]
 
 ## Use-Cases
 
@@ -235,3 +235,9 @@ spec:
                 resources:
                   k8s.cluster.name: "cluster-1"
 ```
+
+[Gateway API]: https://gateway-api.sigs.k8s.io/
+[support levels]: https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels
+[CEL]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access_loggers/filters/cel/v3/cel.proto#extension-envoy-access-loggers-extension-filters-cel
+[HttpGrpcAccessLogConfig]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access_loggers/grpc/v3/als.proto#extensions-access-loggers-grpc-v3-httpgrpcaccesslogconfig
+[TcpGrpcAccessLogConfig]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access_loggers/grpc/v3/als.proto#extensions-access-loggers-grpc-v3-tcpgrpcaccesslogconfig
diff --git a/site/content/en/latest/design/backend-traffic-policy.md b/site/content/en/latest/design/backend-traffic-policy.md
index 3cc0709b946..3dceec44409 100644
--- a/site/content/en/latest/design/backend-traffic-policy.md
+++ b/site/content/en/latest/design/backend-traffic-policy.md
@@ -29,14 +29,14 @@ then the configuration from the policy that is targeting the xRoute resource wil
 Here is an example highlighting how a user can configure this API.
 
 ```yaml
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -48,7 +48,7 @@ spec:
       protocol: HTTP
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: ipv4-route
@@ -70,7 +70,7 @@ spec:
             type: PathPrefix
             value: /
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: ipv6-route
diff --git a/site/content/en/latest/design/bootstrap.md b/site/content/en/latest/design/bootstrap.md
index 4475710ad5d..c0581347a24 100644
--- a/site/content/en/latest/design/bootstrap.md
+++ b/site/content/en/latest/design/bootstrap.md
@@ -53,7 +53,7 @@ Here is an example where a user inputs a `GatewayClass` and the CLI generates th
 
 ```
 cat <<EOF | egctl x translate --from gateway-api --to gateway-api -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -65,7 +65,7 @@ EOF
 ```
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -173,7 +173,7 @@ unmarshalled into the Bootstrap object as well as ensure the user can override c
 
 ```
 cat <<EOF | egctl x translate --from gateway-api --to gateway-api -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -275,7 +275,7 @@ EOF
 ```
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -376,6 +376,6 @@ spec:
 ```
 
 [Issue 31]: https://github.com/envoyproxy/gateway/issues/31
-[EnvoyProxy]: https://gateway.envoyproxy.io/latest/api/config_types.html#envoyproxy
-[GatewayClass]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.GatewayClass
-[parametersRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.ParametersReference 
+[EnvoyProxy]: ../../api/extension_types#envoyproxy
+[GatewayClass]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayClass
+[parametersRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.ParametersReference 
diff --git a/site/content/en/latest/design/client-traffic-policy.md b/site/content/en/latest/design/client-traffic-policy.md
index fab62b92078..9cd72d84575 100644
--- a/site/content/en/latest/design/client-traffic-policy.md
+++ b/site/content/en/latest/design/client-traffic-policy.md
@@ -26,14 +26,14 @@ to define configuration that affect the connection between the downstream client
 Here is an example highlighting how a user can configure this API.
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -45,7 +45,7 @@ spec:
       protocol: HTTP
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
diff --git a/site/content/en/latest/design/config-api.md b/site/content/en/latest/design/config-api.md
index 343718f2c6e..1c6f3057848 100644
--- a/site/content/en/latest/design/config-api.md
+++ b/site/content/en/latest/design/config-api.md
@@ -285,14 +285,14 @@ GatewayClass and Gateway resources define the data plane infrastructure. Note th
 running with the Kubernetes provider.
 
 ```yaml
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: example-class
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: example-gateway
@@ -312,7 +312,7 @@ The following example will configure the data plane to use a ClusterIP service i
 service:
 
 ```yaml
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: example-class
@@ -323,7 +323,7 @@ spec:
     group: gateway.envoyproxy.io
     kind: EnvoyProxy
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: example-gateway
@@ -346,8 +346,8 @@ spec:
 __Note:__ The NetworkPublishing API is currently undefined and is provided here for illustration purposes only.
 
 [issue_51]: https://github.com/envoyproxy/gateway/issues/51
-[design_doc]: https://github.com/envoyproxy/gateway/blob/main/docs/design/SYSTEM_DESIGN.md
+[design_doc]: ../system-design/
 [gw_api]: https://gateway-api.sigs.k8s.io/
-[gc]: https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.GatewayClass
+[gc]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayClass
 [cr]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
 [union]: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#unions
diff --git a/site/content/en/latest/design/eg-metrics.md b/site/content/en/latest/design/eg-metrics.md
index 60b93840852..0ca0e7229ec 100644
--- a/site/content/en/latest/design/eg-metrics.md
+++ b/site/content/en/latest/design/eg-metrics.md
@@ -37,13 +37,13 @@ The use-cases include:
 
 ### Standards
 
-Our metrics, will be built upon the [OpenTelemetry](https://opentelemetry.io/) standards. All metrics will be configured via the [OpenTelemetry SDK](https://opentelemetry.io/docs/specs/otel/metrics/sdk/), which offers neutral libraries that can be connected to various backends.
+Our metrics, will be built upon the [OpenTelemetry][] standards. All metrics will be configured via the [OpenTelemetry SDK][], which offers neutral libraries that can be connected to various backends.
 
 This approach allows the Envoy Gateway code to concentrate on the crucial aspect - generating the metrics - and delegate all other tasks to systems designed for telemetry ingestion.
 
 ### Attributes
 
-OpenTelemetry defines a set of [Semantic Conventions](https://opentelemetry.io/docs/concepts/semantic-conventions/), including [Kubernetes specific ones](https://opentelemetry.io/docs/specs/otel/resource/semantic_conventions/k8s/).
+OpenTelemetry defines a set of [Semantic Conventions][], including [Kubernetes specific ones][].
 
 These attributes can be expressed in logs (as keys of structured logs), traces (as attributes), and metrics (as labels).
 
@@ -53,7 +53,7 @@ We aim to use attributes consistently where applicable. Where possible, these sh
 
 Envoy Gateway supports both **PULL/PUSH** mode metrics, with Metrics exported via Prometheus by default.
 
-Additionally, Envoy Gateway can export metrics using both the [OTEL gRPC metrics exporter](https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/#general) and [OTEL HTTP metrics exporter](https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/#general), which pushes metrics by grpc/http to a remote OTEL collector.
+Additionally, Envoy Gateway can export metrics using both the [OTEL gRPC metrics exporter][] and [OTEL HTTP metrics exporter][], which pushes metrics by grpc/http to a remote OTEL collector.
 
 Users can extend these in two ways:
 
@@ -84,7 +84,7 @@ I propose the following:
 
 Metrics offer the greatest potential for providing guarantees. They often directly influence alerts and dashboards, making changes highly impactful. This contrasts with traces and logs, which are often used for ad-hoc analysis, where minor changes to information can be easily understood by a human.
 
-Moreover, there is precedent for this: [Kubernetes Metrics Lifecycle](https://kubernetes.io/docs/concepts/cluster-administration/system-metrics/#metric-lifecycle) has well-defined processes, and Envoy Gateway's dataplane (Envoy Proxy) metrics are de facto stable.
+Moreover, there is precedent for this: [Kubernetes Metrics Lifecycle][] has well-defined processes, and Envoy Gateway's dataplane (Envoy Proxy) metrics are de facto stable.
 
 Currently, all Envoy Gateway metrics lack defined stability. I suggest we categorize all existing metrics as either:
 
@@ -223,3 +223,11 @@ telemetry:
           port: 4318
           protocol: http
 ```
+
+[OpenTelemetry]: https://opentelemetry.io/
+[OpenTelemetry SDK]: https://opentelemetry.io/docs/specs/otel/metrics/sdk/
+[Semantic Conventions]: https://opentelemetry.io/docs/concepts/semantic-conventions/
+[Kubernetes specific ones]: https://opentelemetry.io/docs/specs/otel/resource/semantic_conventions/k8s/
+[OTEL gRPC metrics exporter]: https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/#general
+[OTEL HTTP metrics exporter]: https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/#general
+[Kubernetes Metrics Lifecycle]: https://kubernetes.io/docs/concepts/cluster-administration/system-metrics/#metric-lifecycle
diff --git a/site/content/en/latest/design/envoy-patch-policy.md b/site/content/en/latest/design/envoy-patch-policy.md
index d34937d05ef..47422b0baa3 100644
--- a/site/content/en/latest/design/envoy-patch-policy.md
+++ b/site/content/en/latest/design/envoy-patch-policy.md
@@ -32,14 +32,14 @@ resource objects.
 Here is an example highlighting how a user can configure global ratelimiting using an external rate limit service using this API.
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -51,7 +51,7 @@ spec:
       protocol: HTTP
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -167,10 +167,10 @@ patches will work.
 [Gateway API]: https://gateway-api.sigs.k8s.io/
 [Kubernetes]: https://kubernetes.io/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch/
 [Kustomize]: https://github.com/kubernetes-sigs/kustomize/blob/master/examples/jsonpatch.md
-[Extension APIs]: https://gateway.envoyproxy.io/latest/api/extension_types.html
-[RateLimit]: https://gateway.envoyproxy.io/latest/user/rate-limit.html
-[EnvoyGateway]: https://gateway.envoyproxy.io/latest/api/config_types.html#envoygateway
-[Extending the Control Plane]: https://gateway.envoyproxy.io/latest/design/extending-envoy-gateway.html
+[Extension APIs]: ../../api/extension_types/
+[RateLimit]: ../../user/rate-limit/
+[EnvoyGateway]: ../../api/extension_types/#envoygateway
+[Extending the Control Plane]: ../extending-envoy-gateway
 [EnvoyFilter]: https://istio.io/latest/docs/reference/config/networking/envoy-filter
-[egctl x translate]: https://gateway.envoyproxy.io/latest/user/egctl.html#egctl-experimental-translate
-[Bootstrap configuration using EnvoyProxy API]: https://gateway.envoyproxy.io/latest/user/customize-envoyproxy.html#customize-envoyproxy-bootstrap-config
+[egctl x translate]: ../../user/egctl#egctl-experimental-translate
+[Bootstrap configuration using EnvoyProxy API]: ../../user/customize-envoyproxy#customize-envoyproxy-bootstrap-config
diff --git a/site/content/en/latest/design/extending-envoy-gateway.md b/site/content/en/latest/design/extending-envoy-gateway.md
index d4f36cc7a4a..cb2127f3869 100644
--- a/site/content/en/latest/design/extending-envoy-gateway.md
+++ b/site/content/en/latest/design/extending-envoy-gateway.md
@@ -110,7 +110,7 @@ spec:
   ...
 
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -140,7 +140,7 @@ if they specify an `group` that matches the `group` of an `ExtensionRef` filter.
 modified configuration. If an extension is not registered or if the registered extension does not specify support for the `group` of an `ExtensionRef` filter then Envoy Gateway will treat it as an unknown resource
 and provide an error to the user.
 
-**Note:** Currently (as of [v1beta1][]) Gateway API does not provide a means to specify the namespace or version of an object referenced as an `ExtensionRef`. The extension mechanism will assume that
+**Note:** Currently (as of [v1][]) Gateway API does not provide a means to specify the namespace or version of an object referenced as an `ExtensionRef`. The extension mechanism will assume that
 the namespace of any `ExtensionRef` is the same as the namespace of the `HTTPRoute` or `GRPCRoute` it is attached to rather than treating the `name` field of an `ExtensionRef` as a `name.namespace` string.
 If Gateway API adds support for these fields then the design of the Envoy Gateway extensions will be updated to support them.
 
@@ -305,21 +305,21 @@ whenever Envoy Gateway creates an instance of Envoy Proxy. An extension develope
 Extending Envoy Gateway by using an external extension server which makes use of hook points in Envoy Gateway does comes with a few trade-offs. One known trade-off is the impact of the time that it takes for the hook calls to be executed. Since an extension would make use of hook points in Envoy Gateway that use gRPC for communication, the time it takes to perform these requests could become a concern for some extension developers. One way to minimize the request time of the hook calls is to load the extension server as a sidecar to Envoy Gateway to minimize the impact of networking on the hook calls.
 
 [official goals]: https://github.com/envoyproxy/gateway/blob/main/GOALS.md#extensibility
-[ExtensionRef filters]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.LocalObjectReference
-[ExtensionRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.LocalObjectReference
-[ExtensionRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.LocalObjectReference
-[backendRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.BackendObjectReference
+[ExtensionRef filters]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.LocalObjectReference
+[ExtensionRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.LocalObjectReference
+[ExtensionRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.LocalObjectReference
+[backendRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendObjectReference
 [Gateway API Policy attachments]: https://gateway-api.sigs.k8s.io/references/policy-attachment/?h=policy
 [Policy Attachments]: https://gateway-api.sigs.k8s.io/references/policy-attachment/?h=policy
 [policyAttachments]: https://gateway-api.sigs.k8s.io/references/policy-attachment/?h=policy
 [Envoy]: https://www.envoyproxy.io/
 [Envoy specific configuration (xDS)]: https://www.envoyproxy.io/docs/envoy/v1.25.1/configuration/configuration
-[v1beta1]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1
-[rate limiting]: https://gateway.envoyproxy.io/v0.3.0/user/rate-limit.html
-[authentication]: https://gateway.envoyproxy.io/v0.3.0/user/authn.html
-[HTTPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRoute
-[GRPCRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
-[EnvoyGateway config]: https://gateway.envoyproxy.io/v0.3.0/api/config_types.html#envoygateway
+[v1]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1
+[rate limiting]: ../../user/rate-limit/
+[authentication]: ../../user/jwt-authentication/
+[HTTPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRoute
+[GRPCRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
+[EnvoyGateway config]: ../../api/extension_types/#envoygateway
 [controller-runtime]: https://github.com/kubernetes-sigs/controller-runtime
 [Unstructured]: https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured
 [Listener]: https://www.envoyproxy.io/docs/envoy/v1.23.0/api-v3/config/listener/v3/listener.proto#config-listener-v3-listener
diff --git a/site/content/en/latest/design/gatewayapi-translator.md b/site/content/en/latest/design/gatewayapi-translator.md
index b83ed82588d..a086b80bfee 100644
--- a/site/content/en/latest/design/gatewayapi-translator.md
+++ b/site/content/en/latest/design/gatewayapi-translator.md
@@ -38,7 +38,7 @@ __Note:__ Envoy Gateway does not collapse listeners across multiple Gateways.
 
 ```yaml
 kind: Gateway
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: gateway-1
   namespace: envoy-gateway
@@ -65,7 +65,7 @@ spec:
 
 ```yaml
 kind: Gateway
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: gateway-1
   namespace: envoy-gateway
@@ -91,7 +91,7 @@ spec:
 
 ```yaml
 kind: Gateway
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: gateway-1
   namespace: envoy-gateway
@@ -118,7 +118,7 @@ spec:
 
 ```yaml
 kind: Gateway
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: gateway-1
   namespace: envoy-gateway
@@ -250,4 +250,4 @@ type RouteContext interface {
 }
 ```
 
-[message bus]: watching.md
+[message bus]: ../watching/
diff --git a/site/content/en/latest/design/metrics.md b/site/content/en/latest/design/metrics.md
index c87b23ad4e5..78b05eea98e 100644
--- a/site/content/en/latest/design/metrics.md
+++ b/site/content/en/latest/design/metrics.md
@@ -6,11 +6,11 @@ title: "Observability: Metrics"
 
 Envoy provide robust platform for metrics, Envoy support three different kinds of stats: counter, gauges, histograms.
 
-Envoy enables prometheus format output via the `/stats/prometheus` [admin endpoint](https://www.envoyproxy.io/docs/envoy/latest/operations/admin).
+Envoy enables prometheus format output via the `/stats/prometheus` [admin endpoint][].
 
-Envoy support different kinds of sinks, but EG will only support [Open Telemetry sink](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/stat_sinks/open_telemetry/v3/open_telemetry.proto).
+Envoy support different kinds of sinks, but EG will only support [Open Telemetry sink][].
 
-Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since metrics is not covered by `Core` or `Extended` APIs, EG should provide an easy to config metrics per `EnvoyProxy`.
+Envoy Gateway leverages [Gateway API][] for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels][] for implementers such as Envoy Gateway to expose features. Since metrics is not covered by `Core` or `Extended` APIs, EG should provide an easy to config metrics per `EnvoyProxy`.
 
 ## Goals
 
@@ -78,7 +78,7 @@ type PrometheusProvider struct {
 
 ### Example
 
-1. The following is an example to disable prometheus metric.
+- The following is an example to disable prometheus metric.
 
 ```yaml mdox-exec="sed '1,12d' examples/kubernetes/metric/disable-prometheus.yaml"
 apiVersion: gateway.envoyproxy.io/v1alpha1
@@ -93,7 +93,7 @@ spec:
         disable: true
 ```
 
-1. The following is an example to send metric via Open Telemetry sink.
+- The following is an example to send metric via Open Telemetry sink.
 
 ```yaml mdox-exec="sed '1,12d' examples/kubernetes/metric/otel-sink.yaml"
 apiVersion: gateway.envoyproxy.io/v1alpha1
@@ -110,3 +110,8 @@ spec:
             host: otel-collector.monitoring.svc.cluster.local
             port: 4317
 ```
+
+[admin endpoint]: https://www.envoyproxy.io/docs/envoy/latest/operations/admin
+[Open Telemetry sink]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/stat_sinks/open_telemetry/v3/open_telemetry.proto
+[Gateway API]: https://gateway-api.sigs.k8s.io/
+[support levels]: https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels
diff --git a/site/content/en/latest/design/pprof.md b/site/content/en/latest/design/pprof.md
index e2dd3082b26..40d75ea8f83 100644
--- a/site/content/en/latest/design/pprof.md
+++ b/site/content/en/latest/design/pprof.md
@@ -42,7 +42,7 @@ PROFILE	| FUNCTION
 
 Here is an example configuration to open admin server and enable Pprof:
 
-``` yaml
+```yaml
 apiVersion: gateway.envoyproxy.io/v1alpha1
 gateway:
     controllerName: "gateway.envoyproxy.io/gatewayclass-controller"
diff --git a/site/content/en/latest/design/rate-limit.md b/site/content/en/latest/design/rate-limit.md
index e35d44c8239..315f9b7138e 100644
--- a/site/content/en/latest/design/rate-limit.md
+++ b/site/content/en/latest/design/rate-limit.md
@@ -7,7 +7,7 @@ title: "Rate Limit Design"
 Rate limit is a feature that allows the user to limit the number of incoming requests
 to a predefined value based on attributes within the traffic flow.
 
-Here are some reasons why a user may want to implements Rate limits
+Here are some reasons why a user may want to implement Rate limits
 
 * To prevent malicious activity such as DDoS attacks.
 * To prevent applications and its resources (such as a database) from getting overloaded.
@@ -49,7 +49,7 @@ spec:
         requests: 10
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -93,7 +93,7 @@ spec:
         requests: 1000
         unit: Second
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -142,7 +142,7 @@ spec:
         requests: 10
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -187,7 +187,7 @@ spec:
         requests: 10
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -253,7 +253,7 @@ spec:
         requests: 10
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -302,7 +302,6 @@ spec:
         requests: 100
         unit: Second
 ---
-
 apiVersion: gateway.envoyproxy.io/v1alpha1
 kind: RateLimitFilter
 metadata:
@@ -319,7 +318,7 @@ spec:
         requests: 1000
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -401,12 +400,12 @@ attribute such as [IP subnet][] in the future that are not relevant in the [HTTP
   * A Status field within the RateLimitFilter API will be added to reflect whether the specific configuration was programmed correctly in these multiple locations or not.
 
 [PolicyAttachment]: https://gateway-api.sigs.k8s.io/references/policy-attachment/
-[HTTPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRoute
-[HTTPRouteRule]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteRule
-[HTTPBackendRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1.HTTPBackendRef
-[matches]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteMatch
-[rule]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteMatch
-[extensionRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilterType
+[HTTPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRoute
+[HTTPRouteRule]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule
+[HTTPBackendRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef
+[matches]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch
+[rule]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch
+[extensionRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteFilterType
 [IP subnet]: https://en.wikipedia.org/wiki/Subnetwork
 [Actions]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-msg-config-route-v3-ratelimit-action
 [descriptors]: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/rate_limit_filter.html?highlight=descriptor#example-1
@@ -415,5 +414,5 @@ attribute such as [IP subnet][] in the future that are not relevant in the [HTTP
 [rate limit filter]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/ratelimit/v3/rate_limit.proto#envoy-v3-api-msg-extensions-filters-http-ratelimit-v3-ratelimit 
 [rate limit service]: https://www.envoyproxy.io/docs/envoy/latest/configuration/other_features/rate_limit#config-rate-limit-service
 [reference implementation]: https://github.com/envoyproxy/ratelimit
-[EnvoyGateway]: https://github.com/envoyproxy/gateway/blob/main/api/config/v1alpha1/envoygateway_types.go
+[EnvoyGateway]: https://github.com/envoyproxy/gateway/blob/main/api/v1alpha1/envoygateway_types.go
 [rate limit service configuration]: https://github.com/envoyproxy/ratelimit#configuration
diff --git a/site/content/en/latest/design/security-policy.md b/site/content/en/latest/design/security-policy.md
index b7413b92ad0..b39165feb03 100644
--- a/site/content/en/latest/design/security-policy.md
+++ b/site/content/en/latest/design/security-policy.md
@@ -16,20 +16,20 @@ on the traffic entering the gateway.
 
 ## Implementation
 `SecurityPolicy` is a [Policy Attachment][] type API that can be used to extend [Gateway API][]
-to define authentication and authorization rules..
+to define authentication and authorization rules.
 
 ### Example
 Here is an example highlighting how a user can configure this API.
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -41,7 +41,7 @@ spec:
       protocol: HTTPS
       port: 443
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -109,7 +109,7 @@ entire Gateway then
 this route's parentRef which in turn overrides a Policy targeting the Gateway the listener/section is a part of. 
 
 ## Alternatives
-* The project can indefintely wait for these configuration parameters to be part of the [Gateway API].
+* The project can indefinitely wait for these configuration parameters to be part of the [Gateway API][].
 
 [Policy Attachment]: https://gateway-api.sigs.k8s.io/references/policy-attachment 
 [Gateway API]: https://gateway-api.sigs.k8s.io/
diff --git a/site/content/en/latest/design/system-design.md b/site/content/en/latest/design/system-design.md
index 16123948ee7..c5375247534 100644
--- a/site/content/en/latest/design/system-design.md
+++ b/site/content/en/latest/design/system-design.md
@@ -159,16 +159,16 @@ The draft for this document is [here][draft_design].
 [grl]: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/other_features/global_rate_limiting
 [rls]: https://github.com/envoyproxy/ratelimit
 [rlf]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/ratelimit/v3/rate_limit.proto#envoy-v3-api-msg-extensions-filters-http-ratelimit-v3-ratelimit
-[crf]: https://gateway-api.sigs.k8s.io/v1alpha2/api-types/httproute/#filters-optional
+[crf]: https://gateway-api.sigs.k8s.io/api-types/httproute/#filters-optional
 [gwapi_conflicts]: https://gateway-api.sigs.k8s.io/concepts/guidelines/#conflicts
 [listener]: https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/listeners#config-listeners
 [route]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-msg-config-route-v3-route
-[be_ref]: https://gateway-api.sigs.k8s.io/v1alpha2/api-types/httproute/#backendrefs-optional
+[be_ref]: https://gateway-api.sigs.k8s.io/api-types/httproute/#backendrefs-optional
 [cluster]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/cluster/v3/cluster.proto#config-cluster-v3-cluster
 [draft_design]: https://docs.google.com/document/d/1riyTPPYuvNzIhBdrAX8dpfxTmcobWZDSYTTB5NeybuY/edit
 [cr]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
-[be]: https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.BackendObjectReference
+[be]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendObjectReference
 [svc]: https://kubernetes.io/docs/concepts/services-networking/service/
-[ wcd ]: ./watching.md
+[wcd]: ../watching
 [Issue #37]: https://github.com/envoyproxy/gateway/issues/37
-[roadmap]: roadmap.md
+[roadmap]: ../../contributions/roadmap/
diff --git a/site/content/en/latest/design/tcp-udp-design.md b/site/content/en/latest/design/tcp-udp-design.md
index f517e24feda..8dc29830164 100644
--- a/site/content/en/latest/design/tcp-udp-design.md
+++ b/site/content/en/latest/design/tcp-udp-design.md
@@ -6,8 +6,8 @@ Even though most of the use cases for Envoy Gateway are at Layer-7, Envoy Gatewa
 and UDP traffic. This document will explore the options we have when operating Envoy Gateway at Layer-4 and explain the 
 design decision.
 
-Envoy can work as a non-transparent proxy or a transparent proxy for both [TCP](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/other_features/ip_transparency#arch-overview-ip-transparency-original-src-listener)
- and [UDP](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/udp/udp_proxy/v3/udp_proxy.proto#envoy-v3-api-msg-extensions-filters-udp-udp-proxy-v3-udpproxyconfig)
+Envoy can work as a non-transparent proxy or a transparent proxy for both [TCP][]
+ and [UDP][]
 , so ideally, Envoy Gateway should also be able to work in these two modes:
 
 ## Non-transparent Proxy Mode
@@ -47,3 +47,6 @@ In a Kubernetes cluster, Envoy Gateway will have to carefully cooperate with CNI
 
 The implementation will only support proxying in non-transparent mode i.e. the backend will see the source IP and 
 port of the deployed Envoy instance instead of the client.
+
+[TCP]: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/other_features/ip_transparency#arch-overview-ip-transparency-original-src-listener
+[UDP]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/udp/udp_proxy/v3/udp_proxy.proto#envoy-v3-api-msg-extensions-filters-udp-udp-proxy-v3-udpproxyconfig
diff --git a/site/content/en/latest/design/tracing.md b/site/content/en/latest/design/tracing.md
index 66f9454bc32..a2790690fa6 100644
--- a/site/content/en/latest/design/tracing.md
+++ b/site/content/en/latest/design/tracing.md
@@ -4,11 +4,11 @@ title: "Observability: Tracing"
 
 ## Overview
 
-Envoy supports extensible tracing to different sinks, Zipkin, OpenTelemetry etc. Overview of Envoy tracing can be found [here](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/observability/tracing).
+Envoy supports extensible tracing to different sinks, Zipkin, OpenTelemetry etc. Overview of Envoy tracing can be found [here][tracing].
 
-Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since tracing is not covered by `Core` or `Extended` APIs, EG should provide an easy to config tracing per `EnvoyProxy`.
+Envoy Gateway leverages [Gateway API][] for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels][] for implementers such as Envoy Gateway to expose features. Since tracing is not covered by `Core` or `Extended` APIs, EG should provide an easy to config tracing per `EnvoyProxy`.
 
-Only OpenTelemetry sink can be configured currently, you can use [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) to export to other tracing backends.
+Only OpenTelemetry sink can be configured currently, you can use [OpenTelemetry Collector][] to export to other tracing backends.
 
 ## Goals
 
@@ -159,3 +159,8 @@ spec:
             name: X-Header-1
             defaultValue: "-"
 ```
+
+[tracing]: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/observability/tracing
+[Gateway API]: https://gateway-api.sigs.k8s.io/
+[support levels]: https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels
+[OpenTelemetry Collector]: https://opentelemetry.io/docs/collector/
diff --git a/site/content/en/latest/user/cors.md b/site/content/en/latest/user/cors.md
index f05cbf6ec18..d8867ccb8d2 100644
--- a/site/content/en/latest/user/cors.md
+++ b/site/content/en/latest/user/cors.md
@@ -114,7 +114,7 @@ kubectl delete securitypolicy/cors-example
 
 Checkout the [Developer Guide](../../contributions/develop/) to get involved in the project.
 
-[SecurityPolicy]: https://gateway.envoyproxy.io/latest/design/security-policy
+[SecurityPolicy]: ../../design/security-policy/
 [cors]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
 [Gateway]: https://gateway-api.sigs.k8s.io/api-types/gateway
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute
diff --git a/site/content/en/latest/user/customize-envoyproxy.md b/site/content/en/latest/user/customize-envoyproxy.md
index 278989d53b5..a6d93810988 100644
--- a/site/content/en/latest/user/customize-envoyproxy.md
+++ b/site/content/en/latest/user/customize-envoyproxy.md
@@ -17,7 +17,7 @@ First, you need to add ParametersRef in GatewayClass, and refer to EnvoyProxy Co
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -318,5 +318,5 @@ Any errors in the configuration will be surfaced as status within the `GatewayCl
 You can also validate this configuration using [egctl translate][].
 
 [Gateway API documentation]: https://gateway-api.sigs.k8s.io/
-[EnvoyProxy]: https://gateway.envoyproxy.io/latest/api/config_types.html#envoyproxy 
-[egctl translate]: https://gateway.envoyproxy.io/latest/user/egctl/#validating-gateway-api-configuration
+[EnvoyProxy]: ../../api/extension_types#envoyproxy 
+[egctl translate]: ../egctl/#validating-gateway-api-configuration
diff --git a/site/content/en/latest/user/deployment-mode.md b/site/content/en/latest/user/deployment-mode.md
index 08ea5febc5c..88428796359 100644
--- a/site/content/en/latest/user/deployment-mode.md
+++ b/site/content/en/latest/user/deployment-mode.md
@@ -5,10 +5,10 @@ title: "Deployment Mode"
 
 ### One GatewayClass per Envoy Gateway
 
-* Envoy Gateway can accept a single [GatewayClass](https://gateway-api.sigs.k8s.io/api-types/gatewayclass/)
+* Envoy Gateway can accept a single [GatewayClass][]
 resource. If you've instantiated multiple GatewayClasses, we recommend running multiple Envoy Gateway controllers
 in different namespaces, linking a GatewayClass to each of them. 
-* Support for accepting multiple GatewayClass is being tracked [here](https://github.com/envoyproxy/gateway/issues/1231).
+* Support for accepting multiple GatewayClass is being tracked [here][issue1231].
 
 ### Supported Modes
 
@@ -18,7 +18,7 @@ in different namespaces, linking a GatewayClass to each of them.
 and **creates** managed data plane resources such as EnvoyProxy `Deployment` in the **namespace where Envoy Gateway is running**.
 * Envoy Gateway also supports **Namespaced** deployment mode, you can watch resources in the specific namespaces by assigning
 `EnvoyGateway.provider.kubernetes.watch.namespaces` and **creates** managed data plane resources in the **namespace where Envoy Gateway is running**.
-* Support for alternate deployment modes is being tracked [here](https://github.com/envoyproxy/gateway/issues/1117).
+* Support for alternate deployment modes is being tracked [here][issue1117].
 
 ### Multi-tenancy
 
@@ -38,14 +38,14 @@ Lets create a `GatewayClass` linked to the marketing team's Envoy Gateway contro
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg-marketing
 spec:
   controllerName: gateway.envoyproxy.io/marketing-gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -113,7 +113,7 @@ spec:
                 fieldRef:
                   fieldPath: metadata.namespace
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -211,14 +211,14 @@ Lets create a `GatewayClass` linked to the product team's Envoy Gateway controll
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg-product
 spec:
   controllerName: gateway.envoyproxy.io/product-gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -286,7 +286,7 @@ spec:
                 fieldRef:
                   fieldPath: metadata.namespace
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -398,3 +398,7 @@ Handling connection for 8889
 <
 * Connection #0 to host localhost left intact
 ```
+
+[GatewayClass]: https://gateway-api.sigs.k8s.io/api-types/gatewayclass/
+[issue1231]: https://github.com/envoyproxy/gateway/issues/1231
+[issue1117]: https://github.com/envoyproxy/gateway/issues/1117
diff --git a/site/content/en/latest/user/egctl.md b/site/content/en/latest/user/egctl.md
index 949c953f15f..739a137d131 100644
--- a/site/content/en/latest/user/egctl.md
+++ b/site/content/en/latest/user/egctl.md
@@ -15,14 +15,14 @@ resources.
 
 ```shell
 cat <<EOF | egctl x translate --from gateway-api --to xds -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -58,7 +58,7 @@ spec:
   selector:
     app: backend
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -259,14 +259,14 @@ You can also use the `--type`/`-t` flag to retrieve specific output types. In th
 
 ```shell
 cat <<EOF | egctl x translate --from gateway-api --to xds -t route -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -302,7 +302,7 @@ spec:
   selector:
     app: backend
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -353,14 +353,14 @@ For example, this will provide the similar result as the above:
 
 ```shell
 cat <<EOF | egctl x translate --add-missing-resources --from gateway-api --to gateway-api -t route -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -372,7 +372,7 @@ spec:
       protocol: HTTP
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -396,7 +396,7 @@ spec:
 EOF
 ```
 
-You can see the output contains a [EnvoyProxy](https://gateway.envoyproxy.io/latest/api/config_types.html#envoyproxy) resource that
+You can see the output contains a [EnvoyProxy][] resource that
 can be used as a starting point to modify the xDS bootstrap resource for the managed Envoy Proxy fleet.
 
 ```yaml
@@ -572,14 +572,14 @@ Sometimes you might find that egctl doesn't provide an expected result. For exam
 
 ```shell
 cat <<EOF | egctl x translate --from gateway-api --type route --to xds -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -590,7 +590,7 @@ spec:
       protocol: TLS
       port: 8443
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -623,14 +623,14 @@ You can add an additional target `gateway-api` to show the processed Gateway API
 
 ```shell
 cat <<EOF | egctl x translate --from gateway-api --type route --to gateway-api,xds -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -641,7 +641,7 @@ spec:
       protocol: TLS
       port: 8443
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -740,3 +740,5 @@ xds:
   envoy-gateway-system-eg:
     '@type': type.googleapis.com/envoy.admin.v3.RoutesConfigDump
 ```
+
+[EnvoyProxy]: ../../api/extension_types#envoyproxy
diff --git a/site/content/en/latest/user/envoy-patch-policy.md b/site/content/en/latest/user/envoy-patch-policy.md
index e531e584792..2980baccbb2 100644
--- a/site/content/en/latest/user/envoy-patch-policy.md
+++ b/site/content/en/latest/user/envoy-patch-policy.md
@@ -27,7 +27,7 @@ Before proceeding, you should be able to query the example backend using HTTP.
 
 ### Enable EnvoyPatchPolicy
 
-* By default EnvoyPatchPolicy][] is disabled. Lets enable it in the [EnvoyGateway][] startup configuration
+* By default [EnvoyPatchPolicy][] is disabled. Lets enable it in the [EnvoyGateway][] startup configuration
 
 * The default installation of Envoy Gateway installs a default [EnvoyGateway][] configuration and attaches it
 using a `ConfigMap`. In the next step, we will update this resource to enable EnvoyPatchPolicy. 
@@ -194,9 +194,9 @@ across versions for these reasons
 * Envoy Gateway might alter the xDS translation creating a different xDS output
 such as changing the `name` field of resources.
 
-[EnvoyPatchPolicy]: https://gateway.envoyproxy.io/latest/api/extension_types.html#envoypatchpolicy
-[EnvoyGateway]: https://gateway.envoyproxy.io/latest/api/config_types.html#envoygateway
+[EnvoyPatchPolicy]: ../../api/extension_types#envoypatchpolicy
+[EnvoyGateway]: ../../api/extension_types#envoygateway
 [JSON Patch]: https://datatracker.ietf.org/doc/html/rfc6902
 [xDS]: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/operations/dynamic_configuration
 [Local Reply Modification]: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/local_reply
-[egctl x translate]: https://gateway.envoyproxy.io/latest/user/egctl.html#egctl-experimental-translate
+[egctl x translate]: ../egctl#egctl-experimental-translate
diff --git a/site/content/en/latest/user/gateway-address.md b/site/content/en/latest/user/gateway-address.md
index 06570cbe832..95aeb3aa4a3 100644
--- a/site/content/en/latest/user/gateway-address.md
+++ b/site/content/en/latest/user/gateway-address.md
@@ -65,5 +65,5 @@ envoy-gateway-metrics-service   ClusterIP      10.96.124.73    <none>        844
 
 __Note:__ If the `Gateway.Spec.Addresses` is explicitly set, it will be the only addresses that populates the Gateway status.
 
-[Addresses]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.GatewayAddress
+[Addresses]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayAddress
 [External IPs]: https://kubernetes.io/docs/concepts/services-networking/service/#external-ips
diff --git a/site/content/en/latest/user/gateway-api-metrics.md b/site/content/en/latest/user/gateway-api-metrics.md
index d2f93f32da6..a7764edbfc1 100644
--- a/site/content/en/latest/user/gateway-api-metrics.md
+++ b/site/content/en/latest/user/gateway-api-metrics.md
@@ -2,7 +2,7 @@
 title: "Gateway API Metrics"
 ---
 
-Resource metrics for Gateway API objects are available using the [Gateway API State Metrics](https://github.com/Kuadrant/gateway-api-state-metrics) project.
+Resource metrics for Gateway API objects are available using the [Gateway API State Metrics][gasm] project.
 The project also provides example dashboard for visualising the metrics using Grafana, and example alerts using Prometheus & Alertmanager.
 
 ## Prerequisites
@@ -31,9 +31,9 @@ kubectl -n monitoring port-forward service/prometheus-k8s 9090:9090 > /dev/null
 
 Navigate to [http://localhost:9090](http://localhost:9090).
 Metrics can be queried from the 'Graph' tab e.g. `gatewayapi_gateway_created`
-See the [Gateway API State Metrics README](https://github.com/Kuadrant/gateway-api-state-metrics/tree/main#metrics) for the full list of Gateway API metrics available.
+See the [Gateway API State Metrics README][gasm-readme] for the full list of Gateway API metrics available.
 
-Alerts can be see in the 'Alerts' tab.
+Alerts can be seen in the 'Alerts' tab.
 Gateway API specific alerts will be grouped under the 'gateway-api.rules' heading.
 
 ***Note:*** Alerts are defined in a PrometheusRules custom resource in the 'monitoring' namespace. You can modify the alert rules by updating this resource.
@@ -49,6 +49,11 @@ kubectl -n monitoring port-forward service/grafana 3000:3000 > /dev/null &
 
 Navigate to [http://localhost:3000](http://localhost:3000) and sign in with admin/admin.
 The Gateway API State dashboards will be available in the 'Default' folder and tagged with 'gateway-api'.
-See the [Gateway API State Metrics README](https://github.com/Kuadrant/gateway-api-state-metrics/tree/main#dashboards) for further information on available dashboards.
+See the [Gateway API State Metrics README][gasm-dashboards] for further information on available dashboards.
 
 ***Note:*** Dashboards are loaded from configmaps. You can modify the dashboards in the Grafana UI, however you will need to export them from the UI and update the json in the configmaps to persist changes.
+
+
+[gasm]: https://github.com/Kuadrant/gateway-api-state-metrics
+[gasm-readme]: https://github.com/Kuadrant/gateway-api-state-metrics/tree/main#metrics
+[gasm-dashboards]: https://github.com/Kuadrant/gateway-api-state-metrics/tree/main#dashboards
diff --git a/site/content/en/latest/user/gatewayapi-support.md b/site/content/en/latest/user/gatewayapi-support.md
index d70064dde25..a8d27dd6a36 100644
--- a/site/content/en/latest/user/gatewayapi-support.md
+++ b/site/content/en/latest/user/gatewayapi-support.md
@@ -22,18 +22,18 @@ deployment.
 
 ## HTTPRoute
 
-An [HTTPRoute][] configures routing of HTTP traffic through one or more Gateways. The following HTTPRoute filters are
+A [HTTPRoute][] configures routing of HTTP traffic through one or more Gateways. The following HTTPRoute filters are
 supported by Envoy Gateway:
 
-- `requestHeaderModifier`: [RequestHeaderModifiers](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `requestHeaderModifier`: [RequestHeaderModifiers][http-filter]
   can be used to modify or add request headers before the request is proxied to its destination.
-- `responseHeaderModifier`: [ResponseHeaderModifiers](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `responseHeaderModifier`: [ResponseHeaderModifiers][http-filter]
   can be used to modify or add response headers before the response is sent back to the client.
-- `requestMirror`: [RequestMirrors](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `requestMirror`: [RequestMirrors][http-filter]
   configure destinations where the requests should also be mirrored to. Responses to mirrored requests will be ignored.
-- `requestRedirect`: [RequestRedirects](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `requestRedirect`: [RequestRedirects][http-filter]
   configure policied for how requests that match the HTTPRoute should be modified and then redirected.
-- `urlRewrite`: [UrlRewrites](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `urlRewrite`: [UrlRewrites][http-filter]
   allow for modification of the request's hostname and path before it is proxied to its destination.
 - `extensionRef`: [ExtensionRefs][] are used by Envoy Gateway to implement extended filters. Currently, Envoy Gateway
   supports rate limiting and request authentication filters. For more information about these filters, refer to the
@@ -66,11 +66,11 @@ A [GRPCRoute][] configures routing of [gRPC][] requests through one or more Gate
 hostname, gRPC service, gRPC method, or HTTP/2 Header. Envoy Gateway supports the following filters on GRPCRoutes to
 provide additional traffic processing:
 
-- `requestHeaderModifier`: [RequestHeaderModifiers](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter)
+- `requestHeaderModifier`: [RequestHeaderModifiers][grpc-filter]
   can be used to modify or add request headers before the request is proxied to its destination.
-- `responseHeaderModifier`: [ResponseHeaderModifiers](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter)
+- `responseHeaderModifier`: [ResponseHeaderModifiers][grpc-filter]
   can be used to modify or add response headers before the response is sent back to the client.
-- `requestMirror`: [RequestMirrors](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter)
+- `requestMirror`: [RequestMirrors][grpc-filter]
   configure destinations where the requests should also be mirrored to. Responses to mirrored requests will be ignored.
 
 __Notes:__
@@ -94,25 +94,26 @@ these types of cross-namespace references. Envoy Gateway supports the following
   namespace.
 - Allowing a Gateway's [SecretObjectReference][] to reference a secret in a different namespace.
 
-[system design]: https://gateway.envoyproxy.io/latest/design/system-design.html
+[system design]: ../../design/system-design/
 [Gateway API]: https://gateway-api.sigs.k8s.io/
-[GatewayClass]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.GatewayClass
-[parameters reference]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.ParametersReference
-[Gateway]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.Gateway
-[HTTPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRoute
+[GatewayClass]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayClass
+[parameters reference]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.ParametersReference
+[Gateway]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.Gateway
+[HTTPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRoute
 [Service]: https://kubernetes.io/docs/concepts/services-networking/service/
-[BackendRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.BackendRef
-[HTTPBackendRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPBackendRef
-[TCPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute
-[UDPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.UDPRoute
-[GRPCRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
+[BackendRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendRef
+[HTTPBackendRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef
+[TCPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute
+[UDPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.UDPRoute
+[GRPCRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
 [gRPC]: https://grpc.io/
-[TLSRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.TLSRoute
-[ReferenceGrant]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1.ReferenceGrant
-[SecretObjectReference]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.SecretObjectReference
-[rate limiting]: https://gateway.envoyproxy.io/latest/user/rate-limit.html
-[request authentication]: https://gateway.envoyproxy.io/latest/user/authn.html
-[EnvoyProxy]: https://gateway.envoyproxy.io/latest/api/config_types.html#envoyproxy
+[TLSRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.TLSRoute
+[ReferenceGrant]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.ReferenceGrant
+[SecretObjectReference]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.SecretObjectReference
+[rate limiting]: ../rate-limit/
+[request authentication]: ../jwt-authentication/
+[EnvoyProxy]: ../../api/extension_types#envoyproxy
 [resolving conflicts]: https://gateway-api.sigs.k8s.io/concepts/guidelines/?h=conflict#conflicts
-[ExtensionRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilterType
-[grpc-filter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter
+[ExtensionRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteFilterType
+[grpc-filter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter
+[http-filter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteFilter
diff --git a/site/content/en/latest/user/grafana-integration.md b/site/content/en/latest/user/grafana-integration.md
index 01010dd8009..3c1aa0a8b6d 100644
--- a/site/content/en/latest/user/grafana-integration.md
+++ b/site/content/en/latest/user/grafana-integration.md
@@ -10,7 +10,7 @@ This guide shows you how to visualise the metrics exposed to prometheus using gr
 Follow the steps from the [Quickstart Guide](../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
-Follow the steps from the [Proxy Observability](proxy-observability.md#Metrics) to enable prometheus metrics.
+Follow the steps from the [Proxy Observability](../proxy-observability#Metrics) to enable prometheus metrics.
 
 [Prometheus](https://prometheus.io) is used to scrape metrics from the Envoy Proxy instances. Install Prometheus:
 
diff --git a/site/content/en/latest/user/http-request-headers.md b/site/content/en/latest/user/http-request-headers.md
index 0dbdbe13d3b..25b675a16d7 100644
--- a/site/content/en/latest/user/http-request-headers.md
+++ b/site/content/en/latest/user/http-request-headers.md
@@ -26,7 +26,7 @@ header in the request.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -109,7 +109,7 @@ filter.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -180,7 +180,7 @@ filter.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -245,7 +245,7 @@ Headers can be added/set/removed in a single filter on the same HTTPRoute and th
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -280,6 +280,6 @@ EOF
 ```
 
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
-[HTTPRoute filters]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter
+[HTTPRoute filters]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteFilter
 [Gateway API documentation]: https://gateway-api.sigs.k8s.io/
-[req_filter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPHeaderFilter
+[req_filter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPHeaderFilter
diff --git a/site/content/en/latest/user/http-request-mirroring.md b/site/content/en/latest/user/http-request-mirroring.md
index aaea240f5ca..95d3d0cfa54 100644
--- a/site/content/en/latest/user/http-request-mirroring.md
+++ b/site/content/en/latest/user/http-request-mirroring.md
@@ -2,7 +2,7 @@
 title: "HTTPRoute Request Mirroring"
 ---
 
-The [HTTPRoute][] resource allows one or more [backendRefs][] to be provided. Requests will be routed to these upstreams. It is possible to divide the traffic between these backends using [Traffic Splitting](http-traffic-splitting.md), but it is also possible to mirror requests to another Service instead. Request mirroring is accomplished using Gateway API's [HTTPRequestMirrorFilter][] on the `HTTPRoute`.
+The [HTTPRoute][] resource allows one or more [backendRefs][] to be provided. Requests will be routed to these upstreams. It is possible to divide the traffic between these backends using [Traffic Splitting][], but it is also possible to mirror requests to another Service instead. Request mirroring is accomplished using Gateway API's [HTTPRequestMirrorFilter][] on the `HTTPRoute`.
 
 When requests are made to a `HTTPRoute` that uses a `HTTPRequestMirrorFilter`, the response will never come from the `backendRef` defined in the filter. Responses from the mirror `backendRef` are always ignored.
 
@@ -79,7 +79,7 @@ service from the quickstart, and mirror request to the service that was just dep
 
 ```shell
 kubectl apply -f - <<EOF
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-mirror
@@ -166,7 +166,7 @@ When an `HTTPRoute` has multiple `backendRefs` and an `HTTPRequestMirrorFilter`,
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-mirror
@@ -205,7 +205,7 @@ Multiple `HTTPRequestMirrorFilters` are not supported on the same `HTTPRoute` `r
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-mirror
@@ -244,7 +244,8 @@ EOF
 Error from server: error when creating "STDIN": admission webhook "validate.gateway.networking.k8s.io" denied the request: spec.rules[0].filters: Invalid value: "RequestMirror": cannot be used multiple times in the same rule
 ```
 
-[Quickstart Guide]: quickstart.md
+[Quickstart Guide]: ../quickstart/
+[Traffic Splitting]: ../http-traffic-splitting/
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
-[backendRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.BackendRef
-[HTTPRequestMirrorFilter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRequestMirrorFilter
+[backendRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendRef
+[HTTPRequestMirrorFilter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRequestMirrorFilter
diff --git a/site/content/en/latest/user/http-response-headers.md b/site/content/en/latest/user/http-response-headers.md
index 9a0c3e38386..76cf33362b4 100644
--- a/site/content/en/latest/user/http-response-headers.md
+++ b/site/content/en/latest/user/http-response-headers.md
@@ -24,7 +24,7 @@ value of the header in the response.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -107,7 +107,7 @@ filter.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -179,7 +179,7 @@ filter.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -244,7 +244,7 @@ Headers can be added/set/removed in a single filter on the same HTTPRoute and th
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -280,4 +280,4 @@ EOF
 
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
 [Gateway API documentation]: https://gateway-api.sigs.k8s.io/
-[req_filter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPHeaderFilter
+[req_filter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPHeaderFilter
diff --git a/site/content/en/latest/user/http-routing.md b/site/content/en/latest/user/http-routing.md
index 2b0f4cf1e35..4d710c8a047 100644
--- a/site/content/en/latest/user/http-routing.md
+++ b/site/content/en/latest/user/http-routing.md
@@ -134,4 +134,4 @@ traffic was routed to the foo backend service.
 [GatewayClass]: https://gateway-api.sigs.k8s.io/api-types/gatewayclass/
 [Gateway]: https://gateway-api.sigs.k8s.io/api-types/gateway/
 [Envoy proxy]: https://www.envoyproxy.io/
-[spec]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteSpec
+[spec]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteSpec
diff --git a/site/content/en/latest/user/http-traffic-splitting.md b/site/content/en/latest/user/http-traffic-splitting.md
index 960adbcc2ea..49e6ca89c2f 100644
--- a/site/content/en/latest/user/http-traffic-splitting.md
+++ b/site/content/en/latest/user/http-traffic-splitting.md
@@ -17,7 +17,7 @@ When a single backendRef is configured in a HTTPRoute, it will receive 100% of t
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -149,7 +149,7 @@ Then create an HTTPRoute that uses both the app from the quickstart and the seco
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -219,7 +219,7 @@ backend-2 service.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -265,7 +265,7 @@ with status code `500`.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -310,4 +310,4 @@ $ curl -vvv --header "Host: backends.example" "http://${GATEWAY_HOST}/get"
 ```
 
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
-[backendRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.BackendRef
+[backendRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendRef
diff --git a/site/content/en/latest/user/http-urlrewrite.md b/site/content/en/latest/user/http-urlrewrite.md
index 60c0bebeeef..945a24a7a44 100644
--- a/site/content/en/latest/user/http-urlrewrite.md
+++ b/site/content/en/latest/user/http-urlrewrite.md
@@ -17,7 +17,7 @@ You can configure to rewrite the prefix in the url like below. In this example,
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-filter-url-rewrite
@@ -116,7 +116,7 @@ You can configure to rewrite the fullpath in the url like below. In this example
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-filter-url-rewrite
@@ -210,7 +210,7 @@ You can configure to rewrite the hostname like below. In this example, any reque
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-filter-url-rewrite
@@ -294,4 +294,4 @@ $ curl -L -vvv --header "Host: path.rewrite.example" "http://${GATEWAY_HOST}/get
 
 You can see that the `X-Forwarded-Host` is `path.rewrite.example`, but the actual host is `envoygateway.io`.
 
-[HTTPURLRewriteFilter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPURLRewriteFilter
+[HTTPURLRewriteFilter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPURLRewriteFilter
diff --git a/site/content/en/latest/user/jwt-authentication.md b/site/content/en/latest/user/jwt-authentication.md
index 36663f35fd2..368b6af9d09 100644
--- a/site/content/en/latest/user/jwt-authentication.md
+++ b/site/content/en/latest/user/jwt-authentication.md
@@ -12,7 +12,7 @@ This instantiated resource can be linked to a [Gateway][Gateway], [HTTPRoute][HT
 ## Prerequisites
 
 Follow the steps from the [Quickstart](../quickstart) guide to install Envoy Gateway and the example manifest.
-For GRPC - follow the steps from the [GRPC Routing](grpc-routing.md) example.
+For GRPC - follow the steps from the [GRPC Routing](../grpc-routing) example.
 Before proceeding, you should be able to query the example backend using HTTP or GRPC.
 
 ## Configuration
@@ -162,7 +162,7 @@ kubectl delete securitypolicy/jwt-example
 
 Checkout the [Developer Guide](../../contributions/develop/) to get involved in the project.
 
-[SecurityPolicy]: https://gateway.envoyproxy.io/latest/design/security-policy
+[SecurityPolicy]: ../../design/security-policy/
 [jwt]: https://tools.ietf.org/html/rfc7519
 [jwks]: https://tools.ietf.org/html/rfc7517
 [Gateway]: https://gateway-api.sigs.k8s.io/api-types/gateway
diff --git a/site/content/en/latest/user/rate-limit.md b/site/content/en/latest/user/rate-limit.md
index 7b997e60226..ee671039fef 100644
--- a/site/content/en/latest/user/rate-limit.md
+++ b/site/content/en/latest/user/rate-limit.md
@@ -158,7 +158,7 @@ EOF
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-ratelimit
@@ -310,7 +310,7 @@ EOF
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-ratelimit
@@ -441,7 +441,7 @@ EOF
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-ratelimit
@@ -533,7 +533,7 @@ spec:
           requests: 3
           unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-ratelimit
@@ -634,7 +634,7 @@ spec:
           requests: 3
           unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
diff --git a/site/content/en/latest/user/secure-gateways.md b/site/content/en/latest/user/secure-gateways.md
index dba8d3a972b..805aeb8b1a6 100644
--- a/site/content/en/latest/user/secure-gateways.md
+++ b/site/content/en/latest/user/secure-gateways.md
@@ -173,7 +173,7 @@ namespace to reference Secrets in the "envoy-gateway-system" namespace:
 
 ```console
 $ cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1alpha2
 kind: ReferenceGrant
 metadata:
   name: example
@@ -212,7 +212,7 @@ Update the Gateway HTTPS listener with `namespace: envoy-gateway-system`, for ex
 
 ```console
 $ cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -260,11 +260,11 @@ This section gives a walkthrough to generate RSA and ECDSA derived certificates
 Follow the steps from the [Quickstart Guide](../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
-Follow the steps in the [TLS Certificates](secure-gateways.md#tls-certificates) section in the guide to generate self-signed RSA derived Server certificate and private key, and configure those in the Gateway listener configuration to terminate HTTPS traffic.
+Follow the steps in the [TLS Certificates](../secure-gateways#tls-certificates) section in the guide to generate self-signed RSA derived Server certificate and private key, and configure those in the Gateway listener configuration to terminate HTTPS traffic.
 
 ## Pre-checks
 
-While testing in [Cluster without External LoadBalancer Support](secure-gateways.md#clusters-without-external-loadbalancer-support), we can query the example app through Envoy proxy while enforcing an RSA cipher, as shown below:
+While testing in [Cluster without External LoadBalancer Support](../secure-gateways#clusters-without-external-loadbalancer-support), we can query the example app through Envoy proxy while enforcing an RSA cipher, as shown below:
 
 ```shell
 curl -v -HHost:www.example.com --resolve "www.example.com:8443:127.0.0.1" \
@@ -295,7 +295,7 @@ Moving forward in the doc, we will be configuring the existing Gateway listener
 
 ## TLS Certificates
 
-Reuse the the CA certificate and key pair generated in the [Secure Gateways](secure-gateways.md#tls-certificates) guide and use this CA to sign both RSA and ECDSA Server certificates.
+Reuse the CA certificate and key pair generated in the [Secure Gateways](../secure-gateways#tls-certificates) guide and use this CA to sign both RSA and ECDSA Server certificates.
 Note the CA certificate and key names are `example.com.crt` and `example.com.key` respectively.
 
 
@@ -372,11 +372,11 @@ This sections gives a walkthrough to generate multiple certificates correspondin
 Follow the steps from the [Quickstart Guide](../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
-Follow the steps in the [TLS Certificates](secure-gateways.md#tls-certificates) section in the guide to generate self-signed RSA derived Server certificate and private key, and configure those in the Gateway listener configuration to terminate HTTPS traffic.
+Follow the steps in the [TLS Certificates](../secure-gateways#tls-certificates) section in the guide to generate self-signed RSA derived Server certificate and private key, and configure those in the Gateway listener configuration to terminate HTTPS traffic.
 
 ## Additional Configurations
 
-Using the [TLS Certificates](secure-gateways.md#tls-certificates) section in the guide we first generate additional Secret for another Host `www.sample.com`.
+Using the [TLS Certificates](../secure-gateways#tls-certificates) section in the guide we first generate additional Secret for another Host `www.sample.com`.
 
 ```shell
 openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -subj '/O=sample Inc./CN=sample.com' -keyout sample.com.key -out sample.com.crt
@@ -446,7 +446,7 @@ Since the multiple certificates are configured on the same Gateway listener, Env
 
 ### Clusters with External LoadBalancer Support
 
-Refer to the steps mentioned earlier in the guide under [Testing in clusters with External LoadBalancer Support](secure-gateways.md#clusters-with-external-loadbalancer-support)
+Refer to the steps mentioned earlier in the guide under [Testing in clusters with External LoadBalancer Support](../secure-gateways#clusters-with-external-loadbalancer-support)
 
 ## Next Steps
 
diff --git a/site/content/en/latest/user/tcp-routing.md b/site/content/en/latest/user/tcp-routing.md
index d06ae77f7a4..d51c845f206 100644
--- a/site/content/en/latest/user/tcp-routing.md
+++ b/site/content/en/latest/user/tcp-routing.md
@@ -35,13 +35,13 @@ Install the GatewayClass and a `tcp-gateway` Gateway first.
 ```shell
 cat <<EOF | kubectl apply -f -
 kind: GatewayClass
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: tcp-gateway
@@ -300,5 +300,5 @@ Content-Length: 267
 
 You can see that the traffic routing to `bar` service when sending request to `8089` port.
 
-[TCPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute
+[TCPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute
 [Gateway API documentation]: https://gateway-api.sigs.k8s.io/
diff --git a/site/content/en/latest/user/tls-cert-manager.md b/site/content/en/latest/user/tls-cert-manager.md
index 0cc9d59c3af..d3077a86bd0 100644
--- a/site/content/en/latest/user/tls-cert-manager.md
+++ b/site/content/en/latest/user/tls-cert-manager.md
@@ -148,7 +148,7 @@ cert-manager then follows the [Certificate Lifecycle](https://cert-manager.io/do
 To know how to issue the certificate, an ClusterIssuer is configured, and referenced through annotations on the Gateway resource, which you did above.
 Once a matching ClusterIssuer is found, that plugin does what needs to be done to acquire a signed certificate.
 
-In the case of the ACME protocol (used by Let's Encrypt,) cert-manager can also use an HTTP Gateway to solve the HTTP-01 challenge type.
+In the case of the ACME protocol (used by Let's Encrypt), cert-manager can also use an HTTP Gateway to solve the HTTP-01 challenge type.
 This is the other side of cert-manager's Gateway API support:
 the [ACME issuer](https://github.com/cert-manager/cert-manager/tree/master/pkg/issuer/acme/http/httproute.go) creates a temporary [HTTPRoute](https://gateway-api.sigs.k8s.io/api-types/httproute/), lets the ACME server(s) query it, and deletes it again.
 
diff --git a/site/content/en/v0.6.0/design/backend-traffic-policy.md b/site/content/en/v0.6.0/design/backend-traffic-policy.md
index 3cc0709b946..f4b7dd32f52 100644
--- a/site/content/en/v0.6.0/design/backend-traffic-policy.md
+++ b/site/content/en/v0.6.0/design/backend-traffic-policy.md
@@ -29,14 +29,14 @@ then the configuration from the policy that is targeting the xRoute resource wil
 Here is an example highlighting how a user can configure this API.
 
 ```yaml
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -48,7 +48,7 @@ spec:
       protocol: HTTP
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: ipv4-route
@@ -70,7 +70,7 @@ spec:
             type: PathPrefix
             value: /
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: ipv6-route
@@ -150,6 +150,6 @@ entire Gateway then
 
 ## Alternatives
 
-- The project can indefintely wait for these configuration parameters to be part of the [Gateway API][].
+- The project can indefinitely wait for these configuration parameters to be part of the [Gateway API][].
 
 [Gateway API]: https://gateway-api.sigs.k8s.io/
diff --git a/site/content/en/v0.6.0/design/bootstrap.md b/site/content/en/v0.6.0/design/bootstrap.md
index 4475710ad5d..c0581347a24 100644
--- a/site/content/en/v0.6.0/design/bootstrap.md
+++ b/site/content/en/v0.6.0/design/bootstrap.md
@@ -53,7 +53,7 @@ Here is an example where a user inputs a `GatewayClass` and the CLI generates th
 
 ```
 cat <<EOF | egctl x translate --from gateway-api --to gateway-api -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -65,7 +65,7 @@ EOF
 ```
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -173,7 +173,7 @@ unmarshalled into the Bootstrap object as well as ensure the user can override c
 
 ```
 cat <<EOF | egctl x translate --from gateway-api --to gateway-api -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -275,7 +275,7 @@ EOF
 ```
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -376,6 +376,6 @@ spec:
 ```
 
 [Issue 31]: https://github.com/envoyproxy/gateway/issues/31
-[EnvoyProxy]: https://gateway.envoyproxy.io/latest/api/config_types.html#envoyproxy
-[GatewayClass]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.GatewayClass
-[parametersRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.ParametersReference 
+[EnvoyProxy]: ../../api/extension_types#envoyproxy
+[GatewayClass]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayClass
+[parametersRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.ParametersReference 
diff --git a/site/content/en/v0.6.0/design/client-traffic-policy.md b/site/content/en/v0.6.0/design/client-traffic-policy.md
index fab62b92078..8a767bac613 100644
--- a/site/content/en/v0.6.0/design/client-traffic-policy.md
+++ b/site/content/en/v0.6.0/design/client-traffic-policy.md
@@ -26,14 +26,14 @@ to define configuration that affect the connection between the downstream client
 Here is an example highlighting how a user can configure this API.
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -45,7 +45,7 @@ spec:
       protocol: HTTP
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -108,7 +108,7 @@ entire Gateway then
 
 ## Alternatives
 
-* The project can indefintely wait for these configuration parameters to be part of the [Gateway API].
+* The project can indefinitely wait for these configuration parameters to be part of the [Gateway API][].
 
 [Direct Policy Attachment]: https://gateway-api.sigs.k8s.io/references/policy-attachment/#direct-policy-attachment
 [Gateway API]: https://gateway-api.sigs.k8s.io/
diff --git a/site/content/en/v0.6.0/design/config-api.md b/site/content/en/v0.6.0/design/config-api.md
index 343718f2c6e..1c6f3057848 100644
--- a/site/content/en/v0.6.0/design/config-api.md
+++ b/site/content/en/v0.6.0/design/config-api.md
@@ -285,14 +285,14 @@ GatewayClass and Gateway resources define the data plane infrastructure. Note th
 running with the Kubernetes provider.
 
 ```yaml
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: example-class
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: example-gateway
@@ -312,7 +312,7 @@ The following example will configure the data plane to use a ClusterIP service i
 service:
 
 ```yaml
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: example-class
@@ -323,7 +323,7 @@ spec:
     group: gateway.envoyproxy.io
     kind: EnvoyProxy
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: example-gateway
@@ -346,8 +346,8 @@ spec:
 __Note:__ The NetworkPublishing API is currently undefined and is provided here for illustration purposes only.
 
 [issue_51]: https://github.com/envoyproxy/gateway/issues/51
-[design_doc]: https://github.com/envoyproxy/gateway/blob/main/docs/design/SYSTEM_DESIGN.md
+[design_doc]: ../system-design/
 [gw_api]: https://gateway-api.sigs.k8s.io/
-[gc]: https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.GatewayClass
+[gc]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayClass
 [cr]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
 [union]: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#unions
diff --git a/site/content/en/v0.6.0/design/envoy-patch-policy.md b/site/content/en/v0.6.0/design/envoy-patch-policy.md
index d34937d05ef..83ccb035b4d 100644
--- a/site/content/en/v0.6.0/design/envoy-patch-policy.md
+++ b/site/content/en/v0.6.0/design/envoy-patch-policy.md
@@ -20,7 +20,7 @@ Envoy xDS API and its capabilities, this API is being introduced.
 * Add an API allowing users to modify the generated xDS Configuration
 
 ## Non Goals
-* Support multiple patch mechanisims
+* Support multiple patch mechanisms
 
 ## Implementation
 `EnvoyPatchPolicy` is a [Direct Policy Attachment][] type API that can be used to extend [Gateway API][]
@@ -32,14 +32,14 @@ resource objects.
 Here is an example highlighting how a user can configure global ratelimiting using an external rate limit service using this API.
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -51,7 +51,7 @@ spec:
       protocol: HTTP
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -167,10 +167,10 @@ patches will work.
 [Gateway API]: https://gateway-api.sigs.k8s.io/
 [Kubernetes]: https://kubernetes.io/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch/
 [Kustomize]: https://github.com/kubernetes-sigs/kustomize/blob/master/examples/jsonpatch.md
-[Extension APIs]: https://gateway.envoyproxy.io/latest/api/extension_types.html
-[RateLimit]: https://gateway.envoyproxy.io/latest/user/rate-limit.html
-[EnvoyGateway]: https://gateway.envoyproxy.io/latest/api/config_types.html#envoygateway
-[Extending the Control Plane]: https://gateway.envoyproxy.io/latest/design/extending-envoy-gateway.html
+[Extension APIs]: ../../api/extension_types/
+[RateLimit]: ../../user/rate-limit/
+[EnvoyGateway]: ../../api/extension_types#envoygateway
+[Extending the Control Plane]: ../extending-envoy-gateway/
 [EnvoyFilter]: https://istio.io/latest/docs/reference/config/networking/envoy-filter
-[egctl x translate]: https://gateway.envoyproxy.io/latest/user/egctl.html#egctl-experimental-translate
-[Bootstrap configuration using EnvoyProxy API]: https://gateway.envoyproxy.io/latest/user/customize-envoyproxy.html#customize-envoyproxy-bootstrap-config
+[egctl x translate]: ../../user/egctl#egctl-experimental-translate
+[Bootstrap configuration using EnvoyProxy API]: ../../user/customize-envoyproxy#customize-envoyproxy-bootstrap-config
diff --git a/site/content/en/v0.6.0/design/extending-envoy-gateway.md b/site/content/en/v0.6.0/design/extending-envoy-gateway.md
index d4f36cc7a4a..d84f553efde 100644
--- a/site/content/en/v0.6.0/design/extending-envoy-gateway.md
+++ b/site/content/en/v0.6.0/design/extending-envoy-gateway.md
@@ -110,7 +110,7 @@ spec:
   ...
 
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -140,7 +140,7 @@ if they specify an `group` that matches the `group` of an `ExtensionRef` filter.
 modified configuration. If an extension is not registered or if the registered extension does not specify support for the `group` of an `ExtensionRef` filter then Envoy Gateway will treat it as an unknown resource
 and provide an error to the user.
 
-**Note:** Currently (as of [v1beta1][]) Gateway API does not provide a means to specify the namespace or version of an object referenced as an `ExtensionRef`. The extension mechanism will assume that
+**Note:** Currently (as of [v1][]) Gateway API does not provide a means to specify the namespace or version of an object referenced as an `ExtensionRef`. The extension mechanism will assume that
 the namespace of any `ExtensionRef` is the same as the namespace of the `HTTPRoute` or `GRPCRoute` it is attached to rather than treating the `name` field of an `ExtensionRef` as a `name.namespace` string.
 If Gateway API adds support for these fields then the design of the Envoy Gateway extensions will be updated to support them.
 
@@ -302,24 +302,24 @@ whenever Envoy Gateway creates an instance of Envoy Proxy. An extension develope
 
 ## Known Challenges
 
-Extending Envoy Gateway by using an external extension server which makes use of hook points in Envoy Gateway does comes with a few trade-offs. One known trade-off is the impact of the time that it takes for the hook calls to be executed. Since an extension would make use of hook points in Envoy Gateway that use gRPC for communication, the time it takes to perform these requests could become a concern for some extension developers. One way to minimize the request time of the hook calls is to load the extension server as a sidecar to Envoy Gateway to minimize the impact of networking on the hook calls.
+Extending Envoy Gateway by using an external extension server which makes use of hook points in Envoy Gateway does come with a few trade-offs. One known trade-off is the impact of the time that it takes for the hook calls to be executed. Since an extension would make use of hook points in Envoy Gateway that use gRPC for communication, the time it takes to perform these requests could become a concern for some extension developers. One way to minimize the request time of the hook calls is to load the extension server as a sidecar to Envoy Gateway to minimize the impact of networking on the hook calls.
 
-[official goals]: https://github.com/envoyproxy/gateway/blob/main/GOALS.md#extensibility
-[ExtensionRef filters]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.LocalObjectReference
-[ExtensionRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.LocalObjectReference
-[ExtensionRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.LocalObjectReference
-[backendRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.BackendObjectReference
+[official goals]: ../goals#extensibility
+[ExtensionRef filters]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.LocalObjectReference
+[ExtensionRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.LocalObjectReference
+[ExtensionRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.LocalObjectReference
+[backendRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef
 [Gateway API Policy attachments]: https://gateway-api.sigs.k8s.io/references/policy-attachment/?h=policy
 [Policy Attachments]: https://gateway-api.sigs.k8s.io/references/policy-attachment/?h=policy
 [policyAttachments]: https://gateway-api.sigs.k8s.io/references/policy-attachment/?h=policy
 [Envoy]: https://www.envoyproxy.io/
 [Envoy specific configuration (xDS)]: https://www.envoyproxy.io/docs/envoy/v1.25.1/configuration/configuration
-[v1beta1]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1
-[rate limiting]: https://gateway.envoyproxy.io/v0.3.0/user/rate-limit.html
-[authentication]: https://gateway.envoyproxy.io/v0.3.0/user/authn.html
-[HTTPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRoute
-[GRPCRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
-[EnvoyGateway config]: https://gateway.envoyproxy.io/v0.3.0/api/config_types.html#envoygateway
+[v1]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1
+[rate limiting]: ../../user/rate-limit/
+[authentication]: ../../user/jwt-authentication/
+[HTTPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRoute
+[GRPCRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
+[EnvoyGateway config]: ../../api/extension_types#envoygateway
 [controller-runtime]: https://github.com/kubernetes-sigs/controller-runtime
 [Unstructured]: https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured
 [Listener]: https://www.envoyproxy.io/docs/envoy/v1.23.0/api-v3/config/listener/v3/listener.proto#config-listener-v3-listener
diff --git a/site/content/en/v0.6.0/design/gatewayapi-translator.md b/site/content/en/v0.6.0/design/gatewayapi-translator.md
index b83ed82588d..a086b80bfee 100644
--- a/site/content/en/v0.6.0/design/gatewayapi-translator.md
+++ b/site/content/en/v0.6.0/design/gatewayapi-translator.md
@@ -38,7 +38,7 @@ __Note:__ Envoy Gateway does not collapse listeners across multiple Gateways.
 
 ```yaml
 kind: Gateway
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: gateway-1
   namespace: envoy-gateway
@@ -65,7 +65,7 @@ spec:
 
 ```yaml
 kind: Gateway
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: gateway-1
   namespace: envoy-gateway
@@ -91,7 +91,7 @@ spec:
 
 ```yaml
 kind: Gateway
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: gateway-1
   namespace: envoy-gateway
@@ -118,7 +118,7 @@ spec:
 
 ```yaml
 kind: Gateway
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: gateway-1
   namespace: envoy-gateway
@@ -250,4 +250,4 @@ type RouteContext interface {
 }
 ```
 
-[message bus]: watching.md
+[message bus]: ../watching/
diff --git a/site/content/en/v0.6.0/design/local-envoy-gateway.md b/site/content/en/v0.6.0/design/local-envoy-gateway.md
index aad0dc5f6f2..81265297e14 100644
--- a/site/content/en/v0.6.0/design/local-envoy-gateway.md
+++ b/site/content/en/v0.6.0/design/local-envoy-gateway.md
@@ -30,7 +30,7 @@ Envoy Proxy fleet on Kubernetes.
 with two fields called `resource` and `infrastructure` to allow the user to configure
 the sub providers for providing resource configuration and an infrastructure to deploy
 the Envoy Proxy data plane in.
-* A `File` resource provider will be introduced to enable retrieveing configuration locally
+* A `File` resource provider will be introduced to enable retrieving configuration locally
 by reading from the configuration from a file.
 * A `Host` infrastructure provider will be introduced to allow Envoy Gateway to spawn a 
 Envoy Proxy child process on the host.
diff --git a/site/content/en/v0.6.0/design/metrics.md b/site/content/en/v0.6.0/design/metrics.md
index c87b23ad4e5..a154a31e871 100644
--- a/site/content/en/v0.6.0/design/metrics.md
+++ b/site/content/en/v0.6.0/design/metrics.md
@@ -78,7 +78,7 @@ type PrometheusProvider struct {
 
 ### Example
 
-1. The following is an example to disable prometheus metric.
+- The following is an example to disable prometheus metric.
 
 ```yaml mdox-exec="sed '1,12d' examples/kubernetes/metric/disable-prometheus.yaml"
 apiVersion: gateway.envoyproxy.io/v1alpha1
@@ -93,7 +93,7 @@ spec:
         disable: true
 ```
 
-1. The following is an example to send metric via Open Telemetry sink.
+- The following is an example to send metric via Open Telemetry sink.
 
 ```yaml mdox-exec="sed '1,12d' examples/kubernetes/metric/otel-sink.yaml"
 apiVersion: gateway.envoyproxy.io/v1alpha1
diff --git a/site/content/en/v0.6.0/design/rate-limit.md b/site/content/en/v0.6.0/design/rate-limit.md
index e35d44c8239..46ad240c143 100644
--- a/site/content/en/v0.6.0/design/rate-limit.md
+++ b/site/content/en/v0.6.0/design/rate-limit.md
@@ -7,7 +7,7 @@ title: "Rate Limit Design"
 Rate limit is a feature that allows the user to limit the number of incoming requests
 to a predefined value based on attributes within the traffic flow.
 
-Here are some reasons why a user may want to implements Rate limits
+Here are some reasons why a user may want to implement Rate limits
 
 * To prevent malicious activity such as DDoS attacks.
 * To prevent applications and its resources (such as a database) from getting overloaded.
@@ -49,7 +49,7 @@ spec:
         requests: 10
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -93,7 +93,7 @@ spec:
         requests: 1000
         unit: Second
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -142,7 +142,7 @@ spec:
         requests: 10
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -187,7 +187,7 @@ spec:
         requests: 10
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -253,7 +253,7 @@ spec:
         requests: 10
         unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -352,7 +352,7 @@ spec:
 * The user has created two `RateLimitFilter`s  and has attached it to a `HTTPRoute` - one(`ratelimit-all-safeguard-app`) to
 ensure that the backend does not get overwhelmed with requests, any excess requests are rate limited irrespective of
 the attributes within the traffic flow, and another(`ratelimit-per-user`) to rate limit each distinct user client
-who can be differentiated using the `x-user-id` header, to ensure that each client does not make exessive requests to the backend.
+who can be differentiated using the `x-user-id` header, to ensure that each client does not make excessive requests to the backend.
 * If user `baz` (identified with the header and value of `x-user-id: baz`) sends 90 requests within the first second, and
 user `bar` sends 11 more requests during that same interval of 1 second, and user `bar` sends the 101th request within that second,
 the rule defined in `ratelimit-all-safeguard-app` gets activated and Envoy Gateway will ratelimit the request sent by `bar` (and any other
@@ -401,12 +401,12 @@ attribute such as [IP subnet][] in the future that are not relevant in the [HTTP
   * A Status field within the RateLimitFilter API will be added to reflect whether the specific configuration was programmed correctly in these multiple locations or not.
 
 [PolicyAttachment]: https://gateway-api.sigs.k8s.io/references/policy-attachment/
-[HTTPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRoute
-[HTTPRouteRule]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteRule
-[HTTPBackendRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1.HTTPBackendRef
-[matches]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteMatch
-[rule]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteMatch
-[extensionRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilterType
+[HTTPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRoute
+[HTTPRouteRule]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule
+[HTTPBackendRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef
+[matches]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch
+[rule]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch
+[extensionRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteFilterType
 [IP subnet]: https://en.wikipedia.org/wiki/Subnetwork
 [Actions]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-msg-config-route-v3-ratelimit-action
 [descriptors]: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/rate_limit_filter.html?highlight=descriptor#example-1
@@ -415,5 +415,5 @@ attribute such as [IP subnet][] in the future that are not relevant in the [HTTP
 [rate limit filter]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/ratelimit/v3/rate_limit.proto#envoy-v3-api-msg-extensions-filters-http-ratelimit-v3-ratelimit 
 [rate limit service]: https://www.envoyproxy.io/docs/envoy/latest/configuration/other_features/rate_limit#config-rate-limit-service
 [reference implementation]: https://github.com/envoyproxy/ratelimit
-[EnvoyGateway]: https://github.com/envoyproxy/gateway/blob/main/api/config/v1alpha1/envoygateway_types.go
+[EnvoyGateway]: https://github.com/envoyproxy/gateway/blob/main/api/v1alpha1/envoygateway_types.go
 [rate limit service configuration]: https://github.com/envoyproxy/ratelimit#configuration
diff --git a/site/content/en/v0.6.0/design/security-policy.md b/site/content/en/v0.6.0/design/security-policy.md
index b7413b92ad0..b39165feb03 100644
--- a/site/content/en/v0.6.0/design/security-policy.md
+++ b/site/content/en/v0.6.0/design/security-policy.md
@@ -16,20 +16,20 @@ on the traffic entering the gateway.
 
 ## Implementation
 `SecurityPolicy` is a [Policy Attachment][] type API that can be used to extend [Gateway API][]
-to define authentication and authorization rules..
+to define authentication and authorization rules.
 
 ### Example
 Here is an example highlighting how a user can configure this API.
 
 ```
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -41,7 +41,7 @@ spec:
       protocol: HTTPS
       port: 443
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -109,7 +109,7 @@ entire Gateway then
 this route's parentRef which in turn overrides a Policy targeting the Gateway the listener/section is a part of. 
 
 ## Alternatives
-* The project can indefintely wait for these configuration parameters to be part of the [Gateway API].
+* The project can indefinitely wait for these configuration parameters to be part of the [Gateway API][].
 
 [Policy Attachment]: https://gateway-api.sigs.k8s.io/references/policy-attachment 
 [Gateway API]: https://gateway-api.sigs.k8s.io/
diff --git a/site/content/en/v0.6.0/design/system-design.md b/site/content/en/v0.6.0/design/system-design.md
index 16123948ee7..956482ffcc3 100644
--- a/site/content/en/v0.6.0/design/system-design.md
+++ b/site/content/en/v0.6.0/design/system-design.md
@@ -167,8 +167,8 @@ The draft for this document is [here][draft_design].
 [cluster]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/cluster/v3/cluster.proto#config-cluster-v3-cluster
 [draft_design]: https://docs.google.com/document/d/1riyTPPYuvNzIhBdrAX8dpfxTmcobWZDSYTTB5NeybuY/edit
 [cr]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
-[be]: https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.BackendObjectReference
+[be]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendObjectReference
 [svc]: https://kubernetes.io/docs/concepts/services-networking/service/
-[ wcd ]: ./watching.md
+[ wcd ]: ../watching/
 [Issue #37]: https://github.com/envoyproxy/gateway/issues/37
-[roadmap]: roadmap.md
+[roadmap]: ../../contributions/roadmap/
diff --git a/site/content/en/v0.6.0/user/cors.md b/site/content/en/v0.6.0/user/cors.md
index 05481aa44b2..d8867ccb8d2 100644
--- a/site/content/en/v0.6.0/user/cors.md
+++ b/site/content/en/v0.6.0/user/cors.md
@@ -114,7 +114,7 @@ kubectl delete securitypolicy/cors-example
 
 Checkout the [Developer Guide](../../contributions/develop/) to get involved in the project.
 
-[SecurityPolicy]: https://gateway.envoyproxy.io/v0.6.0/design/security-policy
+[SecurityPolicy]: ../../design/security-policy/
 [cors]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
 [Gateway]: https://gateway-api.sigs.k8s.io/api-types/gateway
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute
diff --git a/site/content/en/v0.6.0/user/customize-envoyproxy.md b/site/content/en/v0.6.0/user/customize-envoyproxy.md
index e08e115ac7a..356a3d7b089 100644
--- a/site/content/en/v0.6.0/user/customize-envoyproxy.md
+++ b/site/content/en/v0.6.0/user/customize-envoyproxy.md
@@ -17,7 +17,7 @@ First, you need to add ParametersRef in GatewayClass, and refer to EnvoyProxy Co
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
@@ -318,5 +318,5 @@ Any errors in the configuration will be surfaced as status within the `GatewayCl
 You can also validate this configuration using [egctl translate][].
 
 [Gateway API documentation]: https://gateway-api.sigs.k8s.io/
-[EnvoyProxy]: https://gateway.envoyproxy.io/v0.6.0/api/config_types.html#envoyproxy 
-[egctl translate]: https://gateway.envoyproxy.io/v0.6.0/user/egctl/#validating-gateway-api-configuration
+[EnvoyProxy]: ../../api/extension_types#envoyproxy 
+[egctl translate]: ../egctl#validating-gateway-api-configuration
diff --git a/site/content/en/v0.6.0/user/deployment-mode.md b/site/content/en/v0.6.0/user/deployment-mode.md
index 0e6a7d58a23..e6c7b73bfdd 100644
--- a/site/content/en/v0.6.0/user/deployment-mode.md
+++ b/site/content/en/v0.6.0/user/deployment-mode.md
@@ -38,14 +38,14 @@ Lets create a `GatewayClass` linked to the marketing team's Envoy Gateway contro
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg-marketing
 spec:
   controllerName: gateway.envoyproxy.io/marketing-gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -113,7 +113,7 @@ spec:
                 fieldRef:
                   fieldPath: metadata.namespace
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -211,14 +211,14 @@ Lets create a `GatewayClass` linked to the product team's Envoy Gateway controll
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg-product
 spec:
   controllerName: gateway.envoyproxy.io/product-gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -286,7 +286,7 @@ spec:
                 fieldRef:
                   fieldPath: metadata.namespace
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -374,7 +374,7 @@ Handling connection for 8889
 * Connection #0 to host localhost left intact
 ```
 
-With the below command you can ensure that you are no able to access the marketing team's backend exposed using the `www.marketing.example.com` hostname
+With the below command you can ensure that you are not able to access the marketing team's backend exposed using the `www.marketing.example.com` hostname
 and the product team's data plane.
 
 ```shell
diff --git a/site/content/en/v0.6.0/user/egctl.md b/site/content/en/v0.6.0/user/egctl.md
index 38daed73a4b..937c783cc02 100644
--- a/site/content/en/v0.6.0/user/egctl.md
+++ b/site/content/en/v0.6.0/user/egctl.md
@@ -15,14 +15,14 @@ resources.
 
 ```shell
 cat <<EOF | egctl x translate --from gateway-api --to xds -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -58,7 +58,7 @@ spec:
   selector:
     app: backend
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -259,14 +259,14 @@ You can also use the `--type`/`-t` flag to retrieve specific output types. In th
 
 ```shell
 cat <<EOF | egctl x translate --from gateway-api --to xds -t route -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -302,7 +302,7 @@ spec:
   selector:
     app: backend
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -353,14 +353,14 @@ For example, this will provide the similar result as the above:
 
 ```shell
 cat <<EOF | egctl x translate --add-missing-resources --from gateway-api --to gateway-api -t route -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -372,7 +372,7 @@ spec:
       protocol: HTTP
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -396,7 +396,7 @@ spec:
 EOF
 ```
 
-You can see the output contains a [EnvoyProxy](https://gateway.envoyproxy.io/v0.6.0/api/config_types.html#envoyproxy) resource that
+You can see the output contains a [EnvoyProxy](../../api/extension_types#envoyproxy) resource that
 can be used as a starting point to modify the xDS bootstrap resource for the managed Envoy Proxy fleet.
 
 ```yaml
@@ -572,14 +572,14 @@ Sometimes you might find that egctl doesn't provide an expected result. For exam
 
 ```shell
 cat <<EOF | egctl x translate --from gateway-api --type route --to xds -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -590,7 +590,7 @@ spec:
       protocol: TLS
       port: 8443
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
@@ -623,14 +623,14 @@ You can add an additional target `gateway-api` to show the processed Gateway API
 
 ```shell
 cat <<EOF | egctl x translate --from gateway-api --type route --to gateway-api,xds -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -641,7 +641,7 @@ spec:
       protocol: TLS
       port: 8443
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: backend
diff --git a/site/content/en/v0.6.0/user/envoy-patch-policy.md b/site/content/en/v0.6.0/user/envoy-patch-policy.md
index e6a2e6f3a1f..9bf6459d2cd 100644
--- a/site/content/en/v0.6.0/user/envoy-patch-policy.md
+++ b/site/content/en/v0.6.0/user/envoy-patch-policy.md
@@ -27,7 +27,7 @@ Before proceeding, you should be able to query the example backend using HTTP.
 
 ### Enable EnvoyPatchPolicy
 
-* By default EnvoyPatchPolicy][] is disabled. Lets enable it in the [EnvoyGateway][] startup configuration
+* By default [EnvoyPatchPolicy][] is disabled. Lets enable it in the [EnvoyGateway][] startup configuration
 
 * The default installation of Envoy Gateway installs a default [EnvoyGateway][] configuration and attaches it
 using a `ConfigMap`. In the next step, we will update this resource to enable EnvoyPatchPolicy. 
@@ -194,9 +194,9 @@ across versions for these reasons
 * Envoy Gateway might alter the xDS translation creating a different xDS output
 such as changing the `name` field of resources.
 
-[EnvoyPatchPolicy]: https://gateway.envoyproxy.io/v0.6.0/api/extension_types.html#envoypatchpolicy
-[EnvoyGateway]: https://gateway.envoyproxy.io/v0.6.0/api/config_types.html#envoygateway
+[EnvoyPatchPolicy]: ../../api/extension_types#envoypatchpolicy
+[EnvoyGateway]: ../../api/extension_types#envoygateway
 [JSON Patch]: https://datatracker.ietf.org/doc/html/rfc6902
 [xDS]: https://www.envoyproxy.io/docs/envoy/v0.6.0/intro/arch_overview/operations/dynamic_configuration
 [Local Reply Modification]: https://www.envoyproxy.io/docs/envoy/v0.6.0/configuration/http/http_conn_man/local_reply
-[egctl x translate]: https://gateway.envoyproxy.io/v0.6.0/user/egctl.html#egctl-experimental-translate
+[egctl x translate]: ../egctl#egctl-experimental-translate
diff --git a/site/content/en/v0.6.0/user/gateway-address.md b/site/content/en/v0.6.0/user/gateway-address.md
index bee4735c168..8f2458327a5 100644
--- a/site/content/en/v0.6.0/user/gateway-address.md
+++ b/site/content/en/v0.6.0/user/gateway-address.md
@@ -65,5 +65,5 @@ envoy-gateway-metrics-service   ClusterIP      10.96.124.73    <none>        844
 
 __Note:__ If the `Gateway.Spec.Addresses` is explicitly set, it will be the only addresses that populates the Gateway status.
 
-[Addresses]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.GatewayAddress
+[Addresses]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayAddress
 [External IPs]: https://kubernetes.io/docs/concepts/services-networking/service/#external-ips
diff --git a/site/content/en/v0.6.0/user/gateway-api-metrics.md b/site/content/en/v0.6.0/user/gateway-api-metrics.md
index d2f93f32da6..fef51bde69f 100644
--- a/site/content/en/v0.6.0/user/gateway-api-metrics.md
+++ b/site/content/en/v0.6.0/user/gateway-api-metrics.md
@@ -33,7 +33,7 @@ Navigate to [http://localhost:9090](http://localhost:9090).
 Metrics can be queried from the 'Graph' tab e.g. `gatewayapi_gateway_created`
 See the [Gateway API State Metrics README](https://github.com/Kuadrant/gateway-api-state-metrics/tree/main#metrics) for the full list of Gateway API metrics available.
 
-Alerts can be see in the 'Alerts' tab.
+Alerts can be seen in the 'Alerts' tab.
 Gateway API specific alerts will be grouped under the 'gateway-api.rules' heading.
 
 ***Note:*** Alerts are defined in a PrometheusRules custom resource in the 'monitoring' namespace. You can modify the alert rules by updating this resource.
diff --git a/site/content/en/v0.6.0/user/gatewayapi-support.md b/site/content/en/v0.6.0/user/gatewayapi-support.md
index d9265fd139d..064bb5b2b1b 100644
--- a/site/content/en/v0.6.0/user/gatewayapi-support.md
+++ b/site/content/en/v0.6.0/user/gatewayapi-support.md
@@ -25,15 +25,15 @@ deployment.
 An [HTTPRoute][] configures routing of HTTP traffic through one or more Gateways. The following HTTPRoute filters are
 supported by Envoy Gateway:
 
-- `requestHeaderModifier`: [RequestHeaderModifiers](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `requestHeaderModifier`: [RequestHeaderModifiers][http-filter]
   can be used to modify or add request headers before the request is proxied to its destination.
-- `responseHeaderModifier`: [ResponseHeaderModifiers](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `responseHeaderModifier`: [ResponseHeaderModifiers][http-filter]
   can be used to modify or add response headers before the response is sent back to the client.
-- `requestMirror`: [RequestMirrors](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `requestMirror`: [RequestMirrors][http-filter]
   configure destinations where the requests should also be mirrored to. Responses to mirrored requests will be ignored.
-- `requestRedirect`: [RequestRedirects](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `requestRedirect`: [RequestRedirects][http-filter]
   configure policied for how requests that match the HTTPRoute should be modified and then redirected.
-- `urlRewrite`: [UrlRewrites](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter)
+- `urlRewrite`: [UrlRewrites][http-filter]
   allow for modification of the request's hostname and path before it is proxied to its destination.
 - `extensionRef`: [ExtensionRefs][] are used by Envoy Gateway to implement extended filters. Currently, Envoy Gateway
   supports rate limiting and request authentication filters. For more information about these filters, refer to the
@@ -66,11 +66,11 @@ A [GRPCRoute][] configures routing of [gRPC][] requests through one or more Gate
 hostname, gRPC service, gRPC method, or HTTP/2 Header. Envoy Gateway supports the following filters on GRPCRoutes to
 provide additional traffic processing:
 
-- `requestHeaderModifier`: [RequestHeaderModifiers](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter)
+- `requestHeaderModifier`: [RequestHeaderModifiers][grpc-filter]
   can be used to modify or add request headers before the request is proxied to its destination.
-- `responseHeaderModifier`: [ResponseHeaderModifiers](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter)
+- `responseHeaderModifier`: [ResponseHeaderModifiers][grpc-filter]
   can be used to modify or add response headers before the response is sent back to the client.
-- `requestMirror`: [RequestMirrors](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter)
+- `requestMirror`: [RequestMirrors][grpc-filter]
   configure destinations where the requests should also be mirrored to. Responses to mirrored requests will be ignored.
 
 __Notes:__
@@ -94,25 +94,26 @@ these types of cross-namespace references. Envoy Gateway supports the following
   namespace.
 - Allowing a Gateway's [SecretObjectReference][] to reference a secret in a different namespace.
 
-[system design]: https://gateway.envoyproxy.io/v0.6.0/design/system-design.html
+[system design]: ../../design/system-design/
 [Gateway API]: https://gateway-api.sigs.k8s.io/
-[GatewayClass]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.GatewayClass
-[parameters reference]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.ParametersReference
-[Gateway]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.Gateway
-[HTTPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRoute
+[GatewayClass]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.GatewayClass
+[parameters reference]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.ParametersReference
+[Gateway]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.Gateway
+[HTTPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRoute
 [Service]: https://kubernetes.io/docs/concepts/services-networking/service/
-[BackendRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.BackendRef
-[HTTPBackendRef]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPBackendRef
-[TCPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute
-[UDPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.UDPRoute
-[GRPCRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
+[BackendRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendRef
+[HTTPBackendRef]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPBackendRef
+[TCPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute
+[UDPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.UDPRoute
+[GRPCRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
 [gRPC]: https://grpc.io/
-[TLSRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.TLSRoute
-[ReferenceGrant]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1.ReferenceGrant
-[SecretObjectReference]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.SecretObjectReference
-[rate limiting]: https://gateway.envoyproxy.io/v0.6.0/user/rate-limit.html
-[request authentication]: https://gateway.envoyproxy.io/v0.6.0/user/authn.html
-[EnvoyProxy]: https://gateway.envoyproxy.io/v0.6.0/api/config_types.html#envoyproxy
+[TLSRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.TLSRoute
+[ReferenceGrant]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.ReferenceGrant
+[SecretObjectReference]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.SecretObjectReference
+[rate limiting]: ../rate-limit/
+[request authentication]: ../jwt-authentication/
+[EnvoyProxy]: ../../api/extension_types#envoyproxy
 [resolving conflicts]: https://gateway-api.sigs.k8s.io/concepts/guidelines/?h=conflict#conflicts
-[ExtensionRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilterType
-[grpc-filter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter
+[ExtensionRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteFilterType
+[grpc-filter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteFilter
+[http-filter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteFilter
diff --git a/site/content/en/v0.6.0/user/grafana-integration.md b/site/content/en/v0.6.0/user/grafana-integration.md
index 07ec52b7257..d8acf06f669 100644
--- a/site/content/en/v0.6.0/user/grafana-integration.md
+++ b/site/content/en/v0.6.0/user/grafana-integration.md
@@ -10,7 +10,7 @@ This guide shows you how to visualise the metrics exposed to prometheus using gr
 Follow the steps from the [Quickstart Guide](../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
-Follow the steps from the [Proxy Observability](proxy-observability.md#Metrics) to enable prometheus metrics.
+Follow the steps from the [Proxy Observability](../proxy-observability#Metrics) to enable prometheus metrics.
 
 [Prometheus](https://prometheus.io) is used to scrape metrics from the Envoy Proxy instances. Install Prometheus:
 
diff --git a/site/content/en/v0.6.0/user/http-request-headers.md b/site/content/en/v0.6.0/user/http-request-headers.md
index 0dbdbe13d3b..25b675a16d7 100644
--- a/site/content/en/v0.6.0/user/http-request-headers.md
+++ b/site/content/en/v0.6.0/user/http-request-headers.md
@@ -26,7 +26,7 @@ header in the request.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -109,7 +109,7 @@ filter.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -180,7 +180,7 @@ filter.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -245,7 +245,7 @@ Headers can be added/set/removed in a single filter on the same HTTPRoute and th
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -280,6 +280,6 @@ EOF
 ```
 
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
-[HTTPRoute filters]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteFilter
+[HTTPRoute filters]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteFilter
 [Gateway API documentation]: https://gateway-api.sigs.k8s.io/
-[req_filter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPHeaderFilter
+[req_filter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPHeaderFilter
diff --git a/site/content/en/v0.6.0/user/http-request-mirroring.md b/site/content/en/v0.6.0/user/http-request-mirroring.md
index aaea240f5ca..db6bcca33f2 100644
--- a/site/content/en/v0.6.0/user/http-request-mirroring.md
+++ b/site/content/en/v0.6.0/user/http-request-mirroring.md
@@ -2,7 +2,7 @@
 title: "HTTPRoute Request Mirroring"
 ---
 
-The [HTTPRoute][] resource allows one or more [backendRefs][] to be provided. Requests will be routed to these upstreams. It is possible to divide the traffic between these backends using [Traffic Splitting](http-traffic-splitting.md), but it is also possible to mirror requests to another Service instead. Request mirroring is accomplished using Gateway API's [HTTPRequestMirrorFilter][] on the `HTTPRoute`.
+The [HTTPRoute][] resource allows one or more [backendRefs][] to be provided. Requests will be routed to these upstreams. It is possible to divide the traffic between these backends using [Traffic Splitting](../http-traffic-splitting/), but it is also possible to mirror requests to another Service instead. Request mirroring is accomplished using Gateway API's [HTTPRequestMirrorFilter][] on the `HTTPRoute`.
 
 When requests are made to a `HTTPRoute` that uses a `HTTPRequestMirrorFilter`, the response will never come from the `backendRef` defined in the filter. Responses from the mirror `backendRef` are always ignored.
 
@@ -79,7 +79,7 @@ service from the quickstart, and mirror request to the service that was just dep
 
 ```shell
 kubectl apply -f - <<EOF
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-mirror
@@ -166,7 +166,7 @@ When an `HTTPRoute` has multiple `backendRefs` and an `HTTPRequestMirrorFilter`,
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-mirror
@@ -205,7 +205,7 @@ Multiple `HTTPRequestMirrorFilters` are not supported on the same `HTTPRoute` `r
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-mirror
@@ -244,7 +244,7 @@ EOF
 Error from server: error when creating "STDIN": admission webhook "validate.gateway.networking.k8s.io" denied the request: spec.rules[0].filters: Invalid value: "RequestMirror": cannot be used multiple times in the same rule
 ```
 
-[Quickstart Guide]: quickstart.md
+[Quickstart Guide]: ../quickstart/
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
-[backendRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.BackendRef
-[HTTPRequestMirrorFilter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRequestMirrorFilter
+[backendRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendRef
+[HTTPRequestMirrorFilter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRequestMirrorFilter
diff --git a/site/content/en/v0.6.0/user/http-response-headers.md b/site/content/en/v0.6.0/user/http-response-headers.md
index 9a0c3e38386..76cf33362b4 100644
--- a/site/content/en/v0.6.0/user/http-response-headers.md
+++ b/site/content/en/v0.6.0/user/http-response-headers.md
@@ -24,7 +24,7 @@ value of the header in the response.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -107,7 +107,7 @@ filter.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -179,7 +179,7 @@ filter.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -244,7 +244,7 @@ Headers can be added/set/removed in a single filter on the same HTTPRoute and th
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -280,4 +280,4 @@ EOF
 
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
 [Gateway API documentation]: https://gateway-api.sigs.k8s.io/
-[req_filter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPHeaderFilter
+[req_filter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPHeaderFilter
diff --git a/site/content/en/v0.6.0/user/http-routing.md b/site/content/en/v0.6.0/user/http-routing.md
index ae3a581306c..ab1e3118655 100644
--- a/site/content/en/v0.6.0/user/http-routing.md
+++ b/site/content/en/v0.6.0/user/http-routing.md
@@ -134,4 +134,4 @@ traffic was routed to the foo backend service.
 [GatewayClass]: https://gateway-api.sigs.k8s.io/api-types/gatewayclass/
 [Gateway]: https://gateway-api.sigs.k8s.io/api-types/gateway/
 [Envoy proxy]: https://www.envoyproxy.io/
-[spec]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteSpec
+[spec]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteSpec
diff --git a/site/content/en/v0.6.0/user/http-traffic-splitting.md b/site/content/en/v0.6.0/user/http-traffic-splitting.md
index 960adbcc2ea..49e6ca89c2f 100644
--- a/site/content/en/v0.6.0/user/http-traffic-splitting.md
+++ b/site/content/en/v0.6.0/user/http-traffic-splitting.md
@@ -17,7 +17,7 @@ When a single backendRef is configured in a HTTPRoute, it will receive 100% of t
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -149,7 +149,7 @@ Then create an HTTPRoute that uses both the app from the quickstart and the seco
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -219,7 +219,7 @@ backend-2 service.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -265,7 +265,7 @@ with status code `500`.
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-headers
@@ -310,4 +310,4 @@ $ curl -vvv --header "Host: backends.example" "http://${GATEWAY_HOST}/get"
 ```
 
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
-[backendRefs]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.BackendRef
+[backendRefs]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.BackendRef
diff --git a/site/content/en/v0.6.0/user/http-urlrewrite.md b/site/content/en/v0.6.0/user/http-urlrewrite.md
index 60c0bebeeef..945a24a7a44 100644
--- a/site/content/en/v0.6.0/user/http-urlrewrite.md
+++ b/site/content/en/v0.6.0/user/http-urlrewrite.md
@@ -17,7 +17,7 @@ You can configure to rewrite the prefix in the url like below. In this example,
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-filter-url-rewrite
@@ -116,7 +116,7 @@ You can configure to rewrite the fullpath in the url like below. In this example
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-filter-url-rewrite
@@ -210,7 +210,7 @@ You can configure to rewrite the hostname like below. In this example, any reque
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-filter-url-rewrite
@@ -294,4 +294,4 @@ $ curl -L -vvv --header "Host: path.rewrite.example" "http://${GATEWAY_HOST}/get
 
 You can see that the `X-Forwarded-Host` is `path.rewrite.example`, but the actual host is `envoygateway.io`.
 
-[HTTPURLRewriteFilter]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPURLRewriteFilter
+[HTTPURLRewriteFilter]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPURLRewriteFilter
diff --git a/site/content/en/v0.6.0/user/jwt-authentication.md b/site/content/en/v0.6.0/user/jwt-authentication.md
index 213d75c5d09..e11358c22fa 100644
--- a/site/content/en/v0.6.0/user/jwt-authentication.md
+++ b/site/content/en/v0.6.0/user/jwt-authentication.md
@@ -12,7 +12,7 @@ This instantiated resource can be linked to a [Gateway][Gateway], [HTTPRoute][HT
 ## Prerequisites
 
 Follow the steps from the [Quickstart](../quickstart) guide to install Envoy Gateway and the example manifest.
-For GRPC - follow the steps from the [GRPC Routing](grpc-routing.md) example.
+For GRPC - follow the steps from the [GRPC Routing](../grpc-routing/) example.
 Before proceeding, you should be able to query the example backend using HTTP or GRPC.
 
 ## Configuration
@@ -162,7 +162,7 @@ kubectl delete securitypolicy/jwt-example
 
 Checkout the [Developer Guide](../../contributions/develop/) to get involved in the project.
 
-[SecurityPolicy]: https://gateway.envoyproxy.io/v0.6.0/design/security-policy
+[SecurityPolicy]: ../../design/security-policy
 [jwt]: https://tools.ietf.org/html/rfc7519
 [jwks]: https://tools.ietf.org/html/rfc7517
 [Gateway]: https://gateway-api.sigs.k8s.io/api-types/gateway
diff --git a/site/content/en/v0.6.0/user/rate-limit.md b/site/content/en/v0.6.0/user/rate-limit.md
index 027a26cd69e..c3078d1cd95 100644
--- a/site/content/en/v0.6.0/user/rate-limit.md
+++ b/site/content/en/v0.6.0/user/rate-limit.md
@@ -158,7 +158,7 @@ EOF
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-ratelimit
@@ -310,7 +310,7 @@ EOF
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-ratelimit
@@ -441,7 +441,7 @@ EOF
 
 ```shell
 cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-ratelimit
@@ -533,7 +533,7 @@ spec:
           requests: 3
           unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: http-ratelimit
@@ -634,7 +634,7 @@ spec:
           requests: 3
           unit: Hour
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: example
@@ -821,9 +821,9 @@ kubectl rollout restart deployment envoy-gateway -n envoy-gateway-system
 ```
 
 [Global Rate Limiting]: https://www.envoyproxy.io/docs/envoy/v0.6.0/intro/arch_overview/other_features/global_rate_limiting
-[BackendTrafficPolicy]: https://gateway.envoyproxy.io/v0.6.0/api/extension_types.html#backendtrafficpolicy
+[BackendTrafficPolicy]: ../../api/extension_types#backendtrafficpolicy
 [Envoy Ratelimit]: https://github.com/envoyproxy/ratelimit
-[EnvoyGateway]: https://gateway.envoyproxy.io/v0.6.0/api/config_types.html#envoygateway
+[EnvoyGateway]: ../../api/extension_types#envoygateway
 [Gateway]: https://gateway-api.sigs.k8s.io/api-types/gateway/
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/api-types/httproute/
 [GRPCRoute]: https://gateway-api.sigs.k8s.io/api-types/grpcroute/
diff --git a/site/content/en/v0.6.0/user/secure-gateways.md b/site/content/en/v0.6.0/user/secure-gateways.md
index dba8d3a972b..805aeb8b1a6 100644
--- a/site/content/en/v0.6.0/user/secure-gateways.md
+++ b/site/content/en/v0.6.0/user/secure-gateways.md
@@ -173,7 +173,7 @@ namespace to reference Secrets in the "envoy-gateway-system" namespace:
 
 ```console
 $ cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1alpha2
 kind: ReferenceGrant
 metadata:
   name: example
@@ -212,7 +212,7 @@ Update the Gateway HTTPS listener with `namespace: envoy-gateway-system`, for ex
 
 ```console
 $ cat <<EOF | kubectl apply -f -
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: eg
@@ -260,11 +260,11 @@ This section gives a walkthrough to generate RSA and ECDSA derived certificates
 Follow the steps from the [Quickstart Guide](../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
-Follow the steps in the [TLS Certificates](secure-gateways.md#tls-certificates) section in the guide to generate self-signed RSA derived Server certificate and private key, and configure those in the Gateway listener configuration to terminate HTTPS traffic.
+Follow the steps in the [TLS Certificates](../secure-gateways#tls-certificates) section in the guide to generate self-signed RSA derived Server certificate and private key, and configure those in the Gateway listener configuration to terminate HTTPS traffic.
 
 ## Pre-checks
 
-While testing in [Cluster without External LoadBalancer Support](secure-gateways.md#clusters-without-external-loadbalancer-support), we can query the example app through Envoy proxy while enforcing an RSA cipher, as shown below:
+While testing in [Cluster without External LoadBalancer Support](../secure-gateways#clusters-without-external-loadbalancer-support), we can query the example app through Envoy proxy while enforcing an RSA cipher, as shown below:
 
 ```shell
 curl -v -HHost:www.example.com --resolve "www.example.com:8443:127.0.0.1" \
@@ -295,7 +295,7 @@ Moving forward in the doc, we will be configuring the existing Gateway listener
 
 ## TLS Certificates
 
-Reuse the the CA certificate and key pair generated in the [Secure Gateways](secure-gateways.md#tls-certificates) guide and use this CA to sign both RSA and ECDSA Server certificates.
+Reuse the CA certificate and key pair generated in the [Secure Gateways](../secure-gateways#tls-certificates) guide and use this CA to sign both RSA and ECDSA Server certificates.
 Note the CA certificate and key names are `example.com.crt` and `example.com.key` respectively.
 
 
@@ -372,11 +372,11 @@ This sections gives a walkthrough to generate multiple certificates correspondin
 Follow the steps from the [Quickstart Guide](../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
-Follow the steps in the [TLS Certificates](secure-gateways.md#tls-certificates) section in the guide to generate self-signed RSA derived Server certificate and private key, and configure those in the Gateway listener configuration to terminate HTTPS traffic.
+Follow the steps in the [TLS Certificates](../secure-gateways#tls-certificates) section in the guide to generate self-signed RSA derived Server certificate and private key, and configure those in the Gateway listener configuration to terminate HTTPS traffic.
 
 ## Additional Configurations
 
-Using the [TLS Certificates](secure-gateways.md#tls-certificates) section in the guide we first generate additional Secret for another Host `www.sample.com`.
+Using the [TLS Certificates](../secure-gateways#tls-certificates) section in the guide we first generate additional Secret for another Host `www.sample.com`.
 
 ```shell
 openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -subj '/O=sample Inc./CN=sample.com' -keyout sample.com.key -out sample.com.crt
@@ -446,7 +446,7 @@ Since the multiple certificates are configured on the same Gateway listener, Env
 
 ### Clusters with External LoadBalancer Support
 
-Refer to the steps mentioned earlier in the guide under [Testing in clusters with External LoadBalancer Support](secure-gateways.md#clusters-with-external-loadbalancer-support)
+Refer to the steps mentioned earlier in the guide under [Testing in clusters with External LoadBalancer Support](../secure-gateways#clusters-with-external-loadbalancer-support)
 
 ## Next Steps
 
diff --git a/site/content/en/v0.6.0/user/tcp-routing.md b/site/content/en/v0.6.0/user/tcp-routing.md
index 2aa083ec8a1..a31e57744d7 100644
--- a/site/content/en/v0.6.0/user/tcp-routing.md
+++ b/site/content/en/v0.6.0/user/tcp-routing.md
@@ -35,13 +35,13 @@ Install the GatewayClass and a `tcp-gateway` Gateway first.
 ```shell
 cat <<EOF | kubectl apply -f -
 kind: GatewayClass
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 metadata:
   name: eg
 spec:
   controllerName: gateway.envoyproxy.io/gatewayclass-controller
 ---
-apiVersion: gateway.networking.k8s.io/v1beta1
+apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: tcp-gateway
@@ -300,5 +300,5 @@ Content-Length: 267
 
 You can see that the traffic routing to `bar` service when sending request to `8089` port.
 
-[TCPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute
+[TCPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute
 [Gateway API documentation]: https://gateway-api.sigs.k8s.io/
diff --git a/site/content/en/v0.6.0/user/tls-cert-manager.md b/site/content/en/v0.6.0/user/tls-cert-manager.md
index ae45758fda7..7776fbb2413 100644
--- a/site/content/en/v0.6.0/user/tls-cert-manager.md
+++ b/site/content/en/v0.6.0/user/tls-cert-manager.md
@@ -432,5 +432,5 @@ eg-https   kubernetes.io/tls   3      42m
 
 ## See Also
 
-* [Secure Gateways](secure-gateways.md)
+* [Secure Gateways](../secure-gateways/)
 * [Securing gateway.networking.k8s.io Gateway Resources](https://cert-manager.io/docs/usage/gateway/)
diff --git a/site/content/en/v0.6.0/user/udp-routing.md b/site/content/en/v0.6.0/user/udp-routing.md
index 29c4111d2cb..8d80fe789cf 100644
--- a/site/content/en/v0.6.0/user/udp-routing.md
+++ b/site/content/en/v0.6.0/user/udp-routing.md
@@ -152,5 +152,5 @@ kubectl delete udproute/coredns
 
 Checkout the [Developer Guide](../../contributions/develop/) to get involved in the project.
 
-[UDPRoute]: https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.UDPRoute
+[UDPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.UDPRoute
 [UDP proxy documentation]: https://www.envoyproxy.io/docs/envoy/v0.6.0/configuration/listeners/udp_filters/udp_proxy