From f49f5b76b95c71150e45fd8ff25cf0b618d68dfd Mon Sep 17 00:00:00 2001
From: Mark Lewis <56076038+ml4@users.noreply.github.com>
Date: Wed, 27 Oct 2021 14:51:41 +0100
Subject: [PATCH] Update index.mdx

Tidy a couple of bullets.
---
 website/content/docs/configuration/index.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/configuration/index.mdx b/website/content/docs/configuration/index.mdx
index 2a2004062fd7..96554e869a74 100644
--- a/website/content/docs/configuration/index.mdx
+++ b/website/content/docs/configuration/index.mdx
@@ -177,13 +177,13 @@ to specify where the configuration is.
 
 The following parameters are used on backends that support [high availability][high-availability].
 
-- `api_addr` `(string: "")` - Specifies the address (full URL) to advertise to
+- `api_addr` `(string: "")` – Specifies the address (full URL) to advertise to
   other Vault servers in the cluster for client redirection. This value is also
   used for [plugin backends][plugins]. This can also be provided via the
   environment variable `VAULT_API_ADDR`. In general this should be set as a full
   URL that points to the value of the [`listener`](#listener) address.
 
-- `cluster_addr` `(string: "")` - – Specifies the address to advertise to other
+- `cluster_addr` `(string: "")` – Specifies the address to advertise to other
   Vault servers in the cluster for request forwarding. This can also be provided
   via the environment variable `VAULT_CLUSTER_ADDR`. This is a full URL, like
   `api_addr`, but Vault will ignore the scheme (all cluster members always