Fix list construction for frame size error

Closes httpwg#1030.

draft-ietf-httpbis-http2bis.xml

@@ -491,13 +491,17 @@ HTTP Frame {
  </t>
  </aside>
  <t>
- An endpoint MUST send an error code of <xref target="FRAME_SIZE_ERROR" format="none">FRAME_SIZE_ERROR</xref> if a frame exceeds the size
- defined in <xref target="SETTINGS_MAX_FRAME_SIZE" format="none">SETTINGS_MAX_FRAME_SIZE</xref>, exceeds any limit defined for the frame type,
- or is too small to contain mandatory frame data. A frame size error in a frame that
- could alter the state of the entire connection MUST be treated as a <xref target="ConnectionErrorHandler">connection error</xref>; this includes any frame carrying
- a <xref target="FieldBlock">field block</xref> (that is, <xref target="HEADERS" format="none">HEADERS</xref>,
- <xref target="PUSH_PROMISE" format="none">PUSH_PROMISE</xref>, and <xref target="CONTINUATION" format="none">CONTINUATION</xref>), <xref target="SETTINGS" format="none">SETTINGS</xref>,
- and any frame with a stream identifier of 0.
+ An endpoint MUST send an error code of <xref target="FRAME_SIZE_ERROR"
+ format="none">FRAME_SIZE_ERROR</xref> if a frame exceeds the size defined in <xref
+ target="SETTINGS_MAX_FRAME_SIZE" format="none">SETTINGS_MAX_FRAME_SIZE</xref>, exceeds any
+ limit defined for the frame type, or is too small to contain mandatory frame data. A frame
+ size error in a frame that could alter the state of the entire connection MUST be treated
+ as a <xref target="ConnectionErrorHandler">connection error</xref>; this includes any
+ frame carrying a <xref target="FieldBlock">field block</xref> (that is, <xref
+ target="HEADERS" format="none">HEADERS</xref>, <xref target="PUSH_PROMISE"
+ format="none">PUSH_PROMISE</xref>, and <xref target="CONTINUATION"
+ format="none">CONTINUATION</xref>), a <xref target="SETTINGS"
+ format="none">SETTINGS</xref> frame, and any frame with a stream identifier of 0.
  </t>
  <t>
  Endpoints are not obligated to use all available space in a frame. Responsiveness can be