Ignore:
Timestamp:
Jul 14, 2012, 10:52:23 AM (7 years ago)
Author:
julian.reschke@…
Message:

spelling fixes

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1774 r1776  
    899899      <div id="rfc.iref.s.2"></div>
    900900      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
    901       <p id="rfc.section.2.1.1.p.1">Implementors need to be aware that the software represents the user in their interactions over the Internet, and need to allow
     901      <p id="rfc.section.2.1.1.p.1">Implementers need to be aware that the software represents the user in their interactions over the Internet, and need to allow
    902902         the user to be aware of any actions they take which might have an unexpected significance to themselves or others.
    903903      </p>
     
    20822082      </p>
    20832083      <div class="note" id="rfc.section.4.7.5.p.2">
    2084          <p> <b>Note</b> to implementors: some deployed proxies are known to return <a href="#status.400" class="smpl">400 (Bad Request)</a> or <a href="#status.500" class="smpl">500 (Internal Server
     2084         <p> <b>Note</b> to implementers: some deployed proxies are known to return <a href="#status.400" class="smpl">400 (Bad Request)</a> or <a href="#status.500" class="smpl">500 (Internal Server
    20852085               Error)</a> when DNS lookups time out.
    20862086         </p>
     
    22052205      <p id="rfc.section.5.3.p.5">HTTP uses charset in two contexts: within an <a href="#header.accept-charset" class="smpl">Accept-Charset</a> request header field (in which the charset value is an unquoted token) and as the value of a parameter in a <a href="#header.content-type" class="smpl">Content-Type</a> header field (within a request or response), in which case the parameter value of the charset parameter can be quoted.
    22062206      </p>
    2207       <p id="rfc.section.5.3.p.6">Implementors need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
     2207      <p id="rfc.section.5.3.p.6">Implementers need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    22082208      </p>
    22092209      <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
     
    27632763      </p>
    27642764      <div class="note" id="rfc.section.9.4.p.10">
    2765          <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not
     2765         <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementers of the fact that users are not
    27662766            familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
    27672767            users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available.
     
    30583058      <div class="note" id="rfc.section.9.17.p.7">
    30593059         <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    3060             against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
     3060            against software that is known to contain security holes. Server implementers are encouraged to make this field a configurable
    30613061            option.
    30623062         </p>
     
    36053605      </p>
    36063606      <p id="rfc.section.11.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    3607          against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the <a href="#header.server" class="smpl">Server</a> header field a configurable option.
     3607         against software that is known to contain security holes. Implementers <em class="bcp14">SHOULD</em> make the <a href="#header.server" class="smpl">Server</a> header field a configurable option.
    36083608      </p>
    36093609      <p id="rfc.section.11.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
     
    39343934      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
    39353935      <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1
    3936          applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
     3936         applications. Implementers are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
    39373937         with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that
    39383938         experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
Note: See TracChangeset for help on using the changeset viewer.