From cef7f2f546a535a2f7116382c77f89a500520755 Mon Sep 17 00:00:00 2001 From: ptux Date: Mon, 3 Jan 2022 08:58:28 +0900 Subject: [PATCH] fix glossary --- .../docs/tasks/debug-application-cluster/debug-application.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/debug-application-cluster/debug-application.md b/content/en/docs/tasks/debug-application-cluster/debug-application.md index 477c9b8248..f3c8ea5269 100644 --- a/content/en/docs/tasks/debug-application-cluster/debug-application.md +++ b/content/en/docs/tasks/debug-application-cluster/debug-application.md @@ -57,7 +57,7 @@ If a Pod is stuck in the `Waiting` state, then it has been scheduled to a worker Again, the information from `kubectl describe ...` should be informative. The most common cause of `Waiting` pods is a failure to pull the image. There are three things to check: * Make sure that you have the name of the image correct. -* Have you pushed the image to the repository? +* Have you pushed the image to the registry? * Run a manual `docker pull ` on your machine to see if the image can be pulled. #### My pod is crashing or otherwise unhealthy