Merge pull request #32497 from michaelryanpeter/BZ1959224

BZ1959224 Remove duplicate "number of"

Author: kalexand-rh

modules/application-health-about.adoc

@@ -51,7 +51,7 @@ 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 default is 0.
-* `periodSeconds`: The delay, in seconds, between performing probes. The default is `10`. This value must be greater than `timeoutSeconds`. 
+* `periodSeconds`: The delay, in seconds, between performing probes. The default is `10`. This value must be greater than `timeoutSeconds`.
 * `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`. This value must be lower than `periodSeconds`.
 * `successThreshold`: The number of times that the probe must report success after a failure 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:
@@ -171,7 +171,7 @@ spec:
 <4> The type of probe, here a container command probe.
 <5> The command line to execute inside the container.
 <6> How often in seconds to perform the probe.
-<7> The number of number of consecutive successes needed to show success after a failure.
+<7> The number of consecutive successes needed to show success after a failure.
 <8> The number of times to try the probe after a failure.
 
 .Sample readiness probe and liveness probe with a TCP socket test in a deployment