Wording changes and formatting

src/cps/email/checker.md

@@ -4,28 +4,26 @@ This site is a work in progress and will be updated regularly.  Please check bac
 
 # DMARC Check Website
 
-The DMARC Check website is a tool to check your email authentication compliance with DMARC.
+The DMARC Check tool can check your email authentication compliance with DMARC.
 
 <https://dmarc-check.itsec.tamu.edu>
 
 After navigating to this site, you will be presented with a unique email address in the form of:
 
 `##########@dmarc.itsec.tamu.edu`
 
-This is a one-time-use address to which you can send an email from an external third party mailer (marketing platforms, cloud apps, etc) to check DMARC compliance. Simply create a test email message with this address as a recipient, and send it.  Be patient!
+This is a one-time-use address to which you can send a message from an external email system (marketing platforms, cloud apps, etc.) to check DMARC compliance. Simply create a test message with this address as a recipient, and send it.  Be patient!
 
 ```admonish warning
-Marketing and mail services may queue mail for several minutes. If you navigate away from this page before the email is received, you will need to start over.
+Email services can queue messages for several minutes. If you navigate away from this page before the message is received, you will need to start over.
 ```
 
 Once received, the tool will attempt to automatically evaluate your message for compliance and display the results on the screen. Should any action be required to become compliant, you will be presented with a list of resources that you can reference.
 
 If the tool reports a DKIM failure, you can follow the steps below for your specific platform to enable DKIM. If your platform is not listed below and our generic guidelines do not apply, please contact `[email protected]` for assistance.
 
 ```admonish info
-For additional information see [KB0021277](https://itselfservice.tamu.edu/tamucs?id=tamucs_kb_article&sys_id=KB0021277) for more information on sending mail using third party mailers.
-```
+This tool is only useful for email sent from a from a third party mailer as `tamu.edu` or a subdomain.
 
-```admonish warning
-This tool is only useful for email sent from an '@tamu.edu' domain or subdomain that has been sent from a third party mailer.
+For additional information see [KB0021277](https://itselfservice.tamu.edu/tamucs?id=tamucs_kb_article&sys_id=KB0021277) for more information on sending messages using third party mailers.
 ```

src/cps/email/dkim.md

