From accebff4b5f357bc4d8ee426fb4825a954649ca3 Mon Sep 17 00:00:00 2001
From: Jeremy Ashkenas <jashkenas@gmail.com>
Date: Tue, 12 Oct 2010 17:38:57 -0400
Subject: [PATCH] ''

---
 index.html | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/index.html b/index.html
index 7f80d34e..c9b1ea36 100644
--- a/index.html
+++ b/index.html
@@ -257,10 +257,11 @@
     <h2 id="Introduction">Introduction</h2>
 
     <p>
-      The core idea behind Backbone is to avoid tying your data to the DOM. It's
+      When working on a heavy-duty JavaScript application, one of the first things
+      you learn is to stop tying your data to the DOM. It's all
       too easy to create JavaScript applications that end up as tangled piles of
       jQuery selectors and callbacks, all trying frantically to keep data in
-      sync between the UI, your JavaScript logic, and the database on your
+      sync between the HTML UI, your JavaScript logic, and the database on your
       server. For rich client-side applications, a more structured approach
       is helpful.
     </p>
@@ -292,8 +293,8 @@
       core libraries, and determine the structure of your HTML for you.
       Loading the "Hello World" of SproutCore includes <i>2.5 megabytes</i> of JavaScript on the
       page; the "Hello World" of Cappuccino includes <i>1.7 megabytes</i> of JS and images.
-      Backbone is a <i>2 kilobyte</i> include that provides the core concepts of
-      models, events (key-value observing), collections, views, and persistence.
+      Backbone is a <i>2 kilobyte</i> include that provides just the core concepts of
+      models, events (key-value binding), collections, views, and persistence.
     </p>
 
     <h2 id="Events">Backbone.Events</h2>