README.md in figleaf-0.0.3 vs README.md in figleaf-0.0.4

@@ -1,15 +1,18 @@
 # Figleaf
 [![Build Status](https://secure.travis-ci.org/challengepost/figleaf.png?branch=master)](http://travis-ci.org/challengepost/figleaf)
 
-
 YAML based DRY settings manager.
 
 The YAML expansion functionality came about by our getting tired of having to
 create a YAML file and then create an initializer that would expand such file
 and include in our applications.
 
+`Figleaf::Settings` can be used to override settings depending on what
+environment your application is running. If it's a Rails app, it will know it
+from `Rails.env`, otherwise it will check for `ENV['ENVIRONMENT']`.
+
 ## Installation
 
 Add this line to your application's Gemfile:
 
     gem 'figleaf'
@@ -49,23 +52,35 @@
 files should be:
 
 ```
 development:
   foo: bar
+  some_bool_property: true
 
 test:
   foo: flob
+  some_bool_property: false
 
 production:
   foo: foo
+  some_bool_property: false
 ```
 
 The Figleaf::Settings parser will create a namespace for your YAML file after the file
 name.
 
 Then, assuming that you named your YAML file `mysetting.yml`. you can just
-access `foo` as `Figleaf::Settings.mysetting["foo"]`. (Inspired by Rails' `database.yml`,
-of course.)
+access `foo` as `Figleaf::Settings.mysetting["foo"]`,
+`Figleaf::Settings.mysetting[:foo]` or even `Figleaf::Settings.mysetting.foo`
+(the one caveat of the method expansion is that you can't access attributes that
+collide with Hash methods that way, like `key`). (Inspired by Rails'
+`database.yml`, of course.) In the case of boolean values, the property is
+available as a predicate (eg: `Figleaf::Settings.mysetting.some_bool_property?`)
+
+You can also use `Figleaf::Settings.override_with_local!` to load particular
+file settings in runtime.
+
+Properties can also be lambdas.
 
 ## Contributing
 
 1. Fork it
 2. Create your feature branch (`git checkout -b my-new-feature`)