From b558cb589ded504d0fd669d64712ee820d522be2 Mon Sep 17 00:00:00 2001
From: Rowan Smith <86935689+rowansmithhc@users.noreply.github.com>
Date: Thu, 29 Jul 2021 21:41:08 +1000
Subject: [PATCH] Fixed typo for 'forward' value in relation to caching
 (#12199)

---
 website/content/docs/agent/caching/index.mdx    | 2 +-
 website/content/docs/enterprise/consistency.mdx | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/agent/caching/index.mdx b/website/content/docs/agent/caching/index.mdx
index b144d4a20b..55989e55bf 100644
--- a/website/content/docs/agent/caching/index.mdx
+++ b/website/content/docs/agent/caching/index.mdx
@@ -209,7 +209,7 @@ page.
   or `"never"`.
 
 - `when_inconsistent` `(string: optional)` - Set to one of `"fail"`, `"retry"`,
-   or `"forward-active_node"`.
+   or `"forward"`.
 
 ### Configuration (Persist)
 
diff --git a/website/content/docs/enterprise/consistency.mdx b/website/content/docs/enterprise/consistency.mdx
index 39a3f43f4d..898d03e98f 100644
--- a/website/content/docs/enterprise/consistency.mdx
+++ b/website/content/docs/enterprise/consistency.mdx
@@ -192,7 +192,7 @@ The option `when_inconsistent` controls how stale reads are prevented:
 - `"fail"` means that when a `412` response is seen, it is returned to the client
 - `"retry"` means that `412` responses will be retried automatically by Agent,
   so the client doesn't have to deal with them
-- `"forward-active-node"` makes Agent provide the
+- `"forward"` makes Agent provide the
   `X-Vault-Inconsistent: forward-active-node` header as described above under
   Conditional Forwarding