Changeset 758 for draft-ietf-httpbis/latest

Timestamp:

08/02/10 16:19:43 (11 years ago)

Author:

julian.reschke@…

Message:

lang/grammar

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (2 diffs)
• p2-semantics.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -910 +910 @@
       <p id="rfc.section.6.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
       <p id="rfc.section.6.1.p.3">In the common case, an HTTP response is a representation of the resource located at the request-URI. However, this is not
-         always the case. To determine the URI of the resource a response is associated with, the following rules are used (first match
-         winning):
+         always the case. To determine the URI of the resource a response is associated with, the following rules are used (with the
+         first applicable one being selected):
       </p>
       <ol>
@@ -1152 +1152 @@
       <div id="rfc.iref.s.5"></div>
       <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
-      <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced
+      <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and has resulted in a new resource being created. The newly created resource can be referenced
          by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header
          field. The response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -672 +672 @@
    located at the request-URI. However, this is not always the case. To
    determine the URI of the resource a response is associated with, the
-   following rules are used (first match winning):
+   following rules are used (with the first applicable one being selected):
 </t>
 <t><list style="numbers">
@@ -1170 +1170 @@
   <iref primary="true" item="Status Codes" subitem="201 Created" x:for-anchor=""/>
 <t>
-   The request has been fulfilled and resulted in a new resource being
+   The request has been fulfilled and has resulted in a new resource being
    created. The newly created resource can be referenced by the URI(s)
    returned in the entity of the response, with the most specific URI