README.md in trust-0.6.3 vs README.md in trust-0.7.0

@@ -139,11 +139,35 @@
 ```
 
 #### On ActiveRecord objects you will use permits?
 
 ``` Ruby
[e-mail]? :edit            # does the current user have permission to edit the given customer?
-Customer.permits? :create, @client  # does the current user have permission to create customers?
[e-mail]? :edit                             # does the current user have permission to edit the given customer?
+Customer.permits? :create, @client                   # does the current user have permission to create customers for client?
+Customer.permits? :create, @client, :by => @auditor  # does the auditor have permission to create customers?
+Customer.permits? :create, :for => @client, :by => @auditor  # same as above
+```
+
+#### You can also designate actors in your model so you can test if other people has access to do operations on a subject
+
+Include the Actor role in the class
+``` Ruby
+class Auditor
+  include Trust::Actor
+  ...
+end
+```
+
+Now you can test if the auditor has permission to modify customer for client. Three ways of writing it
+``` Ruby
+  @auditor.can? :update, @customer, @client
+  @auditor.can? :update, @customer, :for => @client
+  @auditor.can? :update, @customer, :parent => @client
+```
+
+The above is the same as
+``` Ruby
[e-mail]? :update, @client, :by => @auditor 
 ```
 
 ## Instance variables
 
 The filter ```load_resource``` will automatically load the instance for the resource in the controller. It will by default use the controller_path to determine the name of the instance variable. Here are a couple of examples: