Change:
exhaustive, but gives the top-level categories of events.  The API may expand this list. <del> Connection Ready A Connection Ready event signals to an application that a given Connection is ready to send and/or receive Content.  If the Connection relies on handshakes to establish state between peers, then it is assumed that these steps have been taken. Connection Finished A Connection Finished event signals to an application that a given Connection is no longer usable for sending or receiving Content.  This should deliver a useful error to the application. Connection Received A Connection Received event signals to an application that a given Listener has passively received a Connection. Content Received A Content Received event delivers received content to the application, based on a Receive action.  This may include an error if the action failed. Content Sent A Content Sent event notifies the application of the status of its Send action.  This may be an error, an indication that Content has been processed by the protocol stack, or potentially [MICHAEL: Why "potentially" - because you're not sure about it?  If it may be such an indication, "potentially" should be removed (this seems like the right thing to do for me).] an indication that Content has been acknowledged by a peer. Path Properties Changed A Path Properties Changed event notifies the application that some property of the Connection has changed that may influence how and where data is sent and/or received. </del> <ins> Connection Ready: A Connection Ready event signals to an application that a given Connection is ready to send and/or receive Content.  If the Connection relies on handshakes to establish state between peers, then it is assumed that these steps have been taken. Connection Finished: A Connection Finished event signals to an application that a given Connection is no longer usable for sending or receiving Content.  This should deliver a useful error to the application. Connection Received: A Connection Received event signals to an application that a given Listener has passively received a Connection. Content Received: A Content Received event delivers received content to the application, based on a Receive action.  This may include an error if the action failed. Content Sent: A Content Sent event notifies the application of the status of its Send action.  This may be an error, an indication that Content has been processed by the protocol stack, or potentially [MICHAEL: Why "potentially" - because you're not sure about it?  If it may be such an indication, "potentially" should be removed (this seems like the right thing to do for me).] an indication that Content has been acknowledged by a peer. Path Properties Changed: A Path Properties Changed event notifies the application that some property of the Connection has changed that may influence how and where data is sent and/or received. </ins> 4.1.6. <del> Close </del> <ins> Close() is the action an application may take on a Connection to indicate that it no longer intends to send data, is no longer willing to receive data, and that the protocol should signal this state to the remote endpoint if applicable. </ins> <del> Close is the action an application may take on a Connection to indicate that it no longer intends to send data, is no longer willing to receive data, and that the protocol should signal this state to the remote endpoint if applicable. Abort Abort is an action the application may take on a Connection to indicate a Close, but with the additional indication that the transport system should not attempt to deliver any outstanding data. </del> <ins> Abort() is an action the application may take on a Connection to indicate a Close, but with the additional indication that the transport system should not attempt to deliver any outstanding data. </ins> 4.2.

Discussion:
Incorporate Preconnection into the architecture and API draft.
Looks good. I pushed a commit to complete the change of the list style to include the implementation concepts section.