Changeset 163 for draft-ietf-httpbis/latest/p5-range.html

Timestamp:

Jan 11, 2008, 9:09:10 PM (12 years ago)

Author:

fielding@…

Message:

editorial: make introductions more active and consistent

File:

• draft-ietf-httpbis/latest/p5-range.html (modified) (1 diff)

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

@@ -530 +530 @@
          to be rendered by a device with limited local storage.
       </p>
-      <p id="rfc.section.1.p.2">This document defines aspects of HTTP/1.1 related to range requests, partial responses, and the multipart/byteranges media
-         type. The protocol for range requests is an <em class="bcp14">OPTIONAL</em> feature of HTTP/1.1, designed so resources or recipients that do not implement this feature can respond as if it is a normal
-         GET request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken
-         for full responses by intermediate caches that might not implement the feature.
-      </p>
-      <p id="rfc.section.1.p.3">Although the HTTP/1.1 range request mechanism is designed to allow for extensible range types, this specification only defines
+      <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. The protocol for
+         range requests is an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so resources or recipients that do not implement this feature can respond as if it is a normal GET
+         request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
+         full responses by intermediate caches that might not implement the feature.
+      </p>
+      <p id="rfc.section.1.p.3">Although the HTTP range request mechanism is designed to allow for extensible range types, this specification only defines
          requests for byte ranges.
       </p>