From de36bd7f42bf982b0edc4460428ccc954e0a732a Mon Sep 17 00:00:00 2001 From: Rob Genova Date: Fri, 18 Aug 2017 23:18:20 +0000 Subject: [PATCH] Reword long-ish sentence. --- website/source/intro/getting-started/jobs.html.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/website/source/intro/getting-started/jobs.html.md b/website/source/intro/getting-started/jobs.html.md index ff290126b..5d8079089 100644 --- a/website/source/intro/getting-started/jobs.html.md +++ b/website/source/intro/getting-started/jobs.html.md @@ -250,13 +250,10 @@ changed, another user has modified the job and the plan's results are potentially invalid. ``` -Here we can see the `plan` reports it will ignore two allocations and do one -create/destroy update which stops the old allocation and starts the new -allocation because we have changed the version of redis to run. - -The reason the plan only reports a single change to occur is because the job -file has an `update` stanza that tells Nomad to perform rolling updates when the -job changes at a rate of `max_parallel`, which is set to 1 in the example file. +The plan output shows us that one allocation will be updated and that the other +two will be ignored. This is due to the `max_parallel` setting in the `update` +stanza, which is set to 1 to instruct Nomad to perform only a single change at +a time. Once ready, use `run` to push the updated specification: