anchor.diff:    <h3>Server</h3>
   
     <p>
  -  In superfluous, the server is composed of
  -  <a href="http://www.senchalabs.org/connect/">connect middleware</a> running
  -  on <a href="http://nodejs.org">node.js</a>. The server is responsible for
  +  In superfluous, the server is composed of <a
  +  href="http://www.senchalabs.org/connect/">connect middleware</a> running on
  +  <a href="http://nodejs.org">node.js</a>. The server is responsible for
     sending <b>apps</b> (a <b>page</b> can be considered a type of app) to the
  -  client.  Each server can host one or more web apps, each living at a URL. For each
  -  app, its server controller handles all requests to that URL and its sub URLs.
  +  client.  The server hosts multiple web apps, each handling a URL path and
  +  it's sub paths.
   
     <p>
     In addition to delivering the app to the client, the server is generally
  
positive.code:   The bridge has two main functions, <b>call</b> and <b>controller</b>, invoked in the following way:
    <code>bridge.call("path/to/client/module", "method_name", arg1, arg2, ...,)</code>
    <br /> and <br />
    <code>bridge.controller("foo", "method_name", arg1, arg2, ...,)</code>. 
  </p>
  </div>
  
  
negative.code:   <p>
    <b>Re-usability</b> - Components are <b>Backbone.Views</b> that encapsulate
    re-usable portions of rendering, event handling and data synchronization
    code. Using components on a site adds structure and well defined behaviors.
    Every component is responsible for managing its sub DOM, so their
    responsibilities are clear cut.
    <br />
  
    <div class="alert">Many large web codebases today are using Component based
  