README.markdown in i2cssh-1.4.0 vs README.markdown in i2cssh-1.4.1

@@ -7,11 +7,11 @@
 ## Installing 
 
     $ gem install i2cssh
 
 ## Usage
-    Usage: i2cssh [options]
+    Usage: i2cssh [options] [username@host [username@host]]
     -A, --forward-agent              Enable SSH agent forwarding
     -l, --login LOGIN                SSH login name
     -F, --fullscreen                 Make the window fullscreen
     -C, --columns COLUMNS            Number of columns (rows will be calculated)
     -R, --rows ROWS                  Number of rows (columns will be calculated)
@@ -21,12 +21,23 @@
     -2, --iterm2                     Use iTerm2 instead of iTerm
     -f, --file FILE                  Cluster file (one hostname per line)
     -c, --cluster CLUSTERNAME        Name of the cluster specified in ~/.i2csshrc
     -m, --machines a,b,c             Comma-separated list of hosts
 
-For -c and -m options, the format username@cluster or username@host.
+For -c and -m options, the format username@cluster or username@host can be used.
 
+The following commands are exactly the same, however, they might serve different purposes:
+
+    $ i2cssh -m user1@host1,user2@host2
+    $ i2cssh user1@host1 user2@host2
+
+Using the -l option will override all usernames:
+
+    $ i2css -l foo user1@host1 user2@host2
+
+This will connect to both host1 and host2 as the user foo
+
 ## i2csshrc
 
 The i2csshrc file is a YAML formatted file that contains the following structure:
 
     ---
@@ -50,10 +61,9 @@
 Make sure the config file is valid YAML (e.g. use spaces instead of tabs)
 
 ## Known issues
 
 - i2cssh uses rb-appscript and that only seems to work on ruby 1.8.7 and breaks on 1.9.x
-- Only a single username can be used when using -m username@host.
 
 ## TODO
 
 - Functional parity with csshX (as far as possible)