Original text:
containing these properties can be passed to the Send Action.  For other uses of the message context, see msg-ctx. <del> Note that message properties are per-Message, not per-Send if partial </del>  Messages are sent (send-partial).  All data blocks associated with a single Message share properties specified in the Message Contexts. For example, it would not make sense to have the beginning of a This enumerated property specifies the application's preferred tradeoffs for sending this Message; it is a per-Message override of <del> the Capacity Profile protocol and path selection property (see prop- cap-profile). The following values are valid for Transmission Profile: No special optimizations of the tradeoff between delay, delay variation, and bandwidth efficiency should be made when sending this message. Response time (latency) should be optimized at the expense of efficiently using the available capacity when sending this message.  This can be used by the system to disable the coalescing of multiple small Messages into larger packets (Nagle's algorithm); to prefer immediate acknowledgment from the peer endpoint when supported by the underlying transport; to signal a preference for lower-latency, higher-loss treatment; and so on. [TODO: This is inconsistent with {prop-cap-profile}} - needs to be fixed] </del>  7.4.9. MessageContext object can be passed to the Send action and is retuned by each Send and Receive related events. <del> Message properties can be set and queried using the Message Context: </del>  To get or set Message Properties, the optional scope parameter is left empty, for framing meta-data, the framer is passed. all Connections are defined in the subsections below. Note that many protocol properties have a corresponding selection <del> property, which prefers protocols providing a specific transport feature that controlled by that protocol property.  [EDITOR'S NOTE: todo: add these cross-references up to selection-props] </del>  11.1.1.

Reviewer comments:
This also addresses two inline [EDITOR's NOTE] items. One was about the per-message override capacity profile being inconsistent with the other one; this was solved by removing details, such that the other one defines the possible choices. Another was about selection vs. connection properties, with broken text. There was no need to add the references as the editor's note says, I thought.
this LGTM, thanks!

Revised text:
containing these properties can be passed to the Send Action.  For other uses of the message context, see msg-ctx.  <ins> Note that Message Properties are per-Message, not per-Send if partial </ins> Messages are sent (send-partial).  All data blocks associated with a single Message share properties specified in the Message Contexts. For example, it would not make sense to have the beginning of a This enumerated property specifies the application's preferred tradeoffs for sending this Message; it is a per-Message override of  <ins> the Capacity Profile connection property (see prop-cap-profile). </ins> 7.4.9. MessageContext object can be passed to the Send action and is retuned by each Send and Receive related events.  <ins> Message Properties can be set and queried using the Message Context: </ins> To get or set Message Properties, the optional scope parameter is left empty, for framing meta-data, the framer is passed. all Connections are defined in the subsections below. Note that many protocol properties have a corresponding selection  <ins> property, which prefers protocols providing a supporting transport feature. </ins> 11.1.1.