diff --git a/draft-ietf-tsvwg-rfc4960-bis.xml b/draft-ietf-tsvwg-rfc4960-bis.xml
index fb80fa1..b9a7e64 100644
--- a/draft-ietf-tsvwg-rfc4960-bis.xml
+++ b/draft-ietf-tsvwg-rfc4960-bis.xml
@@ -146,7 +146,7 @@ as SYN attacks.</t></li>
 for which all of these limitations of TCP are relevant.
 While this application directly motivated the development of SCTP, other
 applications might find SCTP a good match to their requirements.
-One example for this are datachannels in the WebRTC infrastructure.</t>
+One example of this is the use of data channels in the WebRTC infrastructure.</t>
 </section>
 
 <section>
@@ -217,7 +217,7 @@ addresses.</t>
 </dd>
 <dt>Bundling:</dt>
 <dd>
-<t>An optional multiplexing operation, whereby more than one user message can
+<t>An optional multiplexing operation, whereby more than one user or control message can
 be carried in the same SCTP packet.
 Each user message occupies its own DATA chunk.</t>
 </dd>
@@ -244,7 +244,7 @@ the Cumulative TSN Ack field of a SACK chunk.</t>
 </dd>
 <dt>Flightsize:</dt>
 <dd>
-<t>The amount of bytes of outstanding data to a particular destination transport
+<t>The number of bytes of outstanding data to a particular destination transport
 address at any given time.</t>
 </dd>
 <dt>Idle destination address:</dt>
@@ -272,7 +272,7 @@ messages sent within the stream on which the message was sent.</t>
 </dd>
 <dt>Outstanding data (or "data outstanding" or "data in flight"):</dt>
 <dd>
-<t>The total amount of the DATA chunks associated with outstanding TSNs.
+<t>The total size of the DATA chunks associated with outstanding TSNs.
 A retransmitted DATA chunk is counted once in outstanding data.
 A DATA chunk that is classified as lost but that has not yet been
 retransmitted is not in outstanding data.</t>
@@ -382,7 +382,7 @@ correlations if they are so desired.</t>
 <dd>
 <t>A 16-bit sequence number used internally by SCTP to ensure sequenced delivery
 of the user messages within a given stream.
-One Stream Sequence Number is attached to each user message.</t>
+One Stream Sequence Number is attached to each (ordered) user message.</t>
 </dd>
 <dt>Tie-Tags:</dt>
 <dd>
@@ -699,7 +699,7 @@ have been incorporated in this document:</t>
 <li><t>Describe the packet size handling more precise by introducing PMTU,
        PMDCS and AMDCS.</t></li>
 <li><t>Add the definition of control chunk.</t></li>
-<li><t>Improve the description of the handling of INIT chunks with invalid
+<li><t>Improve the description of the handling of INIT and INIT ACK chunks with invalid
        mandatory parameters.</t></li>
 <li><t>Allow using L > 1 for Appropriate Byte Counting (ABC) during
        slow start.</t></li>
@@ -708,7 +708,7 @@ have been incorporated in this document:</t>
 <li><t>Improve the terminology to make clear that this specification does not
        describe a full mesh architecture.</t></li>
 <li><t>Improve the description of sequence number generation
-       (TSN and SSN).</t></li>
+       (TSN and Stream Sequence Number).</t></li>
 <li><t>Improve the description of reneging.</t></li>
 <li><t>Don't require the change of the cumulative TSN ACK anymore for increasing
        the congestion window.
@@ -740,7 +740,7 @@ A chunk contains either control information or user data.</t>
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 </artwork>
 <t>INIT, INIT ACK and SHUTDOWN COMPLETE chunks MUST NOT be bundled
-into one SCTP packet.
+with any other chunks into an SCTP packet.
 All other chunks MAY be bundled to form an SCTP packet that does not exceed
 the PMTU.
 See <xref target='sec_bundling'/> for more details on chunk bundling.</t>
@@ -899,7 +899,7 @@ Chunk Flags, Chunk Length, and Chunk Value fields.
 Therefore, if the Chunk Value field is zero-length, the Length field will be
 set to 4.
 The Chunk Length field does not count any chunk padding.
-However, it does include padding of any variable-length parameter except the
+However, it does include any padding of variable-length parameters other than the
 last parameter in the chunk.</t>
 <t>Note: A robust implementation is expected to accept the chunk whether or not
 the final padding has been included in the Chunk Length.</t>
@@ -1021,9 +1021,10 @@ parameters and has to report them according to
 <xref target='sec_parameter_format'/>, it SHOULD bundle the ERROR chunk
 containing the "Unrecognized Parameters" error cause with the chunk sent
 in response (e.g., COOKIE ECHO).
