Fix some hyperlinks in the markdown files

Author: tengqm

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

@@ -87,7 +87,10 @@ A minimal Ingress resource example:
 An Ingress needs `apiVersion`, `kind`, `metadata` and `spec` fields.
 The name of an Ingress object must be a valid
 [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
-For general information about working with config files, see [deploying applications](/docs/tasks/run-application/run-stateless-application-deployment/), [configuring containers](/docs/tasks/configure-pod-container/configure-pod-configmap/), [managing resources](/docs/concepts/cluster-administration/manage-deployment/).
+For general information about working with config files, see
+[deploying applications](/docs/tasks/run-application/run-stateless-application-deployment/),
+[configuring containers](/docs/tasks/configure-pod-container/configure-pod-configmap/),
+[managing resources](/docs/concepts/workloads/management/).
 Ingress frequently uses annotations to configure some options depending on the Ingress controller, an example of which
 is the [rewrite-target annotation](https://github.com/kubernetes/ingress-nginx/blob/main/docs/examples/rewrite/README.md).
 Different [Ingress controllers](/docs/concepts/services-networking/ingress-controllers) support different annotations.

content/en/docs/concepts/windows/intro.md

@@ -368,7 +368,7 @@ Depending on the requirements for your workload these values may need to be adju
 Refer to
 [Hardware requirements for Windows Server Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/get-started/hardware-requirements)
 for the most up-to-date information on minimum hardware requirements. For guidance on deciding on resources for
-production worker nodes refer to [Production worker nodes Kubernetes documentation](https://kubernetes.io/docs/setup/production-environment/#production-worker-nodes).
+production worker nodes refer to [Production worker nodes Kubernetes documentation](/docs/setup/production-environment/#production-worker-nodes).
 
 To optimize system resources, if a graphical user interface is not required,
 it may be preferable to use a Windows Server OS installation that excludes
@@ -432,4 +432,4 @@ For a detailed explanation of Windows distribution channels see the
 
 Information on the different Windows Server servicing channels
 including their support models can be found at
-[Windows Server servicing channels](https://docs.microsoft.com/en-us/windows-server/get-started/servicing-channels-comparison).
+[Windows Server servicing channels](https://docs.microsoft.com/en-us/windows-server/get-started/servicing-channels-comparison).

content/en/docs/concepts/workloads/controllers/deployment.md

@@ -1083,7 +1083,7 @@ thus that Deployment will not be able to roll back.
 
 If you want to roll out releases to a subset of users or servers using the Deployment, you
 can create multiple Deployments, one for each release, following the canary pattern described in
-[managing resources](/docs/concepts/cluster-administration/manage-deployment/#canary-deployments).
+[managing resources](/docs/concepts/workloads/management/#canary-deployments).
 
 ## Writing a Deployment Spec
 

content/en/docs/tasks/administer-cluster/decrypt-data.md

@@ -62,7 +62,7 @@ control how Kubernetes API data is encrypted in etcd.
 If it is not specified, you do not have encryption at rest enabled.
 
 The format of that configuration file is YAML, representing a configuration API kind named
-[`EncryptionConfiguration`](/docs/reference/config-api/apiserver-encryption.v1/).
+[`EncryptionConfiguration`](/docs/reference/config-api/apiserver-config.v1/).
 You can see an example configuration
 in [Encryption at rest configuration](/docs/tasks/administer-cluster/encrypt-data/#understanding-the-encryption-at-rest-configuration).
 

content/en/docs/tasks/administer-cluster/encrypt-data.md

@@ -189,7 +189,7 @@ Ensure that the exemption is listed _before_ the wildcard '`*.*`' item in the re
 to give it precedence.
 
 For more detailed information about the `EncryptionConfiguration` struct, please refer to the
-[encryption configuration API](/docs/reference/config-api/apiserver-encryption.v1/).
+[encryption configuration API](/docs/reference/config-api/apiserver-config.v1/).
 
 {{< caution >}}
 If any resource is not readable via the encryption configuration (because keys were changed),

content/en/docs/tasks/administer-cluster/kms-provider.md

@@ -334,7 +334,7 @@ These healthcheck endpoint paths are hard coded and generated/controlled by the
 Until the steps defined in [Ensuring all secrets are encrypted](#ensuring-all-secrets-are-encrypted) are performed, the `providers` list should end with the `identity: {}` provider to allow unencrypted data to be read.  Once all resources are encrypted, the `identity` provider should be removed to prevent the API server from honoring unencrypted data.
 
 For details about the `EncryptionConfiguration` format, please check the
-[API server encryption API reference](/docs/reference/config-api/apiserver-encryption.v1/).
+[API server encryption API reference](/docs/reference/config-api/apiserver-config.v1/).
 
 ## Verifying that the data is encrypted
 

content/en/docs/tasks/administer-cluster/kubelet-config-file.md

@@ -146,7 +146,7 @@ and replaces every field present in a higher priority file.
 Since the configuration could now be spread over multiple files with this feature, if someone wants to inspect the final actuated configuration,
 they can follow these steps to inspect the kubelet configuration:
 
-1. Start a proxy server using [`kubectl proxy`](/docs/reference/kubectl/generated/kubectl-commands#proxy) in your terminal.
+1. Start a proxy server using [`kubectl proxy`](/docs/reference/kubectl/generated/kubectl_proxy/) in your terminal.
 
    ```bash
    kubectl proxy