Changeset 756 for draft-ietf-httpbis/latest/p6-cache.html

Timestamp:

02/02/10 12:04:50 (12 years ago)

Author:

julian.reschke@…

Message:

editorial: consistently uppercase sentence starts after "Note:"

File:

• draft-ietf-httpbis/latest/p6-cache.html (modified) (7 diffs)

draft-ietf-httpbis/latest/p6-cache.html

@@ -402 +402 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-02-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-02-02">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. 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.">
@@ -428 +428 @@
             </tr>
             <tr>
-               <td class="left">Expires: August 5, 2010</td>
+               <td class="left">Expires: August 6, 2010</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -489 +489 @@
             <tr>
                <td class="left"></td>
-               <td class="right">February 1, 2010</td>
+               <td class="right">February 2, 2010</td>
             </tr>
          </tbody>
@@ -519 +519 @@
       <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
       </p>
-      <p>This Internet-Draft will expire in August 5, 2010.</p>
+      <p>This Internet-Draft will expire in August 6, 2010.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1230 +1230 @@
       <p>For example</p>  <pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
 </pre><div class="note" id="rfc.section.3.3.p.6"> 
-         <p> <b>Note:</b> if a response includes a Cache-Control field with the max-age directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), that directive overrides the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches.
+         <p> <b>Note:</b> If a response includes a Cache-Control field with the max-age directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), that directive overrides the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches.
          </p> 
       </div>
@@ -1252 +1252 @@
       </p>
       <div class="note" id="rfc.section.3.4.p.4"> 
-         <p> <b>Note:</b> because the meaning of "Pragma: no-cache" as a response-header field is not actually specified, it does not provide a reliable
+         <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" as a response-header field is not actually specified, it does not provide a reliable
             replacement for "Cache-Control: no-cache" in a response.
          </p> 
@@ -1385 +1385 @@
       <p id="rfc.section.4.p.4">This is not to be construed to prohibit the history mechanism from telling the user that a view might be stale.</p>
       <div class="note" id="rfc.section.4.p.5"> 
-         <p> <b>Note:</b> if history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors
+         <p> <b>Note:</b> If history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors
             to avoid using HTTP expiration controls and cache controls when they would otherwise like to. Service authors may consider
             it important that users not be presented with error messages or warning messages when they use navigation controls (such as