README.md in vitrine-0.0.11 vs README.md in vitrine-0.0.12

@@ -65,15 +65,21 @@
 
 ## Packaging and baking
 
 At this point the best way to bake a Vitrine site is to crawl it externally, but we are going to implement
 baking at some point. The idea is that you will end up upgrading the site to either a Node app or a Ruby app
-with it's own +config.ru+ - if after that point you still wish to use Vitrine, you can use it like a Rack
+with it's own `config.ru` - if after that point you still wish to use Vitrine, you can use it like a Rack
 middleware.
 
 ## Using as a middleware
 
-Most actions in Vitrine will fall through to 404, so `Vitrine::App` can be used with `Rack::Cascade`
+Most actions in Vitrine will fall through to 404, so `Vitrine::App` can be used as a middleware handler.
+Put Vitrine into your application stack and it will complement your main application very nicely. But don't
+forget to set `:root` - like so:
+
+    use Vitrine::App.new do | vitrine |
+      vitrine.settings.set :root => File.dirname(__FILE__)
+    end
 
 ## Contributing to vitrine
  
 * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
 * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.