docs: audit and fix 3 pages (typography across help/channels)

docs/channels/signal.md

@@ -226,7 +226,7 @@ Groups:
 
 - Use `message action=react` with `channel=signal`.
 - Targets: sender E.164 or UUID (use `uuid:<id>` from pairing output; bare UUID works too).
-- `messageId` is the Signal timestamp for the message you’re reacting to.
+- `messageId` is the Signal timestamp for the message you're reacting to.
 - Group reactions require `targetAuthor` or `targetAuthorUuid`.
 
 Examples:

docs/help/gpt55-codex-agentic-parity-maintainers.md

@@ -98,7 +98,7 @@ PR D is the proof layer. It should not be the reason runtime-correctness PRs are
 
 ### PR B
 
-- auth/proxy/runtime failures stop collapsing into generic “model failed” handling
+- auth/proxy/runtime failures stop collapsing into generic "model failed" handling
 - `/elevated full` is only described as available when it is actually available
 - blocked reasons are visible to both the model and the user-facing runtime
 

docs/help/scripts.md

@@ -13,7 +13,7 @@ Use these when a task is clearly tied to a script; otherwise prefer the CLI.
 
 - Scripts are **optional** unless referenced in docs or release checklists.
 - Prefer CLI surfaces when they exist (example: auth monitoring uses `openclaw models status --check`).
-- Assume scripts are host‑specific; read them before running on a new machine.
+- Assume scripts are host-specific; read them before running on a new machine.
 
 ## Auth monitoring scripts