Editorial tweak

draft-ietf-httpbis-http2.xml

@@ -3660,15 +3660,15 @@ HTTP2-Settings    = token68
 
         <section title="TLS 1.2 Features">
           <t>
-            The TLS 1.2 implementation MUST disable compression.  TLS compression can lead to the
-            exposure of information that would not otherwise be revealed <xref target="RFC3749"/>.
-            Generic compression is unnecessary since HTTP/2 provides compression features that are
-            more aware of context and therefore likely to be more appropriate for use for
-            performance, security or other reasons.
+            TLS record compression MUST be disabled.  TLS compression can lead to the exposure of
+            information that would not otherwise be revealed <xref target="RFC3749"/>.  Generic
+            compression is unnecessary since HTTP/2 provides compression features that are more
+            aware of context and therefore likely to be more appropriate for use for performance,
+            security or other reasons.
           </t>
           <t>
-            The TLS 1.2 implementation MUST disable renegotiation.  An endpoint MUST treat a TLS
-            renegotiation as a <xref target="ConnectionErrorHandler">connection error</xref> of type
+            TLS renegotiation MUST be disabled.  An endpoint MUST treat a TLS renegotiation as a
+            <xref target="ConnectionErrorHandler">connection error</xref> of type
             <x:ref>PROTOCOL_ERROR</x:ref>.  Note that disabling renegotiation can result in
             long-lived connections becoming unusable due to limits on the number of messages the
             underlying cipher suite can encipher.
@@ -3717,10 +3717,10 @@ HTTP2-Settings    = token68
           <t>
             Clients MAY advertise support of cipher suites that are prohibited by the above
             restrictions in order to allow for connection to servers that do not support HTTP/2.
-            This enables a fallback to protocols without these constraints without the additional
-            latency imposed by using a separate connection for fallback.  Clients that offer suites
-            that are not valid for use in HTTP/2 SHOULD place all valid cipher suites before any
-            invalid suites in the TLS ClientHello.
+            This enables a fallback to protocols that don't have these constraints without the
+            additional latency imposed by using a separate connection for fallback.  Clients that
+            offer suites that are not valid for use in HTTP/2 SHOULD place all valid cipher suites
+            before any invalid suites in the TLS ClientHello.
           </t>
         </section>
       </section>