Some cleanup: correct some grammar and do a few minor rewordings

svn path=/trunk/; revision=22837

11 files changed, 37 insertions, 37 deletions

diff --git a/docbook/wsug_src/WSUG_app_files.xml b/docbook/wsug_src/WSUG_app_files.xml
index 3d230a119d..7f1caa3533 100644
--- a/docbook/wsug_src/WSUG_app_files.xml
+++ b/docbook/wsug_src/WSUG_app_files.xml
@@ -555,7 +555,7 @@ c0-a8-1c-00      CEO
 	you are currently working on, but on the domain server.
 	</para>
 	<para>
-	As Wireshark is using the correct places to store it's profile data,
+	As Wireshark is using the correct places to store its profile data,
 	your settings will travel with you, if you logon to a different computer 
 	the next time.
 	</para>
diff --git a/docbook/wsug_src/WSUG_app_howitworks.xml b/docbook/wsug_src/WSUG_app_howitworks.xml
index cde9d5d639..1bf9fa6605 100644
--- a/docbook/wsug_src/WSUG_app_howitworks.xml
+++ b/docbook/wsug_src/WSUG_app_howitworks.xml
@@ -52,7 +52,7 @@
 
   <section><title>Protocol dissectors</title>
   <para>
-  Each protocol has it's own protocol dissector. A dissector is called from 
+  Each protocol has its own protocol dissector. A dissector is called from 
   Wireshark, if the packet data seems to be of that corresponding protocol. The 
   dissector  will then process the packet data and call back Wireshark if it 
   couldn't dissect all the data in that packet to do any further dissections.
@@ -97,7 +97,7 @@
   is just unknown to Wireshark.
   </para>
   <para>
-  You can control the way how Wireshark calls it's dissectors, see <xref 
+  You can control the way Wireshark calls its dissectors, see <xref 
   linkend="ChAdvProtocolDissectionSection"/> for details.
   </para>
   </section>
diff --git a/docbook/wsug_src/WSUG_app_messages.xml b/docbook/wsug_src/WSUG_app_messages.xml
index 16c08d6e08..48c175bf9b 100644
--- a/docbook/wsug_src/WSUG_app_messages.xml
+++ b/docbook/wsug_src/WSUG_app_messages.xml
@@ -22,7 +22,7 @@
 		<command>Wrong dissector</command>
 	    Wireshark erroneously has chosen the wrong protocol dissector for 
 		this packet. This will happen e.g. if you are using a protocol  
-		not on it's well known TCP or UDP port. You may try Analyze|Decode As 
+		not on its well known TCP or UDP port. You may try Analyze|Decode As 
 		to circumvent this problem.
 	  </para>
 	</listitem>
diff --git a/docbook/wsug_src/WSUG_app_tools.xml b/docbook/wsug_src/WSUG_app_tools.xml
index 1310bb424b..3610e07f24 100644
--- a/docbook/wsug_src/WSUG_app_tools.xml
+++ b/docbook/wsug_src/WSUG_app_tools.xml
@@ -964,7 +964,7 @@ where &lt;input-filename&gt; specifies input filename (use - for standard input)
 	  <para>
 	    To write the C code to stdout.
 	    <programlisting>idl2wrs  &lt;your file.idl&gt;</programlisting>
-	    eg: <programlisting>idl2wrs echo.idl</programlisting>
+	    e.g.: <programlisting>idl2wrs echo.idl</programlisting>
 	  </para>
 	</listitem>
 	<listitem>
@@ -983,7 +983,7 @@ where &lt;input-filename&gt; specifies input filename (use - for standard input)
 	<listitem>
 	  <para>To write the C code to stdout.
 	    <programlisting>Usage: omniidl  -p ./ -b wireshark_be &lt;your file.idl&gt;</programlisting>
-	    eg:
+	    e.g.:
 	    <programlisting>omniidl  -p ./ -b wireshark_be echo.idl</programlisting>
 	  </para>
 	</listitem>
@@ -1060,7 +1060,7 @@ edit Makefile.nmake
 	<listitem>
 	  <para>
 	    If it complains about being unable to find some modules
-	    (eg tempfile.py),
+	    (e.g. Tempfile.Py),
 	    you may want to check if PYTHONPATH is set correctly.
 	    On my Linux box, it is  PYTHONPATH=/usr/lib/python2.4/
 	  </para>
