aboutsummaryrefslogtreecommitdiffstats
path: root/dev-docs/osterman.md
diff options
context:
space:
mode:
Diffstat (limited to 'dev-docs/osterman.md')
-rw-r--r--dev-docs/osterman.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/dev-docs/osterman.md b/dev-docs/osterman.md
index 75e058c..fca9ca0 100644
--- a/dev-docs/osterman.md
+++ b/dev-docs/osterman.md
@@ -71,7 +71,7 @@ bot.memory["os_last"] - {(channel, nick): timestamp} last message time
`os_join_flood` is keyed by `(channel, host)` so join flood counts are isolated
per channel. A user joining multiple channels quickly does not bleed the flood
-counter across channels. `os_nick_flood` is network-wide by design — NICK changes
+counter across channels. `os_nick_flood` is network-wide by design; NICK changes
apply across all channels.
The other modules access these keys with safe fallbacks in case of load order
@@ -137,7 +137,7 @@ Event types: `join`, `part`, `quit`, `kick`, `ban`, `nick`, `mute`, `unmute`,
| Greetings, idle warns, bad word warn | `bot.notice` | nick |
`_notice(bot, nick, text)` in `commands.py` and `help.py` calls
-`bot.notice(text, nick)` — a true IRC NOTICE, not a PRIVMSG. This is the
+`bot.notice(text, nick)`: a true IRC NOTICE, not a PRIVMSG. This is the
standard approach for automated bot feedback that should not trigger other
bots or appear as a regular chat message.
@@ -205,7 +205,7 @@ indices, then `del N`. This avoids ambiguity with regex special characters.
### !unban db cleanup
`cmd_unban` removes matching entries from the internal ban database using
-`fnmatch.fnmatch(b["mask"], mask)` — tests whether the stored ban mask matches
+`fnmatch.fnmatch(b["mask"], mask)`: tests whether the stored ban mask matches
the target being unbanned. The argument order matters: `fnmatch(pattern, string)`
where the stored mask is the pattern and the unban target is the string being
tested against it.
@@ -222,7 +222,7 @@ Sent as IRC NOTICE to the joining user. Controlled by the `greet` config key.
### !seen scoping
-In channel: checks only the current channel — live presence check against
+In channel: checks only the current channel. Live presence check against
`bot.channels[channel]`, then DB query with `AND channel = ?`. Reports in channel.
In PM: owner/ACL only. Cross-channel lookup across all joined channels and