docs: fix broken links (#4217)

* docs: fix broken links

* fix

* address review comment

* fix

* fix

Author: zirain

site-src/api-types/backendtlspolicy.md

@@ -164,12 +164,12 @@ Status defines the observed state of the BackendTLSPolicy and is not user-config
 way you do for other Gateway API objects to verify correct operation.  Note that the status in BackendTLSPolicy
 uses `PolicyAncestorStatus` to allow you to know which parentReference set that particular status.
 
-[backendtlspolicy]: ../reference/spec.md#gateway.networking.k8s.io/v1alpha3.BackendTLSPolicy
-[validation]: ../reference/spec.md#gateway.networking.k8s.io/v1alpha3.BackendTLSPolicy.Validation
-[caCertificateRefs]: ../reference/spec.md#gateway.networking.k8s.io/v1alpha3.BackendTLSPolicyValidation.CACertificateRefs
-[wellKnownCACertificates]: ../reference/spec.md#gateway.networking.k8s.io/v1alpha3.BackendTLSPolicyValidation.WellKnownCACertificates
-[hostname]: ../reference/spec.md#gateway.networking.k8s.io/v1.PreciseHostname
+[backendtlspolicy]: ../reference/spec.md#backendtlspolicy
+[validation]: ../reference/spec.md#backendtlspolicyvalidation
+[caCertificateRefs]: ../reference/spec.md#localobjectreference
+[wellKnownCACertificates]: ../reference/spec.md#localobjectreference
+[hostname]: ../reference/spec.md#precisehostname
 [rfc-3986]: https://tools.ietf.org/html/rfc3986
-[targetRefs]: ../references/spec/#gateway.networking.k8s.io/v1alpha2.PolicyTargetReference
-[subjectAltNames]: ../references/spec/#gateway.networking.k8s.io/v1alpha3.BackendTLSPolicyValidation 
-[options]: ../references/spec/#gateway.networking.k8s.io/v1alpha3.GatewayTLSConfig
+[targetRefs]: ../reference/spec.md#localpolicytargetreferencewithsectionname
+[subjectAltNames]: ../reference/spec.md#subjectaltname
+[options]: ../reference/spec.md#backendtlspolicyspec

site-src/api-types/gatewayclass.md

@@ -141,5 +141,5 @@ example.net/gateway/v2.1 // Use version 2.1
 example.net/gateway      // Use the default version
 ```
 
-[gatewayclass]: ../reference/spec.md#gateway.networking.k8s.io/v1.GatewayClass
+[gatewayclass]: ../reference/spec.md#gatewayclass
 [ingress-class-api]: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class

site-src/api-types/grpcroute.md

@@ -272,12 +272,12 @@ Multiple GRPCRoutes can be attached to a single Gateway resource. Importantly,
 only one Route rule may match each request. For more information on how conflict
 resolution applies to merging, refer to the [API specification][grpcrouterule].
 
-[grpcroute]: ../reference/spec.md#gateway.networking.k8s.io/v1.GRPCRoute
-[grpcrouterule]: ../reference/spec.md#gateway.networking.k8s.io/v1.GRPCRouteRule
-[hostname]: ../reference/spec.md#gateway.networking.k8s.io/v1.Hostname
+[grpcroute]: ../reference/spec.md#grpcroute
+[grpcrouterule]: ../reference/spec.md#grpcrouterule
+[hostname]: ../reference/spec.md#hostname
 [rfc-3986]: https://tools.ietf.org/html/rfc3986
-[matches]: ../reference/spec.md#gateway.networking.k8s.io/v1.GRPCRouteMatch
-[filters]: ../reference/spec.md#gateway.networking.k8s.io/v1.GRPCRouteFilter
-[backendRef]: ../reference/spec.md#gateway.networking.k8s.io/v1.GRPCBackendRef
-[parentRef]: ../reference/spec.md#gateway.networking.k8s.io/v1.ParentRef
-[name]: ../reference/spec.md#gateway.networking.k8s.io/v1.SectionName
+[matches]: ../reference/spec.md#grpcroutematch
+[filters]: ../reference/spec.md#grpcroutefilter
+[backendRef]: ../reference/spec.md#grpcbackendref
+[parentRef]: ../reference/spec.md#parentreference
+[name]: ../reference/spec.md#sectionname

site-src/api-types/httproute.md

@@ -336,14 +336,14 @@ only one Route rule may match each request. For more information on how conflict
 resolution applies to merging, refer to the [API specification][httprouterule].
 
 
-[httproute]: ../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRoute
-[httprouterule]: ../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteRule
-[hostname]: ../reference/spec.md#gateway.networking.k8s.io/v1.Hostname
+[httproute]: ../reference/spec.md#httproute
+[httprouterule]: ../reference/spec.md#httprouterule
+[hostname]: ../reference/spec.md#hostname
 [rfc-3986]: https://tools.ietf.org/html/rfc3986
-[matches]: ../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteMatch
-[filters]: ../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteFilter
-[backendRef]: ../reference/spec.md#gateway.networking.k8s.io/v1.HTTPBackendRef
-[parentRef]: ../reference/spec.md#gateway.networking.k8s.io/v1.ParentRef
-[timeouts]: ../reference/spec.md#gateway.networking.k8s.io/v1.HTTPRouteTimeouts
+[matches]: ../reference/spec.md#httproutematch
+[filters]: ../reference/spec.md#httproutefilter
+[backendRef]: ../reference/spec.md#httpbackendref
+[parentRef]: ../reference/spec.md#parentreference
+[timeouts]: ../reference/spec.md#httproutetimeouts
 [appProtocol]: https://kubernetes.io/docs/concepts/services-networking/service/#application-protocol
-[sectionName]: ../reference/spec.md#gateway.networking.k8s.io/v1.SectionName
+[sectionName]: ../reference/spec.md#sectionname

site-src/api-types/referencegrant.md

@@ -90,7 +90,7 @@ While the API is simplistic in nature, it comes with a few notable decisions:
    other. This makes it impossible for them to conflict with each other.
 
 Please see the [API
-Specification](../reference/spec.md#gateway.networking.k8s.io/v1alpha2.ReferenceGrant)
+Specification](../reference/spec.md#referencegrant)
 for more details on how specific ReferenceGrant fields are interpreted.
 
 ## Implementation Guidelines