From 2932648c05d73cc709b7f6553a30821c069c9e87 Mon Sep 17 00:00:00 2001 From: Amir Yalon Date: Thu, 22 Dec 2016 10:51:20 +0200 Subject: [PATCH] Correct heading level in encryption documentation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The ‘RPC Encryption’ heading is semantically at the same level as ‘Gossip Encryption’. --- website/source/docs/agent/encryption.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/agent/encryption.html.markdown b/website/source/docs/agent/encryption.html.markdown index 1cd091483f..faec7153be 100644 --- a/website/source/docs/agent/encryption.html.markdown +++ b/website/source/docs/agent/encryption.html.markdown @@ -53,7 +53,7 @@ $ consul agent -data-dir=/tmp/consul -config-file=encrypt.json All nodes within a Consul cluster must share the same encryption key in order to send and receive cluster information. -# RPC Encryption with TLS +## RPC Encryption with TLS Consul supports using TLS to verify the authenticity of servers and clients. To enable this, Consul requires that all clients and servers have key pairs that are generated by a single