From 7bd9665a46e89579284ae63cebb910f5a2b5f74a Mon Sep 17 00:00:00 2001 From: Justin Weissig Date: Thu, 9 May 2019 03:24:06 -0700 Subject: [PATCH] docs: better sentence flow (#6705) Fixed for sentence flow: "When you bring up your server back up" to "When you bring your server back up". --- website/source/docs/concepts/seal.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/concepts/seal.html.md b/website/source/docs/concepts/seal.html.md index 73d177191..189d189fb 100644 --- a/website/source/docs/concepts/seal.html.md +++ b/website/source/docs/concepts/seal.html.md @@ -100,7 +100,7 @@ The seal can be migrated from Shamir keys to Auto Unseal and vice versa. To migrate from Shamir keys to Auto Unseal, take your server cluster offline and update the [seal configuration](/docs/configuration/seal/index.html) with the appropriate seal -configuration. When you bring up your server back up, run the unseal process with the +configuration. When you bring your server back up, run the unseal process with the `-migrate` flag. All unseal commands must specify the `-migrate` flag. Once the required threshold of unseal keys are entered, the unseal keys will be migrated to recovery keys. @@ -112,7 +112,7 @@ $ vault operator unseal -migrate To migrate from Auto Unseal to Shamir keys, take your server cluster offline and update the [seal configuration](/docs/configuration/seal/index.html) and add `disabled = "true"` to the seal block. This allows the migration to use this information to decrypt the key -but will not unseal Vault. When you bring up your server back up, run the unseal process +but will not unseal Vault. When you bring your server back up, run the unseal process with the `-migrate` flag and use the Recovery Keys to perform the migration. All unseal commands must specify the `-migrate` flag. Once the required threshold of recovery keys are entered, the recovery keys will be migrated to be used as unseal keys.