chore: Run pnpm format:fix.

docs/start/pairing.md

@@ -11,8 +11,8 @@ read_when:
 “Pairing” is OpenClaw’s explicit **owner approval** step.
 It is used in two places:
 
-1) **DM pairing** (who is allowed to talk to the bot)
-2) **Node pairing** (which devices/nodes are allowed to join the gateway network)
+1. **DM pairing** (who is allowed to talk to the bot)
+2. **Node pairing** (which devices/nodes are allowed to join the gateway network)
 
 Security context: [Security](/gateway/security)
 
@@ -23,6 +23,7 @@ When a channel is configured with DM policy `pairing`, unknown senders get a sho
 Default DM policies are documented in: [Security](/gateway/security)
 
 Pairing codes:
+
 - 8 characters, uppercase, no ambiguous chars (`0O1I`).
 - **Expire after 1 hour**. The bot only sends the pairing message when a new request is created (roughly once per hour per sender).
 - Pending DM pairing requests are capped at **3 per channel** by default; additional requests are ignored until one expires or is approved.
@@ -39,12 +40,12 @@ Supported channels: `telegram`, `whatsapp`, `signal`, `imessage`, `discord`, `sl
 ### Where the state lives
 
 Stored under `~/.openclaw/credentials/`:
+
 - Pending requests: `<channel>-pairing.json`
 - Approved allowlist store: `<channel>-allowFrom.json`
 
 Treat these as sensitive (they gate access to your assistant).
 
-
 ## 2) Node device pairing (iOS/Android/macOS/headless nodes)
 
 Nodes connect to the Gateway as **devices** with `role: node`. The Gateway
@@ -61,6 +62,7 @@ openclaw devices reject <requestId>
 ### Where the state lives
 
 Stored under `~/.openclaw/devices/`:
+
 - `pending.json` (short-lived; pending requests expire)
 - `paired.json` (paired devices + tokens)
 
@@ -69,7 +71,6 @@ Stored under `~/.openclaw/devices/`:
 - The legacy `node.pair.*` API (CLI: `openclaw nodes pending/approve`) is a
   separate gateway-owned pairing store. WS nodes still require device pairing.
 
-
 ## Related docs
 
 - Security model + prompt injection: [Security](/gateway/security)