diff --git a/docbook/wsug_src/WSUG_chapter_advanced.xml b/docbook/wsug_src/WSUG_chapter_advanced.xml
index e8690c642c..a47b583bda 100644
--- a/docbook/wsug_src/WSUG_chapter_advanced.xml
+++ b/docbook/wsug_src/WSUG_chapter_advanced.xml
@@ -305,7 +305,7 @@
       <section id="ChAdvExpertDialogDetails">
         <title>Details tab</title>
         <para>The Details tab provides the expert infos in a "log
-        like" view, each entry in it's own line (much like the
+        like" view, each entry in its own line (much like the
         packet list). As the amount of expert infos of a capture
         file can easily become very large, getting an idea of the
         interesting infos with this view can take quite a while.
@@ -752,7 +752,7 @@
       <title>Name Resolution drawbacks</title>
       <para>Name resolution can be invaluable while working with
       Wireshark and may even save you hours of work. Unfortunately,
-      it also has it's drawbacks.</para>
+      it also has its drawbacks.</para>
       <itemizedlist>
         <listitem>
           <para>
@@ -788,7 +788,7 @@
           performance. However, if the name resolution information
           should change while Wireshark is running, Wireshark won't
           notice a change to the name resolution information once
-          it's get cached. If this information changes while
+          it gets cached. If this information changes while
           Wireshark is running, e.g. a new DHCP lease takes effect,
           Wireshark won't notice it. XXX - is this true for all or
           only for DNS info?</para>
diff --git a/docbook/wsug_src/WSUG_chapter_build_install.xml b/docbook/wsug_src/WSUG_chapter_build_install.xml
index d5ae01a9b6..7cf98de3a4 100644
--- a/docbook/wsug_src/WSUG_chapter_build_install.xml
+++ b/docbook/wsug_src/WSUG_chapter_build_install.xml
@@ -209,7 +209,7 @@ make install
       Under RedHat 6.x and beyond (and distributions based on it, like 
       Mandrake) you can simply install each of the packages you need from 
       RPMs. Most Linux systems will install GTK+ and GLib in any case, 
-      however, you will probably need to install the devel versions of 
+      however you will probably need to install the devel versions of 
       each of these packages. The commands shown in <xref linkend="Ch02Ex4"/> 
 	will install all the needed RPMs if they are not already installed.
 	<example id="Ch02Ex4">
@@ -263,7 +263,7 @@ tar zxvf wireshark-&WiresharkCurrentVersion;-tar.gz
 	    </programlisting>
 	  </para>
 	  <para>
-	    For other versions of UNIX, You will want to use the following 
+	    For other versions of UNIX, you will want to use the following 
 	    commands:
 	    <programlisting>
 gzip -d wireshark-&WiresharkCurrentVersion;-tar.gz
@@ -728,7 +728,7 @@ wireshark-setup-&WiresharkCurrentVersion;.exe /NCRC /S /desktopicon=yes
     </para>
 	<warning><title>Warning!</title>
 	<para>
-	If you have an older version of WinPcap installed, you must un-install it 
+	If you have an older version of WinPcap installed, you must uninstall it 
 	before installing the current version. Recent versions of the WinPcap 
 	installer will take care of this.
 	</para>
@@ -743,8 +743,8 @@ wireshark-setup-&WiresharkCurrentVersion;.exe /NCRC /S /desktopicon=yes
 	start the uninstallation procedure.
     </para>
     <para>
-	The Wireshark uninstaller will provide several options which things to be 
-	uninstalled, the default is to remove the core components but keep the personal 
+	The Wireshark uninstaller will provide several options as to which things are to be 
+	uninstalled; the default is to remove the core components but keep the personal 
 	settings, WinPcap and alike.
     </para>
     <para>
diff --git a/docbook/wsug_src/WSUG_chapter_capture.xml b/docbook/wsug_src/WSUG_chapter_capture.xml
index a52c54e892..c9e0e98417 100644
--- a/docbook/wsug_src/WSUG_chapter_capture.xml
+++ b/docbook/wsug_src/WSUG_chapter_capture.xml
@@ -23,7 +23,7 @@
 	captured time, captured number of packets.
 	</para></listitem>
 	<listitem><para>
-	Simultaneously show decoded packets while keep on capturing.
+	Simultaneously show decoded packets while Wireshark keeps on capturing.
 	</para></listitem>
 	<listitem><para>
 	Filter packets, reducing the amount of data to be captured, see <xref 
@@ -529,8 +529,8 @@ wireshark -i eth0 -k
 	    </term>
 	    <listitem>
 	      <para>
