commit b25fd8a98ca48abdabfe52ce3bfdd00a8f9fc003
from: Alexander Barton <alex@barton.de>
date: Sun Feb 24 17:53:33 2013 UTC

Commands.txt: Update description of the "KICK" command

commit - be08349dcb2ed3e89040112a241e022ee802baa4
commit + b25fd8a98ca48abdabfe52ce3bfdd00a8f9fc003
blob - 2967b43d8afc5398dda46ceaa1d39d37aa661ea7
blob + 92d25c7f23b8266de286f16efe06de851531b5c9
--- doc/Commands.txt
+++ doc/Commands.txt
@@ -441,12 +441,19 @@ Channel Commands
 	If the channel(s) do not exist, then they will be created.
 
 - KICK
-	KICK <channel> <nick> [<kick-message>]
+	KICK <channel>[,<channel>[,...]] <nickname>[,<nickname>[,...]] [<reason>]
 	.
-	Remove <nick> from <channel>, optional with a <kick-message>.
+	Remove users(s) with <nickname>(s) from <channel>(s).
 	.
-	Only <channel> operators are able to KICK.
+	There must be either exactly one <channel> parameter and multiple
+	<nickname> parameters, or as many <channel> parameters as there are
+	<nickname> parameters. The <reason> is shown to the users being
+	kicked, and the nickname of the current user is used when <reason>
+	is omitted.
 
+	References:
+	 - RFC 2812, 3.2.8 "Kick command"
+
 - LIST
 	LIST [<channels> [<server>]]
 	.