diff --git a/public/docs/js/latest/quickstart.jade b/public/docs/js/latest/quickstart.jade
index a9023f69e9..89b3eb4525 100644
--- a/public/docs/js/latest/quickstart.jade
+++ b/public/docs/js/latest/quickstart.jade
@@ -77,7 +77,7 @@ include ../../../_includes/_util-fns
   +makeExample('gettingstarted/js/app.js', 'class-w-annotations')
 
   :markdown
-    We're creating a visual component named **`appComponent`** by chaining the 
+    We're creating a visual component named **`AppComponent`** by chaining the 
     `Component` and `Class` methods that belong to the **global Angular namespace, `ng`**.
 
     ```
diff --git a/public/docs/ts/latest/quickstart.jade b/public/docs/ts/latest/quickstart.jade
index 331039d9b8..57b8b353ce 100644
--- a/public/docs/ts/latest/quickstart.jade
+++ b/public/docs/ts/latest/quickstart.jade
@@ -75,7 +75,7 @@ include ../../../_includes/_util-fns
     We'd be correct to guess that someday our application will
     consist of more components arising in tree-like fashion from this root.
 
-    In the top line we imported the `Component`, `View`, and `bootstrap` methods
+    In the top line we imported the `Component` and `bootstrap` symbols
     from the Angular 2 library. That's the way we do things now.
     We no longer expect to find our code or any library code in a global namespace.
     We `import` exactly what we need, as we need it, from named file and library resources.
@@ -417,7 +417,7 @@ include ../../../_includes/_util-fns
     We're about to build a small application that demonstrates the great things
     we can build with Angular 2.
 
-    <!--TODO: Join us on the [Tour of Heroes](./toh-pt1) -->
+    <!--TODO: Join us on the [Tour of Heroes](./toh-pt1.html) -->
 
 
 <!-- Move this to the Style Guide when we have one -->
diff --git a/public/docs/ts/latest/tutorial/index.jade b/public/docs/ts/latest/tutorial/index.jade
index ec8805188d..bbeed1dcff 100644
--- a/public/docs/ts/latest/tutorial/index.jade
+++ b/public/docs/ts/latest/tutorial/index.jade
@@ -56,4 +56,4 @@ include ../../../../_includes/_util-fns
 
     And we’ll meet many of the core fundamentals of Angular along the way.
  
-    [Let's get started!](./toh-pt1.html).
+    [Let's get started!](./toh-pt1.html)
diff --git a/public/docs/ts/latest/tutorial/toh-pt1.jade b/public/docs/ts/latest/tutorial/toh-pt1.jade
index a2a6dbef8f..3d89a3c92d 100644
--- a/public/docs/ts/latest/tutorial/toh-pt1.jade
+++ b/public/docs/ts/latest/tutorial/toh-pt1.jade
@@ -5,7 +5,7 @@ include ../../../../_includes/_util-fns
   :markdown
     # Once Upon a Time
 
-    Every story starts somewhere. Our story starts where the [QuickStart](../quickstart) ends.
+    Every story starts somewhere. Our story starts where the [QuickStart](../quickstart.html) ends.
 
     Follow the "QuickStart" steps. They provide the prerequisites, the folder structure,
     and the core files for our Tour of Heroes.
@@ -181,7 +181,7 @@ include ../../../../_includes/_util-fns
  
   .alert.is-helpful
     :markdown
-      Learn more about `ng-model` in the [Template Syntax](../guide/template-syntax#ng-model)
+      Learn more about `ng-model` in the [Template Syntax](../guide/template-syntax.html#ng-model)
   :markdown
     Replace the  `<input>` with the following HTML
 
diff --git a/public/docs/ts/latest/tutorial/toh-pt2.jade b/public/docs/ts/latest/tutorial/toh-pt2.jade
index b82976f0ac..172cda0f90 100644
--- a/public/docs/ts/latest/tutorial/toh-pt2.jade
+++ b/public/docs/ts/latest/tutorial/toh-pt2.jade
@@ -124,7 +124,7 @@ include ../../../../_includes/_util-fns
   .alert.is-helpful
     :markdown
       Learn more about `ng-for` and local template variables in the 
-      [Template Syntax](../guide/template-syntax#ng-for) chapter.
+      [Template Syntax](../guide/template-syntax.html#ng-for) chapter.
 
   :markdown
     With this background in mind, we now insert some content between the `<li>` tags 
@@ -232,7 +232,7 @@ include ../../../../_includes/_util-fns
     That’s the same `hero` variable we defined previously in the `ng-for`.
   .alert.is-helpful
     :markdown
-      Learn more about Event Binding in the [Templating Syntax](../guide/template-syntax#event-binding) chapter.
+      Learn more about Event Binding in the [Templating Syntax](../guide/template-syntax.html#event-binding) chapter.
   :markdown
     ## Add the click handler
     Our event binding refers to an `onSelect` method that doesn’t exist yet. 
@@ -312,7 +312,7 @@ include ../../../../_includes/_util-fns
       In other words, they give structure to the way Angular displays content in the DOM.
        
       Learn more about `ng-if`, `ng-for` and other structural directives in the 
-      [Template Syntax](../guide/template-syntax#directives) chapter
+      [Template Syntax](../guide/template-syntax.html#directives) chapter
     
   :markdown
     We learned previously with `NgFor` that we must declare every directive we use in the component’s `@Component` decorator. 
@@ -370,7 +370,7 @@ include ../../../../_includes/_util-fns
   .alert.is-helpful    
     :markdown
       Learn more about `ng-class` in the 
-      [Template Syntax](../guide/template-syntax#ng-class) chapter
+      [Template Syntax](../guide/template-syntax.html#ng-class) chapter
          
   :markdown
     Notice in the template that the `ng-class` name is surrounded in square brackets (`[]`).  
@@ -380,7 +380,7 @@ include ../../../../_includes/_util-fns
   .alert.is-helpful
     :markdown
       Learn more about about one-way property data binding in the
-      [Template Syntax](../guide/template-syntax#property-binding) chapter
+      [Template Syntax](../guide/template-syntax.html#property-binding) chapter
   :markdown
     We've added yet another new directive to our template that we have to import and declare 
     in the component’s `directives` array as we’ve done twice before.