Ignore:
Timestamp:
Jul 12, 2010, 5:41:49 PM (9 years ago)
Author:
fielding@…
Message:

minor prose tweaks - editorial

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r848 r849  
    720720         effectively in many different contexts and for which implementations can evolve independently over time.
    721721      </p>
    722       <p id="rfc.section.1.p.3">HTTP is also designed for use as a generic protocol for translating communication to and from other Internet information systems.
    723          HTTP proxies and gateways provide access to alternative information services by translating their diverse protocols into a
    724          hypertext format that can be viewed and manipulated by clients in the same way as HTTP services.
     722      <p id="rfc.section.1.p.3">HTTP is also designed for use as an intermediation protocol for translating communication to and from non-HTTP information
     723         systems. HTTP proxies and gateways can provide access to alternative information services by translating their diverse protocols
     724         into a hypertext format that can be viewed and manipulated by clients in the same way as HTTP services.
    725725      </p>
    726726      <p id="rfc.section.1.p.4">One consequence of HTTP flexibility is that the protocol cannot be defined in terms of what occurs behind the interface. Instead,
     
    764764         </p>
    765765      </div>
    766       <p id="rfc.section.1.2.p.3">As a syntactical convention, ABNF rule names prefixed with "obs-" denote "obsolete" grammar rules that appear for historical
     766      <p id="rfc.section.1.2.p.3">As a syntactic convention, ABNF rule names prefixed with "obs-" denote "obsolete" grammar rules that appear for historical
    767767         reasons.
    768768      </p>
Note: See TracChangeset for help on using the changeset viewer.