From 8e54b4b5cf2223921609b1fcb7af3a268d166e43 Mon Sep 17 00:00:00 2001
From: Luke Kysow <1034429+lkysow@users.noreply.github.com>
Date: Fri, 20 Jan 2023 12:00:30 -0800
Subject: [PATCH] Update gossip.mdx

Fix description of topic. I think it was copy pasted incorrectly.
---
 .../deployment-configurations/vault/data-integration/gossip.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/k8s/deployment-configurations/vault/data-integration/gossip.mdx b/website/content/docs/k8s/deployment-configurations/vault/data-integration/gossip.mdx
index 187064d9f0..dd2915ba52 100644
--- a/website/content/docs/k8s/deployment-configurations/vault/data-integration/gossip.mdx
+++ b/website/content/docs/k8s/deployment-configurations/vault/data-integration/gossip.mdx
@@ -7,7 +7,7 @@ description: >-
 
 # Storing Gossip Encryption Key in Vault
 
-This topic describes how to configure the Consul Helm chart to use TLS certificates issued by Vault in the Consul controller and connect inject webhooks.
+This topic describes how to configure the Consul Helm chart to use a gossip encryption key stored in Vault.
 
 ## Overview
 Complete the steps outlined in the [Data Integration](/docs/k8s/deployment-configurations/vault/data-integration) section to use a gossip encryption key stored in Vault.