README.md in faye-websocket-0.6.1 vs README.md in faye-websocket-0.6.2

@@ -172,12 +172,10 @@
 
 Both the server- and client-side `WebSocket` objects support the following API:
 
 * <b>`on(:open) { |event| }`</b> fires when the socket connection is
   established. Event has no attributes.
-* <b>`onerror`</b> fires when the connection attempt fails. Event has no
-  attributes.
 * <b>`on(:message) { |event| }`</b> fires when the socket receives a message.
   Event has one attribute, <b>`data`</b>, which is either a `String` (for text
   frames) or an `Array` of byte-sized integers (for binary frames).
 * <b>`on(:error) { |event| }`</b> fires when there is a protocol error due to
   bad data sent by the other peer. This event is purely informational, you do
@@ -275,11 +273,11 @@
 supported web servers.
 
 
 ### Running the app with Thin
 
-If you use Thin to server your application you need to include this line after
+If you use Thin to serve your application you need to include this line after
 loading `faye/websocket`:
 
 ```ruby
 Faye::WebSocket.load_adapter('thin')
 ```
@@ -358,9 +356,16 @@
 
 Puma has a command line interface for starting your application:
 
 ```
 $ puma config.ru -p 9292
+```
+
+Or, you can use `rackup`. In development mode, this adds middlewares that don't
+work with async apps, so you must start it in production mode:
+
+```
+$ rackup config.ru -s puma -E production -p 9292
 ```
 
 
 ### Running the app with Rainbows