README.md in lotus-validations-0.2.1 vs README.md in lotus-validations-0.2.2

@@ -55,18 +55,50 @@
 require 'lotus/validations'
 
 class Person
   include Lotus::Validations
 
-  attribute :name
+  attribute :name,  presence: true
+  attribute :email, presence: true
 end
 
-person = Person.new(name: 'Luca', age: 32)
-person.name # => "Luca"
-person.age  # => raises NoMethodError because `:age` wasn't defined as attribute.
+person = Person.new(name: 'Luca', email: '[e-mail]', age: 32)
+person.name  # => "Luca"
+person.email # => "[e-mail]"
+person.age   # => raises NoMethodError because `:age` wasn't defined as attribute.
 ```
 
+### Validations
+
+If you prefer Lotus::Validations to **only define validations**, but **not attributes**,
+you can use the following alternative syntax.
+
+```ruby
+require 'lotus/validations'
+
+class Person
+  include Lotus::Validations
+  attr_accessor :name, :email
+
+  # Custom initializer
+  def initialize(attributes = {})
+    @name, @email = attributes.values_at(:name, :email)
+  end
+
+  validates :name,  presence: true
+  validates :email, presence: true
+end
+
+person = Person.new(name: 'Luca', email: '[e-mail]')
+person.name  # => "Luca"
+person.email # => "[e-mail]"
+```
+
+This is a bit more verbose, but offers a great level of flexibility for your
+Ruby objects. It also allows to use Lotus::Validations in combination with
+**other frameworks**.
+
 ### Coercions
 
 If a Ruby class is passed to the `:type` option, the given value is coerced, accordingly.
 
 #### Standard coercions
@@ -127,10 +159,10 @@
 end
 
 person = Person.new(fav_number: '23', date: 'Oct 23, 2014')
 person.valid?
 
-person.fav_number # => 23
+person.fav_number # => #<FavNumber:0x007ffc644bba00 @number="23">
 person.date       # => this raises an error, because BirthDate#initialize doesn't accept any arg
 ```
 
 ### Validations