From ff70f6db4f35b802f62e415de3ac7e4a3c25b977 Mon Sep 17 00:00:00 2001
From: Mike Green <772413+mikegreen@users.noreply.github.com>
Date: Wed, 14 Jul 2021 13:10:07 -0600
Subject: [PATCH] docs/stepdown-clarification (#12077)

---
 .../content/docs/commands/operator/step-down.mdx    | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/website/content/docs/commands/operator/step-down.mdx b/website/content/docs/commands/operator/step-down.mdx
index f9906bd738..fa74c0536c 100644
--- a/website/content/docs/commands/operator/step-down.mdx
+++ b/website/content/docs/commands/operator/step-down.mdx
@@ -8,11 +8,14 @@ description: |-
 
 # operator step-down
 
-The `operator step-down` forces the Vault server at the given address to step
-down from active duty. While the affected node will have a delay before
-attempting to acquire the leader lock again, if no other Vault nodes acquire the
-lock beforehand, it is possible for the same node to re-acquire the lock and
-become active again.
+The `operator step-down` forces the active Vault node within an [HA cluster](/docs/concepts/ha)
+to step down from active duty. When executed against a non-active node, i.e. a 
+standby or [performance standby](/docs/enterprise/performance-standby) node, 
+the request will be forwarded to the active node.  While the 
+affected node will have a delay before attempting to acquire 
+the leader lock again, if no other Vault nodes acquire the
+lock beforehand, it is possible for the same node to re-acquire
+the lock and become active again.
 
 ## Examples