Merge pull request #44595 from tengqm/fix-links

Fix several link errors

content/en/docs/concepts/cluster-administration/flow-control.md

@@ -47,7 +47,7 @@ are not subject to the `--max-requests-inflight` limit.
 
 The API Priority and Fairness feature is controlled by a command-line flag
 and is enabled by default.  See 
-[Options](/docs/reference/command-line-tools-reference/kube-apiserver/options/)
+[Options](/docs/reference/command-line-tools-reference/kube-apiserver/#options)
 for a general explanation of the available kube-apiserver command-line 
 options and how to enable and disable them.  The name of the 
 command-line option for APF is "--enable-priority-and-fairness".  This feature

content/en/docs/concepts/scheduling-eviction/assign-pod-node.md

@@ -306,7 +306,7 @@ Pod affinity rule uses the "hard"
 uses the "soft" `preferredDuringSchedulingIgnoredDuringExecution`.
 
 The affinity rule specifies that the scheduler is allowed to place the example Pod 
-on a node only if that node belongs to a specific [zone](/docs/concepts/scheduling-eviction/topology-spread-constraints/topology-spread-constraints/)
+on a node only if that node belongs to a specific [zone](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
 where other Pods have been labeled with `security=S1`. 
 For instance, if we have a cluster with a designated zone, let's call it "Zone V," 
 consisting of nodes labeled with `topology.kubernetes.io/zone=V`, the scheduler can 
@@ -315,7 +315,7 @@ Zone V already labeled with `security=S1`. Conversely, if there are no Pods with
 labels in Zone V, the scheduler will not assign the example Pod to any node in that zone.
 
 The anti-affinity rule specifies that the scheduler should try to avoid scheduling the Pod 
-on a node if that node belongs to a specific [zone](/docs/concepts/scheduling-eviction/topology-spread-constraints/topology-spread-constraints/)
+on a node if that node belongs to a specific [zone](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
 where other Pods have been labeled with `security=S2`. 
 For instance, if we have a cluster with a designated zone, let's call it "Zone R," 
 consisting of nodes labeled with `topology.kubernetes.io/zone=R`, the scheduler should avoid 

content/en/docs/concepts/services-networking/gateway.md

@@ -191,7 +191,7 @@ guide for details on migrating Ingress resources to Gateway API resources.
 ## {{% heading "whatsnext" %}}
 
 Instead of Gateway API resources being natively implemented by Kubernetes, the specifications
-are defined as [Custom Resources](docs/concepts/extend-kubernetes/api-extension/custom-resources)
+are defined as [Custom Resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
 supported by a wide range of [implementations](https://gateway-api.sigs.k8s.io/implementations/).
 [Install](https://gateway-api.sigs.k8s.io/guides/#installing-gateway-api) the Gateway API CRDs or
 follow the installation instructions of your selected implementation. After installing an

content/en/docs/concepts/storage/persistent-volumes.md

@@ -578,9 +578,7 @@ mounting of NFS filesystems.
 ### Capacity
 
 Generally, a PV will have a specific storage capacity. This is set using the PV's
-`capacity` attribute. Read the glossary term
-[Quantity](/docs/reference/glossary/?all=true#term-quantity) to understand the units
-expected by `capacity`.
+`capacity` attribute which is a {{< glossary_tooltip term_id="quantity" >}} value.
 
 Currently, storage size is the only resource that can be set or requested.
 Future attributes may include IOPS, throughput, etc.

content/en/docs/reference/command-line-tools-reference/feature-gates/network-policy-end-port.md

@@ -22,5 +22,5 @@ stages:
 removed: true
 ---
 Allows you to define ports in a
-[NetworkPolicy](docs/concepts/services-networking/network-policies/)
+[NetworkPolicy](/docs/concepts/services-networking/network-policies/)
 rule as a range of port numbers.

content/en/docs/reference/command-line-tools-reference/feature-gates/topology-aware-hints.md

@@ -20,5 +20,5 @@ stages:
 ---
 Enables topology aware routing based on topology hints
 in EndpointSlices. See [Topology Aware
-Hints](/docs/concepts/services-networking/topology-aware-hints/) for more
+Hints](/docs/concepts/services-networking/topology-aware-routing/) for more
 details.

content/en/docs/reference/kubectl/_index.md

@@ -24,7 +24,7 @@ For details about each command, including all the supported flags and subcommand
 [kubectl](/docs/reference/generated/kubectl/kubectl-commands/) reference documentation.
 
 For installation instructions, see [Installing kubectl](/docs/tasks/tools/#kubectl);
-for a quick guide, see the [cheat sheet](/docs/reference/kubectl/cheatsheet/).
+for a quick guide, see the [cheat sheet](/docs/reference/kubectl/quick-reference/).
 If you're used to using the `docker` command-line tool,
 [`kubectl` for Docker Users](/docs/reference/kubectl/docker-cli-to-kubectl/) explains some equivalent commands for Kubernetes.
 

content/en/docs/tasks/access-application-cluster/access-cluster.md

@@ -26,7 +26,7 @@ Check the location and credentials that kubectl knows about with this command:
 kubectl config view
 ```
 
-Many of the [examples](/docs/reference/kubectl/cheatsheet/) provide an introduction to using
+Many of the [examples](/docs/reference/kubectl/quick-reference/) provide an introduction to using
 `kubectl`, and complete documentation is found in the
 [kubectl reference](/docs/reference/kubectl/).
 

content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md

@@ -465,7 +465,7 @@ sudo kubeadm certs generate-csr
 ```
 
 If external etcd is to be used, follow the
-[External etcd with kubeadm](docs/setup/production-environment/tools/kubeadm/high-availability/#external-etcd-nodes)
+[External etcd with kubeadm](/docs/setup/production-environment/tools/kubeadm/high-availability/#external-etcd-nodes)
 guide to understand what CSR files are needed on the kubeadm and etcd nodes. Other
 `.csr` and `.key` files under `/etc/kubernetes/pki/etcd` can be removed.