aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/cookbook
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/cookbook')
-rw-r--r--docs/content/cookbook/deeplinking.ngdoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/content/cookbook/deeplinking.ngdoc b/docs/content/cookbook/deeplinking.ngdoc
index 4343ded2..f242f82e 100644
--- a/docs/content/cookbook/deeplinking.ngdoc
+++ b/docs/content/cookbook/deeplinking.ngdoc
@@ -5,7 +5,7 @@
Deep linking allows you to encode the state of the application in the URL so that it can be
bookmarked and the application can be restored from the URL to the same state.
-While <angular/> does not force you to deal with bookmarks in any particular way, it has services
+While angular does not force you to deal with bookmarks in any particular way, it has services
which make the common case described here very easy to implement.
# Assumptions
@@ -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:
-* <a href="./examples/settings.html" ng-ext-link>./examples/settings.html</a>
-* <a href="./examples/welcome.html" ng-ext-link>./examples/welcome.html</a>
+* <a href="examples/settings.html" target="_self">./examples/settings.html</a>
+* <a href="examples/welcome.html" target="_self">./examples/welcome.html</a>
<doc:example module="deepLinking">
<doc:source jsfiddle="false">