From e34f8a14fb7a88af4640b09f3ddbb5646b946d9c Mon Sep 17 00:00:00 2001
From: hc-github-team-secure-vault-core
 <82990506+hc-github-team-secure-vault-core@users.noreply.github.com>
Date: Thu, 27 Oct 2022 12:32:05 -0700
Subject: [PATCH] backport of commit 28f091abe4f2aba343f00e3d04e32409c705588d
 (#17710)

Co-authored-by: davidadeleon <56207066+davidadeleon@users.noreply.github.com>
---
 website/content/docs/enterprise/replication.mdx | 7 +++++++
 website/data/docs-nav-data.json                 | 4 ++++
 2 files changed, 11 insertions(+)

diff --git a/website/content/docs/enterprise/replication.mdx b/website/content/docs/enterprise/replication.mdx
index 1b2c1176dac3..9f15236c1cd1 100644
--- a/website/content/docs/enterprise/replication.mdx
+++ b/website/content/docs/enterprise/replication.mdx
@@ -220,6 +220,13 @@ generation until it is used.
 Once a secondary is activated, its cluster information is stored safely behind
 its encrypted barrier.
 
+## Mutual TLS and Load Balancers
+
+Vault generates its own certificates for cluster members. All replication traffic 
+uses the cluster port using these Vault-generated certificates after initial 
+bootstrapping. Because of this, the cluster traffic can NOT be terminated at the 
+cluster port at a load balancer level.
+
 ## Tutorial
 
 Refer to the following tutorials replication setup and best practices:
diff --git a/website/data/docs-nav-data.json b/website/data/docs-nav-data.json
index 656fe3934ab9..3674ce575811 100644
--- a/website/data/docs-nav-data.json
+++ b/website/data/docs-nav-data.json
@@ -658,6 +658,10 @@
         "title": "<code>path-help</code>",
         "path": "commands/path-help"
       },
+      {
+        "title": "<code>patch</code>",
+        "path": "commands/patch"
+      },
       {
         "title": "<code>plugin</code>",
         "routes": [