-If the receiver of the INIT ACK chunk cannot bundle the COOKIE ECHO chunk with
-the ERROR chunk, the ERROR chunk MAY be sent separately but not before the
-COOKIE ACK chunk has been received.</t>
+If the receiver of the chunk with unrecognized parameters cannot bundle the
+ERROR chunk with the chunk sent in response,
+the ERROR chunk MAY be sent separately but not before the
+chunk sent in response has been received.</t>
 <t>Any time a COOKIE ECHO chunk is sent in a packet, it MUST be the first
 chunk.</t>
 </section>
@@ -1242,7 +1243,7 @@ to the INIT chunk.</t>
 <t>The Chunk Flags field in INIT chunks is reserved, and all bits in it SHOULD
 be set to 0 by the sender and ignored by the receiver.
 The sequence of parameters within an INIT chunk can be processed in any
-order.</t>
+order (but must appear within the chunk in the order indicated above).</t>
 <dl newline="true">
 <dt>Initiate Tag: 32 bits (unsigned integer)</dt>
 <dd>
@@ -1275,8 +1276,8 @@ however, an endpoint MAY change the value of a_rwnd it sends in SACK chunks.</t>
 to create in this association.
 The value of 0 MUST NOT be used.</t>
 <t>A receiver of an INIT chunk with the OS value set to 0 MUST discard the
-packet, SHOULD send a packet in response containing an ABORT chunk and using
-the Initiate Tag as the Verification Tag, and MUST NOT change the state of any
+packet, SHOULD send a packet in response containing an ABORT chunk with the
+T bit set, and MUST NOT change the state of any
 existing association.</t>
 </dd>
 <dt>Number of Inbound Streams (MIS): 16 bits (unsigned integer)</dt>
@@ -1288,8 +1289,8 @@ The value 0 MUST NOT be used.</t>
 two endpoints will use the min(requested, offered).
 See <xref target='sec_handle_stream_parameters'/> for details.</t>
 <t>A receiver of an INIT chunk with the MIS value set to 0 MUST discard the
-packet, SHOULD send a packet in response containing an ABORT chunk and using
-the Initiate Tag as the Verification Tag, and MUST NOT change the state of any
+packet, SHOULD send a packet in response containing an ABORT chunk with the
+T bit set, and MUST NOT change the state of any
 existing association.</t>
 </dd>
 <dt>Initial TSN (I-TSN): 32 bits (unsigned integer)</dt>
@@ -1377,8 +1378,8 @@ Address Translation (NAT).</t>
 
 <section>
 <name>Cookie Preservative (9)</name>
-<t>The sender of the INIT chunk SHOULD use this parameter to suggest to the
-receiver of the INIT chunk for a longer life-span of the State Cookie.</t>
+<t>The sender of the INIT chunk uses this parameter to suggest to the
+receiver of the INIT chunk a longer life-span for the State Cookie.</t>
 <artwork align='center'>
  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
@@ -1904,7 +1905,7 @@ chunk (see <xref target='sec_heartbeat_ack_chunk'/>).
 Note also that the HEARTBEAT chunk is both for reachability checking and for
 path verification (see <xref target='sec_path_verifiation'/>).
 When a HEARTBEAT chunk is being used for path verification purposes, it MUST
-hold a random nonce of length 64-bit or longer (<xref target='RFC4086'/>
+include a random nonce of length 64-bit or longer (<xref target='RFC4086'/>
 provides some information on randomness guidelines).</t>
 </dd>
 </dl>
@@ -3110,8 +3111,8 @@ respond with an INIT ACK chunk using the same parameters it sent in its
 original INIT chunk (including its Initiate Tag, unchanged), provided
 that no NEW address has been added to the forming association.
 If the INIT chunk indicates that a new address has been added to the
-association, then the entire INIT chunk MUST be discarded, and SHOULD NOT do any
-changes to the existing association.
+association, then the entire INIT chunk MUST be discarded, and SHOULD NOT
+change the state of any existing association.
 An ABORT chunk SHOULD be sent in response that MAY include the error
 'Restart of an association with new addresses'.
 The error SHOULD list the addresses that were added to the restarting
@@ -4433,7 +4434,7 @@ transmission.</t></li>
 the destination addresses it can send to (not each source-destination pair but
 for each destination).
 The parameters SHOULD decay if the address is not used for a long enough time
-period. <xref target='RFC5681'/> specifies this long enough time as a
+period. <xref target='RFC5681'/> specifies this "long enough time" as a
 retransmission timeout.</t></li>
 <li><t>For each of the destination addresses, an endpoint does slow start upon
 the first transmission to that address.</t></li>
@@ -6480,7 +6481,7 @@ clear this flag.</t>
 <dt>last-time:</dt>
 <dd>
 <t>The time to which this destination was last sent.
-This can be to determine if the sending of a HEARTBEAT chunk is needed.</t>
+This can be used to determine if the sending of a HEARTBEAT chunk is needed.</t>
 </dd>
 </dl>
 </section>