Updating setup with: better language and structure

Author: Maddy-Cloudflare

src/content/docs/cloudflare-one/email-security/setup/index.mdx

@@ -11,30 +11,43 @@ You can deploy Email Security via:
 - [BCC](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup/)/[Journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/office365-journaling/)
 - [MX/Inline](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/)
 
-If you have an integration, you will be able to:
+When you set up an integration, you will be able to:
 
-- Set up [auto-move events](/cloudflare-one/email-security/auto-moves/).
+- Configure [auto-move events](/cloudflare-one/email-security/auto-moves/).
 - [Synchronize a directory](/cloudflare-one/email-security/directories/).
 - Auto pull EMLs for [reclassification](/cloudflare-one/email-security/email-monitoring/search-email/#reclassify-messages) whose disposition is "None".
 - Manually move messages to different inboxes.
 
+With Microsoft Graph API and BCC/Journaling, Cloudflare scans emails after they reach a users' inbox. MX/Inline instead scans emails before they reach users' inbox.
+
 ## Microsoft Graph API
 
-With Microsoft Graph API, Email Security scans emails after they reach users' inbox. 
+When you deploy Email Security via Microsoft Graph API, you authorize Email Security to scan domains via your email provider credentials.
+
+When you deploy Email Security via Microsoft Graph API:
 
-By deploying Email Security via Microsoft Graph API, you authorize Email Security to scan domains via your email provider credentials. 
+- You authorize Email Security to scan domains via your email provider credentials. 
+- Microsoft Graph API requires minimal configuration effort.
+- Your email inbox is moderately protected.
+- Email Security gets API access into your tenant.
 
 ## BCC/Journaling
 
-Email Security scans emails after they reach users' inbox. 
+When you deploy Email Security via BCC/Journaling:
 
-With BCC/Journaling, you send messages to Email Security via BCC or Journaling configurations within your email provider.
+- You send messages to Email Security via BCC or Journaling configurations within your email provider. 
+- BCC/Journaling requires moderate configuration effort.
+- Your email inbox has the lowest level of protection.
+- Email Security receives copies of your email.
 
 ## MX/Inline
 
-With MX/Inline, Email Security scans emails **before** they reach users' inbox.
+When you deploy Email Security via MX/Inline:
 
-MX/Inline allows you to send messages to Email Security to scan before they reach your users' inbox. You may need to update your MX records.
+- You send messages to Email Security to scan before they reach your users' inbox. You may need to update your MX records.
+- MX/Inline requires significant configuration effort.
+- Your email inbox has the highest level of protection.
+- Email Security has partial access to your mail stream.
 
 With MX/Inline, you will not be able to auto-move emails.