diff --git a/meetings/16-09-22TPAC-3.md b/meetings/16-09-22TPAC-3.md
index 04f5908..e34861f 100644
--- a/meetings/16-09-22TPAC-3.md
+++ b/meetings/16-09-22TPAC-3.md
@@ -24,8 +24,7 @@ This meeting will take place on 22 September 2016 as part of [TPAC 2016](https:/
 
 ## Agenda
 
-Input Events
-======
+### Input Events
 
 * Should we have an inputType for the spellchecker specifically? Previously we deicded to use a more general inputType for all possible spell- and grammarchechers which is now called insertNonText, but given that there are only spell checkers currently, it may be transport more information to use a new inputType like: "insertFromSpellcheck" [1]
 
@@ -37,8 +36,7 @@ Proposed solution: Add a method to this beforeinput event to revert the dom chan
 
 * Define "static range potentially affected by event" [5]. While  it's easy to intuitively understand what this means, it seems more difficult to define normatively what part of the DOM can be said to be "affected" [6]. Do we need a definition that makes sure that implementations don't differ, or is this not a realworld concern?
 
-Event order
-===
+#### Event order
 
 * Event order for drag/drop, history, clipboard: Should go into UI events spec? [7]
 
@@ -47,8 +45,7 @@ Event order
 * Anne van Kesteren proposes to move the prose about when the beforeinput/input events are fired into "n the specification that defines the action that causes the event to be dispatched. (UI events is rather bad in that it doesn't actually define actions, it just defines some events, some ordering between them, but nothing that amounts to a model.)" [9]
 
 
-Other issues
-======
+### Other issues
 
 * Format context menu on iOS/Safari, opt-in/out solution presentation of Apple's proposal. [10]
 
@@ -61,18 +58,31 @@ Other issues
 * Set virtual enter key text, presentation of Google's proposal. [14]
 
 [1] https://github.com/w3c/input-events/issues/31
+
 [2] https://github.com/w3c/input-events/issues/17#issuecomment-245739017
+
 [3] https://github.com/w3c/input-events/issues/17#issuecomment-246102307
+
 [4] https://github.com/w3c/input-events/issues/21
+
 [5] https://github.com/w3c/input-events/issues/5
+
 [6] https://github.com/w3c/input-events/issues/5#issuecomment-239940614
+
 [7] https://github.com/w3c/input-events/issues/22
+
 [8] https://github.com/w3c/input-events/issues/9
+
 [9] https://github.com/w3c/input-events/issues/9#issuecomment-239772551
+
 [10] https://github.com/w3c/editing/issues/141
+
 [11] https://github.com/w3c/editing/issues/132
+
 [12] https://github.com/w3c/editing/issues/145
+
 [13] https://github.com/w3c/csswg-drafts/issues/319
+
 [14] https://github.com/w3c/editing/issues/142
 
 Please add your name, and agenda requests here by [editing a branch and making a Pull Request](https://github.com/w3c/WebPlatformWG/edit/gh-pages/meetings/16-09-22TPAC-3.md), or by mail to either the public-webapps mailing list or the chairs of the Web Platform group, which will result in it being posted here.