Merge pull request #7436 from killianmuldoon/fix/links

📖 Fix broken book links

Author: k8s-ci-robot

docs/book/src/security/pod-security-standards.md

@@ -7,7 +7,7 @@ It is using ClusterClass variables and patches to inject the configuration.
 
 ## Adding a basic Pod Security Standards configuration to a ClusterClass
 
-By adding the following variables and patches Pod Security Standards can be added to every ClusterClass which references a [Kubeadm based control plane](../tasks/kubeadm-control-plane.md).
+By adding the following variables and patches Pod Security Standards can be added to every ClusterClass which references a [Kubeadm based control plane](../tasks/control-plane/kubeadm-control-plane.md).
 
 ### Adding the variables to a ClusterClass
 

docs/book/src/tasks/control-plane/kubeadm-control-plane.md

@@ -38,4 +38,4 @@ Cluster API Machines:
   for additional details.
 
 <!-- links -->
-[upgrades]: upgrading-clusters.md#how-to-upgrade-the-kubernetes-control-plane-version
+[upgrades]: ../upgrading-clusters.md#how-to-upgrade-the-kubernetes-control-plane-version

docs/book/src/tasks/updating-machine-templates.md

@@ -33,7 +33,7 @@ field and the controller would orchestrate the upgrade by managing `MachineSets`
 In all cases, the `name` field should be updated to point to the newly-modified
 infrastructure machine template. This will trigger a rolling update. (This same process
 is described in the documentation for [upgrading the underlying machine image for
-KubeadmControlPlane](./kubeadm-control-plane.md) in the "How to upgrade the underlying
+KubeadmControlPlane](./control-plane/kubeadm-control-plane.md) in the "How to upgrade the underlying
 machine image" section.)
 
 Some infrastructure providers _may_, at their discretion, choose to support in-place