@@ -154,7 +154,7 @@ rename the method parameter names. This makes this way of annotating only useful
154
154
155
155
### `$inject` Property Annotation
156
156
157
- To allow the minifers to rename the function parameters and still be able to inject right services,
157
+ To allow the minifiers to rename the function parameters and still be able to inject right services,
158
158
the function needs to be annotated with the `$inject` property. The `$inject` property is an array
159
159
of service names to inject.
160
160
@@ -224,7 +224,7 @@ dependencies.
224
224
- The `run` and `config` methods accept a function, which can also be injected with "service"
225
225
components as dependencies.
226
226
227
- - Controllers are defined by an constructor function, which can be injected with any of the "service"
227
+ - Controllers are defined by a constructor function, which can be injected with any of the "service"
228
228
components as dependencies, but they can also be provided with special dependencies. See "DI in
229
229
Controllers" below.
230
230
@@ -288,7 +288,7 @@ application. For example, there would be one instance for every `ng-controller`
288
288
Moreover, additional dependencies are made available to Controllers:
289
289
290
290
* {@link scope `$scope`}: Controllers are always associated with a point in the DOM and so are provided with
291
- access to the {@link scope scope} at that point. Other components, such as servies only have access to the
291
+ access to the {@link scope scope} at that point. Other components, such as services only have access to the
292
292
singleton {@link $rootScope} service.
293
293
* {@link $route} resolves: If a controller is instantiated as part of a route, then any values that
294
- are resolved as part of the route are made available for injection into the controller.
294
+ are resolved as part of the route are made available for injection into the controller.
0 commit comments