From c2006cdfbdeb5877f0136ae59c4e4bb2428f3d48 Mon Sep 17 00:00:00 2001
From: andre <andre.evangelesta@gmail.com>
Date: Fri, 8 Nov 2013 10:43:40 -0800
Subject: [PATCH] docs(guide/scope) correct explanation of example

Remove reference to 'employee' property as it's not used in the example.

Add $rootScope injection and definition of 'department' property mentioned in text.

Fiddle example of change: http://jsfiddle.net/F9L7z/
---
 docs/content/guide/scope.ngdoc | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/content/guide/scope.ngdoc b/docs/content/guide/scope.ngdoc
index 342877d70d43..9fdefdfa065a 100644
--- a/docs/content/guide/scope.ngdoc
+++ b/docs/content/guide/scope.ngdoc
@@ -126,13 +126,14 @@ a diagram depicting the scope boundaries.
     </div>
     <div ng-controller="ListCtrl">
       <ol>
-        <li ng-repeat="name in names">{{name}}</li>
+        <li ng-repeat="name in names">{{name}} from {{department}}</li>
       </ol>
     </div>
   </file>
   <file name="script.js">
-    function GreetCtrl($scope) {
+    function GreetCtrl($scope, $rootScope) {
       $scope.name = 'World';
+      $rootScope.department = 'Angular';
     }
 
     function ListCtrl($scope) {
@@ -153,7 +154,7 @@ a diagram depicting the scope boundaries.
 
 Notice that Angular automatically places `ng-scope` class on elements where scopes are
 attached. The `<style>` definition in this example highlights in red the new scope locations. The
-child scopes are necessary because the repeater evaluates `{{employee.name}}` expression, but
+child scopes are necessary because the repeater evaluates `{{name}}` expression, but
 depending on which scope the expression is evaluated it produces different result. Similarly the
 evaluation of `{{department}}` prototypically inherits from root scope, as it is the only place
 where the `department` property is defined.