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/p6-cache.xml

    r1689 r1692  
    1515  <!ENTITY ID-MONTH "June">
    1616  <!ENTITY ID-YEAR "2012">
     17  <!ENTITY mdash "&#8212;">
     18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1719  <!ENTITY architecture                "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1820  <!ENTITY notation                    "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    635637</t>
    636638<t>
    637    Additionally, clients can influence freshness calculation -- either
    638    constraining it relaxing it -- by using the max-age and min-fresh
     639   Additionally, clients can influence freshness calculation &mdash; either
     640   constraining it relaxing it &mdash; by using the max-age and min-fresh
    639641   request cache directives. See <xref target="cache-request-directive" />
    640642   for details.
     
    694696<x:note>
    695697   <t>
    696       <x:h>Note:</x:h> RFC 2616 (<xref target="RFC2616" x:fmt=","
     698      &Note; RFC 2616 (<xref target="RFC2616" x:fmt=","
    697699      x:sec="13.9"/>) required that caches do not calculate heuristic
    698700      freshness for URIs with query components (i.e., those containing '?').
     
    12011203<x:note>
    12021204   <t>
    1203        <x:h>Note:</x:h> HTTP/1.0 caches might not implement Cache-Control and
     1205       &Note; HTTP/1.0 caches might not implement Cache-Control and
    12041206       might only implement Pragma: no-cache (see <xref target="header.pragma"
    12051207       />).
     
    13791381      fields defined by this specification. Field names are case-insensitive.
    13801382      </t>
    1381       <t> <x:h>Note:</x:h> This usage of the word "private" only controls
     1383      <t>&Note; This usage of the word "private" only controls
    13821384      where the response can be stored; it cannot ensure the privacy of the
    13831385      message content. Also, private response directives with field-names are
     
    14081410      fields defined by this specification. Field names are case-insensitive.
    14091411      </t>
    1410       <t> <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey
     1412      <t>&Note; Most HTTP/1.0 caches will not recognize or obey
    14111413      this directive. Also, no-cache response directives with field-names are
    14121414      often handled by implementations as if an unqualified no-cache directive
     
    15981600<x:note>
    15991601   <t>
    1600        <x:h>Note:</x:h> If a response includes a Cache-Control field with the
     1602       &Note; If a response includes a Cache-Control field with the
    16011603       max-age directive (see <xref target="cache-response-directive" />),
    16021604       that directive overrides the Expires field. Likewise, the s-maxage
     
    16741676<x:note>
    16751677   <t>
    1676       <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" in responses is not
     1678      &Note; Because the meaning of "Pragma: no-cache" in responses is not
    16771679      specified, it does not provide a reliable replacement for
    16781680      "Cache-Control: no-cache" in them.
Note: See TracChangeset for help on using the changeset viewer.