From e39c20c715ced89a14ea3984bf8ea995d85b0cd9 Mon Sep 17 00:00:00 2001 From: Kent 'picat' Gruber Date: Thu, 5 Nov 2020 16:03:14 -0500 Subject: [PATCH] Capitalize enterprise and add link to enerprise docs --- website/pages/docs/security/security-models/core.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/pages/docs/security/security-models/core.mdx b/website/pages/docs/security/security-models/core.mdx index 128731468..d7776d71d 100644 --- a/website/pages/docs/security/security-models/core.mdx +++ b/website/pages/docs/security/security-models/core.mdx @@ -15,9 +15,9 @@ Consul uses a lightweight gossip and RPC system which provides various essential provide security mechanisms which should be used to enable confidentiality, integrity and authentication. Using defense in depth is crucial for Consul security, and deployment requirements may differ drastically depending on -your use case. Some security features for multi-tenant deployments are offered exclusively in the enterprise version. -This documentation may need to be adapted to your environment, but the general mechanisms for a secure Consul deployment -revolve around: +your use case. Some security features for multi-tenant deployments are offered exclusively in the +[Enterprise](/docs/enterprise) version. This documentation may need to be adapted to your +environment, but the general mechanisms for a secure Consul deployment revolve around: - **mTLS** - Mutual authentication of both the TLS server and client x509 certificates prevents internal abuse from unauthorized access to network components within the cluster.