Changeset 528 for draft-ietf-httpbis

Timestamp:

Mar 4, 2009, 10:27:23 PM (11 years ago)

Author:

mnot@…

Message:

which hunt

File:

• draft-ietf-httpbis/latest-roy/p6-cache.xml (modified) (5 diffs)

draft-ietf-httpbis/latest-roy/p6-cache.xml

@@ -1030 +1030 @@
           <t>The Cache-Control header field can be extended through the use of one or more
             cache-extension tokens, each with an optional value. Informational extensions (those
-            which do not require a change in cache behavior) &MAY; be added without changing the
+            that do not require a change in cache behavior) &MAY; be added without changing the
             semantics of other directives. Behavioral extensions are designed to work by acting as
             modifiers to the existing base of cache directives. Both the new directive and the
-            standard directive are supplied, such that applications which do not understand the new
+            standard directive are supplied, such that applications that do not understand the new
             directive will default to the behavior specified by the standard directive, and those
             that understand the new directive will recognize it as modifying the requirements
@@ -1041 +1041 @@
             directives defined for its native HTTP-version, obeying certain extensions, and ignoring
             all directives that it does not understand.</t>
-          <t>For example, consider a hypothetical new response directive called "community" which
+          <t>For example, consider a hypothetical new response directive called "community" that
             acts as a modifier to the private directive. We define this new directive to mean that,
-            in addition to any non-shared cache, any cache which is shared only by members of the
+            in addition to any non-shared cache, any cache that is shared only by members of the
             community named within its value may cache the response. An origin server wishing to
             allow the UCI community to use an otherwise private response in their shared cache(s)
@@ -1177 +1177 @@
         <x:anchor-alias value="warn-text"/>
         <t>The general-header field "Warning" is used to carry additional information about the status
-          or transformation of a message which might not be reflected in the message. This
+          or transformation of a message that might not be reflected in the message. This
           information is typically used to warn about possible incorrectness introduced by caching
           operations or transformations applied to the entity body of the message.</t>
@@ -1226 +1226 @@
             <t>2xx Warnings that describe some aspect of the entity body or entity headers that is
               not rectified by a validation (for example, a lossy compression of the entity bodies)
-              and which &MUST-NOT; be deleted by caches after validation, unless a full response is
+              and &MUST-NOT; be deleted by caches after validation, unless a full response is
               returned, in which case they &MUST; be.</t>
           </list>
@@ -1293 +1293 @@
 
     <section anchor="history.lists" title="History Lists">
-      <t>User agents often have history mechanisms, such as "Back" buttons and history lists, which
+      <t>User agents often have history mechanisms, such as "Back" buttons and history lists, that
         can be used to redisplay an entity retrieved earlier in a session.</t>
       <t>History mechanisms and caches are different. In particular history mechanisms