docs: typography hygiene across 6 pages (gateway/cli/debug)

vincentkoc · vincentkoc · commit d648673b3105 · 2026-05-06T08:49:27.000-07:00
diff --git a/docs/cli/security.md b/docs/cli/security.md
@@ -2,7 +2,7 @@
 summary: "CLI reference for `openclaw security` (audit and fix common security footguns)"
 read_when:
   - You want to run a quick security audit on config/state
-  - You want to apply safe “fix” suggestions (permissions, tighten defaults)
+  - You want to apply safe "fix" suggestions (permissions, tighten defaults)
 title: "Security"
 ---
 
diff --git a/docs/cli/setup.md b/docs/cli/setup.md
@@ -1,7 +1,7 @@
 ---
 summary: "CLI reference for `openclaw setup` (initialize config + workspace)"
 read_when:
-  - You’re doing first-run setup without full CLI onboarding
+  - You're doing first-run setup without full CLI onboarding
   - You want to set the default workspace path
 title: "Setup"
 ---
diff --git a/docs/debug/node-issue.md b/docs/debug/node-issue.md
@@ -49,7 +49,7 @@ node --import tsx scripts/repro/tsx-name-repro.ts
 
 ## Notes / hypothesis
 
-- `tsx` uses esbuild to transform TS/ESM. esbuild’s `keepNames` emits a `__name` helper and wraps function definitions with `__name(...)`.
+- `tsx` uses esbuild to transform TS/ESM. esbuild's `keepNames` emits a `__name` helper and wraps function definitions with `__name(...)`.
 - The crash indicates `__name` exists but is not a function at runtime, which implies the helper is missing or overwritten for this module in the Node 25 loader path.
 - Similar `__name` helper issues have been reported in other esbuild consumers when the helper is missing or rewritten.
 
diff --git a/docs/gateway/bridge-protocol.md b/docs/gateway/bridge-protocol.md
@@ -77,7 +77,7 @@ Payload fields (all optional unless noted):
 - Bind the bridge to a tailnet IP: `bridge.bind: "tailnet"` in
   `~/.openclaw/openclaw.json` (historical only; `bridge.*` is no longer valid).
 - Clients connect via MagicDNS name or tailnet IP.
-- Bonjour does **not** cross networks; use manual host/port or wide-area DNS‑SD
+- Bonjour does **not** cross networks; use manual host/port or wide-area DNS-SD
   when needed.
 
 ## Versioning
diff --git a/docs/gateway/configuration-examples.md b/docs/gateway/configuration-examples.md
@@ -532,7 +532,7 @@ public-key upgrades still require manual approval.
 
 ### Secure DM mode (shared inbox / multi-user DMs)
 
-If more than one person can DM your bot (multiple entries in `allowFrom`, pairing approvals for multiple people, or `dmPolicy: "open"`), enable **secure DM mode** so DMs from different senders don’t share one context by default:
+If more than one person can DM your bot (multiple entries in `allowFrom`, pairing approvals for multiple people, or `dmPolicy: "open"`), enable **secure DM mode** so DMs from different senders don't share one context by default:
 
 ```json5
 {
diff --git a/docs/gateway/tailscale.md b/docs/gateway/tailscale.md
@@ -35,7 +35,7 @@ Control UI/WebSocket auth can use Tailscale identity headers
 the identity by resolving the `x-forwarded-for` address via the local Tailscale
 daemon (`tailscale whois`) and matching it to the header before accepting it.
 OpenClaw only treats a request as Serve when it arrives from loopback with
-Tailscale’s `x-forwarded-for`, `x-forwarded-proto`, and `x-forwarded-host`
+Tailscale's `x-forwarded-for`, `x-forwarded-proto`, and `x-forwarded-host`
 headers.
 For Control UI operator sessions that include browser device identity, this
 verified Serve path also skips the device-pairing round trip. It does not bypass

Original file line number	Diff line number	Diff line change
`@@ -532,7 +532,7 @@ public-key upgrades still require manual approval.`
`532`	`532`
`533`	`533`	`### Secure DM mode (shared inbox / multi-user DMs)`
`534`	`534`
`535`		-If more than one person can DM your bot (multiple entries in `allowFrom`, pairing approvals for multiple people, or `dmPolicy: "open"`), enable secure DM mode so DMs from different senders don’t share one context by default:
	`535`	+If more than one person can DM your bot (multiple entries in `allowFrom`, pairing approvals for multiple people, or `dmPolicy: "open"`), enable secure DM mode so DMs from different senders don't share one context by default:
`536`	`536`
`537`	`537`	```json5
`538`	`538`	`{`