Three visitor-facing strings in the deployment-package handoff source use em dashes, which violate the firm's brand voice rule (No em dashes anywhere. Use commas, colons, semicolons, periods.):
app.jsx:148 — <li>Flat fee — never rises in suit</li>hero.jsx:78 — <a className="sa-btn sa-btn-ghost" href="tel:5028888888"><Icon.Phone … />Call Now — Free Case Review</a>hero.jsx:133 — <p className="heroC-sub">Over $500 million recovered for injured Kentuckians. Every result below is a real case we resolved — not a confidential number, not a guess.</p>Replacement style options (pick one per string):
Flat fee, never rises in suitCall Now: Free Case ReviewEvery result below is a real case we resolved. Not a confidential number, not a guess.Downloads/deployment-package/handoff/source/app.jsx, hero.jsx (and verify data.jsx, tweaks-panel.jsx are comment-only after the changes)Downloads/deployment-package/handoff/README.mdresults-page.html to /var/www/html/public_html/wp-content/uploads/2026/results-page.html on the LIVE Cloudways app (app21392), then purge Cloudflare for the file URL. The wrapping iframe block on WordPress page 54 needs no further changes.Sam asked me to defer fixes inside the package back to the package author rather than have me edit and rebuild a third-party build. The deploy itself succeeded; this is the only outstanding brand-compliance item for the page.
results-page.html into Chrome.—. Zero matches is the success condition.playwright-visual-qa skill (v1.2 or later) against /about-us/our-results/ and confirm the hero CTA reads Call Now: Free Case Review (or whichever replacement was used) and the subhead reads with periods instead of em dashes.