summaryrefslogtreecommitdiff
path: root/data/chanserv.example.conf
diff options
context:
space:
mode:
authornekoswag <nekoswag@users.noreply.github.com>2017-12-30 21:32:22 +0100
committerAdam <adam@sigterm.info>2017-12-30 15:32:22 -0500
commit0da41502832b2018580f25522ea70a521fad1548 (patch)
tree46403bf10de30ad13ecfacbee2bb4279dc7f18bc /data/chanserv.example.conf
parent68fcb1af9385e99a6d6ddd105cfdba1d75a9a13c (diff)
Update chanserv.example.conf (#206)
Diffstat (limited to 'data/chanserv.example.conf')
-rw-r--r--data/chanserv.example.conf18
1 files changed, 9 insertions, 9 deletions
diff --git a/data/chanserv.example.conf b/data/chanserv.example.conf
index 3c697b88d..301390277 100644
--- a/data/chanserv.example.conf
+++ b/data/chanserv.example.conf
@@ -79,7 +79,7 @@ module
* - cs_secure: Enable channel security, requiring the user to be identified with NickServ in
* order to be considered for being on the access list of the channel
* - secureops: Only allow operator status to be given if the user is on the access list
- * - securefounder: Only allow the real founder of the channel to drop the channel, change it's
+ * - securefounder: Only allow the real founder of the channel to drop the channel, change its
* password, or change the founder or successor
* - signkick: Use of ChanServ's KICK command will cause the user's nick to be signed to the kick.
* - signkick_level: Same as above, but the kick will not be signed if the user is at the same access
@@ -193,7 +193,7 @@ module
*
* If you load cs_xop, you may define a XOP command to associate the privilege with.
*
- * The name of privileges are uesd to associate them with channel modes. If you are using an IRCd that allows you to define additional
+ * The name of privileges are used to associate them with channel modes. If you are using an IRCd that allows you to define additional
* channel status modes, such as InspIRCd, you can associate privileges (and thus access levels, flags, xop) with the mode by naming
* the privileges appropriately. For example, if you had a channel mode called admin, you could create AUTOADMIN, ADMIN, and ADMINME
* privileges which would automatically be associated with that channel mode.
@@ -420,7 +420,7 @@ privilege
*
* Used by chanserv/getkey and nickserv/ajoin.
*
- * Users with this permission can get they channel key with GETKEY and
+ * Users with this permission can get their channel key with GETKEY and
* can use nickserv/ajoin to join channels with keys.
*/
privilege
@@ -836,8 +836,8 @@ command { service = "ChanServ"; name = "HELP"; command = "generic/help"; }
* Provides commands chanserv/access and chanserv/levels.
* Provides the access system "levels".
*
- * Used for giving users access in channels using a levels system. Allows allows redefining which privileges
- * are representated by given level on a per channel basis.
+ * Used for giving users access in channels using a levels system. Allows redefining which privileges
+ * are represented by given level on a per channel basis.
*
* The "LIST" subcommand of chanserv/access will show every access entry on the channel, including access
* entries not added by cs_access. The "level" of these entries will be the representation of the access
@@ -941,7 +941,7 @@ command { service = "ChanServ"; name = "ENTRYMSG"; command = "chanserv/entrymsg"
* Used for giving users access in channels.
*
* The "LIST" subcommand of chanserv/flags will show every access entry on the channel, including access
- * entries not added by cs_flags. The "Flags" of these entries will be the flags representation of the
+ * entries not added by cs_flags. The "flags" of these entries will be the flags representation of the
* privilege set granted by the access entry.
*/
module { name = "cs_flags" }
@@ -1055,7 +1055,7 @@ command { service = "ChanServ"; name = "LOG"; command = "chanserv/log"; group =
* Provides the command chanserv/mode and chanserv/modes.
*
* Used for changing mode locks and changing modes. Multiple commands may be mapped to chanserv/modes, the
- * configuration directive 'set' and 'unset' are used to tell chanserv/modes which modes should be set or
+ * configuration directives 'set' and 'unset' are used to tell chanserv/modes which modes should be set or
* unset when the command is executed.
*/
module
@@ -1287,7 +1287,7 @@ command { service = "ChanServ"; name = "UP"; command = "chanserv/up"; group = "c
* Provides the access system "XOP".
*
* Used for giving users access in channels. Many commands may be linked to chanserv/xop, but the
- * privileges given by each is determined by the privilege:xop settings above. These commands should
+ * privileges given by each are determined by the privilege:xop settings above. These commands should
* be ordered from highest to lowest, as each command inherits the privileges of the commands below
* it.
*
@@ -1309,7 +1309,7 @@ command { service = "ChanServ"; name = "VOP"; command = "chanserv/xop"; group =
/*
* cs_statusupdate
*
- * This module automatically updates users status on channels when the
+ * This module automatically updates users' status on channels when the
* channel's access list is modified.
*/
module { name = "cs_statusupdate" }