polish: final editorial pass — consistency, language, remove false claims

- Sec 01 subtitle: replace stale 'Collaborative Neutrality' → 'Evidence-Based / Version 1'
- Sec 01: fix typo 'If are interested' → 'If you are interested, apply to join the'
- Sec 02: remove '17 experts / 11 organizations' claim (contradicted Sec 01's 8 orgs)
- Sec 03 quote: soften 'it's essential' → plain declarative
- Sec 03 card 01: remove 'stress-testing / deployment post-mortems' (flagged as untrue)
- Sec 03 card 02: 'working group member' → 'working group members' (grammar)
- Sec 03 card 03: 'Unified standards' → 'Shared language' (matches actual output)
- Sec 13 intro: align inclusion language with Sec 01 ('evidence and engagement, not endorsement')

Author: claudyfaucant

privacy-report.html

@@ -2218,15 +2218,15 @@
           <p class="h-section">Opening Statement</p>
         </div>
         <div class="rhs">
-          <p class="subtitle" style="width:258px">The Principle of Collaborative Neutrality</p>
+          <p class="subtitle" style="width:258px">Evidence-Based<br>Version 1</p>
         </div>
       </div>
       <div class="sec01-body">
         <div class="body-text">
           <p>This is Version 1 of a recurring report series from the Enterprise Ethereum Alliance (EEA) Privacy Working Group. It maps the current landscape of enterprise privacy on Ethereum, drawing on six months of work — beginning November 2025 — by experts across 8 organizations: Applied Blockchain, Consensys, COTI, EY, Kaleido, Polygon, ZKsync/Matter Labs, the Ethereum Foundation and the EEA. The work synthesized technical documentation and deployment evidence.</p>
           <p>The privacy space on Ethereum is evolving rapidly. New implementations launch and existing ones mature almost weekly. This document is therefore a snapshot, with a defined scope: the major privacy implementations contributed by EEA member organizations, where solution characteristics can be supported by live pilots or named enterprise deployments. The same evidence rubric applies to every member.</p>
           <p>This report aims to stay as non-technical as practical — but the topic resists oversimplification. At the EEA we believe the only way to arm a reader against buzzwords is through education. The report links throughout to reference work from neutral organizations such as the Ethereum Foundation's Institutional Privacy Task Force (IPTF), whose IPTF Privacy Map offers a near-holistic mapping of known institutional privacy work.</p>
-          <p>Implementations outside this version exist — non-member projects, academic primitives, and recently launched solutions still being evaluated. The most prominent are listed in Additional Privacy Solutions at the end of the report. Future versions will expand coverage as the space matures, as more evidence accumulates, and as additional organizations engage with the working group. Inclusion is a function of evidence and engagement, not endorsement. If are interested in joining this work apply to join <a href="https://webforms.pipedrive.com/f/6UT1OXeG6VRdX4Cf4AHlF5B1f8tS5axIGahvukW1AEHafwmRuRGVAYo1SKByE9gRPR" target="_blank" rel="noopener">EEA</a></p>
+          <p>Implementations outside this version exist — non-member projects, academic primitives, and recently launched solutions still being evaluated. The most prominent are listed in Additional Privacy Solutions at the end of the report. Future versions will expand coverage as the space matures, as more evidence accumulates, and as additional organizations engage with the working group. Inclusion is a function of evidence and engagement, not endorsement. If you are interested in joining this work, apply to join the <a href="https://webforms.pipedrive.com/f/6UT1OXeG6VRdX4Cf4AHlF5B1f8tS5axIGahvukW1AEHafwmRuRGVAYo1SKByE9gRPR" target="_blank" rel="noopener">EEA</a></p>
         </div>
       </div>
     </div>
@@ -2257,7 +2257,7 @@
     <!-- What This Report Provides -->
     <div class="abs report-provides">
       <p class="h-sub">What This Report Provides</p>
-      <p class="body-text">The Enterprise Ethereum Alliance convened a Privacy Working Group of 17 experts across 11 organizations to map the current landscape. Seven EEA member organizations contributed their solutions, creating the first comprehensive enterprise-focused view of privacy capabilities on Ethereum:</p>
+      <p class="body-text">The Enterprise Ethereum Alliance Privacy Working Group mapped the current enterprise privacy landscape on Ethereum. Seven member organizations contributed their solutions, creating the first evidence-based view of privacy capabilities aligned to enterprise requirements:</p>
     </div>
 
     <!-- 7 solutions grid -->
@@ -2322,7 +2322,7 @@
     <!-- Quote -->
     <div class="abs quote-1">
       <div class="quote-bar-purple"></div>
-      <p class="quote-text">Before examining the solutions themselves, it's essential to understand how this assessment was conducted. The following methodology ensures transparency in how we evaluated each privacy solution and determined readiness classifications.</p>
+      <p class="quote-text">Before examining the solutions themselves, it is important to understand how this assessment was conducted. The following methodology explains how each privacy solution was evaluated and how readiness classifications were determined.</p>
     </div>
 
     <!-- Methodology intro + steering -->
@@ -2350,21 +2350,21 @@
         <p class="step">01 — Input</p>
         <div class="body">
           <p class="ttl">Technical documentation</p>
-          <p class="desc">Provider docs, stress-testing results, deployment post-mortems.</p>
+          <p class="desc">Vendor-provided documentation and publicly verifiable deployment evidence.</p>
         </div>
       </div>
       <div class="method-card mc2">
         <p class="step">02 — Process</p>
         <div class="body">
           <p class="ttl">Cross-institutional review</p>
-          <p class="desc">Cross-review of privacy primitives across all working group member.</p>
+          <p class="desc">Cross-review of privacy primitives and vendor claims across all working group members.</p>
         </div>
       </div>
       <div class="method-card mc3">
         <p class="step">03 — Output</p>
         <div class="body">
-          <p class="ttl">Unified standards</p>
-          <p class="desc">Consolidated enterprise requirements into Ethereum-based privacy standards</p>
+          <p class="ttl">Shared language</p>
+          <p class="desc">A common vocabulary for describing privacy capabilities consistently across vendors and future editions.</p>
         </div>
       </div>
     </div>
@@ -3578,8 +3578,8 @@ <h4>Documentation</h4>
     </div>
 
     <div class="abs sec13-intro">
-      <p>Solutions profiled were contributed by EEA member organizations participating in the Privacy Working Group. Inclusion requires EEA membership and active working group participation.</p>
-      <p>Other privacy solutions exist in the Ethereum ecosystem. These are listed below based on publicly available information. Organizations interested in contributing detailed profiles may contact the EEA about membership.</p>
+      <p>Solutions profiled in this report were contributed by EEA member organizations participating in the Privacy Working Group. Inclusion is a function of evidence and engagement, not endorsement.</p>
+      <p>Other privacy solutions exist in the Ethereum ecosystem. The most prominent are listed below based on publicly available information. Organizations interested in contributing to a future edition may apply to join the EEA working group.</p>
     </div>
 
     <div class="abs sec13-table">