fix various minor things noted by Brian Drab

svn path=/trunk/; revision=19230

6 files changed, 19 insertions, 17 deletions

diff --git a/docbook/wsug_graphics/ws-display-filter-tcp.png b/docbook/wsug_graphics/ws-display-filter-tcp.png
index 36260e6455..0a490b43e5 100644
--- a/docbook/wsug_graphics/ws-display-filter-tcp.png
+++ b/docbook/wsug_graphics/ws-display-filter-tcp.png
diff --git a/docbook/wsug_src/WSUG_chapter_advanced.xml b/docbook/wsug_src/WSUG_chapter_advanced.xml
index 5afd30cede..7d66fe9f46 100644
--- a/docbook/wsug_src/WSUG_chapter_advanced.xml
+++ b/docbook/wsug_src/WSUG_chapter_advanced.xml
@@ -573,7 +573,7 @@
 	</orderedlist>
     </para>
     <para>
-	The tooltip of the higher level protocol setting will note you if and
+	The tooltip of the higher level protocol setting will notify you if and
 	which lower level protocol setting has to be considered too.
     </para>
     </section>
@@ -582,7 +582,7 @@
   <section id="ChAdvNameResolutionSection"><title>Name Resolution</title>
     <para>
 	Name resolution tries to resolve some of the numerical address values into
-	a human readable format. There are two possible ways to do this
+	a human readable format. There are two possible ways to do these
 	conversations, depending on the resolution to be done: calling
 	system/network services (like the gethostname function) and/or evaluate
 	from Wireshark specific configuration files.
@@ -597,7 +597,7 @@
 	<section><title>Name Resolution drawbacks</title>
     <para>
 	Name resolution can be invaluable while working with Wireshark and may
-	save you even hours of work. Unfortunately, it also has it's drawbacks.
+	even save you hours of work. Unfortunately, it also has it's drawbacks.
     </para>
       <itemizedlist>
 	<listitem>
@@ -615,7 +615,7 @@
 	So the resolved names might not be available if you open the capture file
 	later or on a different machine.
 	Each time you open a capture file it may look "slightly different",
-	maybe simply because you can't connect a name server (which you could
+	maybe simply because you can't connect to a name server (which you could
 	connect before).
     </para>
 	</listitem>
diff --git a/docbook/wsug_src/WSUG_chapter_capture.xml b/docbook/wsug_src/WSUG_chapter_capture.xml
index b27fba0bbc..54218a12bd 100644
--- a/docbook/wsug_src/WSUG_chapter_capture.xml
+++ b/docbook/wsug_src/WSUG_chapter_capture.xml
@@ -726,7 +726,7 @@ wireshark -i eth0 -k
 	<para>
 	In the usual case, you won't have to choose this link-layer header type. 
 	The following paragraphs describe the exceptional cases, where
-	selecting this type is possible, so you will have a guide what to do:
+	selecting this type is possible, so you will have a guide of what to do:
 	</para>
     <para>
     If you are capturing on an 802.11 device on some versions of BSD, this 
@@ -1017,7 +1017,7 @@ tcp port 23 and not host 10.0.0.5
 	<graphic entityref="WiresharkCaptureInfoDialog" format="JPG"/>
       </figure>
 	This dialog box will inform you about the number of captured packets and 
-	the time since the capture was started. The selection which protocols
+	the time since the capture was started. The selection of which protocols
 	are counted cannot be changed.
 	</para>
 	  <tip><title>Tip!</title>
diff --git a/docbook/wsug_src/WSUG_chapter_introduction.xml b/docbook/wsug_src/WSUG_chapter_introduction.xml
index 136a2e8a90..14fbe6bf10 100644
--- a/docbook/wsug_src/WSUG_chapter_introduction.xml
+++ b/docbook/wsug_src/WSUG_chapter_introduction.xml
@@ -114,10 +114,11 @@
 	<section>
 	<title>Live capture from many different network media</title>
 	<para>
-	  Despite its name, Wireshark can capture traffic from 
-	  network media other than Ethernet. 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: 
+	  Wireshark can capture traffic from many different network media types 
+	  - and despite it's 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: 
 	  <ulink url="&WiresharkMediaPage;"/>.
 	</para>
 	</section>
@@ -225,7 +226,7 @@
 	<listitem><para>Red Hat Linux</para></listitem>
 	<listitem><para>Rock Linux</para></listitem>
 	<listitem><para>Slackware Linux</para></listitem>
-	<listitem><para>Suse Linux</para></listitem>
+	<listitem><para>SUSE Linux</para></listitem>
 	</itemizedlist>
 	</para>
 	</section>
diff --git a/docbook/wsug_src/WSUG_chapter_io.xml b/docbook/wsug_src/WSUG_chapter_io.xml
index 6ad4192d1b..ce980a9ac6 100644
--- a/docbook/wsug_src/WSUG_chapter_io.xml
+++ b/docbook/wsug_src/WSUG_chapter_io.xml
@@ -427,7 +427,7 @@
     <para>
       When using the "Multiple Files" option while doing a capture
 	  (see: <xref linkend="ChCapCaptureFiles"/>), 
-	  the capture data is spreaded over several capture files, called a file 
+	  the capture data is spread over several capture files, called a file 
 	  set. 
     </para>
     <para>
@@ -449,7 +449,7 @@
     <para>
 	  This simple mechanism usually works well, but has it's 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 spreaded over several 
+	  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.
     </para>
 	</sidebar>
diff --git a/docbook/wsug_src/WSUG_chapter_work.xml b/docbook/wsug_src/WSUG_chapter_work.xml
index fee66ed6be..5052507abd 100644
--- a/docbook/wsug_src/WSUG_chapter_work.xml
+++ b/docbook/wsug_src/WSUG_chapter_work.xml
@@ -60,7 +60,7 @@
       </figure>
 	</para>
 	  <para>
-	  The following table gives an overview which functions are available 
+	  The following table gives an overview of which functions are available 
 	  in this pane, where to find the corresponding function in the main menu, 
 	  and a short description of each item.
 	  </para>
@@ -207,7 +207,7 @@
       </figure>
 	  </para>
 	  <para>
-	  The following table gives an overview which functions are available 
+	  The following table gives an overview of which functions are available 
 	  in this pane, where to find the corresponding function in the main menu, 
 	  and a short description of each item.
 	  </para>
@@ -401,7 +401,7 @@
       </figure>
 	  </para>
 	  <para>
-	  The following table gives an overview which functions are available 
+	  The following table gives an overview of which functions are available 
 	  in this pane, where to find the corresponding function in the main menu, 
 	  and a short description of each item.
 	  </para>
@@ -510,7 +510,7 @@
       You can filter on any protocol that Wireshark understands.  
       You can also filter on any field that a dissector adds to the tree 
       view, but only if the dissector has added an abbreviation for the 
-      field. A list of such fields is available in the Wireshark in the 
+      field. A list of such fields is available in Wireshark in the 
       <command>Add Expression...</command> dialog box.  You can find more 
       information on the <command>Add Expression...</command> dialog box 
       in <xref linkend="ChWorkFilterAddExpressionSection"/>.
@@ -953,6 +953,7 @@ eth.src[1-2] == 00:83
 	  <para>
 	    You can leave the <command>Add Expression...</command> dialog 
 	    box without any effect by clicking the <command>Cancel</command>
+		button.
 	  </para>
 	</listitem>
       </varlistentry>