Removing redundant caution warning

Author: Maddy-Cloudflare

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

@@ -12,12 +12,8 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 For customers using Microsoft Exchange, setting up Email Security via BCC is quick and easy. You need to configure an inbound rule to send emails to Email Security via BCC for processing and detection of potential <GlossaryTooltip term="phishing">phishing</GlossaryTooltip> attacks. The following email flow shows how this works:
 
 ![Email flow when setting up a phishing assessment risk for Microsoft Exchange with Email Security.](~/assets/images/email-security/deployment/api-setup/exchange/bcc-exchange-flow.png)

src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/add-domain.mdx

@@ -7,10 +7,8 @@ sidebar:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
 
 <Render file="rename-area1-to-ces" product="email-security" />
-:::
 
 To set up Email Security (formerly Area 1) for Gmail:
 

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

@@ -11,12 +11,8 @@ head:
 
 import { Render, Details } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 For customers using Gmail, setting up Email Security via BCC is quick and easy. All you need to do is create a content compliance filter to send emails to Email Security through BCC. The following email flow shows how this works:
 
 ![Email flow when setting up a phishing assessment risk for Gmail with Email Security.](~/assets/images/email-security/deployment/api-setup/gmail/gmail-bcc-flow.png)

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

@@ -10,12 +10,8 @@ head:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 When you first get started with Email Security (formerly Area 1), you will need to set up a way to connect your current mail environment with Email Security.
 
 ## BCC setup

src/content/docs/email-security/deployment/api/setup/office365-graph-api.mdx

@@ -9,12 +9,8 @@ description: Learn how to scan and protect Office 365 emails with Email Security
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 For customers using Microsoft Office 365, setting up Email Security via Microsoft Graph API is quick and easy. The following email flow shows how this works:
 
 ![Email flow when setting up Email Security with the Microsoft Graph API](~/assets/images/email-security/deployment/api-setup/ms-graph/ms-graph.png)

src/content/docs/email-security/deployment/api/setup/office365-journaling.mdx

@@ -12,12 +12,8 @@ head:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 For customers using Microsoft Office 365, setting up Email Security via journaling is quick and easy. The following email flow shows how this works:
 
 ![Email flow when setting up a phishing assessment risk for Office 365 with Email Security.](~/assets/images/email-security/deployment/api-setup/journaling/office365-journaling-flow.png)

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

@@ -13,12 +13,8 @@ head:
 
 import { Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 ![A schematic showing where Email Security security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/cisco-area1-mx/cisco-area1-mx.png)
 
 In this tutorial, you will learn how to configure Cisco IronPort with Email Security as MX record. This tutorial is broken down into several steps.

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

@@ -13,12 +13,8 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/cisco-cisco-mx/cisco-mx.png)
 
 In this tutorial, you will learn how to configure Email Security with Cisco as MX record. This tutorial is broken down into several steps.

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

@@ -12,12 +12,8 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/gsuite-area1-mx/gsuite-area1-mx.png)
 
 In this tutorial, you will learn how to configure Google Workspace with Email Security as MX record. This tutorial is broken down into several steps.

src/content/docs/email-security/deployment/inline/setup/office-365-area1-mx/index.mdx

@@ -13,12 +13,8 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-:::caution[Area 1 has been renamed]
-
 <Render file="rename-area1-to-ces" product="email-security" />
 
-:::
-
 ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/o365-area1-mx/office365-mx.png)
 
 In this tutorial, you will learn how to configure Microsoft Office 365 with Email Security as its MX record. This tutorial is broken down into several steps. If at any steps during this tutorial you receive a message saying that you need to run the `Enable-OrganizationCustomization` cmdlet, [refer to section 6](#6-execute-enable-organizationcustomization-if-required).