diff options
| author | Igor Minar | 2012-04-06 16:35:17 -0700 |
|---|---|---|
| committer | Igor Minar | 2012-04-09 09:52:27 -0700 |
| commit | 82d90a409692e97a79c3bf4708ee80796c7de2d6 (patch) | |
| tree | b682f2d3042381e2456383f9c9333d30105febf8 /docs/content/tutorial/step_00.ngdoc | |
| parent | 7468bcb80b997e323bb0808d19ee215cc5f7ae84 (diff) | |
| download | angular.js-82d90a409692e97a79c3bf4708ee80796c7de2d6.tar.bz2 | |
fix(docs): change all directive references to use the normalized names
Diffstat (limited to 'docs/content/tutorial/step_00.ngdoc')
| -rw-r--r-- | docs/content/tutorial/step_00.ngdoc | 21 |
1 files changed, 11 insertions, 10 deletions
diff --git a/docs/content/tutorial/step_00.ngdoc b/docs/content/tutorial/step_00.ngdoc index 643ec23b..63123926 100644 --- a/docs/content/tutorial/step_00.ngdoc +++ b/docs/content/tutorial/step_00.ngdoc @@ -172,9 +172,10 @@ __`app/index.html`:__ <html ng-app> - `ng-app` directive is a special tag used to flag an element which Angular should consider to be - the root element of our application. This gives application developers the freedom to tell Angular - if the entire html page or only a portion of it should be treated as the Angular application. + The `ng-app` attribute is represents an Angular directive used to flag an element which Angular + should consider to be the root element of our application. This gives application developers the + freedom to tell Angular if the entire html page or only a portion of it should be treated as the + Angular application. * AngularJS script tag: @@ -182,9 +183,9 @@ __`app/index.html`:__ This code downloads the `angular.js` script and registers a callback that will be executed by the browser when the containing HTML page is fully downloaded. When the callback is executed, Angular -looks for the {@link api/angular.module.ng.$compileProvider.directive.ng-app ng-app} directive. If -Angular finds `ng-app`, it will bootstrap the application with the root of the application DOM being -the element on which the `ng-app` directive was defined. +looks for the {@link api/angular.module.ng.$compileProvider.directive.ngApp ngApp} directive. If +Angular finds the directive, it will bootstrap the application with the root of the application DOM +being the element on which the `ngApp` directive was defined. * Double-curly binding with an expression: @@ -207,7 +208,7 @@ the element on which the `ng-app` directive was defined. ## Bootstrapping AngularJS apps -Bootstrapping AngularJS apps automatically using the `ng-app` directive is very easy and suitable +Bootstrapping AngularJS apps automatically using the `ngApp` directive is very easy and suitable for most cases. In advanced cases, such as when using script loaders, you can use {@link guide/dev_guide.bootstrap.manual_bootstrap imperative / manual way} to bootstrap the app. @@ -219,7 +220,7 @@ There are 3 important things that happen during the app bootstrap: 2. The injector will then create the {@link api/angular.module.ng.$rootScope root scope} that will become the context for the model of our application. -3. Angular will then "compile" the DOM starting at the `ng-app` root element, processing any +3. Angular will then "compile" the DOM starting at the `ngApp` root element, processing any directives and bindings found along the way. @@ -267,6 +268,6 @@ Now let's go to {@link step_01 step 1} and add some content to the web app. Move elsewhere: Note: During the bootstrap the injector and the root scope will then be associated with the - element on which `ng-app` was declared, so when debugging the app you can retrieve them from - browser console via `angular.element(rootElement).scope()` and + element on which the `ngApp` directive was declared, so when debugging the app you can retrieve + them from browser console via `angular.element(rootElement).scope()` and `angular.element(rootElement).injector()`. |