Merge pull request #39 from jpoliv/typos

Typos and other minor changes

README.md

@@ -9,7 +9,7 @@
 
 ## The pcap Next Generation Capture File Format
 
-This is the Github repository for the pcapng file format draft specification. The specification is currently a work-in-progress.
+This is the GitHub repository for the pcapng file format draft specification. The specification is currently a work-in-progress.
 
 Join the [pcapng mailing list](https://www.winpcap.org/mailman/listinfo/pcap-ng-format) to discuss, or view the [list archive](http://www.winpcap.org/pipermail/pcap-ng-format/) to view the previous discussions.
 

draft-tuexen-opsawg-pcapng.xml

@@ -23,7 +23,7 @@
         <postal>
           <street>Stegerwaldstrasse 39</street>
           <code>48565</code>
-          <city> Steinfurt</city>
+          <city>Steinfurt</city>
           <country>DE</country>
         </postal>
         <email>tuexen@fh-muenster.de</email>
@@ -441,7 +441,7 @@ Section Header
             Significant Bit is equal to one are reserved for local use;
             therefore, there is no guarantee that the code used is unique
             among all capture files (generated by other applications), and is
-            most certainly not portable. For cross-platform gloablly unique
+            most certainly not portable. For cross-platform globally unique
             vendor-specific extensions, the Custom Option MUST be used
             instead, as defined in <xref target="section_custom_option"/>).</t>
 
@@ -471,7 +471,7 @@ Section Header
         special 'End of Option' code (opt_endofopt).  Code that
         writes pcapng files MUST put an opt_endofopt option at the end
         of an option list.  Code that reads pcapng files MUST NOT assume
-        an option list will have an opt_endofopt opton at the end; it
+        an option list will have an opt_endofopt option at the end; it
         MUST also check for the end of the block, and SHOULD treat
         blocks where the option list has no opt_endofopt option as if
         the option list had an opt_endofopt option at the end.</t>
@@ -1116,7 +1116,7 @@ Section Header
             is missing, the timestamps stored in the packet MUST be considered
             absolute timestamps. The time zone of the offset can be specified
             with the option if_tzone. TODO: won't a if_tsoffset_low for
-            fractional second offsets be useful for highly syncronized capture
+            fractional second offsets be useful for highly synchronized capture
             systems?</t>
 
             <t>Example: '1234'.</t>
@@ -2188,7 +2188,7 @@ Section Header
 
         <t>For the Custom Options, there are two Custom Data formats
         supported: a UTF-8 string and a binary data payload. The rationale for
-        this separation is that a pcapng display appplication which does not
+        this separation is that a pcapng display application which does not
         understand the specific PEN's Custom Option can still display the data
         as a string if it's a string type code, rather than as hex-ascii of
         the octets.</t>