[ES] Remove trailing spaces (#21379)

Author: vil02

src/content/docs/email-security/account-setup/escalation-contacts.mdx

@@ -43,4 +43,4 @@ You can enable these special notifications through an opt-in process:
 If you select **Critical Service Events**, the contact will be sent a text and/or an email message. They will need to select the link to confirm the subscriptions.
 
 
-::: 
+:::

src/content/docs/email-security/account-setup/sso/azure.mdx

@@ -72,7 +72,7 @@ Your Azure configuration is now complete. It should look similar to this:
 
 :::note
 
-Now that the application configuration is complete, update **User Assignments** and **Application Properties** as needed to ensure that authorized personnel are able to access the new application from their Apps Catalog. Additionally, you may choose to update the application logo image file or the privacy policy URL. 
+Now that the application configuration is complete, update **User Assignments** and **Application Properties** as needed to ensure that authorized personnel are able to access the new application from their Apps Catalog. Additionally, you may choose to update the application logo image file or the privacy policy URL.
 :::
 
 ## 2. Configure Email Security to connect to Azure

src/content/docs/email-security/deployment/api/setup/exchange-bcc-setup.mdx

@@ -77,7 +77,7 @@ For customers using Microsoft Exchange, setting up Email Security via BCC is qui
 
 :::note
 
-If you have multiple rules, you may need to change the order of the BCC rule and move it to the right location in your rule sequence. This is needed so you can send BCC messages to Email Security (formerly Area 1). Usually, the Email Security BCC rule will be at the top of the ruleset. The configured conditions of the Email Security BCC rule will only trigger for inbound messages. 
+If you have multiple rules, you may need to change the order of the BCC rule and move it to the right location in your rule sequence. This is needed so you can send BCC messages to Email Security (formerly Area 1). Usually, the Email Security BCC rule will be at the top of the ruleset. The configured conditions of the Email Security BCC rule will only trigger for inbound messages.
 :::
 
 ## Email processing and reports

src/content/docs/email-security/deployment/inline/setup/gsuite-area1-mx.mdx

@@ -161,7 +161,7 @@ When you are finished entering these details, select **SAVE**.
 
 :::note
 
-Google handles Groups (that is, distributions lists) differently from user mail accounts. The compliance filters actions are limited to the **Users** account type. If you heavily use Google Groups (that is, distribution lists), quarantining malicious messages using the Email Security quarantine is the recommended method to ensure full protection. 
+Google handles Groups (that is, distributions lists) differently from user mail accounts. The compliance filters actions are limited to the **Users** account type. If you heavily use Google Groups (that is, distribution lists), quarantining malicious messages using the Email Security quarantine is the recommended method to ensure full protection.
 :::
 
 ## 3. Add your domain to Email Security

src/content/docs/email-security/email-configuration/admin-quarantine.mdx

@@ -28,7 +28,7 @@ The messages sent to Admin Quarantine are determined by your [domain settings](/
 
 :::note[Note]
 
-Quarantine by disposition needs to be configured manually per domain. 
+Quarantine by disposition needs to be configured manually per domain.
 :::
 
 ## Access Admin Quarantine

src/content/docs/email-security/email-configuration/email-policies/link-actions.mdx

@@ -55,7 +55,7 @@ Email Link Isolation is now enabled.
 
 :::note
 
-Email Link Isolation does not have advanced configuration options. If you need more fine-grained control over what users can do in an isolated browser session, you must have a Cloudflare Zero Trust account and make your changes on [Browser Isolation](/cloudflare-one/policies/browser-isolation/). 
+Email Link Isolation does not have advanced configuration options. If you need more fine-grained control over what users can do in an isolated browser session, you must have a Cloudflare Zero Trust account and make your changes on [Browser Isolation](/cloudflare-one/policies/browser-isolation/).
 :::
 
 ## URL rewrite ignore patterns

src/content/docs/email-security/email-configuration/phish-submissions/index.mdx

@@ -55,7 +55,7 @@ To enable PSR:
 
 :::note
 
-PSR works only for the phish samples submitted to [user submission addresses](https://horizon.area1security.com/support/service-addresses/). Refer to [Retract settings](/email-security/email-configuration/retract-settings/) to learn more about manual and automatic retraction. 
+PSR works only for the phish samples submitted to [user submission addresses](https://horizon.area1security.com/support/service-addresses/). Refer to [Retract settings](/email-security/email-configuration/retract-settings/) to learn more about manual and automatic retraction.
 :::
 
 ## False positives

src/content/docs/email-security/email-configuration/phish-submissions/phishnet-o365.mdx

@@ -17,7 +17,7 @@ To set up PhishNet with Office 365, you will need:
 
 :::note
 
-Only admin users can deploy PhishNet for all users in Office 365. Non-admin users can deploy PhishNet for themselves, but no other users will have access to it. 
+Only admin users can deploy PhishNet for all users in Office 365. Non-admin users can deploy PhishNet for themselves, but no other users will have access to it.
 :::
 
 ## Set up PhishNet for Office 365
@@ -80,7 +80,7 @@ You have now installed PhishNet for Office 365. After the process is complete, P
 
 :::note
 
-If you cannot find the PhishNet icon, select the **More actions** menu (the three dots menu). 
+If you cannot find the PhishNet icon, select the **More actions** menu (the three dots menu).
 :::
 
 3. Under **Select Submission Type**, select the type of your submission - Spam or Phish.

src/content/docs/email-security/index.mdx

@@ -10,7 +10,7 @@ import { CardGrid, Description, Feature, GlossaryTooltip, LinkTitleCard, Plan, R
 
 <Description>
 
-Stop <GlossaryTooltip term="phishing">phishing</GlossaryTooltip> attacks with Email Security (formerly Area 1) cloud-native email security service. 
+Stop <GlossaryTooltip term="phishing">phishing</GlossaryTooltip> attacks with Email Security (formerly Area 1) cloud-native email security service.
 </Description>
 
 <Plan id="email.email_security.properties.availability.summary" />
@@ -30,31 +30,31 @@ Area 1 is now **Email Security (formerly Area 1)**. Customers who purchased the
 ## Features
 
 <Feature header="Deployment" href="/email-security/deployment/" cta="Evaluate deployment options">
-Email Security (formerly Area 1) provides two architectures to protect your organization: inline or API setup. Inline architecture evaluates email messages before they reach a user's inbox. API architecture evaluates emails when they have already reached a user's inbox. 
+Email Security (formerly Area 1) provides two architectures to protect your organization: inline or API setup. Inline architecture evaluates email messages before they reach a user's inbox. API architecture evaluates emails when they have already reached a user's inbox.
 </Feature>
 
 <Feature header="SSO integration" href="/email-security/account-setup/sso/">
-In addition to standard logins, Email Security (formerly Area 1) offers support for <GlossaryTooltip term="SAML">SAML</GlossaryTooltip> based single sign-on (SSO) logins to your dashboard. 
+In addition to standard logins, Email Security (formerly Area 1) offers support for <GlossaryTooltip term="SAML">SAML</GlossaryTooltip> based single sign-on (SSO) logins to your dashboard.
 </Feature>
 
 <Feature header="Business email compromise" href="/email-security/email-configuration/enhanced-detections/business-email-compromise/">
-Attackers often try to impersonate executives within an organization when sending malicious emails. The Business email compromise (BEC) feature protects against these attacks. 
+Attackers often try to impersonate executives within an organization when sending malicious emails. The Business email compromise (BEC) feature protects against these attacks.
 </Feature>
 
 ***
 
 ## Related products
 
 <RelatedProduct header="Cloudflare Zero Trust" href="/cloudflare-one/" product="cloudflare-one">
-Cloudflare Zero Trust replaces legacy security perimeters with Cloudflare's global network, making the Internet faster and safer for teams around the world. 
+Cloudflare Zero Trust replaces legacy security perimeters with Cloudflare's global network, making the Internet faster and safer for teams around the world.
 </RelatedProduct>
 
 <RelatedProduct header="Email Routing" href="/email-routing/" product="email-routing">
-Email Routing simplifies the way you create and manage custom email addresses. Email Security (formerly Area 1) helps secure your mail infrastructure from phishing attacks. 
+Email Routing simplifies the way you create and manage custom email addresses. Email Security (formerly Area 1) helps secure your mail infrastructure from phishing attacks.
 </RelatedProduct>
 
 <RelatedProduct header="DMARC Management" href="/dmarc-management/" product="dmarc-management">
-Stop brand impersonation. Track and manage every source that is sending emails from your domain. 
+Stop brand impersonation. Track and manage every source that is sending emails from your domain.
 </RelatedProduct>
 
 ***
@@ -65,7 +65,7 @@ Stop brand impersonation. Track and manage every source that is sending emails f
 
 <LinkTitleCard title="Pricing" href="https://www.cloudflare.com/products/zero-trust/email-security/" icon="seti:shell">
 
-Email Security (formerly Area 1) is available as a standalone product purchase. 
+Email Security (formerly Area 1) is available as a standalone product purchase.
 </LinkTitleCard>
 
 </CardGrid>

src/content/docs/email-security/reporting/audit-logs.mdx

@@ -32,5 +32,5 @@ To review preview logs:
 4. From the dropdown, select one of the **Preview** logs. This will show you what would have been retracted with Post Delivery Response or Phish Submission Response enabled.
 
 :::note
-&#x20;<Render file="timestamp" /> 
+&#x20;<Render file="timestamp" />
 :::