-		If this option is checked, the following capture info dialog will be 
-		hidden.
+		If this option is checked, the capture info dialog described in 
+                <xref linkend="ChCapRunningSection"/> will be hidden.
 	      </para>
 	    </listitem>
 	  </varlistentry>
@@ -1071,7 +1071,7 @@ tcp port 23 and not src host 10.0.0.5
 	<section id="ChCapRestartSection"><title>Restart a running capture</title>
     <para>
       A running capture session can be restarted with the same capture options 
-	  than the last time, this will remove all packets previously captured.
+	  as the last time, this will remove all packets previously captured.
 	  This can be useful, if some uninteresting packets are captured and 
 	  there's no need to keep them.
     </para>
diff --git a/docbook/wsug_src/WSUG_chapter_introduction.xml b/docbook/wsug_src/WSUG_chapter_introduction.xml
index 9193118b68..e71adb7d91 100644
--- a/docbook/wsug_src/WSUG_chapter_introduction.xml
+++ b/docbook/wsug_src/WSUG_chapter_introduction.xml
@@ -115,7 +115,7 @@
 	<title>Live capture from many different network media</title>
 	<para>
 	  Wireshark can capture traffic from many different network media types 
-	  - and despite it's name including wireless LAN as well.
+	  - and despite its name - including wireless LAN as well.
 	  Which media types are supported, depends on many things like the 
 	  operating system you are using.
 	  An overview of the supported media types can be found at: 
@@ -198,7 +198,7 @@
 	for details and workarounds</para></listitem>
 	<listitem><para>Wireshark won't benefit much from Multiprocessor/Hyperthread 
 	systems as time consuming tasks like filtering packets are single threaded.
-	No rule without exception: during an "Update list of packets in real 
+	No rule is without exception: during an "Update list of packets in real 
 	time" capture, capturing traffic runs in one process and dissecting and 
 	displaying packets runs in another process - which should benefit from two 
 	processors.</para></listitem>
@@ -247,7 +247,7 @@
 	three reasons: 
 	None of the developers actively use those systems any longer which 
 	makes support difficult.
-	The libraries Wireshark depends on (GTK, WinPCap, ...) also dropping support 
+	The libraries Wireshark depends on (GTK, WinPCap, ...) are also dropping support 
 	for these systems.
 	Microsoft also dropped support for these systems.
 	</para></listitem>
diff --git a/docbook/wsug_src/WSUG_chapter_io.xml b/docbook/wsug_src/WSUG_chapter_io.xml
index 2fe73ec31f..783f945afe 100644
--- a/docbook/wsug_src/WSUG_chapter_io.xml
+++ b/docbook/wsug_src/WSUG_chapter_io.xml
@@ -501,7 +501,7 @@
   <section id="ChIOOutputFormatsSection">
     <title>Output File Formats</title>
     <para>
-	Wireshark can save the packet data in it's "native" file format (libpcap) 
+	Wireshark can save the packet data in its "native" file format (libpcap) 
 	and in the file formats of some other protocol analyzers, so other tools 
 	can read the capture data.
     </para>
@@ -706,7 +706,7 @@
 	  pattern (prefix and suffix) than the currently loaded file. 
     </para>
     <para>
-	  This simple mechanism usually works well, but has it's drawbacks. If several 
+	  This simple mechanism usually works well, but has its drawbacks. If several 
 	  file sets were captured with the same prefix and suffix, Wireshark will detect 
 	  them as a single file set. If files were renamed or spread over several 
 	  directories the mechanism will fail to find all files of a set.
diff --git a/docbook/wsug_src/WSUG_chapter_use.xml b/docbook/wsug_src/WSUG_chapter_use.xml
index 15acd0e270..ff56b6445d 100644
--- a/docbook/wsug_src/WSUG_chapter_use.xml
+++ b/docbook/wsug_src/WSUG_chapter_use.xml
@@ -62,8 +62,8 @@
 
   <section id="ChUseMainWindowSection"><title>The Main window</title>
 	<para>
-      Lets look at Wireshark's user interface. <xref linkend="ChUseFig01"/> shows
-	Wireshark as you would usually see it after some packets captured or loaded
+      Let's look at Wireshark's user interface. <xref linkend="ChUseFig01"/> shows
+	Wireshark as you would usually see it after some packets are captured or loaded
 	(how to do this will be described later).
 	<figure id="ChUseFig01">
 	  <title>The Main window</title>
@@ -71,7 +71,7 @@
 	</figure>
     </para>
     <para>
