Ignore:
Timestamp:
Jun 23, 2012, 5:01:38 AM (7 years ago)
Author:
julian.reschke@…
Message:

Simplify use of "Note:", make upper/lowercase of sentence start consistent; use "—" where appropriate

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1689 r1692  
    1616  <!ENTITY ID-YEAR "2012">
    1717  <!ENTITY mdash "&#8212;">
     18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1819  <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1920  <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    308309<x:note>
    309310  <t>
    310     <x:h>Note:</x:h> The term 'user agent' covers both those situations where
     311    &Note; The term 'user agent' covers both those situations where
    311312    there is a user (human) interacting with the software agent (and for which
    312313    user interface or interactive suggestions might be made, e.g., warning the
     
    11871188<x:note>
    11881189  <t>
    1189    <x:h>Note:</x:h> The "Set-Cookie" header field as implemented in
     1190   &Note; The "Set-Cookie" header field as implemented in
    11901191   practice can occur multiple times, but does not use the list syntax, and
    11911192   thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
     
    19781979</t>
    19791980<x:note><t>
    1980    <x:h>Note:</x:h> Use of program names for the identification of encoding formats
     1981   &Note; Use of program names for the identification of encoding formats
    19811982   is not desirable and is discouraged for future encodings. Their
    19821983   use here is representative of historical practice, not good
     
    19841985</t></x:note>
    19851986<x:note><t>
    1986    <x:h>Note:</x:h> For compatibility with previous implementations of HTTP,
     1987   &Note; For compatibility with previous implementations of HTTP,
    19871988   applications &SHOULD; consider "x-gzip" and "x-compress" to be
    19881989   equivalent to "gzip" and "compress" respectively.
     
    20092010<x:note>
    20102011  <t>
    2011     <x:h>Note:</x:h> Some incorrect implementations send the "deflate"
     2012    &Note; Some incorrect implementations send the "deflate"
    20122013    compressed data without the zlib wrapper.
    20132014   </t>
     
    20842085         response on behalf of downstream recipients.
    20852086      </t><t>
    2086          <x:h>Note:</x:h> HTTP/1.1 does not define any means to limit the size of a
     2087         &Note; HTTP/1.1 does not define any means to limit the size of a
    20872088         chunked response such that a client can be assured of buffering
    20882089         the entire response.</t>
     
    21282129<x:note>
    21292130  <t>
    2130      <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent
     2131     &Note; "Quality values" is a misnomer, since these values merely represent
    21312132     relative degradation in desired quality.
    21322133  </t>
Note: See TracChangeset for help on using the changeset viewer.