From 6abc5757b1a4c16ec29faba3254b4695b0b90a51 Mon Sep 17 00:00:00 2001 From: James Phillips Date: Tue, 18 Jul 2017 14:48:38 -0700 Subject: [PATCH] Tweaks title. --- website/source/docs/guides/autopilot.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/guides/autopilot.html.md b/website/source/docs/guides/autopilot.html.md index 791986a635..ec1bf91979 100644 --- a/website/source/docs/guides/autopilot.html.md +++ b/website/source/docs/guides/autopilot.html.md @@ -204,7 +204,7 @@ node3 127.0.0.1:8803 alive server 0.7.5 2 dc1 node4 127.0.0.1:8203 alive server 0.8.0 2 dc1 ``` -### Using migrations without a Consul version change +### Migrations Without a Consul Version Change The `UpgradeVersionTag` can be used to override the version information used during a migration, so that the migration logic can be used for updating the cluster when @@ -215,4 +215,4 @@ version in each server's specified [`-node-meta`](/docs/agent/options.html#_node tag. For example, if `UpgradeVersionTag` is set to `build`, and `-node-meta build:0.0.2` is used when starting a server, that server's version will be `0.0.2` when considered in a migration. The upgrade logic will follow semantic versioning and the version string -must be in the form of either `X`, `X.Y`, or `X.Y.Z`. \ No newline at end of file +must be in the form of either `X`, `X.Y`, or `X.Y.Z`.