@@ -135,7 +135,7 @@ started right away: [README-template.md](templates/README-template.md),
 * **Analog Devices Inc.**
 * **Airbus**
 * **Siemens** automatically creates a checklist issue for every new InnerSource project to make maintainers aware of mandatory requirements (e.g. business approval, license & copyright, export control, contributing guidelines, maintainer maturity) as well as best practices (e.g. documentation as code, semantic versioning, continuous integration/deployment).
-* **NatWest Group** - The OSPO's InnerSource playbook includes a blueprint, a checklist for setting up a project for InnerSource with the base documentation standards (`README.md`, `CONTRIBUTING.md`, a communication section) embedded in it. The goal is consistency across projects. The OSPO also offers a readiness assessment against the standard, with must-have and nice-to-have recommendations - for example, rewording a "contact us" section so it invites users to contribute fixes rather than only report problems. See: "Growing InnerSource through OSPO Enablement" (InnerSource Commons Community Call, October 2026, by Pooi Ling Cheong).
+* **NatWest Group** - The OSPO's InnerSource playbook includes a project-setup blueprint with the base documentation standards (`README.md`, `CONTRIBUTING.md`, a communication section) embedded in it, plus a readiness assessment against those standards. See: "Growing InnerSource through OSPO Enablement" (InnerSource Commons Community Call, October 2026, by Pooi Ling Cheong).
 
 ## Authors