docs: clarify pairing commands in faq and troubleshooting

docs/gateway/troubleshooting.md

@@ -36,7 +36,7 @@ If channels are up but nothing answers, check routing and policy before reconnec
 ```bash
 openclaw status
 openclaw channels status --probe
-openclaw pairing list <channel>
+openclaw pairing list --channel <channel> [--account <id>]
 openclaw config get channels
 openclaw logs --follow
 ```
@@ -125,7 +125,7 @@ If channel state is connected but message flow is dead, focus on policy, permiss
 
 ```bash
 openclaw channels status --probe
-openclaw pairing list <channel>
+openclaw pairing list --channel <channel> [--account <id>]
 openclaw status --deep
 openclaw logs --follow
 openclaw config get channels
@@ -290,7 +290,7 @@ Common signatures:
 
 ```bash
 openclaw devices list
-openclaw pairing list <channel>
+openclaw pairing list --channel <channel> [--account <id>]
 openclaw logs --follow
 openclaw doctor
 ```

docs/help/faq.md

@@ -2705,8 +2705,8 @@ Treat inbound DMs as untrusted input. Defaults are designed to reduce risk:
 
 - Default behavior on DM-capable channels is **pairing**:
   - Unknown senders receive a pairing code; the bot does not process their message.
-  - Approve with: `openclaw pairing approve <channel> <code>`
-  - Pending requests are capped at **3 per channel**; check `openclaw pairing list <channel>` if a code didn't arrive.
+  - Approve with: `openclaw pairing approve --channel <channel> [--account <id>] <code>`
+  - Pending requests are capped at **3 per channel**; check `openclaw pairing list --channel <channel> [--account <id>]` if a code didn't arrive.
 - Opening DMs publicly requires explicit opt-in (`dmPolicy: "open"` and allowlist `"*"`).
 
 Run `openclaw doctor` to surface risky DM policies.

docs/help/troubleshooting.md

@@ -62,7 +62,7 @@ flowchart TD
     openclaw status
     openclaw gateway status
     openclaw channels status --probe
-    openclaw pairing list <channel>
+    openclaw pairing list --channel <channel> [--account <id>]
     openclaw logs --follow
     ```