Ignore:
Timestamp:
Jun 23, 2012, 5:01:38 AM (8 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.html

    r1689 r1692  
    452452  }
    453453  @bottom-center {
    454        content: "Expires December 24, 2012";
     454       content: "Expires December 25, 2012";
    455455  }
    456456  @bottom-right {
     
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
     496      <meta name="dct.issued" scheme="ISO8601" content="2012-06-23">
    497497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    498498      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: December 24, 2012</td>
     522               <td class="left">Expires: December 25, 2012</td>
    523523               <td class="right">M. Nottingham, Editor</td>
    524524            </tr>
     
    537537            <tr>
    538538               <td class="left"></td>
    539                <td class="right">June 22, 2012</td>
     539               <td class="right">June 23, 2012</td>
    540540            </tr>
    541541         </tbody>
     
    567567         in progress”.
    568568      </p>
    569       <p>This Internet-Draft will expire on December 24, 2012.</p>
     569      <p>This Internet-Draft will expire on December 25, 2012.</p>
    570570      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    571571      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    923923</pre> <p id="rfc.section.2.3.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section&nbsp;2.3.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
    924924      </p>
    925       <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation -- either constraining it relaxing it -- by using the max-age and
     925      <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation — either constraining it relaxing it — by using the max-age and
    926926         min-fresh request cache directives. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a> for details.
    927927      </p>
     
    13261326            case-insensitive.
    13271327         </li>
    1328          <li> <b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
     1328         <li><b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
    13291329            content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
    13301330            directive was received; i.e., the special handling for the qualified form is not widely implemented.
     
    13451345            case-insensitive.
    13461346         </li>
    1347          <li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
     1347         <li><b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
    13481348            handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
    13491349            form is not widely implemented.
Note: See TracChangeset for help on using the changeset viewer.