From b18e89fbb9602cbd5b5403351b38f061990317c0 Mon Sep 17 00:00:00 2001 From: Trey Tacon Date: Fri, 27 Sep 2019 10:16:04 -0400 Subject: [PATCH] Correct minor typo `Cronjob` -> `CronJob`. --- content/en/docs/concepts/workloads/controllers/cron-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md index eb3f6c065f1ce..47f2e1e363c58 100644 --- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md +++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md @@ -54,7 +54,7 @@ To illustrate this concept further, suppose a CronJob is set to schedule a new J `startingDeadlineSeconds` is set to 200 seconds. If the CronJob controller happens to be down for the same period as the previous example (`08:29:00` to `10:21:00`,) the Job will still start at 10:22:00. This happens as the controller now checks how many missed schedules happened in the last 200 seconds (ie, 3 missed schedules), rather than from the last scheduled time until now. -The Cronjob is only responsible for creating Jobs that match its schedule, and +The CronJob is only responsible for creating Jobs that match its schedule, and the Job in turn is responsible for the management of the Pods it represents. {{% /capture %}}