diff options
| author | Carl Danley | 2013-07-22 11:01:00 -0400 | 
|---|---|---|
| committer | Pawel Kozlowski | 2013-07-27 20:53:41 +0200 | 
| commit | 258e9862840f9d45709664e0e5b2a18540d8828d (patch) | |
| tree | 17386e8499d4103b83e903b437cda808a82579ff /src/ng/parse.js | |
| parent | 1bc99eca08bef4aceb49d4fee7ef9e291f60ff3b (diff) | |
| download | angular.js-258e9862840f9d45709664e0e5b2a18540d8828d.tar.bz2 | |
docs(*): fixed typos and ngdoc parameter names
Diffstat (limited to 'src/ng/parse.js')
| -rw-r--r-- | src/ng/parse.js | 2 | 
1 files changed, 1 insertions, 1 deletions
| diff --git a/src/ng/parse.js b/src/ng/parse.js index 102b3312..9660c76f 100644 --- a/src/ng/parse.js +++ b/src/ng/parse.js @@ -20,7 +20,7 @@ var $parseMinErr = minErr('$parse');  // the expression, which is a stronger but more expensive test. Since reflective calls are expensive anyway, this is not  // such a big deal compared to static dereferencing.  // -// This sandboxing techniqueue is not perfect and doesn't aim to be. The goal is to prevent exploits against the +// This sandboxing technique is not perfect and doesn't aim to be. The goal is to prevent exploits against the  // expression language, but not to prevent exploits that were enabled by exposing sensitive JavaScript or browser apis  // on Scope. Exposing such objects on a Scope is never a good practice and therefore we are not even trying to protect  // against interaction with an object explicitly exposed in this way. | 
