diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
index ed17cc8176f8ef9..0cd6dec01e52bef 100644
--- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
+++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips.mdx
@@ -5,7 +5,9 @@ sidebar:
   order: 4
 ---
 
-When you set up Email Security using an [MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment/), you need to tell your existing email providers to accept messages coming from Email Security's egress IP addresses.
+When you set up Email Security using an [MX/Inline deployment](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment/), your existing email provider will accept messages coming from Email Security's egress IP addresses.
+
+Setting up egress IPs allows Cloudflare to deliver emails to your inbox.
 
 Refer to this page for reference on what IP subnet mask ranges to use.