diff options
| author | dandoyon | 2011-07-29 18:42:16 -0700 |
|---|---|---|
| committer | Vojta Jina | 2011-07-30 16:41:42 +0200 |
| commit | 1f4b417184ce53af15474de065400f8a686430c5 (patch) | |
| tree | 3098ed2ada9a4be843a2e2a12e8c257e7f7fc32f /src/service | |
| parent | 2d8d5aef2918ca0d2503290f86a42701fc98d330 (diff) | |
| download | angular.js-1f4b417184ce53af15474de065400f8a686430c5.tar.bz2 | |
doc(typos): fix couple of typos in the docs
Minor documentation fixes. Should not be any code changes.
One test changed due to dependency on text in documentation.
Diffstat (limited to 'src/service')
| -rw-r--r-- | src/service/updateView.js | 2 | ||||
| -rw-r--r-- | src/service/xhr.js | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/src/service/updateView.js b/src/service/updateView.js index d504772c..9ac7c1fb 100644 --- a/src/service/updateView.js +++ b/src/service/updateView.js @@ -34,7 +34,7 @@ * or 'XHR' (instead of {@link angular.service.$xhr}) then you may be changing the model * without angular knowledge and you may need to call '$updateView()' directly. * - * NOTE: if you wish to update the view immediately (without delay), you can do so by calling + * Note: if you wish to update the view immediately (without delay), you can do so by calling * {@link angular.scope.$eval} at any time from your code: * <pre>scope.$root.$eval()</pre> * diff --git a/src/service/xhr.js b/src/service/xhr.js index dc18419d..40be270e 100644 --- a/src/service/xhr.js +++ b/src/service/xhr.js @@ -6,7 +6,7 @@ * @name angular.service.$xhr * @function * @requires $browser $xhr delegates all XHR requests to the `$browser.xhr()`. A mock version - * of the $browser exists which allows setting expectaitions on XHR requests + * of the $browser exists which allows setting expectations on XHR requests * in your tests * @requires $xhr.error $xhr delegates all non `2xx` response code to this service. * @requires $log $xhr delegates all exceptions to `$log.error()`. @@ -83,7 +83,7 @@ * cookie called `XSRF-TOKEN` on first HTTP GET request. On subsequent non-GET requests the server * can verify that the cookie matches `X-XSRF-TOKEN` HTTP header, and therefore be sure that only * JavaScript running on your domain could have read the token. The token must be unique for each - * user and must be verifiable by the server (to prevent the JavaScript making up its own tokens). + * user and must be verifiable by the server (to prevent the JavaScript making up its own tokens). * We recommend that the token is a digest of your site's authentication cookie with * {@link http://en.wikipedia.org/wiki/Rainbow_table salt for added security}. * |