From 38e2856889b2e7f7f2898d22db18ac273badb287 Mon Sep 17 00:00:00 2001
From: Peter Bacon Darwin <pete@bacondarwin.com>
Date: Mon, 20 Oct 2014 10:32:06 +0100
Subject: [PATCH] docs(guide/introduction): remove ambiguous "code-behind"
 jargon

This commit tries to remove the jargon and explain in plain English what
it means to add "code-behind" via a directive.

Closes #9684
---
 docs/content/guide/introduction.ngdoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/content/guide/introduction.ngdoc b/docs/content/guide/introduction.ngdoc
index 76400d36..c55a2440 100644
--- a/docs/content/guide/introduction.ngdoc
+++ b/docs/content/guide/introduction.ngdoc
@@ -33,7 +33,7 @@ browser new syntax through a construct we call directives. Examples include:
   * Data binding, as in `{{}}`.
   * DOM control structures for repeating/hiding DOM fragments.
   * Support for forms and form validation.
-  * Attaching code-behind to DOM elements.
+  * Attaching new behavior to DOM elements, such as DOM event handling.
   * Grouping of HTML into reusable components.