From e3644c8fd9d729499a987b8a98bd7883ec4466a3 Mon Sep 17 00:00:00 2001
From: maggiewachs <maggie@filamentgroup.com>
Date: Thu, 29 Sep 2011 13:39:54 -0400
Subject: [PATCH] clarified blurb about how events are preserved for form
 buttons

---
 docs/buttons/buttons-types.html | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/docs/buttons/buttons-types.html b/docs/buttons/buttons-types.html
index 1015a77c..563ae6fb 100755
--- a/docs/buttons/buttons-types.html
+++ b/docs/buttons/buttons-types.html
@@ -47,9 +47,8 @@
 		<a href="index.html" data-role="button">Link button</a>
 		
 		<h2>Form buttons</h2>
-		<p>For ease of styling, the framework automatically converts any <code>button</code> element or <code>input</code> with a <code>type</code> of <code>submit</code>, <code>reset</code>, <code>button</code>, or <code>image</code> into a custom styled link-based button &mdash; there is no need to add the <code> data-role="button"</code> attribute. </p>
-		<p>The original form-based button is hidden, but remains in the markup.  When a click event fires on a link button, it triggers a click on the original form button.</p>
-
+		<p>For ease of styling, the framework automatically converts any <code>button</code> or <code>input</code> element with a <code>type</code> of <code>submit</code>, <code>reset</code>, <code>button</code>, or <code>image</code> into a custom styled button &mdash; there is no need to add the <code> data-role="button"</code> attribute. </p>
+		<p>To preserve events bound to the original <code>button</code> or <code>input</code>, the framework hides the original element by making it transparent and positioning it over the new button markup.  When a user clicks on the the custom-styled button, they're actually clicking on the original element.</p>
 
 		<p><strong>Button</strong> based button:</p>
 		<button>Button element</button>