diff --git a/History.txt b/History.txt
index 3dd02c3..3c73bcf 100644
--- a/History.txt
+++ b/History.txt
@@ -1,4 +1,14 @@
-== 0.1.6
+== 0.1.6 (2010-08-24)
+
+=== New
+
+* Generator: exception_logger:stylescripts
+** copies the stylesheet for the exception logger to the public dir
+** copies the javascript for the exception logger to the public dir
+
+=== Changes
+
+* Generator: exception_migration renamed to exception_logger:migration
 
 === Testing
 
@@ -7,6 +17,7 @@
 * Create Tests for logged_exception (Model)
 * Create Tests for logged_exceptions_controller (Controller)
 ** Added Tests for GET requests
+** Added Tests for XHR requests
 
 === Optimization
 
diff --git a/README.rdoc b/README.rdoc
index de8765e..f265230 100644
--- a/README.rdoc
+++ b/README.rdoc
@@ -29,11 +29,13 @@ Inside your ApplicationController:
   include ExceptionLogger::ExceptionLoggable # loades the module
   rescue_from Exception, :with => :log_exception_handler # tells rails to forward the 'Exception' (you can change the type) to the handler of the module
 
-== Database Setup
+== Generators
+
+=== Database Setup
 
 Use
 
-  rails g exception_migration
+  rails g exception_logger:migration
 
 This will create a database migration
 
@@ -41,6 +43,16 @@ This will create a database migration
 
 inside db/migrations
 
+=== Stylesheet and Javascript
+
+You can copy the stylesheet and javascript to your applications public directory by using
+
+  rails g exception_logger:stylescripts
+
+This allows you to customize those files.
+
+This will be also necessary if you use a webserver ( e.g. passenger+nginx ) in front of rails which does the static file handling for you.
+
 == Routing
 
 The gem is preconfigured to extend your routes automatically. You can access the logged exceptions by pointing to "/logged_exceptions" inside your application.
@@ -104,7 +116,9 @@ If you have used the exception_logger plugin for your rails2 application and wan
 
 For more and older details read the README.old File.
 
-== Development and Testing
+== Testing & Development
+
+Testing should always start before the actual development.
 
 You can test this gem very easily. Just run: