From 9e9b22689c3006cbafd745e2aefc6bce6ea61e63 Mon Sep 17 00:00:00 2001 From: BartoszCki Date: Thu, 27 Aug 2020 16:07:59 +0200 Subject: [PATCH] Another typo --- 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 557c935c54..08bb73fb97 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -118,7 +118,7 @@ a Reason field to summarize why the container is in that state. ### `Running` {#container-state-running} The `Running` status indicates that a container is executing without issues. If there -was a `postStart` hook configured, it has already executed and executed. When you use +was a `postStart` hook configured, it has already executed and finished. When you use `kubectl` to query a Pod with a container that is `Running`, you also see information about when the container entered the `Running` state.