From 5c8f26e6d6c19da59e146bf90826144de3f96c2e Mon Sep 17 00:00:00 2001 From: BartoszCki Date: Thu, 27 Aug 2020 15:23:55 +0200 Subject: [PATCH 1/4] Fix a 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 0daf25de1a..316b41fc34 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -45,7 +45,7 @@ higher-level abstraction, called a managing the relatively disposable Pod instances. A given Pod (as defined by a UID) is never "rescheduled" to a different node; instead, -that Pod can be replaced by a new, near-identical Pod, with even the same name i +that Pod can be replaced by a new, near-identical Pod, with even the same name if desired, but with a different UID. When something is said to have the same lifetime as a Pod, such as a From 9328c7d2b194b1d339f9a1ba3c76de4b85b7eb52 Mon Sep 17 00:00:00 2001 From: BartoszCki Date: Thu, 27 Aug 2020 16:00:02 +0200 Subject: [PATCH 2/4] 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 316b41fc34..557c935c54 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -107,7 +107,7 @@ Each state has a specific meaning: ### `Waiting` {#container-state-waiting} -If a container is not in either the `Running` or `Terminated` state, it `Waiting`. +If a container is not in either the `Running` or `Terminated` state, it's `Waiting`. A container in the `Waiting` state is still running the operations it requires in order to complete start up: for example, pulling the container image from a container image registry, or applying {{< glossary_tooltip text="Secret" term_id="secret" >}} From 9e9b22689c3006cbafd745e2aefc6bce6ea61e63 Mon Sep 17 00:00:00 2001 From: BartoszCki Date: Thu, 27 Aug 2020 16:07:59 +0200 Subject: [PATCH 3/4] 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. From 8bcf7bb7445df99830d9e8418d90ba5dd8f2efd6 Mon Sep 17 00:00:00 2001 From: BartoszCki Date: Fri, 28 Aug 2020 00:31:06 +0200 Subject: [PATCH 4/4] Make it idiomatic English --- 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 08bb73fb97..31a92593da 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -107,7 +107,7 @@ Each state has a specific meaning: ### `Waiting` {#container-state-waiting} -If a container is not in either the `Running` or `Terminated` state, it's `Waiting`. +If a container is not in either the `Running` or `Terminated` state, it is `Waiting`. A container in the `Waiting` state is still running the operations it requires in order to complete start up: for example, pulling the container image from a container image registry, or applying {{< glossary_tooltip text="Secret" term_id="secret" >}}