fix build validation warnings

Author: amsliu

support/azure/azure-kubernetes/availability-performance/identify-memory-saturation-aks.md

@@ -25,7 +25,7 @@ The following table outlines the common symptoms of memory saturation.
 | Unschedulable pods | Additional pods can't be scheduled if the node is close to its set memory limit. |
 | Pod eviction | If a node is running out of memory, the kubelet can evict pods. Although the control plane tries to reschedule the evicted pods on other nodes that have resources, there's no guarantee that other nodes have sufficient memory to run these pods. |
 | Node not ready | Memory saturation can cause `kubelet` and `containerd` to become unresponsive, eventually causing node readiness issues. |
-| Out-of-memory (OOM) kill | An OOM problem occurs if the pod eviction can't prevent a node issue. For more information, see [Troubleshoot OOMkilled in AKS clusters](./troubleshoot-oomkilled-in-aks-clusters.md).|
+| Out-of-memory (OOM) kill | An OOM problem occurs if the pod eviction can't prevent a node issue. For more information, see [Troubleshoot OOMkilled in AKS clusters](./troubleshoot-oomkilled-aks-clusters.md).|
 
 ## Troubleshooting checklist
 

…roubleshoot-oomkilled-in-aks-clusters.md …e/troubleshoot-oomkilled-aks-clusters.mdsupport/azure/azure-kubernetes/availability-performance/troubleshoot-oomkilled-in-aks-clusters.md renamed to support/azure/azure-kubernetes/availability-performance/troubleshoot-oomkilled-aks-clusters.md support/azure/azure-kubernetes/availability-performance/troubleshoot-oomkilled-in-aks-clusters.md renamed to support/azure/azure-kubernetes/availability-performance/troubleshoot-oomkilled-aks-clusters.md

@@ -175,7 +175,7 @@ User pods may be OOMKilled due to insufficient memory limits or excessive memory
 
 ### Cause 1: User workloads may be running in a system node pools
 
-It is recommended to create user node pools for user workloads. For more information, see: [Manage system node pools in Azure Kubernetes Service (AKS)](https://learn.microsoft.com/en-us/azure/aks/use-system-pools).
+It is recommended to create user node pools for user workloads. For more information, see: [Manage system node pools in Azure Kubernetes Service (AKS)](/azure/aks/use-system-pools).
 
 ### Cause 2: Application pod keeps restarting due to OOMkilled
 
@@ -184,7 +184,7 @@ to it and it requires more, which will cause the pod to constantly
 restart.
 
 To solve, review request and limits documentation to understand how to modify
-your deployment accordingly. For more information, see [Resource Management for Pods and Containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/%22%20/l%20%22requests-and-limits).
+your deployment accordingly. For more information, see [Resource Management for Pods and Containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits).
 
 `kubectl set resources deployment \<deployment-name\>
 \--limits=memory=\<LIMITS\>Mi ---requests=memory=\<MEMORY\>Mi`

support/azure/azure-kubernetes/toc.yml

@@ -177,7 +177,7 @@
   - name: Troubleshoot pod scheduler errors 
     href: availability-performance/troubleshoot-pod-scheduler-errors.md
   - name: Troubleshoot OOMkilled in AKS clusters
-    href: availability-performance/troubleshoot-oomkilled-in-aks-clusters.md
+    href: availability-performance/troubleshoot-oomkilled-aks-clusters.md
   - name: Troubleshoot node not ready
     items:
     - name: Basic troubleshooting