Move each event type into its own section

build.py

@@ -257,7 +257,6 @@ def process_main_spec():
 		'conventions',
 		'architecture',
 		'event-interfaces',
-		'event-types',
 		'event-uievent',
 		'event-focusevent',
 		'event-mouseevent',

index.bs

@@ -116,10 +116,6 @@ path: sections/event-interfaces.include
 </pre>
 
 <!-- Event Types =========================================================== -->
-<section>
-<pre class="include">
-path: sections/event-types.include
-</pre>
 <pre class="include">
 path: sections/event-uievent.include
 </pre>
@@ -141,7 +137,6 @@ path: sections/event-keyboardevent.include
 <pre class="include">
 path: sections/event-compositionevent.include
 </pre>
-</section>
 
 <!-- Keyboard and key values =============================================== -->
 <pre class="include">

sections/event-compositionevent.txt

@@ -1,3 +1,4 @@
+<section>
 <h3 id="events-compositionevents">Composition Events</h3>
 
 	Composition Events provide a means for inputing text in a supplementary or
@@ -343,3 +344,4 @@
 			is closed, minimized, switched out of focus, or otherwise dismissed,
 			and the focus switched back to the <a>user agent</a>).
 
+</section>

sections/event-focusevent.txt

@@ -1,3 +1,4 @@
+<section>
 <h3 id="events-focusevent">Focus Events</h3>
 
 	<p class="note">
@@ -251,3 +252,4 @@
 			focus. The [=blur=] event MUST fire before the dispatch of this event
 			type. This event type is similar to [=blur=], but does bubble.
 
+</section>

sections/event-inputevent.txt

@@ -1,3 +1,4 @@
+<section>
 <h3 id="events-inputevents">Input Events</h3>
 
 	Input events are sent as notifications whenever the DOM is being updated (or about
@@ -166,3 +167,4 @@
 			DOM has been updated.
 
 
+</section>

sections/event-keyboardevent.txt

@@ -1,3 +1,4 @@
+<section>
 <h3 id="events-keyboardevents">Keyboard Events</h3>
 
 	Keyboard events are device dependent, i.e., they rely on the capabilities of
@@ -593,3 +594,4 @@
 			<a>character value</a>.
 			</p>
 
+</section>

sections/event-mouseevent.txt

@@ -1,3 +1,4 @@
+<section>
 <h3 id="events-mouseevents">Mouse Events</h3>
 
 	The mouse event module originates from the [[HTML401]] <code>onclick</code>,
@@ -2012,3 +2013,4 @@ myDiv.addEventListener("auxclick", function(e) {
 			drag operation with a mouse button pressed.
 			</p>
 
+</section>

sections/event-uievent.txt

@@ -1,3 +1,4 @@
+<section>
 <h3 id="events-uievents">User Interface Events</h3>
 
 	The User Interface event module contains basic event types associated with
@@ -271,3 +272,4 @@
 			controls, or image or markup selections such as in SVG.
 			</p>
 
+</section>

sections/event-wheelevent.txt

@@ -1,3 +1,4 @@
+<section>
 <h3 id="events-wheelevents">Wheel Events</h3>
 
 	Wheels are devices that can be rotated in one or more spatial dimensions, and which can be associated with a pointer device. The coordinate system depends on the
@@ -308,3 +309,4 @@
 			</p>
 
 
+</section>

sections/glossary.txt

@@ -225,8 +225,8 @@ the definitions for more information.
 	characteristics which distinguish it from other event types.  For example,
 	the EVENT{click} event type has different characteristics than the
 	EVENT{mouseover} or EVENT{load} event types. The event type is exposed as
-	the {{Event/type}} attribute on the event object.  See [[#event-types]] for
-	more details.  Also loosely referred to as <em>"event"</em>, such as the
+	the {{Event/type}} attribute on the event object.
+	Also loosely referred to as <em>"event"</em>, such as the
 	<em>EVENT{click} event</em>.
 
 : <dfn>fire</dfn>

sections/introduction.txt

@@ -76,7 +76,7 @@
         type</a> have been met.
 
         A browser conforms specifically to UI Events if it implements the
-        interfaces and related <a>event types</a> specified in [[#event-types]].
+        interfaces and related <a>event types</a> specified in this document.
 
         A conforming browser MUST support scripting, declarative interactivity,
         or some other means of detecting and dispatching events in the manner
@@ -147,7 +147,7 @@
 
         A specification or <a>host language</a> conforms specifically to UI
         Events if it references and uses the interfaces and related <a>event
-        types</a> specified in [[#event-types]]. A conforming specification MAY
+        types</a> specified in this document. A conforming specification MAY
         define additional interfaces and <a>event types</a> appropriate to that
         specification, or MAY extend the UI Events interfaces and <a>event
         types</a> in a manner that does not contradict or conflict with the