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:   App Routes are configured in the <b>routes.json</b> file - it is a global
    index of what apps the server is going to be serving and where. Inside the
    routes.json, each server controller has an entry that tells the router which
    controller to hand requests to when looking at the path of the incoming
    request's URL. Inside each controller is a list of <b>routes</b> that the
    controller will handle.
    </p>
  
    <div class="mtl mbl">
  