fix missing bad

draft-ietf-quic-http.md

@@ -865,7 +865,7 @@ unnecessarily limit parallelism.
 These streams carry frames related to the request/response (see
 {{request-response}}). When a stream terminates cleanly, if the last frame on
 the stream was truncated, this MUST be treated as a connection error (see
-HTTP_BAD_FRAME_SIZE in {{http-error-codes}}).  Streams which terminate abruptly
+HTTP_FRAME_SIZE_ERROR in {{http-error-codes}}).  Streams which terminate abruptly
 may be reset at any point in the frame.
 
 HTTP/3 does not use server-initiated bidirectional streams; clients MUST omit or
@@ -1040,7 +1040,7 @@ Each frame's payload MUST contain exactly the fields identified in its
 description.  A frame payload that contains additional bytes after the
 identified fields or a frame payload that terminates before the end of the
 identified fields MUST be treated as a connection error of type
-HTTP_BAD_FRAME_SIZE.
+HTTP_FRAME_SIZE_ERROR.
 
 ## Frame Definitions {#frames}