aboutsummaryrefslogtreecommitdiffstats
path: root/src/ng/directive/ngBind.js
diff options
context:
space:
mode:
authorjohnlindquist2012-04-12 16:23:34 -0600
committerIgor Minar2012-04-20 10:43:41 -0700
commit0c7252f929c7b7d0c718c4683a712331c6b95776 (patch)
treef120f5c580f0682df95a3012a8947b9767678b2e /src/ng/directive/ngBind.js
parentb94fb5c8c1a96dae771fa36814ed7e2d54c73b8a (diff)
downloadangular.js-0c7252f929c7b7d0c718c4683a712331c6b95776.tar.bz2
docs(ngBind): "makes make" -> "makes"
Diffstat (limited to 'src/ng/directive/ngBind.js')
-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 82402ae8..2ddd3337 100644
--- a/src/ng/directive/ngBind.js
+++ b/src/ng/directive/ngBind.js
@@ -14,7 +14,7 @@
*
* Once scenario in which the use of `ngBind` is prefered 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 make the
+ * 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.
*
* An alternative solution to this problem would be using the