aboutsummaryrefslogtreecommitdiffstats
path: root/src
diff options
context:
space:
mode:
authorts-web2013-09-19 10:01:33 -0400
committerPete Bacon Darwin2013-09-19 20:27:59 +0100
commit72ad746b85e3dcfefd794d7dc376e7ade798ff49 (patch)
treed68f4f28831202dfa982952103674f69e1435f7c /src
parent2468974a53e9a5c05081a89d6ec127a9e7623198 (diff)
downloadangular.js-72ad746b85e3dcfefd794d7dc376e7ade798ff49.tar.bz2
docs(input): fix spelling error and reword for clarity
Diffstat (limited to 'src')
-rw-r--r--src/ng/directive/input.js10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/ng/directive/input.js b/src/ng/directive/input.js
index 1df38b5e..ef55a7a2 100644
--- a/src/ng/directive/input.js
+++ b/src/ng/directive/input.js
@@ -843,13 +843,13 @@ var VALID_CLASS = 'ng-valid',
* @description
*
* `NgModelController` provides API for the `ng-model` directive. The controller contains
- * services for data-binding, validation, CSS update, value formatting and parsing. It
- * specifically does not contain any logic which deals with DOM rendering or listening to
- * DOM events. The `NgModelController` is meant to be extended by other directives where, the
- * directive provides DOM manipulation and the `NgModelController` provides the data-binding.
+ * services for data-binding, validation, CSS updates, and value formatting and parsing. It
+ * purposefully does not contain any logic which deals with DOM rendering or listening to
+ * DOM events. Such DOM related logic should be provided by other directives which make use of
+ * `NgModelController` for data-binding.
* Note that you cannot use `NgModelController` in a directive with an isolated scope,
* as, in that case, the `ng-model` value gets put into the isolated scope and does not get
- * propogated to the parent scope.
+ * propagated to the parent scope.
*
*
* This example shows how to use `NgModelController` with a custom control to achieve