diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md
index 3a49c3aa0f..a9da903deb 100644
--- a/draft-ietf-quic-transport.md
+++ b/draft-ietf-quic-transport.md
@@ -95,19 +95,10 @@ informative:
 
 --- abstract
 
-QUIC is a multiplexed and secure transport protocol that runs on top of UDP.
-QUIC builds on past transport experience, and implements mechanisms that make it
-useful as a modern general-purpose transport protocol.  Using UDP as the basis
-of QUIC is intended to address compatibility issues with legacy clients and
-middleboxes.  QUIC authenticates all of its headers, preventing third parties
-from changing them.  QUIC encrypts most of its headers, thereby limiting
-protocol evolution to QUIC endpoints only.  Therefore, middleboxes, in large
-part, are not required to be updated as new protocol versions are deployed.
-This document describes the core QUIC protocol, including the conceptual design,
-wire format, and mechanisms of the QUIC protocol for connection establishment,
-stream multiplexing, stream and connection-level flow control, and data
-reliability.  Accompanying documents describe QUIC's loss recovery and
-congestion control, and the use of TLS 1.3 for key negotiation.
+This document defines the core of the QUIC transport protocol.  This document
+describes connection establishment, packet format, multiplexing and reliability.
+Accompanying documents describe the cryptographic handshake and loss detection.
+
 
 --- note_Note_to_Readers
 
@@ -124,19 +115,23 @@ code and issues list for this draft can be found at
 # Introduction
 
 QUIC is a multiplexed and secure transport protocol that runs on top of UDP.
-QUIC builds on past transport experience and implements mechanisms that make it
-useful as a modern general-purpose transport protocol.  Using UDP as the
-substrate, QUIC seeks to be compatible with legacy clients and middleboxes.
-QUIC authenticates all of its headers, preventing middleboxes and other third
-parties from changing them, and encrypts most of its headers, limiting protocol
-evolution largely to QUIC endpoints only.
+QUIC aims to provide a flexible set of features that allow it to be a
+general-purpose transport for multiple applications.
+
+QUIC implements techniques learned from experience with TCP, SCTP and other
+transport protocols.  Using UDP as the substrate, QUIC seeks to be compatible
+with legacy clients and middleboxes.  QUIC authenticates all of its headers and
+encrypts most of the data it exchanges, including its signaling.  This allows
+the protocol to evolve without incurring a dependency on upgrades to
+middleboxes.
 
 This document describes the core QUIC protocol, including the conceptual design,
 wire format, and mechanisms of the QUIC protocol for connection establishment,
 stream multiplexing, stream and connection-level flow control, and data
-reliability.  Accompanying documents describe QUIC's loss detection and
-congestion control {{QUIC-RECOVERY}}, and the use of TLS 1.3 for key negotiation
-{{QUIC-TLS}}.
+reliability.
+
+Accompanying documents describe QUIC's loss detection and congestion control
+{{QUIC-RECOVERY}}, and the use of TLS 1.3 for key negotiation {{QUIC-TLS}}.
 
 
 # Conventions and Definitions