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/p3-payload.xml

    r882 r908  
    230230   associated metadata header fields that define how the payload is intended
    231231   to be interpreted by a recipient, the request header fields that
    232    may influence content selection, and the various selection algorithms
     232   might influence content selection, and the various selection algorithms
    233233   that are collectively referred to as HTTP content negotiation.
    234234</t>
     
    394394   method used with one or more tables to convert a sequence of octets
    395395   into a sequence of characters. Note that unconditional conversion in
    396    the other direction is not required, in that not all characters may
    397    be available in a given character set and a character set may provide
     396   the other direction is not required, in that not all characters might
     397   be available in a given character set and a character set might provide
    398398   more than one sequence of octets to represent a particular character.
    399399   This definition is intended to allow various kinds of character
     
    434434   value of a parameter in a Content-Type header (within a request or
    435435   response), in which case the parameter value of the charset parameter
    436    may be quoted.
     436   can be quoted.
    437437</t>
    438438<t>
     
    583583</t>
    584584<t>
    585    A parameter value that matches the <x:ref>token</x:ref> production may be
     585   A parameter value that matches the <x:ref>token</x:ref> production can be
    586586   transmitted as either a token or within a quoted-string. The quoted and
    587587   unquoted values are equivalent.
     
    790790</t>
    791791<t>
    792    Clients that do so risk drawing incorrect conclusions, which may expose
     792   Clients that do so risk drawing incorrect conclusions, which might expose
    793793   additional security risks (e.g., "privilege escalation"). Implementers are
    794794   encouraged to provide a means of disabling such "content sniffing" when it
     
    796796</t>
    797797<t>
    798    Content-Encoding may be used to indicate any additional content
     798   Content-Encoding is used to indicate any additional content
    799799   codings applied to the data, usually for the purpose of data
    800800   compression, that are a property of the representation.  There is
     
    840840   capabilities to be expressed by a client are large (such as when many
    841841   different formats are supported by a user-agent), server-driven
    842    negotiation becomes unwieldy, and may not be appropriate. Conversely,
     842   negotiation becomes unwieldy, and might not be appropriate. Conversely,
    843843   when the number of representations to choose from is very large,
    844    agent-driven negotiation may not be appropriate.
     844   agent-driven negotiation might not be appropriate.
    845845</t>
    846846<t>
     
    892892    </t>
    893893    <t>
    894          It may limit a public cache's ability to use the same response
     894         It might limit a public cache's ability to use the same response
    895895         for multiple user's requests.
    896896    </t>
     
    929929   header fields or body of the initial response, with each
    930930   representation identified by its own URI. Selection from among the
    931    representations may be performed automatically (if the user agent is
     931   representations can be performed automatically (if the user agent is
    932932   capable of doing so) or manually by the user selecting from a
    933933   generated (possibly hypertext) menu.
     
    14551455   contains a report on the action's status and the same report is
    14561456   available (for future access with GET) at the given URI.  For
    1457    example, a purchase transaction made via the POST method may
     1457   example, a purchase transaction made via the POST method might
    14581458   include a receipt document as the payload of the 200 response;
    14591459   the Content-Location value provides an identifier for retrieving
     
    20642064  <seriesInfo name="RFC" value="1950"/>
    20652065  <annotation>
    2066     RFC 1950 is an Informational RFC, thus it may be less stable than
     2066    RFC 1950 is an Informational RFC, thus it might be less stable than
    20672067    this specification. On the other hand, this downward reference was
    20682068    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     
    20832083  <seriesInfo name="RFC" value="1951"/>
    20842084  <annotation>
    2085     RFC 1951 is an Informational RFC, thus it may be less stable than
     2085    RFC 1951 is an Informational RFC, thus it might be less stable than
    20862086    this specification. On the other hand, this downward reference was
    20872087    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     
    21142114  <seriesInfo name="RFC" value="1952"/>
    21152115  <annotation>
    2116     RFC 1952 is an Informational RFC, thus it may be less stable than
     2116    RFC 1952 is an Informational RFC, thus it might be less stable than
    21172117    this specification. On the other hand, this downward reference was
    21182118    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
Note: See TracChangeset for help on using the changeset viewer.