-var injector = angular.injector('NG', 'MyModule')
+var injector = angular.injector('ng', 'MyModule')
Or
-var injector = angular.injector('NG', angular.module.MyModule)
+var injector = angular.injector('ng', angular.module.MyModule)
diff --git a/docs/content/api/index.ngdoc b/docs/content/api/index.ngdoc
index 6c5745dc..ccacef80 100644
--- a/docs/content/api/index.ngdoc
+++ b/docs/content/api/index.ngdoc
@@ -7,23 +7,23 @@
* {@link angular.widget Widgets} - Angular custom DOM element
* {@link angular.directive Directives} - Angular DOM element attributes
* {@link angular.markup Markup} and {@link angular.attrMarkup Attribute Markup}
-* {@link angular.module.NG.$filter Filters} - Angular output filters
-* {@link angular.module.NG.$compile $compile} - Template compiler
+* {@link angular.module.ng.$filter Filters} - Angular output filters
+* {@link angular.module.ng.$compile $compile} - Template compiler
## Angular Scope API
-* {@link angular.module.NG.$rootScope.Scope Scope Object} - Angular scope object
+* {@link angular.module.ng.$rootScope.Scope Scope Object} - Angular scope object
## Angular Services & Dependency Injection API
-* {@link angular.module.NG Angular Services}
+* {@link angular.module.ng Angular Services}
* {@link angular.injector angular.injector() }
## Angular Testing API
-* {@link angular.module.NG_MOCK Testing Mocks API} - Mock objects for testing
+* {@link angular.module.ngMock Testing Mocks API} - Mock objects for testing
* {@link guide/dev_guide.e2e-testing Angular Scenario Runner} - Automated scenario testing
documentation
diff --git a/docs/content/cookbook/deeplinking.ngdoc b/docs/content/cookbook/deeplinking.ngdoc
index f1f1397a..2ef3da4a 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.module.NG.$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.module.NG.$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 9136e0f4..80c23e94 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.module.NG.$rootScope.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 e52f68e3..e3d76d83 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.module.NG.$rootScope.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 aca42369..43ac9bb2 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.module.NG 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 3de9eb25..f566a541 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.module.NG.$rootScope.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.
diff --git a/docs/content/guide/dev_guide.bootstrap.auto_bootstrap.ngdoc b/docs/content/guide/dev_guide.bootstrap.auto_bootstrap.ngdoc
index a75dc52f..d461bfb4 100644
--- a/docs/content/guide/dev_guide.bootstrap.auto_bootstrap.ngdoc
+++ b/docs/content/guide/dev_guide.bootstrap.auto_bootstrap.ngdoc
@@ -98,4 +98,4 @@ APIs are bound to fields of this global object.
## Related API
-{@link api/angular.module.NG.$compile Compiler API}
+{@link api/angular.module.ng.$compile Compiler API}
diff --git a/docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc b/docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc
index 435f1418..c042b2e3 100644
--- a/docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc
+++ b/docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc
@@ -43,4 +43,4 @@ an executable, bi-directionally bound application.
## Related API
-{@link api/angular.module.NG.$compile Compiler API}
+{@link api/angular.module.ng.$compile Compiler API}
diff --git a/docs/content/guide/dev_guide.compiler.directives.creating_directives.ngdoc b/docs/content/guide/dev_guide.compiler.directives.creating_directives.ngdoc
index 18b9d630..2d6723cf 100644
--- a/docs/content/guide/dev_guide.compiler.directives.creating_directives.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.directives.creating_directives.ngdoc
@@ -23,7 +23,7 @@ angular.directive('ng:bind', function(expression, compiledElement) {
The angular compiler exposes methods that you may need to use when writing your own widgets and
directives. For example, the `descend()` method lets you control whether the compiler ignores or
processes child elements of the element it is compiling. For information on this and other
-compiler methods, see the {@link api/angular.module.NG.$compile Compiler API doc}.
+compiler methods, see the {@link api/angular.module.ng.$compile Compiler API doc}.
## Related Docs
diff --git a/docs/content/guide/dev_guide.compiler.extending_compiler.ngdoc b/docs/content/guide/dev_guide.compiler.extending_compiler.ngdoc
index 49f76b2b..90c7f5e2 100644
--- a/docs/content/guide/dev_guide.compiler.extending_compiler.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.extending_compiler.ngdoc
@@ -93,4 +93,4 @@ corresponding spans.
## Related API
-* {@link api/angular.module.NG.$compile $compile()}
+* {@link api/angular.module.ng.$compile $compile()}
diff --git a/docs/content/guide/dev_guide.compiler.markup.ngdoc b/docs/content/guide/dev_guide.compiler.markup.ngdoc
index ef327a5d..0a01da57 100644
--- a/docs/content/guide/dev_guide.compiler.markup.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.markup.ngdoc
@@ -89,4 +89,4 @@ angular.attrMarkup('extraClass', function(attrValue, attrName, element){
## Related API
-* {@link api/angular.module.NG.$compile Compiler API Reference}
+* {@link api/angular.module.ng.$compile Compiler API Reference}
diff --git a/docs/content/guide/dev_guide.compiler.ngdoc b/docs/content/guide/dev_guide.compiler.ngdoc
index cc673751..2789c843 100644
--- a/docs/content/guide/dev_guide.compiler.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.ngdoc
@@ -23,4 +23,4 @@ All compilation takes place in the web browser; no server is involved.
## Related API
-* {@link api/angular.module.NG.$compile Angular Compiler API}
+* {@link api/angular.module.ng.$compile Angular Compiler API}
diff --git a/docs/content/guide/dev_guide.compiler.testing_dom_element.ngdoc b/docs/content/guide/dev_guide.compiler.testing_dom_element.ngdoc
index c7032d2f..e077bf4d 100644
--- a/docs/content/guide/dev_guide.compiler.testing_dom_element.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.testing_dom_element.ngdoc
@@ -14,4 +14,4 @@
## Related API
-* {@link api/angular.module.NG.$compile $compile()}
+* {@link api/angular.module.ng.$compile $compile()}
diff --git a/docs/content/guide/dev_guide.compiler.understanding_compiler.ngdoc b/docs/content/guide/dev_guide.compiler.understanding_compiler.ngdoc
index 4200c823..94bab26d 100644
--- a/docs/content/guide/dev_guide.compiler.understanding_compiler.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.understanding_compiler.ngdoc
@@ -20,7 +20,7 @@ dataset]"`), the link function gets called to set up a listener on each element
Note that angular's built-in widgets, directives, and markup have predefined compile and link
functions that you don't need to modify. When you create your own widgets, directives, or markup,
-you must write compile and link functions for them. Refer to the {@link api/angular.module.NG.$compile
+you must write compile and link functions for them. Refer to the {@link api/angular.module.ng.$compile
Compiler API} for details.
When the angular compiler compiles a page, it proceeds through 3 phases: Compile, Create Root
@@ -53,7 +53,7 @@ Note that while the compile function is executed exactly once, the link function
multiple times, for example, once for each iteration in a repeater.
The angular compiler exposes methods that you will need to make use of when writing your own
-widgets and directives. For information on these methods, see the {@link api/angular.module.NG.$compile
+widgets and directives. For information on these methods, see the {@link api/angular.module.ng.$compile
Compiler API doc}.
@@ -65,4 +65,4 @@ Compiler API doc}.
## Related API
-* {@link api/angular.module.NG.$compile $compile()}
+* {@link api/angular.module.ng.$compile $compile()}
diff --git a/docs/content/guide/dev_guide.compiler.widgets.creating_widgets.ngdoc b/docs/content/guide/dev_guide.compiler.widgets.creating_widgets.ngdoc
index 2c9fbb34..312f4000 100644
--- a/docs/content/guide/dev_guide.compiler.widgets.creating_widgets.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.widgets.creating_widgets.ngdoc
@@ -80,7 +80,7 @@ angular.widget('my:time', function(compileElement){
The angular compiler exposes methods that you may need to use of when writing your own widgets and
directives. For example, the `descend()` method lets you control whether the compiler ignores or
processes child elements of the element it is compiling. For information on this and other
-compiler methods, see the {@link api/angular.module.NG.$compile Compiler API doc}.
+compiler methods, see the {@link api/angular.module.ng.$compile Compiler API doc}.
## Related Topics
@@ -92,4 +92,4 @@ compiler methods, see the {@link api/angular.module.NG.$compile Compiler API doc
## Related API
-* {@link api/angular.module.NG.$compile Compiler API}
+* {@link api/angular.module.ng.$compile Compiler API}
diff --git a/docs/content/guide/dev_guide.compiler.widgets.ngdoc b/docs/content/guide/dev_guide.compiler.widgets.ngdoc
index c9e95a57..003cba53 100644
--- a/docs/content/guide/dev_guide.compiler.widgets.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.widgets.ngdoc
@@ -32,4 +32,4 @@ dev_guide.compiler.widgets.creating_widgets Creating Custom Widgets}.
## Related API
-* {@link api/angular.module.NG.$compile Compiler API}
+* {@link api/angular.module.ng.$compile Compiler API}
diff --git a/docs/content/guide/dev_guide.di.ngdoc b/docs/content/guide/dev_guide.di.ngdoc
index f9ff49c4..b21b05a7 100644
--- a/docs/content/guide/dev_guide.di.ngdoc
+++ b/docs/content/guide/dev_guide.di.ngdoc
@@ -28,5 +28,5 @@ book.
## Related API
-* {@link api/angular.module.NG Service API}
+* {@link api/angular.module.ng Service API}
* {@link api/angular.injector Angular Injector API}
diff --git a/docs/content/guide/dev_guide.di.understanding_di.ngdoc b/docs/content/guide/dev_guide.di.understanding_di.ngdoc
index 1dc9bd85..4c40ff20 100644
--- a/docs/content/guide/dev_guide.di.understanding_di.ngdoc
+++ b/docs/content/guide/dev_guide.di.understanding_di.ngdoc
@@ -7,15 +7,15 @@ While DI is widely used in statically typed languages such as Java or C++, it ha
used in JavaScript. Angular brings the benefits of DI into JavaScript apps.
In angular, DI is implemented as a subsystem that manages dependencies between services,
-controllers, widgets, and filters. The most important of these are {@link api/angular.module.NG
+controllers, widgets, and filters. The most important of these are {@link api/angular.module.ng
services}.
Services are objects that handle common tasks in web applications. Angular provides several{@link
-api/angular.module.NG built-in services}, and you can create your own custom services.
+api/angular.module.ng built-in services}, and you can create your own custom services.
The main job of angular's DI subsystem is to provide services to angular components that depend on
them. The way the DI subsystem provides services is as follows: all services are registered with
-angular's {@link api/angular.module.NG service API}, and all components that depend on services
+angular's {@link api/angular.module.ng service API}, and all components that depend on services
define those dependencies as a property (`$inject`). With this information, the DI subsystem
manages the creation of service objects and the provision of those objects to the components that
need them, at the time they need them. The following illustration steps through the sequence of
@@ -49,7 +49,7 @@ achieve the necessary isolation by having each test create its own separate root
// create a root scope
-var rootScope = angular.module.NG.$rootScope.Scope();
+var rootScope = angular.module.ng.$rootScope.Scope();
// access the service locator
var myService = rootScope.$service('myService');
@@ -74,7 +74,7 @@ equivalent:
// given a user defined service
-angular.module.NG('serviceA', ...);
+angular.module.ng('serviceA', ...);
// inject '$window', 'serviceA', curry 'name';
function fnA($window, serviceA, name){};
@@ -102,4 +102,4 @@ code and insert the `$inject` into the source code so that it can be minified/ob
## Related API
-* {@link api/angular.module.NG Services API}
+* {@link api/angular.module.ng Services API}
diff --git a/docs/content/guide/dev_guide.di.using_di_controllers.ngdoc b/docs/content/guide/dev_guide.di.using_di_controllers.ngdoc
index 3d087d18..fc27a5fd 100644
--- a/docs/content/guide/dev_guide.di.using_di_controllers.ngdoc
+++ b/docs/content/guide/dev_guide.di.using_di_controllers.ngdoc
@@ -14,7 +14,7 @@ MyController.$inject = ['$route'];
In this example, the `MyController` constructor function takes one argument, the {@link
-api/angular.module.NG.$route $route} service. Angular is then responsible for supplying the instance
+api/angular.module.ng.$route $route} service. Angular is then responsible for supplying the instance
of `$route` to the controller when the constructor is instantiated. There are two ways to cause
controller instantiation – by configuring routes with the `$route` service, or by referencing the
controller from the HTML template, as follows:
diff --git a/docs/content/guide/dev_guide.e2e-testing.ngdoc b/docs/content/guide/dev_guide.e2e-testing.ngdoc
index 6dbb9c1e..2cb82416 100644
--- a/docs/content/guide/dev_guide.e2e-testing.ngdoc
+++ b/docs/content/guide/dev_guide.e2e-testing.ngdoc
@@ -78,19 +78,19 @@ Returns the window.location.search of the currently loaded page in the test fram
Returns the window.location.hash (without `#`) of the currently loaded page in the test frame.
## browser().location().url()
-Returns the {@link api/angular.module.NG.$location $location.url()} of the currently loaded page in
+Returns the {@link api/angular.module.ng.$location $location.url()} of the currently loaded page in
the test frame.
## browser().location().path()
-Returns the {@link api/angular.module.NG.$location $location.path()} of the currently loaded page in
+Returns the {@link api/angular.module.ng.$location $location.path()} of the currently loaded page in
the test frame.
## browser().location().search()
-Returns the {@link api/angular.module.NG.$location $location.search()} of the currently loaded page
+Returns the {@link api/angular.module.ng.$location $location.search()} of the currently loaded page
in the test frame.
## browser().location().hash()
-Returns the {@link api/angular.module.NG.$location $location.hash()} of the currently loaded page in
+Returns the {@link api/angular.module.ng.$location $location.hash()} of the currently loaded page in
the test frame.
## expect(future).{matcher}
diff --git a/docs/content/guide/dev_guide.expressions.ngdoc b/docs/content/guide/dev_guide.expressions.ngdoc
index 3d5d0266..4df69d28 100644
--- a/docs/content/guide/dev_guide.expressions.ngdoc
+++ b/docs/content/guide/dev_guide.expressions.ngdoc
@@ -165,15 +165,15 @@ JavaScript method instead.
Built-in types have methods like `[].push()`, but the richness of these methods is limited.
Consider the example below, which allows you to do a simple search over a canned set of contacts.
The example would be much more complicated if we did not have the `Array:$filter()`. There is no
-built-in method on `Array` called {@link api/angular.module.NG.$filter.filter $filter} and angular doesn't add
+built-in method on `Array` called {@link api/angular.module.ng.$filter.filter $filter} and angular doesn't add
it to `Array.prototype` because that could collide with other JavaScript frameworks.
For this reason the scope expression evaluator augments the built-in types to make them act like
-they have extra methods. The actual method for `$filter()` is `angular.module.NG.$filter.filter()`. You can
+they have extra methods. The actual method for `$filter()` is `angular.module.ng.$filter.filter()`. You can
call it from JavaScript.
Extensions: You can further extend the expression vocabulary by adding new methods to
-`angular.module.NG.$filter` or `angular.String`, etc.
+`angular.module.ng.$filter` or `angular.String`, etc.