From 14d92abd5296e4f90e09b713625e8c2df657a1a5 Mon Sep 17 00:00:00 2001 From: jesopo Date: Wed, 3 Jul 2019 11:27:50 +0100 Subject: [PATCH] '``' -> '>' --- docs/help/channels.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/help/channels.md b/docs/help/channels.md index 0ed3e2a9..c6bd98e5 100644 --- a/docs/help/channels.md +++ b/docs/help/channels.md @@ -6,16 +6,16 @@ BitBot responds to `/invite`s sent to him. If you invite him to a channel with a Some networks do not allow `/invite`d users to bypass channel passwords - thus BitBot can't join without a key and then record the key. There's two things you can do to fix this. -`/msg <bot> config channel:#channel key ` +> /msg <bot> config channel:#channel key or -`/msg <bot> raw JOIN #channel :key here` +> /msg <bot> raw JOIN #channel :key here After using either of these to get BitBot initially in to a channel, he will go about recording and updating the channel's key as described above. ### Disabling join-on-invite -`/msg <bot> config server accept-invites off` +> /msg <bot> config server accept-invites off ### Perform commands on join From the channel you wish him to perform commands for, do: -`!cperform add PRIVMSG {CHAN} :hello, I'm {NICK}` +> !cperform add PRIVMSG {CHAN} :hello, I'm {NICK}