@@ -6,7 +6,7 @@ This site is a work in progress and will be updated regularly.  Please check bac
 
 Domain Keys Identified Mail ([DKIM](https://dkim.org/)), is a message-based signature that uses cryptography to sign email and verify that your email was not altered in transit.  Email signed with DKIM confirms your legitimacy and trustworthiness as a sender, which helps deliver your messages to a recipient’s inbox rather than to their junk or spam folders. Over time, DKIM can have a positive impact on your domain reputation, improving your email deliverability.
 
-A DKIM record is a specially formatted DNS TXT record that stores the public key to be used by receiving mail servers when verifying a message’s signature. A DKIM record might look something like this:
+A DKIM record is a specially formatted DNS TXT record that stores the public key to be used by receiving email servers when verifying a message’s signature. A DKIM record might look something like this:
 
 ```shell
 v=DKIM1;t=s;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDBzXkunA
@@ -28,17 +28,17 @@ The DKIM protocol has two steps which utilize a public/private key pair.
 
 ## DKIM Requirements
 
-All domains which send mail are required to have DKIM signing configured for outbound messages.  
+All domains which send email are required to have DKIM signing configured for outbound messages.  
 
 ```admonish info
-DKIM signing is already configured for mail originating in TAMU Gmail, Microsoft 365 Exchange, and mail senders which send mail through smtp-relay.tamu.edu.
+DKIM signing is already configured for email originating in TAMU Gmail, Microsoft 365 Exchange, and applications configured to send email through `smtp-relay.tamu.edu`.
 ```
-DKIM signing is also required for mail sent from third party mailers. Third party mailers include marketing platforms such as MailChimp and Constant Contact.
+All outgoing email, including email sent from third parties like cloud-hosted applications and marketing platforms, should be DKIM signed to ensure deiliverability.
 
 See [KB0021277](https://itselfservice.tamu.edu/tamucs?id=tamucs_kb_article&sys_id=KB0021277) for more information on sending mail using third party mailers.
 
 ```admonish warning
-Messages relayed to external systems via the gateway.tamu.edu delivery setting do not include a DKIM signature. 
+Messages relayed to external systems via the `gateway.tamu.edu` delivery setting do not include a DKIM signature. 
 
 These messages will not deliver to Gmail and Yahoo recipients starting in February 2024.
 ```
@@ -48,10 +48,10 @@ These messages will not deliver to Gmail and Yahoo recipients starting in Februa
 The easiest way to view a DKIM record is to use the command line:
 
 1) Open a console or command line on your computer.
-2) Type `nslookup -q=txt <selector>._domainkey.<subdomain>` where `<selector>` is the DKIM selector and `<subdomain>` is the 'tamu.edu' subdomain name.
+2) Type `nslookup -q=txt <selector>._domainkey.<subdomain>` where `<selector>` is the DKIM selector and `<subdomain>` is the subdomain name.
 
 ```admonish info
-At Texas A&M, the `<selector>` is usually generated by concatenating `pp` to the last six letters of the md5 hash of the domain name.  For example, the subdomain `itsec.tamu.edu` would have a selector of `pp8c7326`.
+At Texas A&M, the `<selector>` is usually generated by concatenating `pp` to the last six letters of the md5 hash of the domain name.  For example, the domain `itsec.tamu.edu` would have a selector of `pp8c7326`.
 ```
 
 3) Press "Enter" to execute the command.

src/cps/email/dmarc.md

@@ -8,7 +8,7 @@ Domain-based Message Authentication, Reporting & Conformance([DMARC](https://dma
 
 1) **Email Authentication** - DMARC combines the authorization and authentication results of two other protocols, SPF and DKIM, to determine whether email sent from your domain is authentic.
 2) **Email Policy** - DMARC publishes a public policy instructing recipient servers how to respond if they receive email from your domain that was determined to be inauthentic.
-3) **Email Reporting** - DMARC provides reporting mechanisms for domain owners to monitor, assess, and confirm that mail being sent from their domain is legitimate.
+3) **Email Reporting** - DMARC provides reporting mechanisms for domain owners to monitor, assess, and confirm that email being sent from their domain is legitimate.
 
 DMARC Policies are creating using a DNS TXT Record.  Here is a sample DMARC record:
 
@@ -27,11 +27,11 @@ Domain Alignment ensures that the email address in the "From:" header is the act
 
 ## DMARC Requirements
 
-All subdomains will inherit the root 'tamu.edu' dommain's DMARC policy. All outgoing mail or mail sent from third party mailers including cloud applications, will need to pass DMARC to ensure deiliverability.
+All subdomains will inherit the `tamu.edu` DMARC policy. All outgoing email, including email sent from third parties like cloud-hosted applications and marketing platforms, is required to pass DMARC to ensure deiliverability.
 
 ## Check a DMARC Record
 
-Subdomains will not have DMARC records, but will inherit from the root 'tamu.edu' domain.  To look up the 'tamu.edu' domain's DMARC record:
+Subdomains will not have DMARC policies of their own, but will inherit from the root `tamu.edu` policy.  To look up the `tamu.edu` DMARC record:
 
 1) Open a console or command line on your computer.
 2) Type `nslookup -q=txt _dmarc.tamu.edu`.

src/cps/email/faq.md

@@ -8,15 +8,14 @@ This site is a work in progress and will be updated regularly.  Please check bac
 
 Email providers like, Gmail and Yahoo are implementing stricter sender guidelines.  These guidelines follow best practices and aim to reduce the amount of fraudulent spam and phishing messages that make it into user's inboxes.  Additionally, these guidelines will likely become standards for all email providers and senders.
 
-## When are these changes needed?
+## When are these changes taking effect?
 
 The majority of the requirements are being implemented in February of 2024.  Google is implementing these changes on February 1, 2024.  Yahoo also specifies a date of early February 2024.  However, some requirements like one-click unsubscribe are being implemented in June of 2024.
 
 ## What are the requirements from Google and Yahoo?
 
-Gmail’s New Email Sender Guidelines
 
-|All Senders|Bulk Senders (>5000 emails per day)|
+|All Senders|Bulk Senders (>5000 messages per day)|
 |-----|-----|
 |SPF or DKIM email authentication|SPF and DKIM email authentication|
 |Valid PTR Records|Valid PTR Records|
@@ -28,65 +27,73 @@ Gmail’s New Email Sender Guidelines
 ||From:header aligned with either SPF domain or DKIM domain|
 ||One-click unsubscribe for marketing mail|
 
-Yahoo's requirements follow the requirements as specified by Google.  For more information see [Googles Email Sender Guidelines](https://support.google.com/mail/answer/81126?sjid=8436365022205706809-NC) and [Yahoo's Email Sender Requirements](https://senders.yahooinc.com/best-practices/).
+For more information:
+- [Googles Email Sender Guidelines](https://support.google.com/mail/answer/81126?sjid=8436365022205706809-NC) 
+- [Yahoo's Email Sender Requirements](https://senders.yahooinc.com/best-practices/).
 
 ## What does Texas A&M's implementation of these standards mean for me?
 
-Exact policies and requirements are still being finalized.  The guidelines provided by Google and Yahoo above will heavily influence the final policy and implementation for Texas A&M services.
+Policies are being finalized. The guidelines provided by Google and Yahoo above will heavily influence the final policy and implementation for Texas A&M.
 
-The implementation will include:
+So far, this includes:
 
-- SPF records to be inherited from tamu.edu, or will include tamu.edu’s SPF record with a softfail
+- SPF records to be inherited from `tamu.edu`, or will include `tamu.edu`’s SPF record with a softfail
 - DKIM signing will be implemented on all outbound mail gateways
-- Third party mailers and cloud applications will utilize DKIM signing for authentication when delivering on behalf of all tamu.edu domains.
+- Third party mailers and cloud applications will utilize DKIM signing for authentication when delivering on behalf of all `tamu.edu` domains.
 - TLS will be used to deliver all outbound mail
 - DMARC compliance will be required for all outbound mail
 
-## What happens if a 'tamu.edu' subdomain does not meet these standards?
+## What happens if a `tamu.edu` domain does not meet these standards?
 
-Failure to comply with these guidelines by February 2024 may result in emails being flagged as spam, quarantined or rejected. Email flagged as spam could significantly impact your reputation and in turn, your communication and marketing efforts.
+Failure to comply with these guidelines by February 2024 may result in messages being flagged as spam, quarantined or rejected. This can significantly impact your domain's reputation and in turn, your communication and marketing efforts.
 
-Repeated violations might lead to your domain or IP address being blacklisted, severely affecting your ability to send emails to users of these services.
+```admonish warning
+Sustained non-compliance can lead to your domain or IP address being blocked entirely, severely affecting your ability to send any messages to users of these services.
+```
+
+## How do I know if I am affected?
 
-## How do I know if my subdomain/service is affected?
+These requirements apply to all messages sent from `tamu.edu` domains.
 
-Mail sent using Texas A&M approved email and marketing platforms should continue to work as intended.  However, services that may be affected are:
+Messages sent using Texas A&M approved email and marketing platforms should continue to work as intended.  However, services that may be affected are:
 
-- Mail sent from third party mailers (marketing platforms like MailChimp and SendGrid)
-- Mail sent directly from cloud applications (SaaS providers, AmazonSES, etc)
-- Mail sent externally that does not flow through approved email gateways
+- Enmail sent from third party mailers (marketing platforms like MailChimp and SendGrid)
+- Email sent directly from cloud applications (SaaS providers, AmazonSES, etc)
+- Email sent externally that does not traverse approved email gateways
 
 ```admonish warning
-If you use a service that impersonates the root 'tamu.edu' domain or 'tamu.edu' subdomains, you may be affected.
+If you use a third-party service that sends messages on behalf of the `tamu.edu` domain or a subdomain, you should verify your compliance with the provided tools.
 
 You can use the [DMARC Check Website](https://dmarc-check.itsec.tamu.edu) to check your DMARC compliance.
 
-For more information on these tools see the [DMARC Check](./checker.md) and [DMARC Report](./reporting.md) pages.
+For more information, see the [DMARC Check](./checker.md) and [DMARC Report](./reporting.md) pages.
 ```
 
 ## What should my SPF record look like?
 
-All 'tamu.edu' subdomains should be configured to inherit from the root 'tamu.edu' domain and should be set to:
+All `tamu.edu` subdomains should be configured to inherit from the root `tamu.edu` domain and should be set to:
 
 `v=spf1 redirect:tamu.edu`
 
-As part of our effort to comply with Google and Yahoo email sender requirements, we will be creating SPF records for all 'tamu.edu' subdomains.  For more information see the [SPF](./spf.md) page.
+```admonish info
+To comply with Google and Yahoo email sender requirements, SPF records will be created for all `tamu.edu` subdomains.  For more information see the [SPF](./spf.md) page.
+```
 
-## How can I check my SPF record?
+## How can I check an SPF record?
 
-The easiest way to check your SPF record is to query DNS.  For detailed instructions see the [SPF](./spf.md) page.
+The easiest way to check an SPF record is to query DNS.  For detailed instructions see the [SPF](./spf.md) page.
 
-## How can I check my DKIM record?
+## How can I check a DKIM record?
 
-The easiest way to check your DKIM record is to query DNS.  For detailed instructions see the [DKIM](./dkim.md) page.
+The easiest way to check a DKIM record is to query DNS.  For detailed instructions see the [DKIM](./dkim.md) page.
 
 ## How can I check my DMARC compliance?
 
-The [DMARC Check website](https://dmarc-check.itsec.tamu.edu) is an automated tool that can be used to check your email authentication compliance with DMARC.
+You can use the [DMARC Check Website](https://dmarc-check.itsec.tamu.edu) to check your DMARC compliance.
 
 For more information on this tool see the [DMARC Check](./checker.md) page.
 
-## How can I find who is sending email on my behalf?
+## How can I see who is sending email from a `tamu.edu` domain?
 
 See the [Resources and Tools](./tools.md) page.
 

src/cps/email/postmaster.md

@@ -11,7 +11,7 @@ According to Gmail, leveraging these tools allows for an assessment of the overa
 ## Access and Setup
 
 ```admonish warning
-Access to Postmaster Tools is reserved for technology professionals who administer 'tamu.edu' email enabled subdomains.
+Access to Postmaster Tools is reserved for technology professionals who administer `tamu.edu` email enabled subdomains.
 ```
 
 1) Request access to the postmaster tools, by opening a ServiceNow ticket or email [[email protected]](mailto:[email protected]).  Please include the domain or list of domains that would like to be granted access.

src/cps/email/protocols.md

@@ -6,7 +6,7 @@ This site is a work in progress and will be updated regularly.  Please check bac
 
 SPF, DKIM and DMARC function as email authentication protocols.  These protocols help providers verify the origin of a message and whether it comes from a trustworthy source.
 
-Technology Services has enabled DMARC for the root tamu.edu domain. DMARC uses both the DKIM and SPF protocols to verify the legitimacy of an email. While this document is intended to explain what these protocols are and how to use them, consider it an overview. This topic is complex.
+Technology Services has enabled DMARC for the `tamu.edu` domain. DMARC uses both the DKIM and SPF protocols to verify the legitimacy of an email. While this document is intended to explain what these protocols are and how to use them, consider it an overview. This topic is complex.
 
 ## What is DMARC?
 

src/cps/email/reporting.md

@@ -72,16 +72,16 @@ The dashboards do not provide information on the status of specific email messag
 ## Using the Site
 
 ```admonish example
-Find who is sending on behalf of a given 'tamu.edu' subdomain.
-```
+Find who is sending on behalf of a given `tamu.edu` subdomain.
 
 1) Login to the [DMARC Reporting website](https://dmarc-report.kb.us-central1.gcp.cloud.es.io:9243/)
 2) Select the hamburger menu -> select 'dashboard' -> select 'DMARC Summary'
 3) Use the 'From Domain' dropdown to select a subdomain.  The dashboards will update based upon the selected 'From Domain'.
 4) In the 'DMARC Passage' pie chart, select the three dots next to 'false' and select 'filter for'
 
-```admonish info
+
 By hovering your mouse over a data table value and using the magnifying glass icons, you can filter on different values.
-```
 
-The dashboards would show data for messages that fail DMARC compliance for the selected "From Domain".  The data can be filtered further to see specific time periods or messages from specific organizations.
+
+The dashboards will show data for messages that fail DMARC compliance for the selected "From Domain".  The data can be filtered further to see specific time periods or messages from specific organizations.
+```

src/cps/email/spf.md

@@ -18,10 +18,10 @@ Publishing an invalid SPF record, including a record containing too many address
 
 ## SPF Requirements
 
-All domains which send mail are required to have an SPF record in DNS. The SPF record should be configured to inherit the policy of the root `tamu.edu` domain.
+All domains which send mail are required to have an SPF record in DNS. The SPF record should be configured to inherit the policy of the `tamu.edu` domain.
 
 ```admonish info
-All subdomains should publish this SPF record:
+To inherit the `tamu.edu` SPF policy, publish this SPF record:
 
 `v=spf1 redirect:tamu.edu`
 

src/cps/email/tools.md

@@ -14,7 +14,7 @@ For more information on this tool see the [DMARC Check](./checker.md) page.
 
 ---
 
-- DMARC Reporting Site (coming soon, reach out to [[email protected]](mailto:[email protected]) for early access) - Technology Services also provides a DMARC reporting site that allows domain owners to proactively manage their email security, identify potential issues, and take corrective actions to enhance the overall email authentication posture of their domain.
+- DMARC Reporting Site (coming soon, reach out to [[email protected]](mailto:[email protected]) for early access) - Technology Services also provides a DMARC reporting site that allows domain custodians to proactively manage their email security, identify potential issues, and take corrective actions to enhance the overall email authentication posture of their domain.
 
 Available Reports: