Fix a bunch of broken links (sigh)

Signed-off-by: [email protected]

site-src/concepts/api-overview.md

@@ -295,7 +295,7 @@ reverse proxy is:
 6. Lastly, the reverse proxy forwards the request to one or more objects, i.e.
    `Service`, in the cluster based on `backendRefs` rules of the `HTTPRoute`.
 
-[north/south]:/concepts/glossary#north-south-traffic
+[north/south]:/concepts/glossary#northsouth-traffic
 
 ### TLS Configuration
 
@@ -335,10 +335,11 @@ important:
     Namespace.
 
 [Ana]:/concepts/roles-and-personas#ana
-[producer route]:/concepts/glossary#provider-route
+[producer route]:/concepts/glossary#producer-route
 [consumer route]:/concepts/glossary#consumer-route
 [GAMMA]:/contributing/gamma
 [service mesh]:/concepts/glossary#service-mesh
+[Route merging rules]:/api-types/httproute#merging
 
 ### How it Works
 
@@ -365,7 +366,7 @@ A typical [east/west] API request flow is:
    likely using [endpoint routing], but it is allowed to use [Service
    routing]).
 
-[east/west]:/concepts/glossary#east-west-traffic
+[east/west]:/concepts/glossary#eastwest-traffic
 [endpoint routing]:/concepts/glossary#endpoint-routing
 [Service routing]:/concepts/glossary#service-routing
 

site-src/concepts/service-facets.md

@@ -42,7 +42,7 @@ endpoint routing can be more predictable when using the Gateway API for both
 formalize guidance for this use case.
 
 [Service]: https://kubernetes.io/docs/concepts/services-networking/service/
-[north/south]:/concepts/glossary#north-south-traffic
-[east/west traffic]:/concepts/glossary#east-west-traffic
+[north/south]:/concepts/glossary#northsouth-traffic
+[east/west traffic]:/concepts/glossary#eastwest-traffic
 [gamma]:/contributing/gamma/
 [Ana]:/concepts/roles-and-personas#ana

site-src/concepts/use-cases.md

@@ -19,10 +19,10 @@ they all have distinct concerns that we need to consider separately.)
 
 ## The Use Cases
 
-- [Basic north/south use case](#basic-north-south-use-case)
+- [Basic north/south use case](#basic-northsouth-use-case)
 - [Multiple applications behind a single
   Gateway](#multiple-applications-behind-a-single-gateway)
-- [Basic east/west use case](#basic-east-west-use-case)
+- [Basic east/west use case](#basic-eastwest-use-case)
 - [Gateway and mesh use case](#gateway-and-mesh-use-case)
 
 [role and personas]:/concepts/roles-and-personas
@@ -76,12 +76,12 @@ Ana and her colleagues control over the application's [routing
 logic](/guides/http-routing) and rollout plans (e.g. [traffic splitting
 rollouts](/guides/traffic-splitting)).
 
-[north/south]:/concepts/glossary#north-south-traffic
+[north/south]:/concepts/glossary#northsouth-traffic
 
 ## Multiple applications behind a single Gateway
 
 This is remarkably similar to the [basic north/south use
-case](#basic-north-south-use-case), but there are multiple application teams:
+case](#basic-northsouth-use-case), but there are multiple application teams:
 Ana and her team are managing a storefront application in the `store`
 Namespace, while Allison and her team are managing a website in the `site`
 Namespace.
@@ -131,15 +131,15 @@ In this case, the separation of concerns across roles allows Ana to take
 advantage of the service mesh, with custom routing logic, without any
 bottlenecks in requests to Charlie or Ian.
 
-[east/west]:/concepts/glossary#east-west-traffic
+[east/west]:/concepts/glossary#eastwest-traffic
 [GAMMA]:/contributing/gamma/
 [service mesh]:/concepts/glossary#service-mesh
 
 ## Gateway and mesh use case
 
-This is effectively a combination of the `multiple applications behind a
+This is effectively a combination of the [multiple applications behind a
 single Gateway](#multiple-applications-behind-a-single-gateway) and [basic
-east/west](#basic-east-west-use-case) use cases:
+east/west](#basic-eastwest-use-case) use cases:
 
 - Charlie and Ian will provision a cluster, a [GatewayClass], and a [Gateway].
 

site-src/index.md

@@ -41,7 +41,7 @@ nature of the Gateway API, as well as allowing for multiple kinds of gateway
 controllers (represented by GatewayClass resources), each with multiple
 instances (represented by Gateway resources), in the same cluster.
 
-[north/south traffic]:/concepts/glossary#north-south-traffic
+[north/south traffic]:/concepts/glossary#northsouth-traffic
 [gateway controller]:/concepts/glossary#gateway-controller
 [gateway-attachment]:/concepts/api-overview#attaching-routes-to-gateways
 
@@ -61,7 +61,7 @@ definition of the different [facets of the Service resource][service-facets].
 
 [gamma]:/contributing/gamma/
 [service-mesh]:/concepts/glossary#service-mesh
-[service-facets]:/concepts/service-facets.md
+[service-facets]:/concepts/service-facets
 [mesh-attachment]:/concepts/api-overview#attaching-routes-to-services
 
 ## Getting started