From fe84f7bef8b7c63158cf1699f3a62793b555fce8 Mon Sep 17 00:00:00 2001
From: hambyiii
Date: Tue, 3 Dec 2013 09:55:09 +0100
Subject: docs($route): clarify examples of route parameters

Putting route parameter examples in braces was misleading newcomers.

Closes #5243
---
 src/ngRoute/route.js | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'src/ngRoute')

diff --git a/src/ngRoute/route.js b/src/ngRoute/route.js
index e56faa30..fb1b952f 100644
--- a/src/ngRoute/route.js
+++ b/src/ngRoute/route.js
@@ -52,13 +52,13 @@ 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 (`: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 (`:name*`).
+   *      * `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 (`: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:
-- 
cgit v1.2.3