Troubeshooting to end of file

Author: kapunahelewong

public/docs/ts/latest/guide/user-input.jade

@@ -196,36 +196,23 @@ figure.image-display
 
   ### Pass values, not elements
 
-  We could have passed the `newHero` into the component's `addHero` method.
-
-  But that would require `addHero` to pick its way through the `<input>` DOM element,
-  something we learned to dislike in our first try at a [keyup component](#keyup1).
-
-  Instead, we grab the input box *value* and pass *that* to `addHero`.
-  The component knows nothing about HTML or the DOM, which is the way we like it.
+  Instead of passing the `newHero` into the component's `addHero` method,
+  get the input box value and pass *that* to `addHero`.
 
   ### Keep template statements simple
-  We bound `(blur)` to *two* JavaScript statements.
-
-  We like the first one, which calls `addHero`.
-  We do not like the second one, which assigns an empty string to the input box value.
-
-  The second statement exists for a good reason. We have to clear the input box after adding the new hero to the list.
-  The component has no way to do that itself because it has no access to the
-  input box (our design choice).
-
-  Although the example *works*, we are rightly wary of JavaScript in HTML.
-  Template statements are powerful. We're supposed to use them responsibly.
-  Complex JavaScript in HTML is irresponsible.
-
-  Should we reconsider our reluctance to pass the input box into the component?
-
-  There should be a better third way. And there is, as we'll see when we learn about `NgModel` in the [Forms](forms.html) chapter.
+  The `(blur)` event is bound to two JavaScript statements.
+  The first statement calls `addHero`.  The second statement, `newHero.value=''`,
+  clears the input box after a new hero is added to the list.
+
+  This works well enough for a demonstration, but
+  it is better not to combine JavaScript and HTML.
+  This example can be improved by using `NgModel`, as described in
+  [Forms](./forms.html).
 .l-main-section
 :marked
   ## Source code
 
-  Here is all the code we talked about in this chapter.
+  Following is all the code discussed in this page.
 +makeTabs(`
   user-input/ts/app/click-me.component.ts,
   user-input/ts/app/keyup.components.ts,
@@ -241,10 +228,11 @@ figure.image-display
 :marked
   ## Summary
 
-  We've mastered the basic primitives for responding to user input and gestures.
-  As powerful as these primitives are, they are a bit clumsy for handling
-  large amounts of user input. We're operating down at the low level of events when
-  we should be writing two-way bindings between data entry fields and model properties.
+  You have mastered the basic primitives for responding to user input and gestures.
 
-  Angular has a two-way binding called `NgModel`, which we'll learn about
-  in the `Forms` chapter.
+  These techniques are useful for small-scale demonstrations, but they
+  quickly become verbose and clumsy when handling large amounts of user input.
+  Two-way data binding is a more elegant and compact way to move
+  values between data entry fields and model properties.
+  The next page, `Forms`, explains how to write
+  two-way bindings with `NgModel`.