docs($routeProvider): fix indentation

Steven Petryk · IgorMinar · commit 696928dbc6d2 · 2014-02-19T08:03:20.000-08:00
Closes angular#6345 Somebody accidentally padded a list with one-too-many indentations, which caused the actual documentation page to render incorrectly. This should fix it.
diff --git a/src/ngRoute/route.js b/src/ngRoute/route.js
@@ -51,19 +51,19 @@ function $RouteProvider(){
    *    `$location.path` will be updated to add or drop the trailing slash to exactly match the
    *    route definition.
    *
-   *      * `path` can contain named groups starting with a colon: e.g. `:name`. All characters up
+   *    * `path` can contain named groups starting with a colon: e.g. `:name`. All characters up
    *        to the next slash are matched and stored in `$routeParams` under the given `name`
    *        when the route matches.
-   *      * `path` can contain named groups starting with a colon and ending with a star:
+   *    * `path` can contain named groups starting with a colon and ending with a star:
    *        e.g.`:name*`. All characters are eagerly stored in `$routeParams` under the given `name`
    *        when the route matches.
-   *      * `path` can contain optional named groups with a question mark: e.g.`:name?`.
+   *    * `path` can contain optional named groups with a question mark: e.g.`:name?`.
    *
    *    For example, routes like `/color/:color/largecode/:largecode*\/edit` will match
    *    `/color/brown/largecode/code/with/slashs/edit` and extract:
    *
-   *      * `color: brown`
-   *      * `largecode: code/with/slashs`.
+   *    * `color: brown`
+   *    * `largecode: code/with/slashs`.
    *
    *
    * @param {Object} route Mapping information to be assigned to `$route.current` on route

Original file line number	Diff line number	Diff line change
`@@ -51,19 +51,19 @@ function $RouteProvider(){`
`51`	`51`	* `$location.path` will be updated to add or drop the trailing slash to exactly match the
`52`	`52`	`* route definition.`
`53`	`53`	`*`
`54`		- * * `path` can contain named groups starting with a colon: e.g. `:name`. All characters up
	`54`	+ * * `path` can contain named groups starting with a colon: e.g. `:name`. All characters up
`55`	`55`	* to the next slash are matched and stored in `$routeParams` under the given `name`
`56`	`56`	`* when the route matches.`
`57`		- * * `path` can contain named groups starting with a colon and ending with a star:
	`57`	+ * * `path` can contain named groups starting with a colon and ending with a star:
`58`	`58`	* e.g.`:name*`. All characters are eagerly stored in `$routeParams` under the given `name`
`59`	`59`	`* when the route matches.`
`60`		- * * `path` can contain optional named groups with a question mark: e.g.`:name?`.
	`60`	+ * * `path` can contain optional named groups with a question mark: e.g.`:name?`.
`61`	`61`	`*`
`62`	`62`	* For example, routes like `/color/:color/largecode/:largecode*\/edit` will match
`63`	`63`	* `/color/brown/largecode/code/with/slashs/edit` and extract:
`64`	`64`	`*`
`65`		- * * `color: brown`
`66`		- * * `largecode: code/with/slashs`.
	`65`	+ * * `color: brown`
	`66`	+ * * `largecode: code/with/slashs`.
`67`	`67`	`*`
`68`	`68`	`*`
`69`	`69`	* @param {Object} route Mapping information to be assigned to `$route.current` on route