@@ -67,10 +67,10 @@ an individual channel!
67
67
So when a user 'foo' sends a command 'bar' to the bot on channel '#baz', first
68
68
the bot checks to see if the user has the anticapability for the command by
69
69
itself, '-bar'. If so, it errors right then and there, telling the user that
70
- he lacks the 'bar' capability. If the user doesn't have that anticapability,
70
+ they lack the 'bar' capability. If the user doesn't have that anticapability,
71
71
then the bot checks to see if the user issued the command over a channel, and
72
72
if so, checks to see if the user has the antichannelcapability for that
73
- command, '#baz,-bar'. If so, again, he tells the user that he lacks the 'bar'
73
+ command, '#baz,-bar'. If so, again, it tells the user that they lack the 'bar'
74
74
capability. If neither of these anticapabilities are present, then the bot
75
75
just responds to the user like normal.
76
76
@@ -94,7 +94,7 @@ reserved for people with the next capability.
94
94
People who are to administer channels with the bot should have the
95
95
'#channel,op' capability--whatever channel they are to administrate, they
96
96
should have that channel capability for 'op'. For example, since I want
97
- inkedmn to be an administrator in #supybot, I'll give him the '#supybot,op'
97
+ inkedmn to be an administrator in #supybot, I'll give them the '#supybot,op'
98
98
capability. This is in addition to his 'admin' capability, since the 'admin'
99
99
capability doesn't give the person having it control over channels.
100
100
'#channel,op' is used for such things as giving/receiving ops, kickbanning
@@ -131,6 +131,6 @@ From an user's perspective, capabilities remove a lot of the mystery and
131
131
esotery of bot control, in addition to giving a bot owner absolutely
132
132
finegrained control over what users are allowed to do with the bot.
133
133
Additionally, defaults can be set by the bot owner for both individual channels
134
- and for the bot as a whole, letting an end-user set the policy he wants the bot
135
- to follow for users that haven't yet registered in his user database. It's
134
+ and for the bot as a whole, letting an end-user set the policy they want the
135
+ bot to follow for users that haven't yet registered in its user database. It's
136
136
really a revolution!
0 commit comments