From e386ef9fa3f56d00989ce7abd28b36de137b8673 Mon Sep 17 00:00:00 2001 From: Jon Benson Date: Wed, 26 Jul 2017 19:24:23 -0700 Subject: [PATCH] Fix typo --- .../update-strategies/rolling-upgrades.html.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/source/docs/operating-a-job/update-strategies/rolling-upgrades.html.md b/website/source/docs/operating-a-job/update-strategies/rolling-upgrades.html.md index 39626772d..f4845b5f7 100644 --- a/website/source/docs/operating-a-job/update-strategies/rolling-upgrades.html.md +++ b/website/source/docs/operating-a-job/update-strategies/rolling-upgrades.html.md @@ -16,7 +16,7 @@ updates a job or task group is annotated with a high-level description of the update strategy using the [`update` stanza][update]. Under the hood, Nomad handles limiting parallelism, interfacing with Consul to determine service health and even automatically reverting to an older, healthy job when a -deployment fails. +deployment fails. ## Enabling Rolling Updates @@ -24,7 +24,7 @@ Rolling updates are enabled by adding the [`update` stanza][update] to the job specification. The `update` stanza may be placed at the job level or in an individual task group. When placed at the job level, the update strategy is inherited by all task groups in the job. When placed at both the job and group -level, the 'update` stanzas are merged, with group stanzas taking precedance +level, the `update` stanzas are merged, with group stanzas taking precedance over job level stanzas. See the [`update` stanza documentation](/docs/job-specification/update.html#upgrade-stanza-inheritance) for an example. @@ -245,7 +245,7 @@ update { healthy_deadline = "10m" # Enable automatically reverting to the last stable job on a failed - # deployment. + # deployment. auto_revert = true } ```