bcp56bis: Status code reason phrase

Port over of PR from mnot repo. Modified last sentence to avoid to much usage of the word "further".
httpwg · Feb 2, 2018 · a1621c7 · a1621c7
1 parent c091c51
commit a1621c7
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/draft-ietf-httpbis-bcp56bis.md b/draft-ietf-httpbis-bcp56bis.md
@@ -383,9 +383,9 @@ application is harmful, as these are not generic semantics, since the consumer n
 context of the application to understand them.
 
 Furthermore, applications using HTTP MUST NOT re-specify the semantics of HTTP status codes, even
-if it is only by copying their definition. They MUST NOT require specific status phrases to be
-used; the status phrase has no function in HTTP, and is not guaranteed to be preserved by
-implementations.
+if it is only by copying their definition. They MUST NOT require specific reason phrases to be
+used; the reason phrase has no function in HTTP, and is not guaranteed to be preserved by
+implementations. The reason phrase is not carried in the {{RFC7540}} message format.
 
 Typically, applications using HTTP will convey application-specific information in the message body
 and/or HTTP header fields, not the status code.