aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/guide/module.ngdoc
diff options
context:
space:
mode:
authorMatt Rohrer2012-09-26 15:30:55 +0200
committerBrian Ford2013-01-17 19:10:46 -0500
commit93070f14885801de7e264b04fdf4cb54b7dc7d9b (patch)
tree9a96a5e4c8ea0e18dc775c2b92bc148c57c00a87 /docs/content/guide/module.ngdoc
parent3c8583e5dd10ff356ac473f53e920fb10eb41571 (diff)
downloadangular.js-93070f14885801de7e264b04fdf4cb54b7dc7d9b.tar.bz2
docs(guide): minor grammar fixes
Diffstat (limited to 'docs/content/guide/module.ngdoc')
-rw-r--r--docs/content/guide/module.ngdoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/content/guide/module.ngdoc b/docs/content/guide/module.ngdoc
index db534eb2..4465c30e 100644
--- a/docs/content/guide/module.ngdoc
+++ b/docs/content/guide/module.ngdoc
@@ -194,7 +194,7 @@ and thus script loaders can take advantage of this property and parallelize the
# Unit Testing
-In its simplest form a unit-test is a way of instantiating a subset of the application in test and
+In its simplest form a unit test is a way of instantiating a subset of the application in test and
then applying a stimulus to it. It is important to realize that each module can only be loaded
once per injector. Typically an app has only one injector. But in tests, each test has its own
injector, which means that the modules are loaded multiple times per VM. Properly structured
@@ -222,8 +222,8 @@ In all of these examples we are going to assume this module definition:
Let's write some tests:
<pre>
describe('myApp', function() {
- // load the application relevant modules then load a special
- // test module which overrides the $window with mock version,
+ // load the relevant application modules then load a special
+ // test module which overrides the $window with a mock version,
// so that calling window.alert() will not block the test
// runner with a real alert box. This is an example of overriding
// configuration information in tests.