[Email Security] Small product name fix (#16484)

* edit to product name

* product name adjustments

* ope missed one

Author: crwaters16

src/content/docs/email-security/api/service-accounts.mdx

@@ -26,7 +26,7 @@ When you connect to the [Email Security (formerly Area 1) API](/email-security/a
 
 If you lose your private key or need to rotate it for security reasons, you can generate a new private key:
 
-1. Log in to the [Cloud Email Security dashboard](https://horizon.area1security.com/).
+1. Log in to the [Email Security dashboard](https://horizon.area1security.com/).
 2. Go to **Settings** (the gear icon).
 3. Go to **Service Accounts**.
 4. On a specific account, select **...** > **Refresh key**.

src/content/docs/reference-architecture/architectures/cloudflare-sase-with-microsoft.mdx

@@ -50,7 +50,7 @@ Microsoft and Cloudflare can be integrated in the following ways.
 * Leveraging Microsoft [InTune](https://learn.microsoft.com/en-us/mem/intune/fundamentals/what-is-intune) device posture in Cloudflare policies to ensure only managed, trusted devices have access to protected resources
 * Using Cloudflare [CASB](/cloudflare-one/applications/scan-apps/) to inspect your [Microsoft 365](https://www.microsoft.com/en-us/microsoft-365/what-is-microsoft-365) tenants and alert on security findings for incorrectly configured accounts and shared files containing sensitive data
 * Using Cloudflare's [Secure Web Gateway](/cloudflare-one/policies/gateway/) to control access to Microsoft SaaS applications such as Outline, OneDrive and Teams
-* Using Cloudflare's [Cloud Email Security](/email-security/) service to increase protection of email from phishing attacks and business email compromise.
+* Using Cloudflare's [Email Security](/email-security/) service to increase protection of email from phishing attacks and business email compromise.
 
 ### Microsoft Entra ID with Cloudflare
 
@@ -91,7 +91,7 @@ Cloudflare's Secure Web Gateway (SWG) can help organizations achieve safe and se
 
 By leveraging Cloudflare SWG as a secure gateway for Microsoft 365 access, organizations can benefit from advanced threat protection, granular access controls, traffic inspection, and centralized visibility, ensuring a safe and secure experience for their users while mitigating risks and maintaining compliance.
 
-### Cloudflare's Cloud Email Security for improved email protection
+### Cloudflare's Email Security for improved email protection
 
 Phishing is the root cause of upwards of 90% of breaches that lead to financial loss and brand damage. Cloudflare's email security solution sits in front of all email going to your Microsoft 365 tenant, filtering out spam, bulk, malicious and spoof content. The solution can leverage Microsoft [rules for quarantine actions](/email-security/deployment/inline/setup/office-365-area1-mx/use-cases/four-user-quarantine-admin-quarantine/), allowing you to fine tune how different email detections are handled.
 
@@ -101,7 +101,7 @@ It is also possible to configure cloud email security to scan [Microsoft 365 inb
 
 ## Summary
 
-By leveraging Cloudflare and its integrations with Microsoft, organizations can establish a Zero Trust security posture that goes beyond the limitations of traditional network security models. With Cloudflare's Zero Trust Network Access (ZTNA), organizations can replace self hosted VPNs and enforce conditional access based on user identity and device posture. The integration with Microsoft Entra ID allows for authentication and access control, while Microsoft InTune provides device posture information. Additionally, Cloudflare's CASB offers visibility into the security of Microsoft 365 configuration, the Secure Web Gateway inspects and filters traffic to Microsoft 365, and Cloud Email Security protects against phishing attacks, ensuring a secure and compliant environment. This approach enables faster and more secure access to applications, while providing granular control over user access based on identity and device posture.
+By leveraging Cloudflare and its integrations with Microsoft, organizations can establish a Zero Trust security posture that goes beyond the limitations of traditional network security models. With Cloudflare's Zero Trust Network Access (ZTNA), organizations can replace self hosted VPNs and enforce conditional access based on user identity and device posture. The integration with Microsoft Entra ID allows for authentication and access control, while Microsoft InTune provides device posture information. Additionally, Cloudflare's CASB offers visibility into the security of Microsoft 365 configuration, the Secure Web Gateway inspects and filters traffic to Microsoft 365, and Email Security protects against phishing attacks, ensuring a secure and compliant environment. This approach enables faster and more secure access to applications, while providing granular control over user access based on identity and device posture.
 
 ![Figure 4: A summary of Cloudflare SASE and Microsoft integrations.](~/assets/images/reference-architecture/cloudflare-sase-with-microsoft/cloudflare-sase-with-microsoft-fig4.svg "Figure 4: A summary of Cloudflare SASE and Microsoft integrations")
 

src/content/docs/reference-architecture/architectures/sase.mdx

@@ -668,7 +668,7 @@ It's worth noting that many of the capabilities described in this document can b
 | Zero Trust Network Access | [How to build Access policies](/cloudflare-one/policies/access/)                                                                                                         |
 | Remote Browser Isolation  | [Understanding browser isolation](/cloudflare-one/policies/browser-isolation/)                                                                                           |
 | API-Driven CASB           | [Scanning SaaS applications](/cloudflare-one/applications/scan-apps/)                                                                                                    |
-| Cloud Email Security      | [Understanding Cloudflare Email Security](/email-security/)                                                                                                              |
+| Email Security      | [Understanding Cloudflare Email Security](/email-security/)                                                                                                              |
 | Replacing your VPN        | [Using Cloudflare to replace your VPN](/learning-paths/replace-vpn/)                                                                                                     |
 
 If you would like to discuss your SASE requirements in greater detail and connect with one of our architects, please visit [https://www.cloudflare.com/cloudflare-one/](https://www.cloudflare.com/cloudflare-one/) and request a consultation.

src/content/docs/reference-architecture/architectures/security.mdx

@@ -574,7 +574,7 @@ The same DLP profiles can also be used in our Cloud Access Security Broker (CASB
 
 A lot of this section has focused on protecting access to private networks and applications, but a business must also protect their employees and their devices. Our [secure web gateway](/cloudflare-one/policies/gateway/) (SWG) service sits between users connected to Cloudflare and any resource they are attempting to access, both public and private. Policies can be written to prevent employees from accessing high-risk websites or known sites that distribute malware. Policies can also be written to mitigate phishing attacks by blocking access to domains and websites known to be part of phishing campaigns. Protecting users and their devices from Internet threats also reduces associated risks of those same users and devices accessing private resources.
 
-Another critical private resource to secure is email. This is often one of the most private of all resources, as it contains confidential communications across your entire organization. It's also a common attack surface, mostly by way of phishing attacks. [Cloud Email Security](https://www.cloudflare.com/zero-trust/products/email-security/) (CES) examines all emails in your employee's inboxes and detects spoofed, malicious, or suspicious emails and can be configured to act accordingly. CES can be integrated by changing your domain MX records and redirecting all email via Cloudflare. Another option, for Microsoft and Google, is to integrate via API and inspect email already in a user’s inbox. For suspicious emails, links in the email are rewritten to leverage Cloudflare's [browser isolation service](/cloudflare-one/policies/browser-isolation/) so that when a user heads to that website, their local machine is protected against any malicious code that might be running in the browser.
+Another critical private resource to secure is email. This is often one of the most private of all resources, as it contains confidential communications across your entire organization. It's also a common attack surface, mostly by way of phishing attacks. [Email Security](https://www.cloudflare.com/zero-trust/products/email-security/) (CES) examines all emails in your employee's inboxes and detects spoofed, malicious, or suspicious emails and can be configured to act accordingly. CES can be integrated by changing your domain MX records and redirecting all email via Cloudflare. Another option, for Microsoft and Google, is to integrate via API and inspect email already in a user’s inbox. For suspicious emails, links in the email are rewritten to leverage Cloudflare's [browser isolation service](/cloudflare-one/policies/browser-isolation/) so that when a user heads to that website, their local machine is protected against any malicious code that might be running in the browser.
 
 ![Cloud email security filters unwanted email traffic from your users inboxes.](~/assets/images/reference-architecture/security/security-ref-arch-23.svg)
 

src/content/partials/email-security/deployment/journaling-connector.mdx

@@ -65,7 +65,7 @@ On the other hand, if your email architecture requires outbound messages to trav
 
 12. Select **Next**.
 
-13. You need to validate the connector by using your tenant’s specific journaling address. To find this address, go to the [Cloud Email Security dashboard](https://horizon.area1security.com/support/service-addresses) > **Support** > **Service Addresses page**.
+13. You need to validate the connector by using your tenant’s specific journaling address. To find this address, go to the [Email Security dashboard](https://horizon.area1security.com/support/service-addresses) > **Support** > **Service Addresses page**.
 
     ![Validate the connector](~/assets/images/email-security/deployment/api-setup/journaling/step13-validate-email.png)
 
@@ -103,7 +103,7 @@ Your connector is now active. You can find it in **Exchange admin center** > **M
 
 7. Select **New rule** to configure a journaling rule, and configure it as follows:
 
-   * **Send journal reports to**: This address is specific to each customer tenant, and can be found in your [Cloud Email Security dashboard](https://horizon.area1security.com/support/service-addresses). For example, `<customer_name>@journaling.mxrecord.io`.
+   * **Send journal reports to**: This address is specific to each customer tenant, and can be found in your [Email Security dashboard](https://horizon.area1security.com/support/service-addresses). For example, `<customer_name>@journaling.mxrecord.io`.
    * **Journal Rule Name**: `Journal Messages to CloudflareArea 1`
    * **Journal messages sent or received from**: *Everyone*
    * **Type of message to journal**: *External messages only*
@@ -114,7 +114,7 @@ Your connector is now active. You can find it in **Exchange admin center** > **M
 
    ![Verify the journal rule information](~/assets/images/email-security/deployment/api-setup/journaling/step9-verify-journal-rules.png)
 
-Once saved, the rule is automatically active. However, it may take a few minutes for the configuration to propagate and start pushing messages to Cloudflare Cloud Email Security. After it propagates, you can access the Cloudflare Cloud Email Security dashboard to check the number of messages processed. This number will grow as journaled messages are sent to Cloudflare Cloud Email Security from your Exchange server.
+Once saved, the rule is automatically active. However, it may take a few minutes for the configuration to propagate and start pushing messages to Cloudflare Email Security. After it propagates, you can access the Cloudflare Email Security dashboard to check the number of messages processed. This number will grow as journaled messages are sent to Cloudflare Email Security from your Exchange server.
 
 ### 3. Compliance
 
@@ -144,7 +144,7 @@ After creating the distribution lists based on regions for your users, configure
 
 7. Select **New rule** to configure a journaling rule, and configure it as follows:
 
-   * **Send journal reports to**: This address is specific to each customer tenant, and can be found in your [Cloud Email Security dashboard](https://horizon.area1security.com/support/service-addresses). If you need to process emails in certain geographic regions, refer to the [Geographic locations](#geographic-locations) table for more information on what address you should use.
+   * **Send journal reports to**: This address is specific to each customer tenant, and can be found in your [Email Security dashboard](https://horizon.area1security.com/support/service-addresses). If you need to process emails in certain geographic regions, refer to the [Geographic locations](#geographic-locations) table for more information on what address you should use.
    * **Journal Rule Name**: `Journal Messages to CloudflareArea 1`
    * **Journal messages sent or received from**: *A specific user or group* and select the user group you [created above](#3-compliance).
    * **Type of message to journal**: *External messages only*
@@ -155,4 +155,4 @@ After creating the distribution lists based on regions for your users, configure
 
    ![Verify the journal rule information](~/assets/images/email-security/deployment/api-setup/journaling/step9-verify-journal-rules.png)
 
-Once saved, the rule is automatically active. However, it may take a few minutes for the configuration to propagate and start pushing messages to Cloudflare Cloud Email Security. After it propagates, you can access the Cloudflare Cloud Email Security dashboard to check the number of messages processed. This number will grow as journaled messages are sent to Cloudflare Cloud Email Security from your Exchange server.
+Once saved, the rule is automatically active. However, it may take a few minutes for the configuration to propagate and start pushing messages to Cloudflare Email Security. After it propagates, you can access the Cloudflare Email Security dashboard to check the number of messages processed. This number will grow as journaled messages are sent to Cloudflare Email Security from your Exchange server.

src/content/partials/email-security/deployment/mx-geographic-locations.mdx

@@ -5,7 +5,7 @@
 
 When configuring the Email Security (formerly Area 1) MX records, it is important to configure hosts with the correct MX priority. This will allow mail flows to the preferred hosts and fail over as needed.
 
-Choose from the following Cloud Email Security MX hosts, and order them by priority. For example, if you are located outside the US and want to prioritize email processing in the EU, add `mailstream-eu1.mxrecord.io` as your first host, and then the US servers.
+Choose from the following Email Security MX hosts, and order them by priority. For example, if you are located outside the US and want to prioritize email processing in the EU, add `mailstream-eu1.mxrecord.io` as your first host, and then the US servers.
 
 | Host                                                                                                                             | Location                | Note                                                                                                                                                                                  |
 | -------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx

@@ -6,7 +6,7 @@ inputParameters: ruleName;;ruleWords;;doFollowing;;img;;ruleName2;;ruleWords2;;d
 import { Image } from 'astro:assets';
 import { GlossaryTooltip, Markdown } from "~/components"
 
-To create the transport rules that will send emails with certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to Cloud Email Security:
+To create the transport rules that will send emails with certain <GlossaryTooltip term="disposition">dispositions</GlossaryTooltip> to Email Security:
 
 1. Open the new [Exchange admin center](https://admin.exchange.microsoft.com/#/homepage).
 

src/content/partials/email-security/deployment/setup-api-overview.mdx

@@ -3,11 +3,11 @@
 
 ---
 
-When you choose an **API deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), email messages only reach Cloud Email Security after they have already reached a user's inbox.
+When you choose an **API deployment** for your [Email Security (formerly Area 1) setup](/email-security/deployment/), email messages only reach Email Security after they have already reached a user's inbox.
 
-Then, through on integrations with your email provider, Cloud Email Security can [retract messages](/email-security/email-configuration/retract-settings/) based on your organization's policies.
+Then, through on integrations with your email provider, Email Security can [retract messages](/email-security/email-configuration/retract-settings/) based on your organization's policies.
 
-![With API deployment, messages travel through Cloud Email Security's email filter after reaching your users.](~/assets/images/email-security/deployment/api-setup/api-deployment-diagram.png)
+![With API deployment, messages travel through Email Security's email filter after reaching your users.](~/assets/images/email-security/deployment/api-setup/api-deployment-diagram.png)
 
 ## Benefits
 
@@ -21,10 +21,10 @@ When you choose API deployment, you get the following benefits:
 
 However, API deployment also has the following disadvantages:
 
-* Cloud Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
-* Cloud Email Security requires read and write access to mailboxes.
+* Email Security is dependent on your email provider's API infrastructure and outages will increase the message dwell time in the inbox.
+* Email Security requires read and write access to mailboxes.
 * Requires API support from your email provider (does not typically support on-premise providers).
-* Your email provider may throttle API requests from Cloud Email Security.
+* Your email provider may throttle API requests from Email Security.
 * Detection rates may be lower if multiple solutions exist.
 * Messages cannot be modified or quarantined.
 * Certain URL rewrite schemes cannot be decoded (for example, Mimecast).