From 7696b56f66110283e7c35514f972cd8fadb0717a Mon Sep 17 00:00:00 2001
From: Axel Tan <68768816+axeltanxl@users.noreply.github.com>
Date: Tue, 3 May 2022 21:57:59 +0800
Subject: [PATCH] Update links

---
 content/en/docs/tasks/debug/debug-application/debug-pods.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/tasks/debug/debug-application/debug-pods.md b/content/en/docs/tasks/debug/debug-application/debug-pods.md
index e8e8662640..77fff23a52 100644
--- a/content/en/docs/tasks/debug/debug-application/debug-pods.md
+++ b/content/en/docs/tasks/debug/debug-application/debug-pods.md
@@ -65,7 +65,7 @@ Again, the information from `kubectl describe ...` should be informative.  The m
 #### My pod is crashing or otherwise unhealthy
 
 Once your pod has been scheduled, the methods described in [Debug Running Pods](
-/docs/tasks/debug/debug-applications/debug-running-pod/) are available for debugging.
+/docs/tasks/debug/debug-application/debug-running-pod/) are available for debugging.
 
 #### My pod is running but not doing what I told it to do
 
@@ -146,12 +146,12 @@ Verify that the pod's `containerPort` matches up with the Service's `targetPort`
 
 #### Network traffic is not forwarded
 
-Please see [debugging service](/docs/tasks/debug/debug-applications/debug-service/) for more information.
+Please see [debugging service](/docs/tasks/debug/debug-application/debug-service/) for more information.
 
 ## {{% heading "whatsnext" %}}
 
 If none of the above solves your problem, follow the instructions in
-[Debugging Service document](/docs/tasks/debug/debug-applications/debug-service/)
+[Debugging Service document](/docs/tasks/debug/debug-application/debug-service/)
 to make sure that your `Service` is running, has `Endpoints`, and your `Pods` are
 actually serving; you have DNS working, iptables rules installed, and kube-proxy
 does not seem to be misbehaving.