From f54ae8b3064645d7f582b7d09aecc6cd7dc89c55 Mon Sep 17 00:00:00 2001 From: Ward Bell Date: Mon, 25 Jan 2016 03:39:34 -0800 Subject: [PATCH] docs(user input): grammar - 'an statement'->'a statement' closes #750 --- public/docs/ts/latest/guide/user-input.jade | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/public/docs/ts/latest/guide/user-input.jade b/public/docs/ts/latest/guide/user-input.jade index f1ee8fc987..012c8be855 100644 --- a/public/docs/ts/latest/guide/user-input.jade +++ b/public/docs/ts/latest/guide/user-input.jade @@ -26,7 +26,7 @@ include ../../../../_includes/_util-fns of JavaScript with restrictions and a few added tricks. When writing a binding we must be aware of a template statement's **execution context**. - The identifiers appearing within an statement belong to a specific context object. + 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: @@ -112,7 +112,7 @@ 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 statement that does ... well, nothing. + 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