diff --git a/website/source/docs/concepts/ha.html.markdown b/website/source/docs/concepts/ha.html.markdown
index ef16af40eb..f92ca23fd7 100644
--- a/website/source/docs/concepts/ha.html.markdown
+++ b/website/source/docs/concepts/ha.html.markdown
@@ -54,11 +54,20 @@ sent over this TLS-protected communication channel, and acted upon by the
 active node. The active node then returns a response to the standby, which
 sends the response back to the requesting client.
 
+## Request Forwarding
+
+If request forwarding is enabled (turned on by default in 0.6.2), clients can
+still force the older/fallback redirection behavior (see below) if desired by
+setting the `X-Vault-No-Request-Forwarding` header to any non-empty value.
+
+Successful cluster setup requires a few configuration parameters, although some
+can be automatically determined.
+
 ## Client Redirection
 
-This is currently the only mode enabled by default. When a standby node
-receives a request, it will redirect the client using a `307` status code to
-the _active node's_ redirect address.
+If `X-Vault-No-Request-Forwarding` header in the request is set to a non-empty
+value, the standby nodes will redirect the client using a `307` status code to
+the *active node's* redirect address.
 
 This is also the fallback method used when request forwarding is turned off or
 there is an error performing the forwarding. As such, a redirect address is
@@ -104,15 +113,6 @@ balancer; at that point hopefully the load balancer's configuration will have
 been updated to know the address of the current leader. This can cause a
 redirect loop and as such is not a recommended setup when it can be avoided.
 
-## Request Forwarding
-
-If request forwarding is enabled (turned on by default in 0.6.2), clients can
-still force the older/fallback redirection behavior if desired by setting the
-`X-Vault-No-Request-Forwarding` header to any non-empty value.
-
-Successful cluster setup requires a few configuration parameters, although some
-can be automatically determined.
-
 ### Per-Node Cluster Listener Addresses
 
 Each `listener` block in Vault's configuration file contains an `address` value