diff --git a/src/ng/directive/ngController.js b/src/ng/directive/ngController.js
index 9e7e3a80..3ad2cfbe 100644
--- a/src/ng/directive/ngController.js
+++ b/src/ng/directive/ngController.js
@@ -34,168 +34,183 @@
* easily be called from the angular markup. Any changes to the data are automatically reflected
* in the View without the need for a manual update.
*
- * Two different declaration styles are included below: one which injects `scope` into the
- * controller, and another which instead binds methods and properties directly onto the controller
- * using `this`. The first option is more common in the Angular community, and is generally used
- * in boilerplates and in this guide. However, there are advantages to binding properties directly
- * to the controller and avoiding scope. Using `controller as` makes it obvious which controller
- * you are accessing in the template when multiple controllers apply to an element. Since there
- * is always a `.` in the bindings, you don't have to worry about prototypal inheritance masking
- * primitives.
-
-
-
-
-
-
- it('should check controller', function() {
- var container = element(by.id('ctrl-exmpl'));
-
- expect(container.findElement(by.model('name'))
- .getAttribute('value')).toBe('John Smith');
-
- var firstRepeat =
- container.findElement(by.repeater('contact in contacts').row(0));
- var secondRepeat =
- container.findElement(by.repeater('contact in contacts').row(1));
-
- expect(firstRepeat.findElement(by.model('contact.value')).getAttribute('value'))
- .toBe('408 555 1212');
- expect(secondRepeat.findElement(by.model('contact.value')).getAttribute('value'))
- .toBe('john.smith@example.org');
-
- firstRepeat.findElement(by.linkText('clear')).click();
-
- expect(firstRepeat.findElement(by.model('contact.value')).getAttribute('value'))
- .toBe('');
-
- container.findElement(by.linkText('add')).click();
-
- expect(container.findElement(by.repeater('contact in contacts').row(2))
- .findElement(by.model('contact.value'))
- .getAttribute('value'))
- .toBe('yourname@example.org');
- });
-
-
+ * Two different declaration styles are included below:
+ *
+ * * one binds methods and properties directly onto the controller using `this`:
+ * `ng-controller="SettingsController1 as settings"`
+ * * one injects `$scope` into the controller:
+ * `ng-controller="SettingsController2"`
+ *
+ * The second option is more common in the Angular community, and is generally used in boilerplates
+ * and in this guide. However, there are advantages to binding properties directly to the controller
+ * and avoiding scope.
+ *
+ * * Using `controller as` makes it obvious which controller you are accessing in the template when
+ * multiple controllers apply to an element.
+ * * If you are writing your controllers as classes you have easier access to the properties and
+ * methods, which will appear on the scope, from inside the controller code.
+ * * Since there is always a `.` in the bindings, you don't have to worry about prototypal
+ * inheritance masking primitives.
+ *
+ * This example demonstrates the `controller as` syntax.
+ *
+ *
+ *
+ *