mirror of https://github.com/openclaw/openclaw.git
docs: more channel heading consistency updates (#22541)
* docs: fix thinking link and add reasoning anchor reference * docs(channels): rename LINE setup heading to onboarding * docs(channels): normalize Nextcloud Talk onboarding headings * docs(channels): use onboarding heading for Matrix setup * docs(channels): standardize Discord onboarding heading * docs(channels): standardize Telegram onboarding heading * docs(channels): standardize WhatsApp onboarding heading * docs(channels): rename iMessage onboarding and configuration sections * docs(channels): rename Slack onboarding and configuration sections * docs(channels): rename Signal onboarding heading * docs(channels): standardize Nostr onboarding and configuration headings * docs(channels): standardize Zalo onboarding and configuration headings * docs(channels): standardize Twitch onboarding heading * docs(channels): standardize Google Chat onboarding heading * docs(channels): standardize Mattermost onboarding heading * docs(channels): standardize Zalo Personal onboarding heading * docs(channels): normalize Discord configuration heading * docs(channels): standardize Microsoft Teams onboarding heading * docs(channels): rename Signal configuration reference heading * docs(channels): rename Matrix configuration reference heading * docs(channels): normalize WhatsApp configuration heading * docs(thinking): link reasoning section heading to in-page anchor * docs(channels): normalize BlueBubbles configuration heading * docs(channels): normalize Feishu configuration heading * docs(channels): standardize Signal setup option headings
This commit is contained in:
parent
78caf9ec3d
commit
d7891badda
|
|
@ -284,7 +284,7 @@ Control whether responses are sent as a single message or streamed in blocks:
|
|||
- Media cap via `channels.bluebubbles.mediaMaxMb` (default: 8 MB).
|
||||
- Outbound text is chunked to `channels.bluebubbles.textChunkLimit` (default: 4000 chars).
|
||||
|
||||
## Configuration reference
|
||||
## Configuration
|
||||
|
||||
Full configuration: [Configuration](/gateway/configuration)
|
||||
|
||||
|
|
|
|||
|
|
@ -523,7 +523,7 @@ See [Get group/user IDs](#get-groupuser-ids) for lookup tips.
|
|||
|
||||
---
|
||||
|
||||
## Configuration reference
|
||||
## Configuration
|
||||
|
||||
Full configuration: [Gateway configuration](/gateway/configuration)
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ Disable with:
|
|||
- If you run the bot on **your personal Signal account**, it will ignore your own messages (loop protection).
|
||||
- For "I text the bot and it replies," use a **separate bot number**.
|
||||
|
||||
## Setup path A: link existing Signal account (QR)
|
||||
## Setup (option A): link existing Signal account (QR)
|
||||
|
||||
1. Install `signal-cli` (JVM or native build).
|
||||
2. Link a bot account:
|
||||
|
|
@ -101,7 +101,7 @@ Example:
|
|||
|
||||
Multi-account support: use `channels.signal.accounts` with per-account config and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern.
|
||||
|
||||
## Setup path B: register dedicated bot number (SMS, Linux)
|
||||
## Setup (option B): register dedicated bot number (SMS, Linux)
|
||||
|
||||
Use this when you want a dedicated bot number instead of linking an existing Signal app account.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue