README.rdoc in transitions-0.1.1 vs README.rdoc in transitions-0.1.2

@@ -49,12 +49,16 @@
 
  require 'transitions'
 
 whereever you load your dependencies in your application.
 
-<b>A word of warning:</b> Use symbols, not strings for declaring the state machine. Using strings is *not* supported as is using whitespace in names (because `transitions` possibly generates methods out of this).
+<b>Know limitations:</b> 
 
+* You can only use one state machine per model. While in theory you can define two or more, this won't work as you would expect. Not supporting this was intentional, if you're interested in the ratione look up version 1.0.0 in the CHANGELOG.
+
+* Use symbols, not strings for declaring the state machine. Using strings is *not* supported as is using whitespace in names (because `transitions` possibly generates methods out of this).
+
 === Features
 
 ==== Events
 
 When you declare an event, say <tt>discontinue</tt>, three methods are declared for
@@ -103,10 +107,10 @@
   end
 
 In addition to just specify the method name on the record as a symbol you can pass a lambda to
 perfom some more complex success callbacks:
 
-  event :discontinue, :success => lambda { |order) AdminNotifier.notify_about_discontinued_order(order) } do
+  event :discontinue, :success => lambda { |order| AdminNotifier.notify_about_discontinued_order(order) } do
     transitions :to => :discontinued, :from => [:available, :out_of_stock]
   end
 
 ==== Timestamps