README.textile in spinebox-0.0.14 vs README.textile in spinebox-0.0.15

@@ -5,29 +5,38 @@
 * Ideal for single or few page applications
 * Fully setup, ready to go spine.js environment
 * Develop in coffee-script and sass with fantastic sprockets asset serving
 * Use generators and scaffolding just like with rails
 * Compile assets and serve the whole app completely static
+* Use partials and helpers in your view just like in rails
+* Compilation only updates actually changed files. This is a premise for delta deployment.
 
 h3. Installation
 
 bc.. $ gem install spinebox
 
 h3. Usage
 
 Create your javascript app or HTML files just as you're used to it.
 
-In the HTML files you can use partials just like in rails:
+h4. Create New Project
 
-bc.. render :partial => "navigation.html"
-
-h4. Create new project
-
 bc.. # Create new project an start developing
 $ spinebox new blog
 $ cd blog
 $ spinebox server
 $ open http://localhost:3000/index.html
+
+h4. Use Partials and Helpers
+
+Partials are prefixed with a @_@ to declare them a partial. So you can create a @_navigation.html.erb@ and use it, e.g.
+in the @index.html.erb@ with:
+
+bc.. <%= render :partial => "index.html" %>
+
+p. Helpers are in the helper folder and included by default in any view. So if you want to create special links, etc. that
+you reuse throughout your project simply create a method named @link_to@ in the helper, any any view and partial will have it
+accessible.
 
 h4. Generate models, views and controllers
 
 bc.. # Generate a model view and a controller
 $ spinebox generate model post title author body