luxolus/open-nomad
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity

Merge pull request #2916 from hashicorp/b-fix-typo

Browse source 
Fix typo
This commit is contained in:
Michael Schurter 2017-07-27 09:43:18 -07:00 committed by GitHub
parent 4f645bf180 e386ef9fa3
commit 3684ae4180
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
website/source/docs/operating-a-job/update-strategies/rolling-upgrades.html.md
View file

@ -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
}
```