readme fixes (#166)

* Add quote

* Fix spelling in readme

README.md

@@ -74,7 +74,7 @@ To compile the js for just one platform, run:
 
     grunt compile:android --platformVersion=4.0.0
 
-To comiple the js for all platforms but pass in a custom path for your cordova-android and cordova-ios platforms, run:
+To compile the js for all platforms but pass in a custom path for your cordova-android and cordova-ios platforms, run:
 
     grunt compile --android='../custompath/cordova-android' --ios='../custompath/cordova-ios'
 
@@ -106,7 +106,7 @@ The `tasks/lib/packager.js` tool is a node.js script that concatenates all of th
 
 The **Cordova** *native-to-webview* bridge is initialized in `src/scripts/bootstrap.js`. This file attaches the `boot` function to the `channel.onNativeReady` event - fired by native with a call to:
 
-    cordova.require('cordova/channel).onNativeReady.fire()
+    cordova.require('cordova/channel').onNativeReady.fire()
 
 The `boot` method does all the work.  First, it grabs the common platform definition (under `src/common/common.js`) and injects all of the objects defined there onto `window` and other global namespaces. Next, it grabs all of the platform-specific object definitions (as defined under `src/<platform>/platform.js`) and overrides those onto `window`. Finally, it calls the platform-specific `initialize` function (located in the platform definition). At this point, Cordova is fully initialized and ready to roll. Last thing we do is wait for the `DOMContentLoaded` event to fire to make sure the page has loaded properly. Once that is done, Cordova fires the `deviceready` event where you can safely attach functions that consume the Cordova APIs.