From e5639400134e4b88cac14fe6f24d4dbd97016cf1 Mon Sep 17 00:00:00 2001 From: lopes22 Date: Mon, 3 Aug 2020 21:11:55 -0400 Subject: [PATCH] Update pod-lifecycle.md --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 2b292d376d..2e856570be 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -124,7 +124,7 @@ about when the container entered the `Running` state. ### `Terminated` {#container-state-terminated} -A container in the `Terminated` state has begin execution and has then either run to +A container in the `Terminated` state had began execution and then has either run to completion or has failed for some reason. When you use `kubectl` to query a Pod with a container that is `Terminated`, you see a reason, and exit code, and the start and finish time for that container's period of execution.