anchor.diff:  
     p This basic Angular app contains the structure for any app you'll build.
   
  -  p.
  -    You can think of Angular apps as a tree of components.  This root component we've been talking about acts as the top
  -    level container for the rest of your application.  You've named this one <code>AppComponent</code>, but there's
  -    nothing special about the name and you can use whatever makes sense to you.
  +  .l-sub-section
  +    h3 It's all a tree
  +    p.
  +      You can think of Angular apps as a tree of components.  This root component we've been talking about acts as the top
  +      level container for the rest of your application.  You've named this one <code>AppComponent</code>, but there's
  +      nothing special about the name and you can use whatever makes sense to you.
   
  -  p.
  -    The root component's job is to give a location in the <code>index.html</code> file where your application will
  -    render through it's element, in this case <code>&lt;my-app&gt;</code>.  There is also nothing special about this
  -    element name and you can pick it as you like.
  +    p.
  +      The root component's job is to give a location in the <code>index.html</code> file where your application will
  +      render through it's element, in this case <code>&lt;my-app&gt;</code>.  There is also nothing special about this
  +      element name and you can pick it as you like.
   
  -  p.
  -    The root component loads the initial template for the application that will load other components to perform
  -    whatever functions your application needs - menu bars, views, forms, etc.  We'll walk through examples of all of
  -    these in the following pages.
  +    p.
  +      The root component loads the initial template for the application that will load other components to perform
  +      whatever functions your application needs - menu bars, views, forms, etc.  We'll walk through examples of all of
  +      these in the following pages.
  +
  +  .l-sub-section
  +    h3 @Component and @View annotations
  +
  +    p.
  +      A component annotation describes details about the component. An annotation can be identified by its at-sign (<code>@</code>).
  +    p.
  +      The <code>@Component</code> annotation defines the HTML tag for the component by specifying the component's CSS selector.
  +    p.
  +      The <code>@View</code> annotation defines the HTML that represents the component. The component you wrote uses an inline template, but you can also have an external template. To use an external template, specify a <code>templateUrl</code> property and give it the path to the HTML file.
  +  
  +  .l-sub-section
  +    h3 import vs. window.angular
  +    p.
  +      The main difference between the ES5 and TypeScript versions is the loading of modules.
  +    
  +    strong TypeScript 
  +    p.
  +      TypeScript supports ES6 module loading syntax. ES6 modules allow for modular loading of JavaScript code. Using ES6 modules you can cherry-pick only what you need for your app.
  +      
  +    pre.prettyprint.lang-typescript
  +      code.
  +        import {Component, View, bootstrap} from 'angular2/angular2';
  +        ...
  +        // bootstrap is available for use because it was imported from angular core
  +        bootstrap(AppComponent);
  +        
  +    strong ES5
  +    p.
  +      In ES5 the script file creates an angular property on the window of the browser. This property contains every piece of Angular core, whether you need it or not. 
  +      
  +    pre.prettyprint.lang-typescript
  +      code.
  +        // window.angular is available because the script file attaches the angular property to the window
  +        document.addEventListener('DOMContentLoaded', function() {
  +          angular.bootstrap(AppComponent);
  +        });
   
     p Exciting!  Not excited yet?  Let's move on to <a href="displaying-data.html">Displaying Data</a>.
  -
  -
  
positive.code:   p.
      In the <code>&lt;body&gt;</code>, add an element called <code>&lt;my-app&gt;</code> that will be the root of your
      application.
  
    pre.prettyprint.lang-html
      code.
  
negative.code:       }
  
        bootstrap(AppComponent);
      
  .l-main-section
    h2#section-run-it Run it!
  
  