From 63be222326f3badbb76371f82d49fed5ab9e3e65 Mon Sep 17 00:00:00 2001 From: Vojta Jina Date: Tue, 13 Mar 2012 13:52:57 -0700 Subject: docs(input): Fix some broken links, add missing $, use ng- in examples --- docs/content/cookbook/deeplinking.ngdoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/content/cookbook/deeplinking.ngdoc') diff --git a/docs/content/cookbook/deeplinking.ngdoc b/docs/content/cookbook/deeplinking.ngdoc index 4db8d1c7..db5f057e 100644 --- a/docs/content/cookbook/deeplinking.ngdoc +++ b/docs/content/cookbook/deeplinking.ngdoc @@ -33,8 +33,8 @@ In this example we have a simple app which consist of two screens: The two partials are defined in the following URLs: -* ./examples/settings.html -* ./examples/welcome.html +* ./examples/settings.html +* ./examples/welcome.html @@ -73,7 +73,7 @@ The two partials are defined in the following URLs: $scope.cancel(); } -
+

Your App Chrome

[ Welcome | Settings ]
@@ -106,7 +106,7 @@ The two partials are defined in the following URLs: routes. * The {@link api/angular.module.ng.$route $route} service then watches the URL and instantiates the appropriate controller when the URL changes. -* The {@link api/angular.module.ng.$compileProvider.directive.ng:view ng:view} widget loads the +* The {@link api/angular.module.ng.$compileProvider.directive.ng-view ng-view} widget loads the view when the URL changes. It also sets the view scope to the newly instantiated controller. * Changing the URL is sufficient to change the controller and view. It makes no difference whether the URL is changed programatically or by the user. -- cgit v1.2.3