diff --git a/CHANGELOG.md b/CHANGELOG.md
index a33abe9..b05dbf9 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,7 @@ All notable changes to the WordPress Security Benchmark.
 - Added a repo-local generated-artifact smoke validator and a dedicated `Validate Artifacts` workflow for PDF, EPUB, and DOCX outputs.
 - Added a Playwright-based PDF visual smoke test and dedicated workflow with committed baselines for critical page regions.
 - Added a cross-format parity check so a small set of canonical phrases must remain present in the Markdown source and generated PDF, EPUB, and DOCX outputs.
+- Added Learn WordPress's [Writing in the WordPress voice](https://learn.wordpress.org/course/writing-in-the-wordpress-voice/) as the recommended WordPress-specific voice and accessibility reference when benchmark findings are adapted into stakeholder communications.
 
 ### Changed
 - Corrected current-version framing to reflect the public WordPress 7.0 release and remove stale pre-release scheduling language.
diff --git a/README.md b/README.md
index a83253f..4d65cfb 100644
--- a/README.md
+++ b/README.md
@@ -82,6 +82,7 @@ This guide is intended for:
 - **System Administrators** & **DevOps Engineers**
 - **Security Engineers**
 - **WordPress Developers**
+- **Maintainers or communicators** who need to summarize audit findings clearly for stakeholders
 
 Each recommendation includes:
 1. **Description**: Clear explanation of the setting.
@@ -89,6 +90,8 @@ Each recommendation includes:
 3. **Audit**: Commands to verify compliance on your server.
 4. **Remediation**: Step-by-step instructions to apply the fix.
 
+Recommended foundational training for anyone adapting benchmark findings into customer-facing reports, advisories, or internal guidance: [Learn WordPress — Writing in the WordPress voice](https://learn.wordpress.org/course/writing-in-the-wordpress-voice/). Pair it with the [WordPress Security Style Guide](https://github.com/dknauss/wp-security-style-guide) when audit results need to be translated into clear, audience-appropriate language.
+
 ---
 
 ## Related Documents
@@ -115,7 +118,7 @@ This benchmark is one of four complementary documents covering WordPress securit
 
 ## AI-Assisted Editorial Process
 
-This document and the three related documents in this series are revised with the assistance of frontier LLMs. Multiple models independently review all four documents for factual errors, outdated guidance, and cross-document misalignments, with the WordPress Advanced Administration Handbook as primary authority. A human editor reviews, approves, or rejects every recommended change before it is applied. For the full methodology, see **[AI-Assisted Documentation Processes](https://github.com/dknauss/ai-assisted-docs)**. The machine-readable editorial agent skills and cross-document consistency rules are in the [skills directory](https://github.com/dknauss/ai-assisted-docs/tree/main/wp-docs-skills).
+This document and the three related documents in this series are revised with the assistance of frontier LLMs. Multiple models independently review all four documents for factual errors, outdated guidance, and cross-document misalignments, using WordPress technical documentation as primary authority for product facts and the Learn WordPress course [Writing in the WordPress voice](https://learn.wordpress.org/course/writing-in-the-wordpress-voice/) as primary authority for WordPress-specific voice and accessibility guidance. A human editor reviews, approves, or rejects every recommended change before it is applied. For the full methodology, see **[AI-Assisted Documentation Processes](https://github.com/dknauss/ai-assisted-docs)**. The machine-readable editorial agent skills and cross-document consistency rules are in the [skills directory](https://github.com/dknauss/ai-assisted-docs/tree/main/wp-docs-skills).
 
 ## Project Health