From b728030be0dbdd0639bd49091b774d4665eecb27 Mon Sep 17 00:00:00 2001
From: Akhlesh <akhlesh.sims@gmail.com>
Date: Tue, 26 Aug 2014 08:11:05 +0530
Subject: [PATCH] docs(guide/directive): update since 'EA' is now the default
 restrict value

11f5aeeee952a395edaf54e3277674f211a82fc7 changed the compiler to use 'EA' as a 'restrict'
value if not specified in the directive object, and the directive guide needed some slight
changes to address this.

Closes #8769
---
 docs/content/guide/directive.ngdoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/content/guide/directive.ngdoc b/docs/content/guide/directive.ngdoc
index b613c5bf..5b6dfd95 100644
--- a/docs/content/guide/directive.ngdoc
+++ b/docs/content/guide/directive.ngdoc
@@ -285,8 +285,8 @@ Great! But what if we wanted to have our directive match the tag name `<my-custo
 If we simply put a `<my-customer>` element into the HTML, it doesn't work.
 
 <div class="alert alert-warning">
-**Note:** When you create a directive, it is restricted to attribute only by default. In order to
-create directives that are triggered by element or class name, you need to use the `restrict` option.
+**Note:** When you create a directive, it is restricted to attribute and elements only by default. In order to
+create directives that are triggered by class name, you need to use the `restrict` option.
 </div>
 
 The `restrict` option is typically set to: