README.md in logster-1.0.0.3.pre vs README.md in logster-1.0.1

@@ -1,6 +1,6 @@
-![logster logo](https://raw.githubusercontent.com/discourse/logster/master/assets/images/logster-logo.png)
+![logster logo](https://raw.githubusercontent.com/discourse/logster/master/assets/images/logo-logster-cropped-small.png)
 
 Logster is an embedded Ruby "exception reporting service" admins can view on live websites, at `http://example.com/logs`
 
 ## Interface
 
@@ -56,10 +56,18 @@
 
 ```
 Logster.store = Logster::RedisStore.new(redis_connection)
 ```
 
+### Heroku Deployment
+In case you may be using the `rails_12factor` gem in a production deployment on Heroku, the standard `Rails.logger` will not cooperate properly with Logster. Extend Rails.logger in your `config/application.rb` or `config/initializers/logster.rb` with: 
+```
+if Rails.env.production?
+    Rails.logger.extend(ActiveSupport::Logger.broadcast(Logster.logger))
+end
+```
+
 ## Thanks
 
 Logster UI is built using [Ember.js](http://emberjs.com/)
 
 ## Contributing
@@ -69,9 +77,15 @@
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create a new Pull Request
 
 # CHANGELOG
+
+- 2015-11-27: Version 1.0.1
+  - New assets and logster logo
+  - Added favicon
+  - Added title
+  - Use rails logger instead of invoking store
 
 - 2015-08-18: Version 0.9.9
   - This marks the largest release of Logster to date, it has been in production use for quite a while, hence the version bump.
   - Feature: automatically group errors in production mode, can be manually controlled via Logster.config.allow_grouping
   - Feature: automatically track application version, can be manually controlled via Logster.config.application_version