Changeset 1544 for draft-ietf-httpbis/latest/p5-range.xml

Timestamp:

21/02/12 02:12:49 (10 years ago)

Author:

fielding@…

Message:

For consistency and readability, do not hyphenate "message body"
unless we are referring to the message-body ABNF rule.

File:

• draft-ietf-httpbis/latest/p5-range.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p5-range.xml

@@ -416 +416 @@
         Content-Length header field is present in the response, its
         value &MUST; match the actual number of octets transmitted in the
-        message-body.
+        message body.
     </t>
     <t>
@@ -556 +556 @@
 </t>
 <t>
-   The combined response message-body consists of the union of partial
+   The combined response message body consists of the union of partial
    content ranges in the new response and each of the selected responses.
    If the union consists of the entire range of the representation, then the
@@ -786 +786 @@
 <t>
    Byte range specifications in HTTP apply to the sequence of bytes in
-   the representation body (not necessarily the same as the message-body).
+   the representation body (not necessarily the same as the message body).
 </t>
 <t anchor="rule.ranges-specifier">
@@ -1409 +1409 @@
    content of multiple ranges (a response to a request for multiple
    non-overlapping ranges), these are transmitted as a multipart
-   message-body (<xref target="RFC2046" x:fmt="," x:sec="5.1"/>). The media type for this purpose is called
+   message body (<xref target="RFC2046" x:fmt="," x:sec="5.1"/>). The media type for this purpose is called
    "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
 </t>