Merge pull request #27857 from openshift-cherrypick-robot/cherry-pick…

…-27814-to-enterprise-4.5

[enterprise-4.5] Modify initialDelaySeconds definition

modules/application-health-about.adoc

@@ -34,7 +34,7 @@ A _startup probe_ indicates whether the application within a container is starte
 +
 Some applications can require additional start-up time on their first initialization. You can use a startup probe with a liveness or readiness probe to delay that probe long enough to handle lengthy start-up time using the `failureThreshold` and `periodSeconds` parameters.
 +
-For example, you can add a startup probe, with a `failureThreshold` of 30 seconds and a `periodSeconds` of 10 seconds (30 * 10 = 300s) for a maximum of 5 minutes, to a liveness probe. After the startup probe succeeds the first time, the liveness probe takes over. 
+For example, you can add a startup probe, with a `failureThreshold` of 30 failures and a `periodSeconds` of 10 seconds (30 * 10s = 300s) for a maximum of 5 minutes, to a liveness probe. After the startup probe succeeds the first time, the liveness probe takes over. 
 
 You can configure liveness, readiness, and startup probes with any of the following types of tests:
 
@@ -50,9 +50,9 @@ initialization is complete.
 
 You can configure several fields to control the behavior of a probe:
 
-* `initialDelaySeconds`: The time, in seconds, after the container starts before the probe can be scheduled. The defaults is `0`.
+* `initialDelaySeconds`: The time, in seconds, after the container starts before the probe can be scheduled. The default is 0.
 * `periodSeconds`: The delay, in seconds, between performing probes. The default is `10`.
-* `timeoutSeconds`: The number of seconds of inactivity after which the probe times out and the container is assumed to have failed. The defaults is `1`.
+* `timeoutSeconds`: The number of seconds of inactivity after which the probe times out and the container is assumed to have failed. The default is `1`.
 * `successThreshold`: The number of times that the probe must report success after a failure in order to reset the container status to successful. The value must be `1` for a liveness probe. The default is `1`. 
 * `failureThreshold`: The number of times that the probe is allowed to fail. The default is 3. After the specified attempts: 
 ** for a liveness probe, the container is restarted 

modules/application-health-configuring.adoc

@@ -55,7 +55,7 @@ spec:
 <3> Optional: Create a Liveness probe.
 <4> Specify a test to perform, here a TCP Socket test.
 <5> Specify the port on which the container is listening.
-<6> Specify the number of seconds before performing the first probe after the container starts.
+<6> Specify the time, in seconds, after the container starts before the probe can be scheduled.
 <7> Specify the number of seconds between probes.
 <8> Optional: Create a Readiness probe.
 <9> Specify the type of test to perform, here an HTTP test.