@@ -21,7 +21,7 @@ multiple views by adding routing, using an Angular module called 'ngRoute'.
21
21
The routing functionality added by this step is provided by angular in the `ngRoute` module, which
22
22
is distributed separately from the core Angular framework.
23
23
24
- We are using [Bower][bower] to install client side dependencies. This step updates the
24
+ We are using [Bower][bower] to install client- side dependencies. This step updates the
25
25
`bower.json` configuration file to include the new dependency:
26
26
27
27
```json
@@ -46,7 +46,7 @@ The new dependency `"angular-route": "~1.3.0"` tells bower to install a version
46
46
angular-route component that is compatible with version 1.3.x. We must tell bower to download
47
47
and install this dependency.
48
48
49
- If you have bower installed globally then you can run `bower install` but for this project we have
49
+ If you have bower installed globally, then you can run `bower install` but for this project, we have
50
50
preconfigured npm to run bower install for us:
51
51
52
52
```
@@ -70,7 +70,7 @@ the current "route" — the view that is currently displayed to the user.
70
70
Application routes in Angular are declared via the {@link ngRoute.$routeProvider $routeProvider},
71
71
which is the provider of the {@link ngRoute.$route $route service}. This service makes it easy to
72
72
wire together controllers, view templates, and the current URL location in the browser. Using this
73
- feature we can implement [deep linking](http://en.wikipedia.org/wiki/Deep_linking), which lets us
73
+ feature, we can implement [deep linking](http://en.wikipedia.org/wiki/Deep_linking), which lets us
74
74
utilize the browser's history (back and forward navigation) and bookmarks.
75
75
76
76
@@ -81,7 +81,7 @@ AngularJS, so it's important for you to understand a thing or two about how it w
81
81
82
82
When the application bootstraps, Angular creates an injector that will be used to find and inject all
83
83
of the services that are required by your app. The injector itself doesn't know anything about what
84
- `$http` or `$route` services do, in fact it doesn't even know about the existence of these services
84
+ `$http` or `$route` services do. In fact, the injector doesn't even know about the existence of these services
85
85
unless it is configured with proper module definitions.
86
86
87
87
The injector only carries out the following steps :
@@ -295,7 +295,7 @@ phonecatControllers.controller('PhoneDetailCtrl', ['$scope', '$routeParams',
295
295
296
296
Again, note that we created a new module called `phonecatControllers`. For small AngularJS
297
297
applications, it's common to create just one module for all of your controllers if there are just a
298
- few. As your application grows it is quite common to refactor your code into additional modules.
298
+ few. As your application grows, it is quite common to refactor your code into additional modules.
299
299
For larger apps, you will probably want to create separate modules for each major feature of
300
300
your app.
301
301
@@ -349,7 +349,7 @@ the same binding into the `phone-list.html` template, the binding will work as e
349
349
350
350
<div style="display: none">
351
351
* In `PhoneCatCtrl`, create a new model called "`hero`" with `this.hero = 'Zoro'`. In
352
- `PhoneListCtrl` let's shadow it with `this.hero = 'Batman'`, and in `PhoneDetailCtrl` we'll use
352
+ `PhoneListCtrl`, let's shadow it with `this.hero = 'Batman'`. In `PhoneDetailCtrl`, we'll use
353
353
`this.hero = "Captain Proton"`. Then add the `<p>hero = {{hero}}</p>` to all three of our templates
354
354
(`index.html`, `phone-list.html`, and `phone-detail.html`). Open the app and you'll see scope
355
355
inheritance and model property shadowing do some wonders.
0 commit comments