Ignore:
Timestamp:
Jul 24, 2010, 1:30:41 AM (9 years ago)
Author:
fielding@…
Message:

(editorial) use might instead of may where it might be confused with MAY

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r879 r908  
    357357</artwork></figure>
    358358<t>
    359    In this case, the response may or may not use the gzip content coding.
     359   In this case, the response might or might not use the gzip content coding.
    360360   If it does not, the response might look like:
    361361</t>
     
    10741074   The exact meaning of this header field depends on the implementation
    10751075   of the origin server and the nature of the original resource. For
    1076    files, it may be just the file system last-modified time. For
    1077    representations with dynamically included parts, it may be the most recent
     1076   files, it might be just the file system last-modified time. For
     1077   representations with dynamically included parts, it might be the most recent
    10781078   of the set of last-modify times for its component parts. For database
    1079    gateways, it may be the last-update time stamp of the record. For
    1080    virtual objects, it may be the last time the internal state changed.
     1079   gateways, it might be the last-update time stamp of the record. For
     1080   virtual objects, it might be the last time the internal state changed.
    10811081</t>
    10821082<t>
Note: See TracChangeset for help on using the changeset viewer.