docs(compiler): update the compiler docs

docs/content/api/index.ngdoc

@@ -4,9 +4,7 @@
 
 ## Angular Compiler API
 
-* {@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.$compileProvider.directive Directives} - Angular DOM element attributes
 * {@link angular.module.ng.$filter Filters} - Angular output filters
 * {@link angular.module.ng.$compile $compile} - Template compiler
 

docs/content/cookbook/deeplinking.ngdoc

@@ -102,11 +102,10 @@ The two partials are defined in the following URLs:
 
 * 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
-routes.
+  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.widget.ng:view ng:view} widget loads the view when the URL changes. It
-also
-  sets the view scope to the newly instantiated controller.
+* 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.

docs/content/cookbook/form.ngdoc

@@ -102,12 +102,12 @@ allow a user to enter data.
 
 # Things to notice
 
-* 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 user data model is initialized {@link api/angular.module.ng.$compileProvider.directive.ng:controller controller} and is
+  available in 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.
+* The {@link api/angular.module.ng.$compileProvider.directive.input input directives} simply refer
+  to the model and are data-bound.
 * The inputs {@link guide/dev_guide.forms validate}. (Try leaving them blank or entering non digits
   in the zip field)
 * In your application you can simply read from or write to the model and the form will be updated.

docs/content/cookbook/helloworld.ngdoc

@@ -29,7 +29,8 @@
 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.
+* The text {@link api/angular.module.ng.$compileProvider.directive.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 double curly brace `{{markup}}`, which binds the name variable to the greeting text.

docs/content/guide/dev_guide.bootstrap.ngdoc

@@ -31,18 +31,19 @@ and manage the whole page. You do this as follows:
 
 You need to declare the angular namespace declaration in the following cases:
 
-* For all browsers if you are using XHTML.
-* For Internet Explorer older than version 9 (because older versions of IE do not render widgets
+* For all types of browser if you are using XHTML.
+* For Internet Explorer older than version 9 (because older versions of IE do not render namespace
 properly for either HTML or XHTML).
 
 
 ## Creating Your Own Namespaces
 
-When you are ready to define your own {@link dev_guide.compiler.widgets widgets}, you must create
-your own namespace in addition to specifying the angular namespace. You use your own namespace to
-form the fully qualified name for widgets that you create.
+When you are ready to define your own {@link api/angular.module.ng.$compileProvider.directive
+directive}, you may chose to create your own namespace in addition to specifying the angular
+namespace. You use your own namespace to form the fully qualified name for directives that you
+create.
 
-For example, you could map the alias `my` to your domain, and create a widget called `my:widget`.
+For example, you could map the alias `my` to your domain, and create a directive called `my:directive`.
 To create your own namespace, simply add another `xmlns` tag to your page, create an alias, and set
 it to your unique domain: