README.md in ruboto-0.11.0 vs README.md in ruboto-0.12.0.rc.0

@@ -40,11 +40,11 @@
 
 <a name="application_generator"></a>
 ### Application generator
 
     $ ruboto gen app --package com.yourdomain.whatever --path path/to/where/you/want/the/app --name NameOfApp --target android-version --min-sdk another-android-version --activity MainActivityName
-Version values must be specified using'android-' and the sdk level number (e.g., android-8 is froyo).
+Version values must be specified using'android-' and the sdk level number (e.g., android-10 is gingerbread).
 
 <a name="class_generator"></a>
 ### Class generator
 
 Generates a Java class (Activity, Service, or BroadcastReceiver) associated with a specific ruboto script.  The generator also generates a corresponding test script.
@@ -163,11 +163,11 @@
       end
     end
 
 The arguments passed to the methods are the same as the arguments that the java methods take. Consult the Android documentation.
 
-Activities also have some special methods defined to make things easier. The easiest way to get an idea of what they are is looking over the [demo scripts](http://github.com/ruboto/ruboto-irb/tree/master/assets/demo-scripts/). You can also read the [ruboto.rb file](http://github.com/ruboto/ruboto/blob/master/assets/src/ruboto.rb) where everything is defined.
+Activities also have some special methods defined to make things easier. The easiest way to get an idea of what they are is looking over the [demo scripts](http://github.com/ruboto/ruboto-irb/tree/master/assets/demo-scripts/). You can also read the [ruboto.rb file](http://github.com/ruboto/ruboto-irb/blob/master/src/ruboto.rb) where everything is defined.
 
 Testing
 -------
 
 For each generated class, a ruby test script is created in the test/src directory.
@@ -229,15 +229,17 @@
 Tips & Tricks
 -------------
 
 ### Emulators
 
+You can start an emulator corresponding to the api level of your project with `rake emulator`.  The emulator will be created for you and will be called after the android version of you rproject, like "Android_4.0.3".
+
 If you're doing a lot of Android development, you'll probably find yourself typing `emulator -avd name_of_emulator` a lot to open emulators. It can be convenient to alias these to shorter commands.
 
 For example, in your `~/.bashrc`, `~/.zshrc`, or similar file, you might put
-    alias eclair="emulator -avd eclair"
-    alias froyo="emulator -avd froyo"
-If you have an "eclair" emulator that runs Android 2.1 and a "froyo" one that runs Android 2.2.
+    alias ics="emulator -avd Android_4.0.3"
+    alias jellyb="emulator -avd Android_4.1.2"
+If you have an "Android_4.0.3" emulator that runs Android 4..0.1 and a "Android_4.1.2" one that runs Android 4.1.2.
 
 
 Alternatives
 ------------