aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/cookbook
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/cookbook')
-rw-r--r--docs/content/cookbook/deeplinking.ngdoc4
-rw-r--r--docs/content/cookbook/form.ngdoc2
-rw-r--r--docs/content/cookbook/helloworld.ngdoc2
-rw-r--r--docs/content/cookbook/index.ngdoc2
-rw-r--r--docs/content/cookbook/mvc.ngdoc2
5 files changed, 6 insertions, 6 deletions
diff --git a/docs/content/cookbook/deeplinking.ngdoc b/docs/content/cookbook/deeplinking.ngdoc
index 27087726..f1f1397a 100644
--- a/docs/content/cookbook/deeplinking.ngdoc
+++ b/docs/content/cookbook/deeplinking.ngdoc
@@ -105,9 +105,9 @@ The two partials are defined in the following URLs:
# Things to notice
* Routes are defined in the `AppCntl` class. The initialization of the controller causes the
- initialization of the {@link api/angular.service.$route $route} service with the proper URL
+ initialization of the {@link api/angular.module.NG.$route $route} service with the proper URL
routes.
-* The {@link api/angular.service.$route $route} service then watches the URL and instantiates the
+* 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.widget.ng:view ng:view} widget loads the view when the URL changes. It
also
diff --git a/docs/content/cookbook/form.ngdoc b/docs/content/cookbook/form.ngdoc
index 1b5bf32b..9136e0f4 100644
--- a/docs/content/cookbook/form.ngdoc
+++ b/docs/content/cookbook/form.ngdoc
@@ -104,7 +104,7 @@ allow a user to enter data.
* The user data model is initialized {@link api/angular.directive.ng:controller controller} and is
available in
- the {@link api/angular.scope scope} with the initial data.
+ the {@link api/angular.module.NG.$rootScope.Scope scope} with the initial data.
* For debugging purposes we have included a debug view of the model to better understand what
is going on.
* The {@link api/angular.widget.input input widgets} simply refer to the model and are data-bound.
diff --git a/docs/content/cookbook/helloworld.ngdoc b/docs/content/cookbook/helloworld.ngdoc
index c93cdbea..e52f68e3 100644
--- a/docs/content/cookbook/helloworld.ngdoc
+++ b/docs/content/cookbook/helloworld.ngdoc
@@ -31,7 +31,7 @@ Take a look through the source and note:
* The script tag that {@link guide/dev_guide.bootstrap bootstraps} the angular environment.
* The text {@link api/angular.widget.input input widget} which is bound to the greeting name text.
* No need for listener registration and event firing on change events.
-* The implicit presence of the `name` variable which is in the root {@link api/angular.scope scope}.
+* The implicit presence of the `name` variable which is in the root {@link api/angular.module.NG.$rootScope.Scope scope}.
* The double curly brace `{{markup}}`, which binds the name variable to the greeting text.
* The concept of {@link guide/dev_guide.templates.databinding data binding}, which reflects any
changes to the
diff --git a/docs/content/cookbook/index.ngdoc b/docs/content/cookbook/index.ngdoc
index 06b898ac..aca42369 100644
--- a/docs/content/cookbook/index.ngdoc
+++ b/docs/content/cookbook/index.ngdoc
@@ -44,7 +44,7 @@ allowing you to send links to specific screens in your app.
# Services
-{@link api/angular.service Services}: Services are long lived objects in your applications that are
+{@link api/angular.module.NG Services}: Services are long lived objects in your applications that are
available across controllers. A collection of useful services are pre-bundled with angular but you
will likely add your own. Services are initialized using dependency injection, which resolves the
order of initialization. This safeguards you from the perils of global state (a common way to
diff --git a/docs/content/cookbook/mvc.ngdoc b/docs/content/cookbook/mvc.ngdoc
index 28b8836f..3de9eb25 100644
--- a/docs/content/cookbook/mvc.ngdoc
+++ b/docs/content/cookbook/mvc.ngdoc
@@ -121,4 +121,4 @@ board variable.
* The view can call any controller function.
* In this example, the `setUrl()` and `readUrl()` functions copy the game state to/from the URL's
hash so the browser's back button will undo game steps. See deep-linking. This example calls {@link
-api/angular.scope.$watch $watch()} to set up a listener that invokes `readUrl()` when needed.
+api/angular.module.NG.$rootScope.Scope#$watch $watch()} to set up a listener that invokes `readUrl()` when needed.