replace "expression" w/ "statement"

Matches changes made in b24c813

Author: kwalrath

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

@@ -12,19 +12,20 @@ include ../../../../_includes/_util-fns
   We can use Angular event bindings <!-- PENDING: link to ./template-syntax.html#event-binding -->
   to respond to [any DOM event](https://developer.mozilla.org/en-US/docs/Web/Events).
 
-  The syntax is simple. We assign a template expression to the DOM event name, surrounded in parentheses.
+  The syntax is simple. We surround the DOM event name with
+  parentheses and assign a quoted template statement to it.
   As an example, here's an event binding that implements a click handler:
 +makeExample('user-input/dart/lib/click_me_component.dart', 'click-me-button')(format=".", language="html")
 
 <a id="click"></a>
 :marked
   The `(click)` to the left of the equal sign identifies the button's click event as the **target of the binding**.
-  The text within quotes on the right is the **template expression** in which we
-  respond to the click event by calling the component's `onClickMe` method. A template expression <!-- PENDING: link to ./template-syntax.html#template-expressions --> is a subset
-  of Dart with a few added tricks.
+  The text within quotes on the right is the **template statement** in which we
+  respond to the click event by calling the component's `onClickMe` method. A template statement <!-- PENDING: link to ./template-syntax.html#template-statements --> is a subset
+  of Dart with restrictions and a few added tricks.
 
-  When writing a binding we must be aware of a template expression's **execution context**.
-  The identifiers appearing within an expression belong to a specific context object.
+  When writing a binding we must be aware of a template statement's **execution context**.
+  The identifiers appearing within a statement belong to a specific context object.
   That object is usually the Angular component that controls the template  ... which it definitely is
   in this case because that snippet of HTML belongs to the following component:
 
@@ -121,8 +122,8 @@ figure.image-display
     Angular only updates the bindings (and therefore the screen)
     if we do something in response to asynchronous events such as keystrokes.
 
-    That's why we bind the `keyup` event to an expression that does ... well, nothing.
-    We're binding to the number 0, the shortest expression we can think of.
+    That's why we bind the `keyup` event to a statement that does ... well, nothing.
+    We're binding to the number 0, the shortest statement we can think of.
     That is all it takes to keep Angular happy. We said it would be clever!
 :marked
   That local template variable is intriguing. It's clearly easier to get to the textbox with that
@@ -140,14 +141,14 @@ figure.image-display
   ## Key event filtering (with `key.enter`)
   Perhaps we don't care about every keystroke.
   Maybe we're only interested in the input box value when the user presses Enter, and we'd like to ignore all other keys.
-  When we bind to the `(keyup)` event, our event handling expression hears *every keystroke*.
+  When we bind to the `(keyup)` event, our event handling statement hears *every keystroke*.
   We could filter the keys first, examining every `$event.keyCode`, and update the `values` property only if the key is Enter.
 
   Angular can filter the key events for us. Angular has a special syntax for keyboard events.
   We can listen for just the Enter key by binding to Angular's `keyup.enter` pseudo-event.
 
   Only then do we update the component's `values` property. (In this example,
-  the update happens inside the event expression. A better practice
+  the update happens inside the event binding statement. A better practice
   would be to put the update code in the component.)
 +makeExample('user-input/dart/lib/keyup_components.dart', 'key-up-component-3' ,'web/keyup_components.dart (v3)')(format=".")
 :marked
@@ -207,7 +208,7 @@ figure.image-display
   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.
 
-  ### Keep template expressions simple
+  ### Keep template statements simple
   We bound `(blur)` to *two* Dart statements.
 
   We like the first one, which calls `addHero`.
@@ -218,7 +219,7 @@ figure.image-display
   input box (our design choice).
 
   Although the example *works*, we are rightly wary of Dart in HTML.
-  Template expressions are powerful. We're supposed to use them responsibly.
+  Template statements are powerful. We're supposed to use them responsibly.
   Complex Dart in HTML is irresponsible.
 
   Should we reconsider our reluctance to pass the input box into the component?