From 06ea7f8937db0919b838d5502b4e6f4afa4923d1 Mon Sep 17 00:00:00 2001
From: Jagger <62120695+jagger-en@users.noreply.github.com>
Date: Mon, 19 Dec 2022 19:30:19 +0100
Subject: [PATCH] Fix typo (#18459)

If there are other typo related changes in flight, this fix can be included there.
---
 website/content/docs/secrets/pki/index.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/secrets/pki/index.mdx b/website/content/docs/secrets/pki/index.mdx
index 052912b3a1..899b241a89 100644
--- a/website/content/docs/secrets/pki/index.mdx
+++ b/website/content/docs/secrets/pki/index.mdx
@@ -8,7 +8,7 @@ description: The PKI secrets engine for Vault generates TLS certificates.
 
 @include 'x509-sha1-deprecation.mdx'
 
--> **Vault as Consul CA provider:** If you are using Vault 1.11.0+ as a Connect CA, run a Consul version which includese the fix for [GH-15525](https://github.com/hashicorp/consul/pull/15525). Refer to this [Knowledge Base article](https://support.hashicorp.com/hc/en-us/articles/11308460105491) for more details.
+-> **Vault as Consul CA provider:** If you are using Vault 1.11.0+ as a Connect CA, run a Consul version which includes the fix for [GH-15525](https://github.com/hashicorp/consul/pull/15525). Refer to this [Knowledge Base article](https://support.hashicorp.com/hc/en-us/articles/11308460105491) for more details.
 
 The PKI secrets engine generates dynamic X.509 certificates. With this secrets
 engine, services can get certificates without going through the usual manual