From 3691e5f7a4277b9edfc4b6088405f1f7f205e76f Mon Sep 17 00:00:00 2001 From: James Phillips Date: Tue, 28 Apr 2015 11:23:35 -0700 Subject: [PATCH] Cleans up some wording on the Consul vs page. --- website/source/intro/vs/consul.html.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/source/intro/vs/consul.html.md b/website/source/intro/vs/consul.html.md index b4af234a66..6ff5fd0471 100644 --- a/website/source/intro/vs/consul.html.md +++ b/website/source/intro/vs/consul.html.md @@ -8,17 +8,17 @@ description: |- # Vault vs. Consul -[Consul](https://consul.io) is system for service discovery, monitoring +[Consul](https://consul.io) is system for service discovery, monitoring, and configuration that is distributed and highly available. Consul also supports an ACL system to restrict access to keys and service information. While Consul can be used to store secret information and gate access using ACLs, it is not designed for that purpose. As such, data is not encrypted in transit nor at rest, it does not have pluggable authentication mechanisms, -there is no per-request auditing mechansim. +and there is no per-request auditing mechansim. -Vault is designed ground up a secret management solution. As such, it -protects secrets in transit and at rest. It provides multiple authentication +Vault is designed from the ground up as a secret management solution. As such, +it protects secrets in transit and at rest. It provides multiple authentication and audit logging mechanisms. Dynamic secret generation allows Vault to avoid providing clients with root privileges to underlying systems and makes it possible to do key rolling and revocation.