README.md in materialist-0.1.0 vs README.md in materialist-1.0.0

@@ -141,31 +141,37 @@
 describes the name of the active record model to be used.
 If missing, materialist skips materialising the resource itself, but will continue
 with any other functionality -- such as `materialize_link`.
 
 #### `capture <key>, as: <column> (default: key)`
-describes mapping a resource key to database column.
+describes mapping a resource key to a database column.
 
+#### `capture_link_href <key>, as: <column>`
+describes mapping a link href (as it appears on the hateous response) to a database column.
+
 #### `link <key>`
 describes materializing from a relation of the resource. This can be nested to any depth as shown above.
 
 When inside the block of a `link` any other part of DSL can be used and will be evaluated in the context of the relation resource.
 
 ### `materialize_link <key>, topic: <topic> (default: key)`
 describes materializing the linked entity.
 This simulates a `:noop` event on the given topic and the `url` of the
 liked resource `<key>` as it appears on the response (`_links`) -- meaning the materializer for the given topic will be invoked.
 
-#### `after_upsert <method>` -- also `after_destroy`
-describes the name of the instance method to be invoked after a record was materialized.
+#### `after_upsert <method> (, <method>(, ...))` -- also `after_destroy`
+describes the name of the instance method(s) to be invoked after a record was materialized.
 
 ```ruby
 class ZoneMaterializer
   include Materialist::Materializer
 
-  after_upsert :my_method
+  after_upsert :my_method, :my_second_method
 
   def my_method(record)
+  end
+  
+  def my_second_method(record)
   end
 end
 ```
 
 ### Materialized record