@@ -264,7 +264,7 @@ function annotate(fn, strictDi, name) {
264264 * function is invoked. There are three ways in which the function can be annotated with the needed
265265 * dependencies.
266266 *
267- * ## Argument names
267+ * #### Argument names
268268 *
269269 * The simplest form is to extract the dependencies from the arguments of the function. This is done
270270 * by converting the function into a string using `toString()` method and extracting the argument
@@ -284,7 +284,7 @@ function annotate(fn, strictDi, name) {
284284 * This method does not work with code minification / obfuscation. For this reason the following
285285 * annotation strategies are supported.
286286 *
287- * ## The `$inject` property
287+ * #### The `$inject` property
288288 *
289289 * If a function has an `$inject` property and its value is an array of strings, then the strings
290290 * represent names of services to be injected into the function.
@@ -300,7 +300,7 @@ function annotate(fn, strictDi, name) {
300300 * expect(injector.annotate(MyController)).toEqual(['$scope', '$route']);
301301 * ```
302302 *
303- * ## The array notation
303+ * #### The array notation
304304 *
305305 * It is often desirable to inline Injected functions and that's when setting the `$inject` property
306306 * is very inconvenient. In these situations using the array notation to specify the dependencies in
@@ -360,8 +360,7 @@ function annotate(fn, strictDi, name) {
360360 * You can use {@link $injector#modules `$injector.modules`} to check whether a module has been loaded
361361 * into the injector, which may indicate whether the script has been executed already.
362362 *
363- * ## Example
364- *
363+ * @example
365364 * Here is an example of loading a bundle of modules, with a utility method called `getScript`:
366365 *
367366 * ```javascript
0 commit comments