From 5a306b7ba3a67f954ebba7bbb48ed5518dcf5ce9 Mon Sep 17 00:00:00 2001
From: Zacky Ma <marchbox@gmail.com>
Date: Mon, 16 Jun 2014 14:07:30 -0700
Subject: [PATCH] docs(guide/compiler): change {{user}} to {{user.name}} in
 example

If user has an `actions` property, it should be an object,
which means if you {{user}}, it'll print out the object.
---
 docs/content/guide/compiler.ngdoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/content/guide/compiler.ngdoc b/docs/content/guide/compiler.ngdoc
index 44151a4c3..5296296b4 100644
--- a/docs/content/guide/compiler.ngdoc
+++ b/docs/content/guide/compiler.ngdoc
@@ -226,7 +226,7 @@ moved to the compile function for performance reasons.
 To understand, let's look at a real-world example with `ngRepeat`:
 
 ```html
-Hello {{user}}, you have these actions:
+Hello {{user.name}}, you have these actions:
 <ul>
   <li ng-repeat="action in user.actions">
     {{action.description}}
@@ -236,7 +236,7 @@ Hello {{user}}, you have these actions:
 
 When the above example is compiled, the compiler visits every node and looks for directives.
 
-`{{user}}` matches the {@link ng.$interpolate interpolation directive}
+`{{user.name}}` matches the {@link ng.$interpolate interpolation directive}
 and `ng-repeat` matches the {@link ng.directive:ngRepeat `ngRepeat` directive}.
 
 But {@link ng.directive:ngRepeat ngRepeat} has a dilemma.