From c285768c6694d8dca84381434c3e7b237f8b3be2 Mon Sep 17 00:00:00 2001
From: kbatuigas <36839689+kbatuigas@users.noreply.github.com>
Date: Thu, 17 May 2018 15:37:53 -0700
Subject: [PATCH] Updated jobs-run-to-completion.md (#8379)

---
 .../concepts/workloads/controllers/jobs-run-to-completion.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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
index cf7412094b..b3a48dfd54 100644
--- a/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
+++ b/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
@@ -192,8 +192,8 @@ 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 six minutes, The
-back-off limit is reset if no new failed Pods appear before the Job's next
+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.
 
 {{< note >}}