README.md in rack-push-notification-0.4.1

- old
+ new

@@ -1,13 +1,11 @@
 Rack::PushNotification
 ======================
 **A Rack-mountable webservice for managing push notifications**
 
-> This is still in early stages of development, so proceed with caution when using this in a production application. Any bug reports, feature requests, or general feedback at this point would be greatly appreciated.
+`Rack::PushNotification` generates API endpoints that can be consumed by iOS apps to register and unregister for push notifications.
 
-`Rack::PushNotification` generates API endpoints that can be consumed by iOS apps to register and unregister for push notifications. Along with the registration API, `Rack::PushNotification` spawns an admin console that gives you a convenient interface to manage device tokens and compose targeted push notification messages.
-
 ## Example Record
 
 <table>
   <tr><td><tt>token</tt></td><td>"ce8be627 2e43e855 16033e24 b4c28922 0eeda487 9c477160 b2545e95 b68b5969"</td></tr>
   <tr><td><tt>alias</tt></td><td>mattt@heroku.com</td></tr>
@@ -27,10 +25,10 @@
 
 **It is strongly recommended that you use `Rack::PushNotification` in conjunction with some sort of Rack authentication middleware, so that the administration endpoints are not accessible without some form of credentials.**
 
 ## Example Usage
 
-Rack::PushNotification can be run as Rack middleware or as a single web application. All that is required is a connection to a Postgres database.
+Rack::PushNotification can be run as Rack middleware or as a single web application. All that is required is a connection to a Postgres database. You must define this with the environment variable `DATABASE_URL`. For rails, use the `rails-database-url` to define this from the `database.yml`.
 
 ### config.ru
 
 ```ruby
 require 'bundler'