edit pass: seven-azure-communication-services-email-articles

Author: ShawnJackson

articles/communication-services/concepts/email/email-attachment-allowed-mime-types.md

@@ -1,7 +1,7 @@
 ---
 title: Allowed attachment types for sending email in Azure Communication Services
 titleSuffix: An Azure Communication Services concept article
-description: Learn about how validation for attachment MIME types works for Email Communication Services in Azure Communication Services.
+description: Learn about how validation for attachment MIME types works in Azure Communication Services.
 author: natekimball-msft
 manager: koagbakp
 services: azure-communication-services
@@ -17,11 +17,11 @@ The [SendMail operation](../../quickstarts/email/send-email.md) allows the optio
 
 ## What is a MIME type?
 
-MIME types are a way to identify the type of data that's being sent over the internet. When users send email requests by using Email Communication Services in Azure Communication Services, they can specify the MIME type of the email content so that the recipient's email client can properly display and interpret the message. If an email message includes an attachment, the MIME type is set to the appropriate file type (for example, `application/pdf` for a PDF document).
+MIME types are a way to identify the type of data that's being sent over the internet. When users send email requests by using Azure Communication Services, they can specify the MIME type of the email content so that the recipient's email client can properly display and interpret the message. If an email message includes an attachment, the MIME type is set to the appropriate file type (for example, `application/pdf` for a PDF document).
 
 Developers can ensure that the recipient's email client properly formats and interprets the email message by using MIME types, irrespective of the software or platform that the system is using. This information helps ensure that the email message is delivered correctly and that the recipient can access the content as intended. Using MIME types can also help to improve the security of email communications, because they can indicate whether an email message includes executable content or other potentially harmful elements.
 
-MIME types are a critical component of email communication. By using MIME types with Email Communication Services in Azure Communication Services, developers can help ensure that their email messages are delivered correctly and securely.
+MIME types are a critical component of email communication. By using MIME types with Azure Communication Services, developers can help ensure that their email messages are delivered correctly and securely.
 
 ## Allowed attachment types
 
@@ -101,9 +101,9 @@ IANA maintains a registry of standardized MIME types. The registry includes a un
 
 ## Next steps
 
-* [Prepare an Email Communication Services resource for Azure Communication Services](./prepare-email-communication-resource.md)
+* [Prepare an email communication resource for Azure Communication Services](./prepare-email-communication-resource.md)
 * [Email domains and sender authentication for Azure Communication Services](./email-domain-and-sender-authentication.md)
-* [Send email by using Email Communication Services in Azure Communication Services](../../quickstarts/email/send-email.md)
+* [Send email by using Azure Communication Services](../../quickstarts/email/send-email.md)
 * [Connect a verified email domain in Azure Communication Services](../../quickstarts/email/connect-email-communication-resource.md)
 
 The following documents might be interesting to you:

articles/communication-services/concepts/email/email-overview.md

@@ -46,9 +46,9 @@ With Azure Communication Services, you can speed up your market entry with scala
 
 ## Next steps
 
-- [Prepare an Email Communication Services resource for Azure Communication Services](./prepare-email-communication-resource.md)
+- [Prepare an email communication resource for Azure Communication Services](./prepare-email-communication-resource.md)
 - [Email domains and sender authentication for Azure Communication Services](./email-domain-and-sender-authentication.md)
