diff --git a/docs/channels/msteams.md b/docs/channels/msteams.md
index ea4ede61b..58028b9eb 100644
--- a/docs/channels/msteams.md
+++ b/docs/channels/msteams.md
@@ -236,7 +236,8 @@ This is often easier than hand-editing JSON manifests.
 2. Find the bot in Teams and send a DM
 3. Check gateway logs for incoming activity
 
-## Setup (minimal text-only)
+## Setup (minimal)
+
 
 1. **Install the Microsoft Teams plugin**
    - From npm: `openclaw plugins install @openclaw/msteams`
diff --git a/docs/channels/twitch.md b/docs/channels/twitch.md
index 6390be668..4e75a5090 100644
--- a/docs/channels/twitch.md
+++ b/docs/channels/twitch.md
@@ -67,7 +67,7 @@ Minimal config:
 - Each account maps to an isolated session key `agent:<agentId>:twitch:<accountName>`.
 - `username` is the bot's account (who authenticates), `channel` is which chat room to join.
 
-## Setup (detailed)
+## Setup (detailed, recommended)
 
 ### Generate credentials
 
diff --git a/docs/channels/zalo.md b/docs/channels/zalo.md
index d230f3032..24e51f870 100644
--- a/docs/channels/zalo.md
+++ b/docs/channels/zalo.md
@@ -53,7 +53,7 @@ It is a good fit for support or notifications where you want deterministic routi
 - DMs share the agent's main session.
 - Groups are not yet supported (Zalo docs state "coming soon").
 
-## Setup (fast path)
+## Setup (quick path)
 
 ### 1) Create a bot token (Zalo Bot Platform)