From a0a150b7f1142a373ce668c47b01313a88f080aa Mon Sep 17 00:00:00 2001
From: Brian Scholer <1260690+briantist@users.noreply.github.com>
Date: Wed, 18 Oct 2023 22:33:46 -0400
Subject: [PATCH] Update step-down.mdx to describe behavior against non-active
 nodes (#23657)

* Update step-down.mdx to describe behavior against non-active nodes

Behavior changed in Vault 1.9:
https://developer.hashicorp.com/vault/docs/v1.9.x/commands/operator/step-down
---
 website/content/api-docs/system/step-down.mdx | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/website/content/api-docs/system/step-down.mdx b/website/content/api-docs/system/step-down.mdx
index 1de82823c3..697cd874d1 100644
--- a/website/content/api-docs/system/step-down.mdx
+++ b/website/content/api-docs/system/step-down.mdx
@@ -12,8 +12,12 @@ The `/sys/step-down` endpoint causes the node to give up active status.
 
 ## Step down leader
 
-This endpoint forces the node to give up active status. If the node does not
-have active status, this endpoint does nothing. Note that the node will sleep
+The step-down endpoint forces nodes to give up "active" status. If you
+call the endpoint against a non-active node, for example, a DR or
+ performance standby node, Vault forwards the request to the active
+  node.
+  
+    Note that the node will sleep
 for ten seconds before attempting to grab the active lock again, but if no
 standby nodes grab the active lock in the interim, the same node may become the
 active node again. Requires a token with `root` policy or `sudo` capability on