Ignore:
Timestamp:
Feb 2, 2010, 4:04:50 AM (10 years ago)
Author:
julian.reschke@…
Message:

editorial: consistently uppercase sentence starts after "Note:"

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.xml

    r754 r756  
    12951295<x:note>
    12961296  <t>
    1297     <x:h>Note:</x:h> if a response includes a Cache-Control field with the max-age
     1297    <x:h>Note:</x:h> If a response includes a Cache-Control field with the max-age
    12981298    directive (see <xref target="cache-response-directive" />), that directive overrides
    12991299    the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches.
     
    13391339<x:note>
    13401340  <t>
    1341     <x:h>Note:</x:h> because the meaning of "Pragma: no-cache" as a response-header field
     1341    <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" as a response-header field
    13421342    is not actually specified, it does not provide a reliable replacement for
    13431343    "Cache-Control: no-cache" in a response.
     
    15611561<x:note>
    15621562  <t>
    1563     <x:h>Note:</x:h> if history list mechanisms unnecessarily prevent users from viewing
     1563    <x:h>Note:</x:h> If history list mechanisms unnecessarily prevent users from viewing
    15641564    stale resources, this will tend to force service authors to avoid using HTTP expiration
    15651565    controls and cache controls when they would otherwise like to. Service authors may
Note: See TracChangeset for help on using the changeset viewer.