Ignore:
Timestamp:
Jul 30, 2010, 6:06:01 PM (9 years ago)
Author:
fielding@…
Message:

Replace lowercase should with less normative words, where possible.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r968 r969  
    409409</t>
    410410<t>
    411    Implementors should be aware of IETF character set requirements <xref target="RFC3629"/>
     411   Implementors need to be aware of IETF character set requirements <xref target="RFC3629"/>
    412412   <xref target="RFC2277"/>.
    413413</t>
     
    13001300    the user, we remind implementors of  the fact that users are not
    13011301    familiar with the details of language matching as described above,
    1302     and should provide appropriate guidance. As an example, users
     1302    and ought to be provided appropriate guidance. As an example, users
    13031303    might assume that on selecting "en-gb", they will be served any
    13041304    kind of English document if British English is not available. A
     
    16071607<section title="Header Field Registration" anchor="header.field.registration">
    16081608<t>
    1609    The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> should be updated
     1609   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    16101610   with the permanent registrations below (see <xref target="RFC3864"/>):
    16111611</t>
     
    16991699<t>
    17001700   The HTTP Content Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/>
    1701    should be updated with the registration below:
     1701   shall be updated with the registration below:
    17021702</t>
    17031703<texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table">
     
    26052605</t>
    26062606<t>
    2607    Implementors should note that conversion will break any cryptographic
     2607   Conversion will break any cryptographic
    26082608   checksums applied to the original content unless the original content
    26092609   is already in canonical form. Therefore, the canonical form is
Note: See TracChangeset for help on using the changeset viewer.