diff --git a/public/docs/ts/latest/tutorial/toh-pt1.jade b/public/docs/ts/latest/tutorial/toh-pt1.jade
index ee5cbcfb59..d7cf496fd1 100644
--- a/public/docs/ts/latest/tutorial/toh-pt1.jade
+++ b/public/docs/ts/latest/tutorial/toh-pt1.jade
@@ -70,9 +70,11 @@ include ../../../../_includes/_util-fns
     The browser should refresh and display our title and hero.
 
     The double curly braces tell our app to read the `title` and `hero` properties from the component and render them.
-    This is the "interpolation" form of one-way data binding;
-    we can learn more about interpolation in the [Displaying Data chapter](displaying-data).
-
+    This is the "interpolation" form of one-way data binding.
+  .l-sub-section
+    :marked
+      Learn more about interpolation in the [Displaying Data chapter](../guide/displaying-data).
+  :marked
     ### Hero object
 
     At the moment, our hero is just a name.  Our hero needs more properties.
@@ -178,7 +180,7 @@ include ../../../../_includes/_util-fns
 
   .l-sub-section
     :marked
-      Learn more about `ng-model` in the [Template Syntax](../guide/template-syntax.html#ng-model)
+      Learn more about `ng-model` in the [Template Syntax chapter](../guide/template-syntax.html#ng-model)
   :marked
     Replace the `<input>` with the following HTML
 
@@ -232,12 +234,10 @@ include ../../../../_includes/_util-fns
 
     The `ng-model` directive is one of many Forms directives which happen to be
     bundled in a convenient array called `FORM_DIRECTIVES`.
-    <!-- TODO
-    .alert.is-helpful
-      :marked
-        Learn more about Angular Forms in the [Forms chapter]()
+  .l-sub-section
     :marked
-    -->
+      Learn more about Angular Forms in the [Forms chapter](../guide/forms)
+  :marked
     Let’s forget about importing `NgModel` and import the `FORM_DIRECTIVES` array instead:
     ```
     import {bootstrap, Component, FORM_DIRECTIVES} from 'angular2/angular2';
diff --git a/public/docs/ts/latest/tutorial/toh-pt2.jade b/public/docs/ts/latest/tutorial/toh-pt2.jade
index e106d26e3d..44fc1e909d 100644
--- a/public/docs/ts/latest/tutorial/toh-pt2.jade
+++ b/public/docs/ts/latest/tutorial/toh-pt2.jade
@@ -123,7 +123,7 @@ include ../../../../_includes/_util-fns
       We can reference this variable within the template to access a hero’s properties.
 
       Learn more about `ng-for` and local template variables in the
-      [Template Syntax](../guide/template-syntax.html#ng-for) chapter.
+      [Template Syntax chapter](../guide/template-syntax.html#ng-for).
 
   :marked
     With this background in mind, we now insert some content between the `<li>` tags
@@ -235,7 +235,7 @@ include ../../../../_includes/_util-fns
     That’s the same `hero` variable we defined previously in the `ng-for`.
   .l-sub-section
     :marked
-      Learn more about Event Binding in the [Templating Syntax](../guide/template-syntax.html#event-binding) chapter.
+      Learn more about Event Binding in the [Templating Syntax chapter](../guide/template-syntax.html#event-binding).
   :marked
     ### Add the click handler
     Our event binding refers to an `onSelect` method that doesn’t exist yet.
@@ -316,7 +316,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.html#directives) chapter
+      [Template Syntax chapter](../guide/template-syntax.html#directives).
 
   :marked
     We learned previously with `NgFor` that we must declare every directive we use in the component’s `@Component` decorator.
@@ -380,7 +380,7 @@ include ../../../../_includes/_util-fns
     :marked
       Learn more about [ng-class](../guide/template-syntax.html#ng-class)
       and [Property Binding](../guide/template-syntax.html#property-binding)
-      in the Template Syntax chapter
+      in the Template Syntax chapter.
   :marked
     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.