Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Commit a84344a

Browse files
ChrisRosepetebacondarwin
authored andcommitted
docs(guide/di): fix typos
Closes #7480
1 parent 7a3cbb3 commit a84344a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/content/guide/di.ngdoc

+4-4
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ rename the method parameter names. This makes this way of annotating only useful
154154

155155
### `$inject` Property Annotation
156156

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,
158158
the function needs to be annotated with the `$inject` property. The `$inject` property is an array
159159
of service names to inject.
160160

@@ -224,7 +224,7 @@ dependencies.
224224
- The `run` and `config` methods accept a function, which can also be injected with "service"
225225
components as dependencies.
226226

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"
228228
components as dependencies, but they can also be provided with special dependencies. See "DI in
229229
Controllers" below.
230230

@@ -288,7 +288,7 @@ application. For example, there would be one instance for every `ng-controller`
288288
Moreover, additional dependencies are made available to Controllers:
289289

290290
* {@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
292292
singleton {@link $rootScope} service.
293293
* {@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

Comments
 (0)