Review comments

Signed-off-by: Laura Lorenz <[email protected]>

Author: lauralorenz

content/en/docs/concepts/workloads/pods/pod-lifecycle.md

@@ -265,16 +265,16 @@ explains the behaviour of `init containers` when specify `restartpolicy` field o
 {{< feature-state feature_state_name="KubeletCrashLoopBackOffMax" >}}
 
 With the alpha feature gate `KubeletCrashLoopBackOffMax` enabled, you can
-reconfigure the maximum delay between container restarts from the default of
-300s (5 minutes). This configuration is set per node using kubelet
-configuration. In your [kubelet
-configuration](https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/),
-set the `CrashLoopBackOff.MaxContainerRestartPeriod` field between `"1s"` and
-`"300s"`. Delays on that node will still start at 10s and increase exponentially
-by 2x each restart, until being capped at your configured maximum. If the
-`CrashLoopBackOff.MaxContainerRestartPeriod` you configure is less than the
-default initial value of 10s, the initial delay will instead be set to the
-configured maximum.
+reconfigure the maximum delay between container start retries from the default
+of 300s (5 minutes). This configuration is set per node using kubelet
+configuration. In your [kubelet configuration](/docs/tasks/administer-cluster/kubelet-config-file/),
+under `crashLoopBackOff` set the `maxContainerRestartPeriod` field between
+`"1s"` and `"300s"`. As described above in [Container restart
+policy](#restart-policy), delays on that node will still start at 10s and
+increase exponentially by 2x each restart, but will now be capped at your
+configured maximum. If the `maxContainerRestartPeriod` you configure is less
+than the default initial value of 10s, the initial delay will instead be set to
+the configured maximum.
 
 See the following kubelet configuration examples:
 

content/en/docs/reference/command-line-tools-reference/feature-gates/kubelet-crash-loop-back-off-max.md

@@ -11,4 +11,4 @@ stages:
     fromVersion: "1.32"
 ---
 Enables support for configurable per-node backoff maximums for restarting
-containers (aka containers in CrashLoopBackOff)
+containers in the CrashLoopBackOff state.