--- a/html/DOM3-Events.html	Tue Feb 24 17:01:10 2015 -0800
+++ b/html/DOM3-Events.html	Tue Feb 24 17:12:26 2015 -0800
@@ -3118,7 +3118,7 @@
 							e.g., it MAY depend on the screen location or the delay between the press and release of the pointing device button.
 							</p>
 
-						<p class="note"><strong>Note:</strong> The <code>click</code> event should only be fired for the primary
+						<p>The <code>click</code> event should only be fired for the primary
 							pointer button (i.e., when <a href="#widl-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>0</code>,
 							<a href="#widl-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>1</code>).
 							Secondary buttons (like the middle or right button on a standard mouse) MUST NOT fire
@@ -3260,7 +3260,7 @@
 							and after the event type <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> otherwise.
 							</p>
 
-						<p class="note"><strong>Note:</strong> As with the <code>click</code> event, the <code>dblclick</code> event
+						<p>As with the <code>click</code> event, the <code>dblclick</code> event
 							should only be fired for the primary pointer button.
 							Secondary buttons MUST NOT fire <code>dblclick</code> events.
 							</p>