backport of commit 88ee1d0 (#17602)

Co-authored-by: Bryce Kalow <[email protected]>
Co-authored-by: Luis (LT) Carbonell <[email protected]>

website/content/docs/agent/index.mdx

@@ -368,7 +368,7 @@ template {
 [caching]: /docs/agent/caching
 [persistent-cache]: /docs/agent/caching/persistent-caches
 [template]: /docs/agent/template
-[template-config]: /docs/agent/template-config
+[template-config]: /docs/agent/template#template-configurations
 [agent-api]: /docs/agent/#agent_api-stanza
 [listener]: /docs/agent#listener-stanza
 [listener_main]: /docs/configuration/listener/tcp

website/content/docs/auth/login-mfa/faq.mdx

@@ -38,11 +38,11 @@ The Step-up Enterprise MFA will co-exist with the newly introduced Login MFA sta
 | [Okta Auth MFA](/docs/auth/okta#mfa)           | This is MFA as part of [Okta Auth method](/docs/auth/okta) in Vault OSS, where MFA is enforced by Okta on login. MFA must be satisfied for authentication to be successful. This is different from the Okta MFA method used with Login MFA and Step-up Enterprise MFA. CLI/API login are supported. | MFA is managed externally by Okta | Supported in Vault OSS        |
 | [Step-up Enterprise MFA](/docs/enterprise/mfa) | MFA in Vault Enterprise provides MFA for login and for step-up access to sensitive resources in Vault. Supports CLI/API based login, and ACL/Sentinel policies.                                                                                                                                     | MFA is managed by Vault           | Supported in Vault Enterprise |
 
-~> **Note**: [The Legacy MFA](/docs/auth/mfa) is a **deprecated** MFA workflow in Vault OSS. Refer [here](#q-what-is-the-legacy-mfa-feature) for more details.
+~> **Note**: [The Legacy MFA](/docs/v1.10.x/auth/mfa) is a **deprecated** MFA workflow in Vault OSS. Refer [here](#q-what-is-the-legacy-mfa-feature) for more details.
 
 ### Q: what is the legacy MFA feature?
 
-[Legacy MFA](/docs/auth/mfa) is functionality that was available in Vault OSS, prior to introducing MFA in the Enterprise version. This is now a deprecated feature. Please see the [Vault Feature Deprecation Notice and Plans](/docs/deprecation) for detailed product plans around deprecated features. We plan to remove Legacy MFA in 1.11.
+[Legacy MFA](/docs/v1.10.x/auth/mfa) is functionality that was available in Vault OSS, prior to introducing MFA in the Enterprise version. This is now a deprecated feature. Please see the [Vault Feature Deprecation Notice and Plans](/docs/deprecation) for detailed product plans around deprecated features. We plan to remove Legacy MFA in 1.11.
 
 ### Q: will HCP Vault support MFA?
 

website/content/docs/enterprise/managed-keys.mdx

@@ -17,11 +17,11 @@ To satisfy these requirements, Vault has a centralized abstraction called
 delegate these operations to a trusted external KMS.
 
 Minimally, a managed key consists of a named managed key entry managed by the
-[`sys/managed-key`](../../api-docs/system/managed-keys) API.  Besides a name,
+[`sys/managed-key`](/api-docs/system/managed-keys) API.  Besides a name,
 there are backend specific configurations to access the key in question.
 
 For PKCS#11 (HSM) backed managed keys, the managed key configuration must
-reference a [kms library stanza](../configuration/kms-library) which points
+reference a [kms library stanza](/docs/configuration/kms-library) which points
 to a PKCS#11 access library on the host machine.
 
 Note that a configured, named managed key corresponds to a single key within

website/content/docs/platform/k8s/injector/annotations.mdx

@@ -95,11 +95,11 @@ them, optional commands to run, etc.
 - `vault.hashicorp.com/template-config-exit-on-retry-failure` - controls whether
   Vault Agent exits after it has exhausted its number of template retry attempts
   due to failures. Defaults to `true`. See [Vault Agent Template
-  Config](/docs/agent/template-config) for more details.
+  Config](/docs/agent/template#template-configurations) for more details.
 
 - `vault.hashicorp.com/template-static-secret-render-interval` - If specified,
   configures how often Vault Agent Template should render non-leased secrets such as KV v2.
-  See [Vault Agent Template Config](/docs/agent/template-config) for more details.
+  See [Vault Agent Template Config](/docs/agent/template#template-configurations) for more details.
 
 - `vault.hashicorp.com/agent-extra-secret` - mounts Kubernetes secret as a volume at
   `/vault/custom` in the sidecar/init containers. Useful for custom Agent configs with

website/content/docs/release-notes/1.12.0.mdx

@@ -94,7 +94,7 @@ The billing period for client counting API can now be specified with the [curren
 
 ### Redis database secrets engine
 
-With the support of the Redis database secrets engine, users can use Vault to manage static and dynamic credentials for Redis OSS. The engine  works similarly to other database secrets engines. Refer to the [Redis](/docs/secrets/redis) documentation for more information. Huge thanks to [Francis Hitchens](https://github.com/fhitchen), who contributed their repository to HashiCorp
+With the support of the Redis database secrets engine, users can use Vault to manage static and dynamic credentials for Redis OSS. The engine  works similarly to other database secrets engines. Refer to the [Redis](/docs/secrets/databases/redis) documentation for more information. Huge thanks to [Francis Hitchens](https://github.com/fhitchen), who contributed their repository to HashiCorp
 
 ### AWS elasticache database secrets engine
 With the support of the AWS ElastiCache database secrets engine, users may use Vault to manage static credentials for AWS Elasticache instances. The engine will work similarly to other database secrets engines. Refer to the [elasticache](/docs/secrets/databases/rediselasticache) documentation for more information.