From fc486ed212f71c2e595af27c9d83557144c3def4 Mon Sep 17 00:00:00 2001 From: Mikaela Suomalainen Date: Thu, 28 Aug 2014 14:43:41 +0300 Subject: [PATCH] Use gender neutral pronouns --- develop/style.rst | 8 ++++---- use/capabilities.rst | 10 +++++----- use/configuration.rst | 2 +- use/getting_started.rst | 2 +- 4 files changed, 11 insertions(+), 11 deletions(-) diff --git a/develop/style.rst b/develop/style.rst index 111f5e0..2f19221 100644 --- a/develop/style.rst +++ b/develop/style.rst @@ -125,13 +125,13 @@ Style Guidelines doing isn't important for the user to pay attention to. A user who likes to keep up with things should enjoy watching our logging at the INFO level; it shouldn't be too low-level, but it should give enough - information that it keeps him relatively interested at peak times. + information that it keeps them relatively interested at peak times. - * WARNING: Appropriate to tell a user when we're doing something that he + * WARNING: Appropriate to tell a user when we're doing something that they really ought to pay attention to. Users should see WARNING and think, - "Hmm, should I tell the Supybot developers about this?" Later, he should + "Hmm, should I tell the Supybot developers about this?" Later, they should decide not to, but it should give the user a moment to pause and think - about what's actually happening with his bot. + about what's actually happening with their bot. * ERROR: Appropriate to tell a user when something has gone wrong. Uncaught exceptions are ERRORs. Conditions that we absolutely want to diff --git a/use/capabilities.rst b/use/capabilities.rst index a720c37..81e9d0a 100644 --- a/use/capabilities.rst +++ b/use/capabilities.rst @@ -72,7 +72,7 @@ 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, 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, he tells the user that he lacks the 'bar' +command, '#baz,-bar'. If so, again, it tells the user that they lack the 'bar' capability. If neither of these anticapabilities are present, then the bot just responds to the user like normal. @@ -96,8 +96,8 @@ reserved for people with the next capability. People who are to administer channels with the bot should have the '#channel,op' capability--whatever channel they are to administrate, they should have that channel capability for 'op'. For example, since I want -inkedmn to be an administrator in #supybot, I'll give him the '#supybot,op' -capability. This is in addition to his 'admin' capability, since the 'admin' +inkedmn to be an administrator in #supybot, I'll give them the '#supybot,op' +capability. This is in addition to their 'admin' capability, since the 'admin' capability doesn't give the person having it control over channels. '#channel,op' is used for such things as giving/receiving ops, kickbanning people, lobotomizing the bot, ignoring users in the channel, and managing the @@ -133,6 +133,6 @@ From an user's perspective, capabilities remove a lot of the mystery and esotery of bot control, in addition to giving a bot owner absolutely finegrained control over what users are allowed to do with the bot. Additionally, defaults can be set by the bot owner for both individual channels -and for the bot as a whole, letting an end-user set the policy he wants the bot -to follow for users that haven't yet registered in his user database. It's +and for the bot as a whole, letting an end-user set the policy they want the bot +to follow for users that haven't yet registered in their user database. It's really a revolution! diff --git a/use/configuration.rst b/use/configuration.rst index fbd0d72..6f762c0 100644 --- a/use/configuration.rst +++ b/use/configuration.rst @@ -177,7 +177,7 @@ configuration and user/channel/ignore database configuration. Just edit the interesting files and then give the bot the ``config reload`` command and it'll work as expected. Do note, however, that -Supybot flushes his configuration files and database to disk every hour +Supybot flushes its configuration files and database to disk every hour or so, and if this happens after you've edited your configuration files but before you reload your changes, you could lose the changes you made. To prevent this, set the `supybot.flush` value to 'Off' while editing diff --git a/use/getting_started.rst b/use/getting_started.rst index 8077bf7..8ff7ce2 100644 --- a/use/getting_started.rst +++ b/use/getting_started.rst @@ -39,7 +39,7 @@ bot that you just made to join your channel? Try this in the channel:: supybot: list Replacing 'supybot' with the actual name you picked for your bot, of course. -Your bot should reply with a list of the plugins he currently has loaded. At +Your bot should reply with a list of the plugins it currently has loaded. At least `Admin`, `Channel`, `Config`, `Misc`, `Owner`, and `User` should be there; if you used supybot-wizard to create your configuration file you may have many more plugins loaded. The list command can also be used to list the