Changeset 677 for draft-ietf-httpbis/latest/p1-messaging.html

Timestamp:

13/08/09 01:21:32 (13 years ago)

Author:

fielding@…

Message:

editorial: wordsmith description of messages

File:

• draft-ietf-httpbis/latest/p1-messaging.html (modified) (1 diff)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -856 +856 @@
       <div id="rfc.iref.r.2"></div>
       <p id="rfc.section.2.1.p.5">A client sends an HTTP request to the server in the form of a request message (<a href="#request" title="Request">Section&nbsp;4</a>), beginning with a method, URI, and protocol version, followed by MIME-like header fields containing request modifiers, client
-         information, and payload metadata, an empty line, and finally the payload body (if any). The server response (<a href="#response" title="Response">Section&nbsp;5</a>) begins with a status line, including the protocol version, a success or error code, and textual reason phrase, followed
-         by MIME-like header fields containing server information, resource metadata, payload metadata, an empty line, and finally
-         the payload body (if any).
-      </p>
-      <p id="rfc.section.2.1.p.6">The following example illustrates a typical message exchange for a GET request on the URI "http://www.example.com/hello.txt":</p>
+         information, and payload metadata, an empty line to indicate the end of the header section, and finally the payload body (if
+         any).
+      </p>
+      <p id="rfc.section.2.1.p.6">A server responds to the client's request by sending an HTTP response message (<a href="#response" title="Response">Section&nbsp;5</a>), beginning with a status line that includes the protocol version, a success or error code, and textual reason phrase, followed
+         by MIME-like header fields containing server information, resource metadata, and payload metadata, an empty line to indicate
+         the end of the header section, and finally the payload body (if any).
+      </p>
+      <p id="rfc.section.2.1.p.7">The following example illustrates a typical message exchange for a GET request on the URI "http://www.example.com/hello.txt":</p>
       <div id="rfc.figure.u.13"></div>
       <p>client request:</p><pre class="text2">GET /hello.txt HTTP/1.1