semantics, not syntax
avoid speculation about how/why we got where we are
Tweak introduction
extraneous 'd'
assigned -> associated
reword request to streams
properly -> efficiently
requests -> streams
We do not intend, we do or do not do.
level -> layer
to -> for
clarify that the server SETTINGS is the preface in the HTTP case
Clarify what "reject an attempt to upgrade" means;
reject if there are multiple headers.
We're shying away from calling things 'hop-by-hop' in HTTP/1
Massage text about the connection preface
Massage prior support caveat
"maintenance frames" only occurred once.
Explicitly draw equivalence to HTTP/1 header fields
"future improvements" -> "variety of flow control algorithms"
shy away from hop/e2e