From fb2d2de66ba7a686ec644e3d8d4e48c7f8dd56e6 Mon Sep 17 00:00:00 2001 From: Jim Kalafut Date: Wed, 22 Aug 2018 15:26:48 -0700 Subject: [PATCH] Fix docs typos (#5158) --- website/source/guides/operations/vault-ha-consul.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/guides/operations/vault-ha-consul.html.md b/website/source/guides/operations/vault-ha-consul.html.md index 3f7bac185e..f41a47983b 100644 --- a/website/source/guides/operations/vault-ha-consul.html.md +++ b/website/source/guides/operations/vault-ha-consul.html.md @@ -127,7 +127,7 @@ this guide would be `10.1.42.101`, `10.1.42.102`, and `10.1.42.103` respectively Note that the web user interface is enabled (`"ui": true`), and Consul will be -logging at DEBBUG level to the system log (`"log_level": "DEBUG"`). For the +logging at DEBUG level to the system log (`"log_level": "DEBUG"`). For the purpose of this guide, the **`acl_enforce_version_8`** is set to `false` so that we do not need to be concerned with ACLs in this guide. However, you would want to enable ACLs in a production environment and follow the [Consul ACL Guide](https://www.consul.io/docs/guides/acl.html#acl-agent-master-token) for @@ -489,7 +489,7 @@ We're setting the following parameters for our `tcp` listener: - `cluster_address` (string: "127.0.0.1:8201") – Specifies the address to bind to for cluster server-to-server requests. This defaults to one port higher than the value of address. This does not usually need to be set, but can be useful in case Vault servers are isolated from each other in such a way that they need to hop through a TCP load balancer or some other scheme in order to talk. This configuration allows for listening on all interfaces (such that a Vault -command against the loopback address would succeed, for example). Specifical +command against the loopback address would succeed, for example). We're also explicitly setting Vault's [HA parameters](/docs/configuration/index.html#high-availability-parameters) (`api_addr` and `cluster_addr`). Often, it's not necessary to configure these two parameters when using Consul as Vault's storage backend, as Consul will attempt to automatically discover and advertise the address of the active Vault node. However, certain cluster configurations might require them to be explicitly set (accesing Vault through a load balancer, for example).