docs: fix broken section anchors in 2-edge and 2.19

linkerd.io/content/2-edge/reference/authorization-policy.md

@@ -187,7 +187,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd:
 The two HTTPRoute resource definitions are similar, but the Linkerd version
 implements experimental features not yet available with the upstream Gateway API
 resource definition. See
-[the HTTPRoute reference documentation](httproute/#linkerd-and-gateway-api-httproutes)
+[the HTTPRoute reference documentation](httproute/#the-policylinkerdio-group)
 for details.
 
 {{< /note >}}

linkerd.io/content/2-edge/reference/circuit-breaking.md

@@ -206,9 +206,9 @@ configure parameters for the unified failure accrual policy:
 [circuit-breaker]: https://www.martinfowler.com/bliki/CircuitBreaker.html
 [503 Service Unavailable]:
   https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503
-[metric]: proxy-metrics/#outbound-xroute-metrics
+[metric]: proxy-metrics/#endpoint-metrics
 [5xx server error]:
   https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#server_error_responses
 [exp-backoff]:
   https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/
-[outbound]: architecture/#meshed-conncections
+[outbound]: architecture/#meshed-connections

linkerd.io/content/2-edge/tasks/configuring-per-route-policy.md

@@ -196,7 +196,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd:
 The two HTTPRoute resource definitions are similar, but the Linkerd version
 implements experimental features not yet available with the upstream Gateway API
 resource definition. See
-[the HTTPRoute reference documentation](../reference/httproute/#linkerd-and-gateway-api-httproutes)
+[the HTTPRoute reference documentation](../reference/httproute/#the-policylinkerdio-group)
 for details.
 
 {{< /note >}}

linkerd.io/content/2-edge/tasks/fault-injection.md

@@ -181,7 +181,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd:
 The two HTTPRoute resource definitions are similar, but the Linkerd version
 implements experimental features not yet available with the upstream Gateway API
 resource definition. See
-[the HTTPRoute reference documentation](../reference/httproute/#linkerd-and-gateway-api-httproutes)
+[the HTTPRoute reference documentation](../reference/httproute/#the-policylinkerdio-group)
 for details.
 
 {{< /note >}}

linkerd.io/content/2-edge/tasks/multicluster.md

@@ -78,7 +78,7 @@ certificates that it receives from peers as part of the mTLS handshake. With a
 common base of trust, we now need to generate a certificate that can be used in
 each cluster to issue certificates to the proxies. If you'd like to get a deeper
 picture into how this all works, check out the
-[deep dive](../features/automatic-mtls/#how-does-it-work).
+[deep dive](../features/automatic-mtls/#how-does-linkerds-mtls-implementation-work).
 
 The trust anchor that we've generated is a self-signed certificate which can be
 used to create new certificates (a certificate authority). To generate the

linkerd.io/content/2-edge/tasks/troubleshooting.md

@@ -2027,7 +2027,7 @@ Example failure:
 ```
 
 This warning indicates that the listed pods have the
-[`deny` default inbound policy](../features/server-policy/#policy-annotations),
+[`deny` default inbound policy](../features/server-policy/#default-policies),
 which may prevent the `linkerd-viz` Prometheus instance from scraping the data
 plane proxies in those pods. If Prometheus cannot scrape a data plane pod,
 `linkerd viz` commands targeting that pod will return no data.

linkerd.io/content/2-edge/tasks/upgrade.md

@@ -110,7 +110,7 @@ linkerd prune | kubectl delete -f -
 ### Upgrading the control plane with Helm
 
 For Helm control plane installations, please follow the instructions at
-[Helm upgrade procedure](install-helm/#helm-upgrade-procedure).
+[Helm upgrade procedure](install-helm/#upgrading-with-helm).
 
 ### Verifying the control plane upgrade
 

linkerd.io/content/2.19/reference/authorization-policy.md

@@ -187,7 +187,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd:
 The two HTTPRoute resource definitions are similar, but the Linkerd version
 implements experimental features not yet available with the upstream Gateway API
 resource definition. See
-[the HTTPRoute reference documentation](httproute/#linkerd-and-gateway-api-httproutes)
+[the HTTPRoute reference documentation](httproute/#the-policylinkerdio-group)
 for details.
 
 {{< /note >}}

linkerd.io/content/2.19/reference/circuit-breaking.md

@@ -157,9 +157,9 @@ configure parameters for the consecutive-failures failure accrual policy:
 [circuit-breaker]: https://www.martinfowler.com/bliki/CircuitBreaker.html
 [503 Service Unavailable]:
   https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503
-[metric]: proxy-metrics/#outbound-xroute-metrics
+[metric]: proxy-metrics/#endpoint-metrics
 [5xx server error]:
   https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#server_error_responses
 [exp-backoff]:
   https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/
-[outbound]: architecture/#meshed-conncections
+[outbound]: architecture/#meshed-connections

linkerd.io/content/2.19/tasks/configuring-per-route-policy.md

@@ -196,7 +196,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd:
 The two HTTPRoute resource definitions are similar, but the Linkerd version
 implements experimental features not yet available with the upstream Gateway API
 resource definition. See
-[the HTTPRoute reference documentation](../reference/httproute/#linkerd-and-gateway-api-httproutes)
+[the HTTPRoute reference documentation](../reference/httproute/#the-policylinkerdio-group)
 for details.
 
 {{< /note >}}

linkerd.io/content/2.19/tasks/fault-injection.md

@@ -181,7 +181,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd:
 The two HTTPRoute resource definitions are similar, but the Linkerd version
 implements experimental features not yet available with the upstream Gateway API
 resource definition. See
-[the HTTPRoute reference documentation](../reference/httproute/#linkerd-and-gateway-api-httproutes)
+[the HTTPRoute reference documentation](../reference/httproute/#the-policylinkerdio-group)
 for details.
 
 {{< /note >}}

linkerd.io/content/2.19/tasks/multicluster.md

@@ -78,7 +78,7 @@ certificates that it receives from peers as part of the mTLS handshake. With a
 common base of trust, we now need to generate a certificate that can be used in
 each cluster to issue certificates to the proxies. If you'd like to get a deeper
 picture into how this all works, check out the
-[deep dive](../features/automatic-mtls/#how-does-it-work).
+[deep dive](../features/automatic-mtls/#how-does-linkerds-mtls-implementation-work).
 
 The trust anchor that we've generated is a self-signed certificate which can be
 used to create new certificates (a certificate authority). To generate the

linkerd.io/content/2.19/tasks/troubleshooting.md

@@ -1854,7 +1854,7 @@ Example failure:
 ```
 
 This warning indicates that the listed pods have the
-[`deny` default inbound policy](../features/server-policy/#policy-annotations),
+[`deny` default inbound policy](../features/server-policy/#default-policies),
 which may prevent the `linkerd-viz` Prometheus instance from scraping the data
 plane proxies in those pods. If Prometheus cannot scrape a data plane pod,
 `linkerd viz` commands targeting that pod will return no data.

linkerd.io/content/2.19/tasks/upgrade.md

@@ -110,7 +110,7 @@ linkerd prune | kubectl delete -f -
 ### Upgrading the control plane with Helm
 
 For Helm control plane installations, please follow the instructions at
-[Helm upgrade procedure](install-helm/#helm-upgrade-procedure).
+[Helm upgrade procedure](install-helm/#upgrading-with-helm).
 
 ### Verifying the control plane upgrade