Revert "fix max container back off cap (kubernetes#8979)" (kubernetes#9074)

soltysh · k8s-ci-robot · commit f630a57c1c67 · 2018-06-15T12:57:28.000-07:00
This reverts commit 8f04c2e.
diff --git a/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
@@ -193,7 +193,7 @@ due to a logical error in configuration etc.
 To do so, set `.spec.backoffLimit` to specify the number of retries before
 considering a Job as failed. The back-off limit is set by default to 6. Failed
 Pods associated with the Job are recreated by the Job controller with an
-exponential back-off delay (10s, 20s, 40s ...) capped at five minutes. The
+exponential back-off delay (10s, 20s, 40s ...) capped at six minutes. The
 back-off count is reset if no new failed Pods appear before the Job's next
 status check.
 
