From 2c0a87a05773727e666660c8a400a439a4b6dcf4 Mon Sep 17 00:00:00 2001
From: vanphan24 <89482663+vanphan24@users.noreply.github.com>
Date: Tue, 11 Jan 2022 13:22:50 -0800
Subject: [PATCH] Clarifies external CA config

It is not clear that this page is to configure an external CA for Connect CA. Added line to clarify that this page is for configuring external CA's for the Connect CA. For the built-in CA, no config is needed.
---
 website/content/docs/k8s/connect/connect-ca-provider.mdx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/website/content/docs/k8s/connect/connect-ca-provider.mdx b/website/content/docs/k8s/connect/connect-ca-provider.mdx
index de1bca22a..3b982f66d 100644
--- a/website/content/docs/k8s/connect/connect-ca-provider.mdx
+++ b/website/content/docs/k8s/connect/connect-ca-provider.mdx
@@ -14,7 +14,8 @@ Consul has support for different certificate authority (CA) providers to be used
 Please see [Connect Certificate Management](/docs/connect/ca) for the information on the providers
 we currently support.
 
-To configure a provider via the Consul Helm chart, you need to follow three steps:
+If Connect is enabled, the built-in Consul CA is automatically enabled for the Connect CA.
+To configure an external CA provider via the Consul Helm chart, you need to follow three steps:
 
 1. Create a configuration file containing your provider information.
 1. Create a Kubernetes secret containing the configuration file.