diff options
| author | ts-web | 2013-09-19 10:01:33 -0400 | 
|---|---|---|
| committer | Pete Bacon Darwin | 2013-09-19 21:09:20 +0100 | 
| commit | fd797cdb7ef2f0c549eeceb57b40f6ba3b000985 (patch) | |
| tree | b0231185a71665e95a69ac6e2e3889b0a6db56eb | |
| parent | ed1dbf2554b3afa41f17f99acefdec89da0dd401 (diff) | |
| download | angular.js-fd797cdb7ef2f0c549eeceb57b40f6ba3b000985.tar.bz2 | |
docs(input): fix spelling error and reword for clarity
| -rw-r--r-- | src/ng/directive/input.js | 10 | 
1 files changed, 5 insertions, 5 deletions
| diff --git a/src/ng/directive/input.js b/src/ng/directive/input.js index 59c1f82b..390aab85 100644 --- a/src/ng/directive/input.js +++ b/src/ng/directive/input.js @@ -824,13 +824,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 | 