-- [Create and manage an Email Communication Services resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
+- [Create and manage an email communication resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
 - [Connect a verified email domain in Azure Communication Services](../../quickstarts/email/connect-email-communication-resource.md)
 
 The following topics might be interesting to you:

articles/communication-services/concepts/email/prepare-email-communication-resource.md

@@ -1,7 +1,7 @@
 ---
-title:  Prepare an Email Communication Services resource for Azure Communication Services
+title:  Prepare an email communication resource for Azure Communication Services
 titleSuffix: An Azure Communication Services concept article
-description: Learn about the Email Communication Services resources and domains for Azure Communication Services.
+description: Learn about the Azure Communication Services email resources and domains.
 author: bashan-git
 manager: sphenry
 services: azure-communication-services
@@ -10,34 +10,32 @@ ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
 ---
-# Prepare an Email Communication Services resource for Azure Communication Services 
+# Prepare an email communication resource for Azure Communication Services 
 
-Similar to Chat, VoIP, and SMS modalities under Azure Communication Services, you can send an email by using an Email Communication Services resource in Azure Communication Services. Sending an email requires certain preconfiguration steps, and you have to rely on an admin in your organization to help set that up. The admin needs to:
+Similar to Chat, VoIP, and SMS modalities under Azure Communication Services, you can send an email by using an Azure Communication Services resource. Sending an email requires certain preconfiguration steps, and you have to rely on an admin in your organization to help set that up. The admin needs to:
 
 - Approve the domain that your organization allows you to send mail from.
 - Define the sender domain for the P1 sender email address (also known as the Mail From email address) that appears on the envelope of the email. For more information, see [RFC 5321](https://tools.ietf.org/html/rfc5321).
 - Define the P2 sender email address that most email recipients will see on their email client. For more information, see [RFC 5322](https://tools.ietf.org/html/rfc5322).
 - Set up and verify the sender domain by adding necessary DNS records for the sender verification to succeed.
 
-After the sender domain is configured correctly and verified, you can link the verified domains with your Email Communication Services resource and start sending emails.
-
 One of the key principles for Azure Communication Services is to have a simplified developer experience. The service's email platform simplifies the experience for developers and eases the back-and-forth operation with organization administrators. It improves the end-to-end experience by allowing admin developers to configure the necessary sender authentication and other compliance-related steps to send email, so you can focus on building the required payload.
 
 Your Azure admin creates a new resource of type **Email Communication Services** and adds the allowed email sender domains under this resource. The domains added under this resource type contain all the sender authentication and engagement tracking configurations that must be completed before you start sending emails.
 
-After the sender domain is configured and verified, you can link these domains with your Email Communication Services resource. You can select which  of the verified domains is suitable for your application and connect them to send emails from your application.  
+After the sender domains are configured and verified, you can link these domains with your Azure Communication Services resource. You can select which of the verified domains is suitable for your application and connect them to send emails from your application.  
 
 ## Admin responsibilities
 
 - Plan all the required email domains for the applications in the organization.
-- Create the new Email Communication Services resource.
+- Create the new email communication resource.
 - Add custom domains or get an Azure-managed domain.
 - Perform the sender verification steps for custom domains.
 - Set up a Domain-based Message Authentication, Reporting, and Conformance (DMARC) policy for the verified sender domains.
 
 ## Developer responsibilities
 
-- Connect the preferred domain to Email Communication Services resources.
+- Connect the preferred domain to Azure Communication Services resources.
 - Generate the email payload and define these required elements:
   - Email headers
   - Email body
@@ -49,7 +47,7 @@ After the sender domain is configured and verified, you can link these domains w
 ## Next steps
 
 - [Email domains and sender authentication for Azure Communication Services](./email-domain-and-sender-authentication.md)
-- [Create and manage an Email Communication Services resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
+- [Create and manage an email communication resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
 - [Connect a verified email domain in Azure Communication Services](../../quickstarts/email/connect-email-communication-resource.md)
 
 The following topics might be interesting to you:

articles/communication-services/concepts/email/sdk-features.md

@@ -18,12 +18,12 @@ You can use email client libraries in Azure Communication Services to add transa
 
 | Assembly               | Protocol             |Open vs. closed source| Namespace                          | Capabilities                                                      |
 | ---------------------- | --------------------- | ---|-------------------------- | --------------------------------------------------------------------------- |
-| Azure Resource Manager | REST | Open            | `Azure.ResourceManager.Communication` | Provision and manage Email Communication Services resources             |
+| Azure Resource Manager | REST | Open            | `Azure.ResourceManager.Communication` | Provision and manage email communication resources             |
 | Email                    | REST | Open              | `Azure.Communication.Email`             | Send and get status on email messages |
 
-### Azure email communication resource
+### Azure email communication resources
 
-Azure Resource Manager for Email Communication Services is meant for email domain administration.
+Azure Resource Manager for email communication resources is meant for email domain administration.
 
 | Area           | JavaScript | .NET | Python | Java SE | iOS | Android | Other                          |
 | -------------- | ---------- | ---- | ------ | ---- | -------------- | -------------- | ------------------------------ |
@@ -44,7 +44,7 @@ This sandbox setup helps developers start building the application. Gradually, y
 
 ## Next steps
 
-* [Create and manage an Email Communication Services resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
+* [Create and manage an email communication resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
 * [Connect a verified email domain in Azure Communication Services](../../quickstarts/email/connect-email-communication-resource.md)
 
 The following topics might be interesting to you:

articles/communication-services/concepts/email/sender-reputation-managed-suppression-list.md

@@ -161,7 +161,7 @@ When users are subscribed to multiple lists in your organization, it's ideal to
 * [Best practices for implementing DMARC](/microsoft-365/security/office-365-security/use-dmarc-to-validate-email?preserve-view=true&view=o365-worldwide#best-practices-for-implementing-dmarc-in-microsoft-365)
 * [Troubleshoot your DMARC implementation](/microsoft-365/security/office-365-security/use-dmarc-to-validate-email?preserve-view=true&view=o365-worldwide#troubleshooting-your-dmarc-implementation)
 * [Email domains and sender authentication for Azure Communication Services](./email-domain-and-sender-authentication.md)
-* [Create and manage an Email Communication Services resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
+* [Create and manage an email communication resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
 * [Connect a verified email domain in Azure Communication Services](../../quickstarts/email/connect-email-communication-resource.md)
 
 The following topics might be interesting to you: