Original text:
requests with a Stream ID greater than or equal to the identifier received in a GOAWAY frame, those requests will not be processed. Clients can safely retry unprocessed requests on a different <del> connection. </del>  Requests on Stream IDs less than the Stream ID in a GOAWAY frame from the server might have been processed; their status cannot be server started to process that POST request if the server does not send a GOAWAY frame to indicate what streams it might have acted on. <del> A client that is unable to retry requests loses all requests that are in flight when the server closes the connection.  An endpoint MAY send multiple GOAWAY frames indicating different identifiers, but the identifier in each frame MUST NOT be greater than the identifier in any previous frame, since clients might already have retried unprocessed requests on another connection.  Receiving a GOAWAY containing a larger identifier than previously received MUST be treated as a connection error of type H3_ID_ERROR. </del>  An endpoint that is attempting to gracefully shut down a connection can send a GOAWAY frame with a value set to the maximum possible see frame-max-push-id.  A smaller value indicates the client will reject pushes with Push IDs greater than or equal to this value. Like the server, the client MAY send subsequent GOAWAY frames so long <del> as the specified Push ID is strictly smaller than all previously sent values. </del>  Even when a GOAWAY indicates that a given request or push will not be processed or accepted upon receipt, the underlying transport

Reviewer comments:
Move "A client that is unable to retry requests [...]" sentence from the beginning of an entirely unrelated paragraph to somewhere more appropriate. Change Push ID requirement on subsequent GOAWAY frames. This was presumably an oversight, because "An endpoint MAY send multiple GOAWAY frames indicating different identifiers [...]" paragraph above is pretty clear and covers both directions already.

Revised text:
requests with a Stream ID greater than or equal to the identifier received in a GOAWAY frame, those requests will not be processed. Clients can safely retry unprocessed requests on a different  <ins> connection.  A client that is unable to retry requests loses all requests that are in flight when the server closes the connection. </ins> Requests on Stream IDs less than the Stream ID in a GOAWAY frame from the server might have been processed; their status cannot be server started to process that POST request if the server does not send a GOAWAY frame to indicate what streams it might have acted on.  <ins> An endpoint MAY send multiple GOAWAY frames indicating different identifiers, but the identifier in each frame MUST NOT be greater than the identifier in any previous frame, since clients might already have retried unprocessed requests on another connection. Receiving a GOAWAY containing a larger identifier than previously received MUST be treated as a connection error of type H3_ID_ERROR. </ins> An endpoint that is attempting to gracefully shut down a connection can send a GOAWAY frame with a value set to the maximum possible see frame-max-push-id.  A smaller value indicates the client will reject pushes with Push IDs greater than or equal to this value. Like the server, the client MAY send subsequent GOAWAY frames so long  <ins> as the specified Push ID is no greater than any previously sent value. </ins> Even when a GOAWAY indicates that a given request or push will not be processed or accepted upon receipt, the underlying transport