diff --git a/website/content/docs/upgrading/upgrade-to-1.12.x.mdx b/website/content/docs/upgrading/upgrade-to-1.12.x.mdx
index c91a30c93c..c0e62d429c 100644
--- a/website/content/docs/upgrading/upgrade-to-1.12.x.mdx
+++ b/website/content/docs/upgrading/upgrade-to-1.12.x.mdx
@@ -207,8 +207,8 @@ PKI secret engine performs a list operation on the stored certificates. If a lar
 of certificates are stored this can cause long start times on active and standby nodes.
 
 There is currently no workaround for this other than limiting the number of certificates stored
-in Vault via the [PKI tidy](/vault/api-docs/secret/pki.mdx#tidy) or using `no_store`
-flag for [PKI roles](/vault/api-docs/secret/pki.mdx#createupdate-role).
+in Vault via the [PKI tidy](/vault/api-docs/secret/pki#tidy) or using `no_store`
+flag for [PKI roles](/vault/api-docs/secret/pki#createupdate-role).
 
 #### Impacted Versions
 
diff --git a/website/content/docs/upgrading/upgrade-to-1.13.x.mdx b/website/content/docs/upgrading/upgrade-to-1.13.x.mdx
index 37c5466526..0491b940e2 100644
--- a/website/content/docs/upgrading/upgrade-to-1.13.x.mdx
+++ b/website/content/docs/upgrading/upgrade-to-1.13.x.mdx
@@ -149,8 +149,8 @@ PKI secret engine performs a list operation on the stored certificates. If a lar
 of certificates are stored this can cause long start times on active and standby nodes.
 
 There is currently no workaround for this other than limiting the number of certificates stored 
-in Vault via the [PKI tidy](/vault/api-docs/secret/pki.mdx#tidy) or using `no_store` 
-flag for [PKI roles](/vault/api-docs/secret/pki.mdx#createupdate-role).
+in Vault via the [PKI tidy](/vault/api-docs/secret/pki#tidy) or using `no_store` 
+flag for [PKI roles](/vault/api-docs/secret/pki#createupdate-role).
 
 #### Impacted Versions