README.md in swiss_db-0.7.2 vs README.md in swiss_db-1.0.0

@@ -1,11 +1,17 @@
-[![endorse](https://api.coderwall.com/jsilverMDX/endorsecount.png)](https://coderwall.com/jsilverMDX)
+If you'd like to support the continued development of SwissDB, please check out our Gratipay: https://gratipay.com/swissdb/
 
 # SwissDb
 
-RubyMotion Android ActiveRecord-like ORM for SQLite
+This is SwissDb, a RubyMotion Android ActiveRecord-like ORM for SQLite.
 
+SwissDb 1.0 is working and stable as of RubyMotion 4.11.
+
+## Example
+
+See: https://github.com/KCErb/swissdb_debug
+
 ## Installation
 
 Add this line to your application's Gemfile:
 
 ```ruby
@@ -20,16 +26,32 @@
 
     $ gem install swiss_db
 
 ## Usage
 
+Usage is the same as ActiveRecord and CoreDataQuery.
+
+```ruby
+Car.create(is_red: true, mileage: (rand * 100_000).floor)
+car = Car.first
+car.is_red = true
+car.save
+mp Car.all.to_a
+car = Car.last
+car.update_attribute('is_red', false)
+
+```
+
+
 # Schemas
 
-Schemas are the exact same from CoreDataQuery and go in the same place. (schemas/)
+Schemas go in the project root under `schemas/`. You can stash multiple schema files here for your own records (`schema1.rb`, `schema2.rb`, etc.) but the schema your app actually uses must be named `schema.rb`.
 
+We're attempting to support both Core Data Query and Active Record type specifications like `datetime` `integer32` and `integer`. In SQLite there are only a few types anyways so that `integer32` and `integer` get created the same.
+
 ```ruby
-schema "0001" do
+schema version: 1 do
 
     entity "Car" do
       boolean   :is_red
       string    :model
       integer32 :tire_size
@@ -44,50 +66,59 @@
     end
 
 end
 ```
 
-Schema name (the "0001") does nothing.
+### Schema Version and Migrations
 
+You must specify a version with your schema. This integer (which must start at 1) is stored internally to the SQLite database and is used to determine if migrations need to be run.
+
+Migrating your database is not yet supported by SwissDB but is the next thing on the To-Do list.
+
 # Models
 
 Models are as such:
 
 ```ruby
-class Model < SwissModel
+class Model < SwissDB::SwissModel
 
   set_class_name "Model" # there are currently no hacks to automatically get this. sorry.
   set_primary_key "primary_key_name" # if not set, will default to "id"
 
 end
 ```
 
-# Set the context
+# Setup SwissDB
 
-Set the context in your bluepotion_application.rb.
+Since SwissDB needs to use your app's context you need to help it get setup like so:
 
 ```ruby
 class BluePotionApplication < PMApplication
 
   home_screen HomeScreen
 
   def on_create
-    DataStore.context = self
+    SwissDB.setup(self)
   end
 end
 ```
 
 # Examples
 
 ```ruby
   Model.first.name
   Model.all.last.name
   Model.all.count
+  Model.find_by_<column>("some value") # dynamic finders
+  Model.create(hash_values) # returns created model
   m = Model.first
-  m.name = "Sam"
-  m.save # will persist the data
+  m.name = "Sam" # changed values will persist in the model instance
+  m.save # will persist the data to the database
   m.update_attribute("name", "chucky")
+  m = Model.new
+  m.thing = "stuff"
+  m.save # upsert, (insert if doesn't exist, and update if does)
 ```
 
 
 That's it! #all, #last, #first, #count, #save, #update_attribute and the usual are now available!
 
@@ -99,14 +130,14 @@
 
 * destroy just one object support
 
 * detect class names of models for tableize
 
-KNOWN LIMITATION: This ORM compiles in the database name and the database version as a constant. Unfortunately I don't know of a way around this yet. This means no DB migrations yet by doing the simple version bump that is supported by Android. If we get a way to configure these from outside the gem, it will open up possibilities such as multiple schemas and migrations. To get around this simply delete your local database when you need to migrate. You can delete the app from the simulator/device (probably) or use my convenience command:
+KNOWN LIMITATION: No DB migrations yet by doing the simple version bump that is supported by Android. To get around this simply delete your local database when you need to migrate. You can delete the app from the simulator/device (probably) or use this convenience command:
 
 ```ruby
-   DataStore.drop_db #=> true if the DB was dropped, false if not
+   SwissDB::DataStore.drop_db #=> true if the DB was dropped, false if not
 ```
 
 ## Contributors
 
 
@@ -122,6 +153,5 @@
 
 
 ## License
 
 The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
-