refactor: rename to openclaw

docs/start/pairing.md

@@ -3,12 +3,12 @@ summary: "Pairing overview: approve who can DM you + which nodes can join"
 read_when:
   - Setting up DM access control
   - Pairing a new iOS/Android node
-  - Reviewing Moltbot security posture
+  - Reviewing OpenClaw security posture
 ---
 
 # Pairing
 
-“Pairing” is Moltbot’s explicit **owner approval** step.
+“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)
@@ -30,15 +30,15 @@ Pairing codes:
 ### Approve a sender
 
 ```bash
-moltbot pairing list telegram
-moltbot pairing approve telegram <CODE>
+openclaw pairing list telegram
+openclaw pairing approve telegram <CODE>
 ```
 
 Supported channels: `telegram`, `whatsapp`, `signal`, `imessage`, `discord`, `slack`.
 
 ### Where the state lives
 
-Stored under `~/.clawdbot/credentials/`:
+Stored under `~/.openclaw/credentials/`:
 - Pending requests: `<channel>-pairing.json`
 - Approved allowlist store: `<channel>-allowFrom.json`
 
@@ -53,20 +53,20 @@ creates a device pairing request that must be approved.
 ### Approve a node device
 
 ```bash
-moltbot devices list
-moltbot devices approve <requestId>
-moltbot devices reject <requestId>
+openclaw devices list
+openclaw devices approve <requestId>
+openclaw devices reject <requestId>
 ```
 
 ### Where the state lives
 
-Stored under `~/.clawdbot/devices/`:
+Stored under `~/.openclaw/devices/`:
 - `pending.json` (short-lived; pending requests expire)
 - `paired.json` (paired devices + tokens)
 
 ### Notes
 
-- The legacy `node.pair.*` API (CLI: `moltbot nodes pending/approve`) is a
+- The legacy `node.pair.*` API (CLI: `openclaw nodes pending/approve`) is a
   separate gateway-owned pairing store. WS nodes still require device pairing.