aboutsummaryrefslogtreecommitdiffstats
path: root/src/ng
diff options
context:
space:
mode:
authorMichal Reichert2013-04-18 12:41:03 +0300
committerPete Bacon Darwin2013-04-19 11:55:16 +0100
commit4c7baf970faa90efe9cbd19933f5648353b02f43 (patch)
tree2d0562e564b2f390e7243ae0bf945c8934397cbd /src/ng
parent5da6b125a7447b4bbabb88b2d82b5634b55c3aea (diff)
downloadangular.js-4c7baf970faa90efe9cbd19933f5648353b02f43.tar.bz2
docs(ngBind): fix typo
Diffstat (limited to 'src/ng')
-rw-r--r--src/ng/directive/ngBind.js2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/ng/directive/ngBind.js b/src/ng/directive/ngBind.js
index 32e802ce..f75fb54b 100644
--- a/src/ng/directive/ngBind.js
+++ b/src/ng/directive/ngBind.js
@@ -12,7 +12,7 @@
* Typically, you don't use `ngBind` directly, but instead you use the double curly markup like
* `{{ expression }}` which is similar but less verbose.
*
- * Once scenario in which the use of `ngBind` is preferred over `{{ expression }}` binding is when
+ * One scenario in which the use of `ngBind` is preferred over `{{ expression }}` binding is when
* it's desirable to put bindings into template that is momentarily displayed by the browser in its
* raw state before Angular compiles it. Since `ngBind` is an element attribute, it makes the
* bindings invisible to the user while the page is loading.