Minor changes

README.md

@@ -5,23 +5,23 @@ An extremely simple Undo-Manager for Backbone.js
 
 #### Advantages of Backbone.Undo.js
 
-*   Easy to include and exclude
+*   **Easy to include and exclude**
 
     In comparison to other Backbone-based undo-managers like *memento*, you don't have to modify your models 
     or collections to use Backbone.Undo.js. You can have your whole application already set up with all the 
     models and collections you need and then add the undo-manager. That makes it easy to not only include 
     Backbone.Undo.js, but also to remove it again if you don't longer want to use it at some point.
     
-*   Uses Backbone-Events
+*   **Uses Backbone-Events**
 
     To detect an action, Backbone.Undo.js listens to the events Backbone triggeres automatically. You don't have 
     to do anything. You don't have to `store()` or `restore()` certain states. Nothing.
 
-*   Memory-friendly
+*   **Only what's necessary**
 
-    Backbone.Undo.js only stores changes, instead of snapshots (clones of models/collections).
+    Backbone.Undo.js only stores the changes, instead of taking snapshots of the models' / collections' current state.
 
-*   Optimized for Usability
+*   **Optimized for Usability**
    
     In a sophisticated webapp one click of the user might trigger several Backbone-Events which are stored as 
     several Undo-Actions within the Undo-Stack. If the user then calls `undo()` it shouldn't just undo the latest