Changeset 697 for draft-ietf-httpbis/latest/p3-payload.xml

Timestamp:

25/09/09 14:43:16 (13 years ago)

Author:

julian.reschke@…

Message:

editorial: rephrase header introductions ("the *-header field 'foobar'" -> "the "foobar" *-header field")

File:

• draft-ietf-httpbis/latest/p3-payload.xml (modified) (10 diffs)

draft-ietf-httpbis/latest/p3-payload.xml

@@ -983 +983 @@
   <x:anchor-alias value="media-range"/>
 <t>
-   The request-header field "Accept" can be used to specify certain media
+   The "Accept" request-header field can be used to specify certain media
    types which are acceptable for the response. Accept headers can be
    used to indicate that the request is specifically limited to a small
@@ -1110 +1110 @@
   <x:anchor-alias value="Accept-Charset-v"/>
 <t>
-   The request-header field "Accept-Charset" can be used to indicate what
+   The "Accept-Charset" request-header field can be used to indicate what
    character sets are acceptable for the response. This field allows
    clients capable of understanding more comprehensive or special-purpose
@@ -1155 +1155 @@
   <x:anchor-alias value="codings"/>
 <t>
-   The request-header field "Accept-Encoding" is similar to Accept, but
+   The "Accept-Encoding" request-header field is similar to Accept, but
    restricts the content-codings (<xref target="content.codings"/>) that are acceptable in
    the response.
@@ -1245 +1245 @@
   <x:anchor-alias value="language-range"/>
 <t>
-   The request-header field "Accept-Language" is similar to Accept, but
+   The "Accept-Language" request-header field is similar to Accept, but
    restricts the set of natural languages that are preferred as a
    response to the request. Language tags are defined in <xref target="language.tags"/>.
@@ -1341 +1341 @@
   <x:anchor-alias value="Content-Encoding-v"/>
 <t>
-   The entity-header field "Content-Encoding" is used as a modifier to the
+   The "Content-Encoding" entity-header field is used as a modifier to the
    media-type. When present, its value indicates what additional content
    codings have been applied to the entity-body, and thus what decoding
@@ -1391 +1391 @@
   <x:anchor-alias value="Content-Language-v"/>
 <t>
-   The entity-header field "Content-Language" describes the natural
+   The "Content-Language" entity-header field describes the natural
    language(s) of the intended audience for the enclosed entity. Note
    that this might not be equivalent to all the languages used within
@@ -1445 +1445 @@
   <x:anchor-alias value="Content-Location-v"/>
 <t>
-   The entity-header field "Content-Location" &MAY; be used to supply the
+   The "Content-Location" entity-header field &MAY; be used to supply the
    resource location for the entity enclosed in the message when that
    entity is accessible from a location separate from the requested
@@ -1496 +1496 @@
   <x:anchor-alias value="Content-MD5-v"/>
 <t>
-   The entity-header field "Content-MD5", as defined in <xref target="RFC1864"/>, is
+   The "Content-MD5" entity-header field, as defined in <xref target="RFC1864"/>, is
    an MD5 digest of the entity-body for the purpose of providing an
    end-to-end message integrity check (MIC) of the entity-body. (Note: a
@@ -1573 +1573 @@
   <x:anchor-alias value="Content-Type-v"/>
 <t>
-   The entity-header field "Content-Type" indicates the media type of the
+   The "Content-Type" entity-header field indicates the media type of the
    entity-body sent to the recipient or, in the case of the HEAD method,
    the media type that would have been sent had the request been a GET.
@@ -2675 +2675 @@
   <x:anchor-alias value="filename-parm"/>
 <t>
-   The Content-Disposition response-header field has been proposed as a
+   The "Content-Disposition" response-header field has been proposed as a
    means for the origin server to suggest a default filename if the user
    requests that the content is saved to a file. This usage is derived