[pcap-ng-format] [Patch] Change wording of a scetion as proposed by Richard Sharpe

[Guy Harris]

On Jun 10, 2013, at 4:52 AM, Anders Broman <anders.broman at ericsson.com> wrote:

> Index: PCAP-DumpFileFormat.xml
> ===================================================================
> --- PCAP-DumpFileFormat.xml	(revision 13)
> +++ PCAP-DumpFileFormat.xml	(working copy)
> @@ -62,6 +62,7 @@
>      </abstract>
>      <note title="Updates">
>        <list style="symbols">
> +        <t>[10 Jun 2013] Anders Broman: changed wording as suggested by Richard Sharpe.</t>
>          <t>[26 Jul 2012] Jasper Bongertz: worked on some TODO items and fixed typos.</t>
>          <t>[27 Jul 2009] Guy Harris: added some missing reserved block types in Appendix B.</t>
>          <t>[27 Jul 2009] Guy Harris: fixed a typo in Appendix B. The range of standardized blocks are in the range 0x00000000-0x7FFFFFFF.</t>
> @@ -87,7 +88,7 @@
>    </front>
>    <middle>
>      <section title="Objectives" toc="default">
> -      <t>The problem of exchanging packet traces becomes more and more critical every day; unfortunately, no standard solutions exist for this task right now. One of the most accepted packet interchange formats is the one defined by libpcap, which is rather old and does not fit for some of the nowadays applications particularly from the extensibility point of view.</t>
> +      <t>The problem of exchanging packet traces becomes more and more critical every day; unfortunately, no standard solutions exist for this task right now. One of the most accepted packet interchange formats is the one defined by libpcap, which is rather old and is lacking in functionality for more modern applications particularly from the extensibility point of view.</t>
>        <t>This document proposes a new format for dumping packet traces. The following goals are being pursued:</t>
>        <list style="symbols">
>          <t>Extensibility: aside of some common functionalities, third parties should be able to enrich the information embedded in the file with proprietary extensions, which will be ignored by tools that are not able to understand them.</t>


I've checked that one in (with the current date).