@@ -264,7 +264,7 @@ function annotate(fn, strictDi, name) {
264
264
* function is invoked. There are three ways in which the function can be annotated with the needed
265
265
* dependencies.
266
266
*
267
- * ## Argument names
267
+ * #### Argument names
268
268
*
269
269
* The simplest form is to extract the dependencies from the arguments of the function. This is done
270
270
* by converting the function into a string using `toString()` method and extracting the argument
@@ -284,7 +284,7 @@ function annotate(fn, strictDi, name) {
284
284
* This method does not work with code minification / obfuscation. For this reason the following
285
285
* annotation strategies are supported.
286
286
*
287
- * ## The `$inject` property
287
+ * #### The `$inject` property
288
288
*
289
289
* If a function has an `$inject` property and its value is an array of strings, then the strings
290
290
* represent names of services to be injected into the function.
@@ -300,7 +300,7 @@ function annotate(fn, strictDi, name) {
300
300
* expect(injector.annotate(MyController)).toEqual(['$scope', '$route']);
301
301
* ```
302
302
*
303
- * ## The array notation
303
+ * #### The array notation
304
304
*
305
305
* It is often desirable to inline Injected functions and that's when setting the `$inject` property
306
306
* is very inconvenient. In these situations using the array notation to specify the dependencies in
@@ -360,8 +360,7 @@ function annotate(fn, strictDi, name) {
360
360
* You can use {@link $injector#modules `$injector.modules`} to check whether a module has been loaded
361
361
* into the injector, which may indicate whether the script has been executed already.
362
362
*
363
- * ## Example
364
- *
363
+ * @example
365
364
* Here is an example of loading a bundle of modules, with a utility method called `getScript`:
366
365
*
367
366
* ```javascript
0 commit comments