Original text:
Preference, which is an Enumeration with five possible values: Prohibit, Avoid, Ignore, Prefer, or Require.  Each of these denotes a level of preference of a given property during protocol <del> selection.  (See selection-props.)  The Preference type is used only on Preconnections, and only for Selection Properties. </del>  3.3. Specify a Local Endpoint using a STUN server: <del> Specify a Local Endpoint using a Any-Source Multicast group to join </del>  on a named local interface: Source-Specific Multicast requires setting both a Local and Remote not be used for sending if the connection was created with the Selection Property "Direction of Communication" set to "unidirectional receive" or if a Message marked as "Final" was <del> sent over this connection.  See msg-final. </del>  Whether the connection can be used to receive data.  A connection cannot be used for reading if the connection was created with the Message (i.e., whether it has actually been transmitted, moved into a buffer on the network interface, moved into a kernel buffer, and so on) when the Sent Event occurs is implementation-specific.  The Sent <del> Event contains a reference to the Message to which it applies. </del>  Sent Events allow an application to obtain an understanding of the amount of buffering it creates.  That is, if an application calls the completion; i.e. when the Message was not sent before its Lifetime (see msg-lifetime) expired.  This is separate from SendError, as it is an expected behavior for partially reliable transports.  The <del> Expired Event contains a reference to the Message to which it applies. </del>  7.2.2.3. system and Protocol Stack to handle, some failure of the underlying Protocol Stack, or a set of Message Properties not consistent with the Connection's transport properties.  The SendError contains a <del> reference to the Message to which it applies. </del>  7.2.3. Each Message Context may contain metadata from protocols in the Protocol Stack; which metadata is available is Protocol Stack <del> dependent.  These are exposed though additional read-only Message </del>  Properties that can be queried from the MessageContext object (see msg-ctx) passed by the receive event.  The following metadata values are supported:

Reviewer comments:
Also spotted some further small nits while reviewing the document, will create a pull request for those.

Revised text:
Preference, which is an Enumeration with five possible values: Prohibit, Avoid, Ignore, Prefer, or Require.  Each of these denotes a level of preference of a given property during protocol  <ins> selection.  (See also selection-props.)  The Preference type is used only on Preconnections, and only for Selection Properties. </ins> 3.3. Specify a Local Endpoint using a STUN server:  <ins> Specify a Local Endpoint using an Any-Source Multicast group to join </ins> on a named local interface: Source-Specific Multicast requires setting both a Local and Remote not be used for sending if the connection was created with the Selection Property "Direction of Communication" set to "unidirectional receive" or if a Message marked as "Final" was  <ins> sent over this connection.  See also msg-final. </ins> Whether the connection can be used to receive data.  A connection cannot be used for reading if the connection was created with the Message (i.e., whether it has actually been transmitted, moved into a buffer on the network interface, moved into a kernel buffer, and so on) when the Sent Event occurs is implementation-specific.  The Sent  <ins> Event contains a reference to the Message Context of the Message to which it applies. </ins> Sent Events allow an application to obtain an understanding of the amount of buffering it creates.  That is, if an application calls the completion; i.e. when the Message was not sent before its Lifetime (see msg-lifetime) expired.  This is separate from SendError, as it is an expected behavior for partially reliable transports.  The  <ins> Expired Event contains a reference to the Message Context of the Message to which it applies. </ins> 7.2.2.3. system and Protocol Stack to handle, some failure of the underlying Protocol Stack, or a set of Message Properties not consistent with the Connection's transport properties.  The SendError contains a  <ins> reference to the Message Context of the Message to which it applies. </ins> 7.2.3. Each Message Context may contain metadata from protocols in the Protocol Stack; which metadata is available is Protocol Stack  <ins> dependent.  These are exposed through additional read-only Message </ins> Properties that can be queried from the MessageContext object (see msg-ctx) passed by the receive event.  The following metadata values are supported: