From b4359001c405bf27c27b16f650b43a0c70e1a3a1 Mon Sep 17 00:00:00 2001
From: Shati Patel <42641846+shati-patel@users.noreply.github.com>
Date: Sat, 23 Jan 2021 14:08:23 +0000
Subject: [PATCH] Update configuring-email-for-notifications.md

---
 .../admin/configuration/configuring-email-for-notifications.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/content/admin/configuration/configuring-email-for-notifications.md b/content/admin/configuration/configuring-email-for-notifications.md
index 8a7abd9ed797..18458967c2a9 100644
--- a/content/admin/configuration/configuring-email-for-notifications.md
+++ b/content/admin/configuration/configuring-email-for-notifications.md
@@ -165,8 +165,7 @@ You'll notice that `metroplex` catches the inbound message, processes it, then m
 
 #### Verify your DNS settings
 
-In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incom
- emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
+In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
 
 #### Check firewall or AWS Security Group settings