Original text:
Group.  As noted in groups, this property is not entangled when Connections are cloned, i.e., changing the Priority on one Connection in a Connection Group does not change it on the other Connections in <del> the same Connection Group.  See priority-in-taps. </del>  7.1.3. 7.1.9.  The following generic Connection Properties are read-only, i.e. they cannot be changed by an application. <del> 7.1.9.1. </del>  zeroRttMsgMaxLen before or during Connection establishment, see also msg- safelyreplayable.  It is given in Bytes. <del> 7.1.9.2. </del>  singularTransmissionMsgMaxLen Packet Size (MPS) as described in Datagram PLPMTUD I-D.ietf-tsvwg- datagram-plpmtud. <del> 7.1.9.3. </del>  sendMsgMaxLen This property represents the maximum Message size that an application can send. <del> 7.1.9.4. </del>  recvMsgMaxLen the remote peer.  This boolean becomes false when "Timeout for aborting Connection" (see conn-timeout) is used. <del> 7.2.4. groupConnLimit Numeric (with special value "Unlimited") Unlimited This property controls the number of Connections that may arrive from a peer as new members of the Connection's group.  Similar to SetNewConnectionLimit(), this limits the number of ConnectionReceived Events that will occur, but constrained to the group of the Connection associated with this property.  In case of a multi- streaming transport, this takes the role of a limit on the number of allowed streams. </del> 7.3. During the lifetime of a connection there are events that can occur

Reviewer comments:
… and move the group limit connection property to the right place (it was misplaced). Note that section 8.2.7 ("Priority in TAPS") already clarifies that a Connection Priority choice doesn't guarantee a certain outcome; this just adds another sentence in the paragraph describing the Connection property to make it clearer (less easy to miss).
Looks ready to merge to me.

Revised text:
Group.  As noted in groups, this property is not entangled when Connections are cloned, i.e., changing the Priority on one Connection in a Connection Group does not change it on the other Connections in  <ins> the same Connection Group.  No guarantees of a specific behavior regarding Connection Priority are given; a transport system may ignore this property.  See priority-in-taps for more details. </ins> 7.1.3. 7.1.9. <ins> groupConnLimit Numeric (with special value "Unlimited") Unlimited This property controls the number of Connections that can be accepted from a peer as new members of the Connection's group.  Similar to SetNewConnectionLimit(), this limits the number of ConnectionReceived Events that will occur, but constrained to the group of the Connection associated with this property.  For a multi-streaming transport, this limits the number of allowed streams. 7.1.10. </ins> The following generic Connection Properties are read-only, i.e. they cannot be changed by an application.  <ins> 7.1.10.1. </ins> zeroRttMsgMaxLen before or during Connection establishment, see also msg- safelyreplayable.  It is given in Bytes.  <ins> 7.1.10.2. </ins> singularTransmissionMsgMaxLen Packet Size (MPS) as described in Datagram PLPMTUD I-D.ietf-tsvwg- datagram-plpmtud.  <ins> 7.1.10.3. </ins> sendMsgMaxLen This property represents the maximum Message size that an application can send.  <ins> 7.1.10.4. </ins> recvMsgMaxLen the remote peer.  This boolean becomes false when "Timeout for aborting Connection" (see conn-timeout) is used.  7.3. During the lifetime of a connection there are events that can occur