-      Wireshark's main window consist of parts that are commonly known from many
+      Wireshark's main window consists of parts that are commonly known from many
 	  other GUI programs.
       <orderedlist>
 	<listitem>
@@ -279,8 +279,8 @@
 	<varlistentry><term><command>View</command></term>
 	  <listitem>
 	    <para>This menu controls the display of the captured data,
-		including the colorization of packets, zooming the font,
-		show a packet in a separate window, expand and collapse trees in packet details, ....
+		including colorization of packets, zooming the font,
+		showing a packet in a separate window, expanding and collapsing trees in packet details, ....
 		See <xref linkend="ChUseViewMenuSection"/>.
 		</para>
 	  </listitem>
@@ -312,7 +312,7 @@
 	<varlistentry><term><command>Statistics</command></term>
 	  <listitem>
 	    <para>
-	      This menu contains menu-items to display various statistic windows,
+	      This menu contains items to display various statistic windows,
 		  including a summary of the packets that have been captured,
 		  display protocol hierarchy statistics and much more.
 		  See <xref linkend="ChUseStatisticsMenuSection"/>.
@@ -480,7 +480,7 @@
 		<entry><command>Export > as "Plain Text" file...</command></entry>
 		<entry></entry>
 		<entry><para>
-		    This menu item allows you to export all, or some, of the packets in
+		    This menu item allows you to export all (or some) of the packets in
 		    the capture file to a plain ASCII text file.
 			It pops up the Wireshark Export dialog box (which is discussed further in
 		    <xref linkend="ChIOExportPlainDialog"/>).
@@ -490,7 +490,7 @@
 		<entry><command>Export > as "PostScript" file...</command></entry>
 		<entry></entry>
 		<entry><para>
-		    This menu item allows you to export the (or some) of the packets in
+		    This menu item allows you to export all (or some) of the packets in
 		    the capture file to a PostScript file.
 			It pops up the Wireshark Export dialog box (which is discussed further in
 		    <xref linkend="ChIOExportPSDialog"/>).
@@ -500,7 +500,7 @@
 		<entry><command>Export > as "CSV" (Comma Separated Values packet summary) file...</command></entry>
 		<entry></entry>
 		<entry><para>
-		    This menu item allows you to export the (or some) of the packet summaries in
+		    This menu item allows you to export all (or some) of the packet summaries in
 		    the capture file to a .csv file (e.g. used by spreadsheet programs).
 			It pops up the Wireshark Export dialog box (which is discussed further in
 		    <xref linkend="ChIOExportCSVDialog"/>).
@@ -510,7 +510,7 @@
 		<entry><command>Export > as "PSML" file...</command></entry>
 		<entry></entry>
 		<entry><para>
-		    This menu item allows you to export the (or some) of the packets in
+		    This menu item allows you to export all (or some) of the packets in
 		    the capture file to a PSML (packet summary markup language) XML file.
 			It pops up the Wireshark Export dialog box (which is discussed further in
 		    <xref linkend="ChIOExportPSMLDialog"/>).
@@ -520,7 +520,7 @@
 		<entry><command>Export > as "PDML" file...</command></entry>
 		<entry></entry>
 		<entry><para>
-		    This menu item allows you to export the (or some) of the packets in
+		    This menu item allows you to export all (or some) of the packets in
 		    the capture file to a PDML (packet details markup language) XML file.
 			It pops up the Wireshark Export dialog box (which is discussed further in
 		    <xref linkend="ChIOExportPDMLDialog"/>).
@@ -545,7 +545,7 @@
 		<entry><command>Print...</command></entry>
 		<entry>Ctrl+P</entry>
 		<entry><para>
-		    This menu item allows you to print all (or some of) the packets in
+		    This menu item allows you to print all (or some) of the packets in
 		    the capture file. It pops up the Wireshark Print dialog
 		    box (which is discussed further in
 		    <xref linkend="ChIOPrintSection"/>).
diff --git a/docbook/wsug_src/WSUG_preface.xml b/docbook/wsug_src/WSUG_preface.xml
index 8009da86fb..0beec59202 100644
--- a/docbook/wsug_src/WSUG_preface.xml
+++ b/docbook/wsug_src/WSUG_preface.xml
@@ -163,7 +163,7 @@
   <section id="PreFeedback">
     <title>Providing feedback about this document</title>
     <para>
-      Should you have any feedback about this document, please send them 
+      Should you have any feedback about this document, please send it 
       to the authors through <ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;</ulink>.
     </para>
   </section>