From e69c2872939cda30f13a1a8390bbc61662c12d9a Mon Sep 17 00:00:00 2001
From: Brian Ford
Date: Wed, 23 Oct 2013 14:04:47 -0700
Subject: docs(guide/directive,guide/compiler,): drastically improve

---
 docs/content/error/compile/nonassign.ngdoc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

(limited to 'docs/content/error/compile/nonassign.ngdoc')

diff --git a/docs/content/error/compile/nonassign.ngdoc b/docs/content/error/compile/nonassign.ngdoc
index 9f78ed3f..3870c2ed 100644
--- a/docs/content/error/compile/nonassign.ngdoc
+++ b/docs/content/error/compile/nonassign.ngdoc
@@ -3,7 +3,9 @@
 @fullName Non-Assignable Expression
 @description
 
-This error occurs when a directive defines an isolate scope property that support two-way data-binding (using the `=` mode in the {@link guide/directive#writing-directives_directive-definition-object  directive definition}) but the directive is used with an expression that is not-assignable.
+This error occurs when a directive defines an isolate scope property
+(using the `=` mode in the {@link api/ng.$compile#description_comprehensive-directive-api_directive-definition-object
+`scope` option} of a directive definition) but the directive is used with an expression that is not-assignable.
 
 In order for the two-way data-binding to work, it must be possible to write new values back into the path defined with the expression.
 
-- 
cgit v1.2.3