big reshuffle:

drafts/definitions.rst

@@ -5,15 +5,15 @@ Definitions
 
 # *Event* -- A JSON object that represents a piece of information to be
 distributed to the the room. The object includes a payload and metadata,
-including a `type` used to indicate what the payload is for and how to process
+including a ``type`` used to indicate what the payload is for and how to process
 them. It also includes one or more references to previous events.
 
 # *Event graph* -- Events and their references to previous events form a
 directed acyclic graph. All events must be a descendant of the first event in a
 room, except for a few special circumstances.
 
 # *State event* -- A state event is an event that has a non-null string valued
-`state_key` field. It may also include a `prev_state` key referencing exactly
+`state_key` field. It may also include a ``prev_state`` key referencing exactly
 one state event with the same type and state key, in the same event graph.
 
 # *State tree* -- A state tree is a tree formed by a collection of state events

drafts/erik-model.rst

@@ -1,4 +1,7 @@
-This is a standalone description of the data architecture of Synapse.  There is a lot of overlap with the currennt specification, so it has been split out here for posterity.  Hopefully all the important bits have been merged into the relevant places in the main spec.
+This is a standalone description of the data architecture of Synapse. There is a
+lot of overlap with the current specification, so it has been split out here for
+posterity. Hopefully all the important bits have been merged into the relevant
+places in the main spec.
 
 
 Model

drafts/general_api.rst

@@ -555,7 +555,7 @@ signature. Requesting the "raw" federation event will have to return these keys.
 
 Account Management API ``[Draft]``
 ----------------------------------
-The registration and login APIs in v2 do not support specifying device IDs. In v2,
+The registration and login APIs in v1 do not support specifying device IDs. In v2,
 this will become *mandatory* when sending your initial request. Access tokens will
 be scoped per device, so using the same device ID twice when logging in will 
 clobber the old access token.
@@ -810,6 +810,11 @@ Notes:
 
 Presence API ``[Draft]``
 ------------------------
+
+.. FIXME
+  this seems to be ignoring activity timers entirely, which were present on
+  the planning etherpad and are present in the actual HTTP API. Needs attention.
+
 The goals of presence are to:
 
 - Let other users know if someone is "online".

drafts/object_model.rst

@@ -1,6 +1,5 @@
-
-
-
+..TODO
+  What are the start & end tokens doing here?!
 
 ::
 

scripts/gendoc.py

@@ -101,6 +101,7 @@ def prepare_env():
         pass
 
 def cleanup_env():
+    #pass
     shutil.rmtree("./tmp")
 
 def main():