From b54c9c82ae5c104f959f69c07e4dc617a6751cc8 Mon Sep 17 00:00:00 2001 From: Seth Hoenig Date: Fri, 1 Apr 2022 09:46:03 -0500 Subject: [PATCH] docs: fix typo in system batch description --- website/content/docs/schedulers.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/schedulers.mdx b/website/content/docs/schedulers.mdx index 635895ab6..43b80e5e5 100644 --- a/website/content/docs/schedulers.mdx +++ b/website/content/docs/schedulers.mdx @@ -67,7 +67,7 @@ according to the job's [restart] stanza; system jobs do not have rescheduling. The `sysbatch` scheduler is used to register jobs that should be run to completion on all clients that meet the job's constraints. The `sysbatch` scheduler will schedule jobs similarly to the `system` scheduler, but like a `batch` job once a -task exists successfully it is not restarted on that client. +task exits successfully it is not restarted on that client. This scheduler type is useful for issuing "one off" commands to be run on every node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]