Mikaela/Limnoria-doc
1
0
Fork 0
mirror of https://github.com/Mikaela/Limnoria-doc.git synced 2024-11-23 12:39:35 +01:00
Code Issues Projects Releases Wiki Activity

Fix typos.

Browse Source
This commit is contained in:
Valentin Lorentz 2020-05-13 19:56:44 +02:00
parent 72c2a684c0
commit e6c5c3a04c
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
use/capabilities.rst
View File

@ -69,7 +69,7 @@ an individual channel!
So when a user 'foo' sends a command 'bar' to the bot on channel '#baz', first
the bot checks to see if the user has the anticapability for the command by
itself, '-bar'. If so, it errors right then and there, telling the user that
he lacks the 'bar' capability. If the user doesn't have that anticapability,
they lacks the 'bar' capability. If the user doesn't have that anticapability,
then the bot checks to see if the user issued the command over a channel, and
if so, checks to see if the user has the antichannelcapability for that
command, '#baz,-bar'. If so, again, it tells the user that they lack the 'bar'
@ -210,8 +210,7 @@ To undo this I would simply do the opposite.::
defaultcapability remove -user.register
defaultcapability remove -unix.progstats
Defaultcapabilities can be restored with two commands from the First is
only in Limnoria at the time of writing::
Defaultcapabilities can be restored with either of these two commands::
config setdefault capabilities
config capabilities [config default capabilities]
@ -219,7 +218,7 @@ only in Limnoria at the time of writing::
Final Word
----------
From a programmer's perspective, capabilties are flexible and easy to use. Any
From a programmer's perspective, capabilities are flexible and easy to use. Any
command can check if a user has any capability, even ones not thought of when
the bot was originally written. Plugins can easily add their own
capabilities--it's as easy as just checking for a capability and documenting