Test CodeTabs

hashicorp · Sep 18, 2024 · 0c3356c · 0c3356c
1 parent 7a71843
commit 0c3356c
Showing 1 changed file with 6 additions and 14 deletions.
diff --git a/website/content/docs/security/encryption/mtls.mdx b/website/content/docs/security/encryption/mtls.mdx
@@ -25,7 +25,7 @@ Implementing TLS encryption in Consul datacenters improves your deployment's sec
 
 - **Comply with security regulations and standards:** Compliance frameworks and regulations like PCI-DSS and HIPAA mandate the encryption of data in transit, which makes TLS a requirement for Consul deployments in regulated environments.
 
-Murtual TLS (mTLS) requires that all clients and servers have key pairs that are generated by a single Certification Authority (CA). We recommend using a private CA that is not shared with other applications.
+Mutual TLS (mTLS) requires that all clients and servers have key pairs that are generated by a single Certification Authority (CA). We recommend using a private CA that is not shared with other applications.
 
 The following parameters in agent configuration files define the agent verification behavior:
 
@@ -126,7 +126,7 @@ Use the operator method if you need to use a third-party CA or need more fine-gr
 <Tabs>
 <Tab heading="Auto-encryption method" group="auto">
 
-<CodeBlockConfig heading="HCL">
+<CodeTabs tabs={[ "HCL", "JSON" ]}>
 
 ```hcl
 addresses = {
@@ -150,10 +150,6 @@ auto_encrypt {
 }
 ```
 
-</CodeBlockConfig>
-
-<CodeBlockConfig heading="JSON">
-
 ```json
 {
   "addresses": {
@@ -178,13 +174,13 @@ auto_encrypt {
 }
 ```
 
-</CodeBlockConfig>
+</CodeTabs>
 
 </Tab>
 
 <Tab heading="Operator method" group="manual">
 
-<CodeBlockConfig heading="HCL">
+<CodeTabs tabs={[ "HCL", "JSON" ]}>
 
 ```hcl
 addresses = {
@@ -205,10 +201,6 @@ tls {
 }
 ```
 
-</CodeBlockConfig>
-
-<CodeBlockConfig heading="JSON">
-
 ```json
 {
   "addresses": {
@@ -230,7 +222,7 @@ tls {
 }
 ```
 
-</CodeBlockConfig>
+</CodeTabs>
 
 </Tab>
 
@@ -416,7 +408,7 @@ Since Consul `1.12` it is possible to have different settings for the HTTP proto
 
 ### Interact with Consul without a client certificate
 
-If you want to avoid the need to present a valid client certificate every time you interact with Consul using the HTTP API, CLI, or UI, configure Consul to trust all incoming HTTPS connections by seting `tls.https.verify_incoming` to `false`. RPC communications are still mTLS encrypted.
+If you want to avoid the need to present a valid client certificate every time you interact with Consul using the HTTP API, CLI, or UI, configure Consul to trust all incoming HTTPS connections by setting `tls.https.verify_incoming` to `false`. RPC communications are still mTLS encrypted.
 
 <CodeTabs>