Merge pull request #13 from pborreli/typos

Fix typos

alpha/mastering-backbone-views.md

@@ -36,7 +36,7 @@ Creating views
 --------------
 
 A view should never ever attach itself to the DOM. It's always the
-parent view's resposibility to create and attach a view to the DOM.
+parent view's responsibility to create and attach a view to the DOM.
 
 Ehm, what does that mean?
 
@@ -86,7 +86,7 @@ It is important that a view has no knowledge about its subviews except
 for their `el`, other dependencies, and their API, i.e.  the events the
 view trigger. This simplifies testing, it simplifies reuse and it
 simplifies maintenance. A subview is just a black box, and they are used
-to split up the responbilities in an application.
+to split up the responsibilities in an application.
 
 Handling DOM events
 -------------------

alpha/super-simple-mvc.md

@@ -21,7 +21,7 @@ For me these are the most important aspects of Backbone.js:
 Let's go through these in order, and see how we can create a super
 simple, albeit simplistic, MV* library while using some great and widely
 used libraries. (The essence of this is not its brevity, but that it is
-suprisingly easy to do, and that we can learn a lot about Backbone.js
+surprisingly easy to do, and that we can learn a lot about Backbone.js
 and similar libraries in the process.)
 
 Creating new components
@@ -64,7 +64,7 @@ View.extend = function(properties) {
 
     // Create child constructor
     var child = function() {
-        // … which only job is to call the parent construtor with all
+        // … which only job is to call the parent constructor with all
         // the arguments
         parent.apply(this, arguments);
     };
@@ -105,7 +105,7 @@ var View = function() {
   this.initialize.apply(this, arguments);
 };
 
-// Empty initialize which should be overriden in subclasses if it
+// Empty initialize which should be overridden in subclasses if it
 // is needed.
 View.prototype.initialize = function() {};
 ```