a few more minor changes.

backbone-fundamentals.rtf

@@ -16,7 +16,7 @@ license
 improve
 }}}
  it.\par}
-{\pard \ql \f0 \sa180 \li0 \fi0 I\u8217'm very pleased to announce that this book will be out in physical form in a few months time via {\field{\*\fldinst{HYPERLINK "http://oreilly.com"}}{\fldrslt{\ul
+{\pard \ql \f0 \sa180 \li0 \fi0 I\u8217'm very pleased to announce that this book will be out in physical form later in the year via {\field{\*\fldinst{HYPERLINK "http://oreilly.com"}}{\fldrslt{\ul
 O\u8217'Reilly Media
 }}}
 . Readers will have the option of purchasing the latest version in either print or a number of digital formats then or can grab a recent version from this repository.\par}
@@ -497,7 +497,7 @@ this
 }}}
  which can help\line \par}
 {\pard \ql \f0 \sa0 \li360 \fi-360 \bullet \tx360\tab Clear and flexible conventions for structuring applications. Backbone doesn\u8217't force usage of all of its components and can work with only those needed.\sa180\par}
-{\pard \ql \f0 \sa180 \li0 \fi0 \b \fs32 ## The Basics\par}
+{\pard \ql \f0 \sa180 \li0 \fi0 \b \fs32 ##The Basics\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 \b \fs28 What is Backbone?\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 Backbone.js is one of a number of JavaScript frameworks for creating MVC-like web applications. On the front-end, it\u8217's my architectural framework of choice as it\u8217's both mature, relatively lightweight and can be easily tested using third-party toolkits such as Jasmine or QUnit. Other MVC frameworks you may be familiar with include Ember.js (SproutCore 2.0), Spine, YUILibrary and JavaScriptMVC.\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 Backbone is maintained by a number of contributors, most notably: Jeremy Ashkenas, creator of CoffeeScript, Docco and Underscore.js. As Jeremy is a believer in detailed documentation, there\u8217's a level of comfort in knowing you\u8217're unlikely to run into issues which are either not explained in the official docs or which can\u8217't be nailed down with some assistance from the #documentcloud IRC channel. I strongly recommend using the latter if you find yourself getting stuck.\par}
@@ -1129,7 +1129,7 @@ galleryApp.model.special.Admin = Backbone.Model.extend(\{\});\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 {\b Recommendation}\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 Reviewing the namespace patterns above, the option that I prefer when writing Backbone applications is nested object namespacing with the object literal pattern.\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 Single global variables may work fine for applications that are relatively trivial. However, larger codebases requiring both namespaces and deep sub-namespaces require a succinct solution that\u8217's both readable and scalable. I feel this pattern achieves both of these objectives and is a good choice for most Backbone development.\par}
-{\pard \ql \f0 \sa180 \li0 \fi0 \b \fs28 Common Questions & Answers\par}
+{\pard \ql \f0 \sa180 \li0 \fi0 \b \fs32 Common Questions & Answers\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 \b \fs24 What is the best approach for rendering and appending Sub-Views in Backbone.js?\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 If you have a nested View setup in your application, there are a few approaches possible for initializing, rendering and appending your sub-views.\par}
 {\pard \ql \f0 \sa180 \li0 \fi0 One possible solution is the following:\par}

build/share.html

@@ -1,5 +1,8 @@
 <div style="width:500px">
-
+
+<iframe src="http://ghbtns.com/github-btn.html?user=addyosmani&repo=backbone-fundamentals&type=watch&count=true"
+  allowtransparency="true" frameborder="0" scrolling="0" width="110px" height="20px"></iframe>
+
  <iframe allowtransparency="true" frameborder="0" scrolling="no" src="http://platform.twitter.com/widgets/tweet_button.1333103182.html#_=1333404284780&amp;count=horizontal&amp;id=twitter-widget-0&amp;lang=en&amp;original_referer=http%3A%2F%2Faddyosmani.github.com%2Fbackbone-fundamentals%2F&amp;size=m&amp;text=Developing%20Backbone.js%20Applications&amp;url=https%3A%2F%2Fgithub.com%2Faddyosmani%2Fbackbone-fundamentals&amp;via=addy_osmani" class="twitter-share-button twitter-count-horizontal" style="width: 107px; height: 20px; " title="Twitter Tweet Button"></iframe>
 <script id="twitter-wjs" src="//platform.twitter.com/widgets.js"></script><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
 

index.html

@@ -32,15 +32,18 @@ <h1>Developing Backbone.js Applications</h1>
 	<h3>By Addy Osmani <a href="http://twitter.com/addyosmani">@addyosmani</a></h3>
 </p>
 <div style="width:500px">
-
+
+<iframe src="http://ghbtns.com/github-btn.html?user=addyosmani&repo=backbone-fundamentals&type=watch&count=true"
+  allowtransparency="true" frameborder="0" scrolling="0" width="110px" height="20px"></iframe>
+
  <iframe allowtransparency="true" frameborder="0" scrolling="no" src="http://platform.twitter.com/widgets/tweet_button.1333103182.html#_=1333404284780&amp;count=horizontal&amp;id=twitter-widget-0&amp;lang=en&amp;original_referer=http%3A%2F%2Faddyosmani.github.com%2Fbackbone-fundamentals%2F&amp;size=m&amp;text=Developing%20Backbone.js%20Applications&amp;url=https%3A%2F%2Fgithub.com%2Faddyosmani%2Fbackbone-fundamentals&amp;via=addy_osmani" class="twitter-share-button twitter-count-horizontal" style="width: 107px; height: 20px; " title="Twitter Tweet Button"></iframe>
 <script id="twitter-wjs" src="//platform.twitter.com/widgets.js"></script><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
 
   <p>&nbsp;<br></p>
 </div>
 <h2 id="prelude">Prelude</h2>
 <p>Welcome to my (in-progress) book about the <a href="http://documentcloud.github.com/backbone/">Backbone.js</a> framework for structuring JavaScript applications. It's released under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported <a href="http://creativecommons.org/licenses/by-nc-sa/3.0/">license</a> meaning you can both grab a copy of the book for free or help to further <a href="https://github.com/addyosmani/backbone-fundamentals/">improve</a> it.</p>
-<p>I'm very pleased to announce that this book will be out in physical form in a few months time via <a href="http://oreilly.com">O'Reilly Media</a>. Readers will have the option of purchasing the latest version in either print or a number of digital formats then or can grab a recent version from this repository.</p>
+<p>I'm very pleased to announce that this book will be out in physical form later in the year via <a href="http://oreilly.com">O'Reilly Media</a>. Readers will have the option of purchasing the latest version in either print or a number of digital formats then or can grab a recent version from this repository.</p>
 <p>Corrections to existing material are always welcome and I hope that together we can provide the community with an up-to-date resource that is of help. My extended thanks go out to <a href="https://github.com/jashkenas">Jeremy Ashkenas</a> for creating Backbone.js and <a href="https://github.com/addyosmani/backbone-fundamentals/contributors">these</a> members of the community for their assistance tweaking this project.</p>
 <p>I hope you find this book helpful!</p>
 <h2 id="table-of-contents">Table Of Contents</h2>
@@ -400,7 +403,7 @@ <h3 id="backbone.js">Backbone.js</h3>
 <li>Doesn't support deeply nested models, though there are Backbone plugins such as <a href="https://github.com/PaulUithol/Backbone-relational">this</a> which can help<br /></li>
 <li>Clear and flexible conventions for structuring applications. Backbone doesn't force usage of all of its components and can work with only those needed.</li>
 </ul>
-<h2 id="the-basics">## <a name="thebasics">The Basics</a></h2>
+<h2 id="the-basics">##<a name="thebasics">The Basics</a></h2>
 <h3 id="what-is-backbone">What is Backbone?</h3>
 <p>Backbone.js is one of a number of JavaScript frameworks for creating MVC-like web applications. On the front-end, it's my architectural framework of choice as it's both mature, relatively lightweight and can be easily tested using third-party toolkits such as Jasmine or QUnit. Other MVC frameworks you may be familiar with include Ember.js (SproutCore 2.0), Spine, YUILibrary and JavaScriptMVC.</p>
 <p>Backbone is maintained by a number of contributors, most notably: Jeremy Ashkenas, creator of CoffeeScript, Docco and Underscore.js. As Jeremy is a believer in detailed documentation, there's a level of comfort in knowing you're unlikely to run into issues which are either not explained in the official docs or which can't be nailed down with some assistance from the #documentcloud IRC channel. I strongly recommend using the latter if you find yourself getting stuck.</p>
@@ -1034,7 +1037,7 @@ <h4 id="what-is-namespacing">What is namespacing?</h4>
 <p><strong>Recommendation</strong></p>
 <p>Reviewing the namespace patterns above, the option that I prefer when writing Backbone applications is nested object namespacing with the object literal pattern.</p>
 <p>Single global variables may work fine for applications that are relatively trivial. However, larger codebases requiring both namespaces and deep sub-namespaces require a succinct solution that's both readable and scalable. I feel this pattern achieves both of these objectives and is a good choice for most Backbone development.</p>
-<h3 id="common-questions-answers"><a name="thebasics-additional-tips" id="thebasics-additional-tips">Common Questions &amp; Answers</a></h3>
+<h2 id="common-questions-answers"><a name="thebasics-additional-tips" id="thebasics-additional-tips">Common Questions &amp; Answers</a></h2>
 <h4 id="what-is-the-best-approach-for-rendering-and-appending-sub-views-in-backbone.js">What is the best approach for rendering and appending Sub-Views in Backbone.js?</h4>
 <p>If you have a nested View setup in your application, there are a few approaches possible for initializing, rendering and appending your sub-views.</p>
 <p>One possible solution is the following:</p>

index.md

@@ -2,7 +2,7 @@
 
 Welcome to my (in-progress) book about the [Backbone.js](http://documentcloud.github.com/backbone/) framework for structuring JavaScript applications. It's released under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported [license](http://creativecommons.org/licenses/by-nc-sa/3.0/) meaning you can both grab a copy of the book for free or help to further [improve](https://github.com/addyosmani/backbone-fundamentals/) it.
 
-I'm very pleased to announce that this book will be out in physical form in a few months time via [O'Reilly Media](http://oreilly.com). Readers will have the option of purchasing the latest version in either print or a number of digital formats then or can grab a recent version from this repository.
+I'm very pleased to announce that this book will be out in physical form later in the year via [O'Reilly Media](http://oreilly.com). Readers will have the option of purchasing the latest version in either print or a number of digital formats then or can grab a recent version from this repository.
 
 Corrections to existing material are always welcome and I hope that together we can provide the community with an up-to-date resource that is of help.
 My extended thanks go out to [Jeremy Ashkenas](https://github.com/jashkenas) for creating Backbone.js and [these](https://github.com/addyosmani/backbone-fundamentals/contributors) members of the community for their assistance tweaking this project.
@@ -520,7 +520,7 @@ It *is* however worth understanding where and why these concepts originated, so
 
 
 
-## <a name="thebasics">The Basics</a>
+##<a name="thebasics">The Basics</a>
 ---
 
 ###What is Backbone?
@@ -1489,7 +1489,7 @@ Reviewing the namespace patterns above, the option that I prefer when writing Ba
 Single global variables may work fine for applications that are relatively trivial. However, larger codebases requiring both namespaces and deep sub-namespaces require a succinct solution that's both readable and scalable. I feel this pattern achieves both of these objectives and is a good choice for most Backbone development.
 
 
-###<a name="thebasics-additional-tips" id="thebasics-additional-tips">Common Questions & Answers</a>
+## <a name="thebasics-additional-tips" id="thebasics-additional-tips">Common Questions & Answers</a>
 
 #### What is the best approach for rendering and appending Sub-Views in Backbone.js?