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": [