triggerHandler: Rephrase description and differences from trigger

Author: gnarf

entries/triggerHandler.xml

@@ -14,9 +14,9 @@
     </argument>
   </signature>
   <longdesc>
-    <p>The <code>.triggerHandler()</code> method behaves similarly to <code>.trigger()</code>, with the following exceptions:</p>
+    <p><code>.triggerHandler( eventType )</code> executes all handlers bound with jQuery for the event type.  It will also execute any method called <code>on{eventType}()</code> found on the element.  The behavior of this method is similar to <a href="/trigger"><code>.trigger()</code></a>, with the following exceptions:</p>
     <ul>
-      <li>The <code>.triggerHandler()</code> method does not cause the default behavior of an event to occur (such as a form submission).</li>
+      <li>The <code>.triggerHandler( "event" )</code> method will not call <code>.event()</code> on the element it is triggered on.  This means <code>.triggerHandler( "submit" )</code> on a form will not call <code>.submit()</code> on the form.</li>
       <li>While <code>.trigger()</code> will operate on all elements matched by the jQuery object, <code>.triggerHandler()</code> only affects the first matched element.</li>
       <li>Events triggered with <code>.triggerHandler()</code> do not bubble up the DOM hierarchy; if they are not handled by the target element directly, they do nothing.</li>
       <li>Instead of returning the jQuery object (to allow chaining), <code>.triggerHandler()</code> returns whatever value was returned by the last handler it caused to be executed. If no handlers are triggered, it returns <code>undefined</code></li>