README.md in faker_maker-0.7.1 vs README.md in faker_maker-1.0.0

@@ -133,14 +133,32 @@
 result = FakerMaker[:basket].build
 ```
 
 will generate a new instance using the Basket factory. Because an actual class is defined, you can instantiate an object directly through `Basket.new` but that will not populate any of the attributes.
 
-It's possible to override attributes at build-time:
+It's possible to override attributes at build-time, either by passing values as a hash:
 
 ```ruby
+result = FakerMaker[:item].build( name: 'Electric Blanket' )
+```
+
+or by passing in a block:
+
+```ruby
 result = FakerMaker[:item].build{ |i| i.name = 'Electric Sheep' }
 ```
+
+if you're crazy enough to want to do both styles during creation, the values in the block will be preserved, e.g.
+
+```ruby
+result = FakerMaker[:item].build( name: 'Electric Blanket' ) do |i| 
+  i.name = 'Electric Sheep'
+end
+```
+
+then the value of `i.name` is 'Electric Sheep'.
+
+Beware when overriding values in this way: there is no type checking. You will get an exception if you try to set a value to an attribute that doesn't exist but you won't get one if you assign, say, an array of values where you would otherwise have a string and vice versa.
 
 Calling `result.to_json` will give a stringified JSON representation. Because ActiveSupport is used under the covers, `as_json` will give you a `Hash` rather than the stringified version.
 
 As a convenience, you can request a JSON representation directly: