README.md in websocket-extensions-0.1.4 vs README.md in websocket-extensions-0.1.5

@@ -225,12 +225,12 @@
 
 then the `permessage-deflate` extension will receive the call:
 
 ```rb
 ext.create_server_session([
-  {'server_no_context_takeover' => true, 'server_max_window_bits' => 8},
-  {'server_max_window_bits' => 15}
+  { 'server_no_context_takeover' => true, 'server_max_window_bits' => 8 },
+  { 'server_max_window_bits' => 15 }
 ])
 ```
 
 The extension must decide which set of parameters it wants to accept, if any,
 and return a *ServerSession* if it wants to accept the parameters and `nil`
@@ -242,12 +242,12 @@
 implement the following methods, as well as the *Session* API listed below.
 
 ```rb
 client_session.generate_offer
 # e.g.  -> [
-#            {'server_no_context_takeover' => true, 'server_max_window_bits' => 8},
-#            {'server_max_window_bits' => 15}
+#            { 'server_no_context_takeover' => true, 'server_max_window_bits' => 8 },
+#            { 'server_max_window_bits' => 15 }
 #          ]
 ```
 
 This must return a set of parameters to include in the client's
 `Sec-WebSocket-Extensions` offer header. If the session wants to offer multiple
@@ -268,10 +268,10 @@
 A *ServerSession* is the type returned by `ext.create_server_session(offers)`. It
 must implement the following methods, as well as the *Session* API listed below.
 
 ```rb
 server_session.generate_response
-# e.g.  -> {'server_max_window_bits' => 8}
+# e.g.  -> { 'server_max_window_bits' => 8 }
 ```
 
 This returns the set of parameters the server session wants to send in its
 `Sec-WebSocket-Extensions` response header. Only one set of parameters is
 returned to the client per extension. Server sessions that would confict on