Minor documentation updates.

svn path=/trunk/; revision=20687

8 files changed, 23 insertions, 31 deletions

diff --git a/docbook/wsug_src/WSUG_app_files.xml b/docbook/wsug_src/WSUG_app_files.xml
index 02bfe443fd..6de06e27be 100644
--- a/docbook/wsug_src/WSUG_app_files.xml
+++ b/docbook/wsug_src/WSUG_app_files.xml
@@ -131,7 +131,7 @@
 	</tip>
     <para>
 	The content format of the configuration files is the same on all platforms.
-	However, to match the different policies for unix and windows platforms, 
+	However, to match the different policies for Unix and windows platforms, 
 	different folders for these files are used.
     </para>
     <table id="AppFilesTabFolders" frame="none">
@@ -399,7 +399,7 @@ c0-00-ff-ff-ff-ff    TR_broadcast
 		  to translate IPv4 and IPv6 addresses into names.
 	    </para>
 	    <para>
-		  This file has the same format as the usual /etc/hosts file in unix systems.
+		  This file has the same format as the usual /etc/hosts file in Unix systems.
 	    </para>
 	    <para>
 	      An example is:
diff --git a/docbook/wsug_src/WSUG_app_tools.xml b/docbook/wsug_src/WSUG_app_tools.xml
index bf110533df..0d3d8786c0 100644
--- a/docbook/wsug_src/WSUG_app_tools.xml
+++ b/docbook/wsug_src/WSUG_app_tools.xml
@@ -1,5 +1,4 @@
 <!-- WSUG Appendix Tools -->
-
 <!-- $Id$ -->
 
 <appendix id="AppTools">
diff --git a/docbook/wsug_src/WSUG_chapter_advanced.xml b/docbook/wsug_src/WSUG_chapter_advanced.xml
index 4fe38c77e6..b2da34fb3a 100644
--- a/docbook/wsug_src/WSUG_chapter_advanced.xml
+++ b/docbook/wsug_src/WSUG_chapter_advanced.xml
@@ -670,7 +670,7 @@
     <para><command>Ethernet manufacturer codes (manuf file)</command>
 	If both ARP and ethers didn't returned a result, Wireshark tries to convert
 	the first 3 bytes of an ethernet address to an abbreviated manufacturer name,
-	which has been assigned by the IEC
+	which has been assigned by the IEEE
 	(e.g. 00:09:5b:01:02:03 -> Netgear_01:02:03).
     </para>
 	</section>
@@ -780,7 +780,7 @@
 	The receiver will calculate the checksum of the received data with the same
 	algorithm as the transmitter.
 	If the received and calculated checksums don't match a transmission error
-	has occured.
+	has occurred.
 	</para>
 	<para>
 	Some checksum algorithms are able to recover (simple) errors by
diff --git a/docbook/wsug_src/WSUG_chapter_introduction.xml b/docbook/wsug_src/WSUG_chapter_introduction.xml
index 99ef2a4b3b..56d8d91d24 100644
--- a/docbook/wsug_src/WSUG_chapter_introduction.xml
+++ b/docbook/wsug_src/WSUG_chapter_introduction.xml
@@ -333,7 +333,7 @@
       way to success.
     </para>
     <para>
-      Not long after that Gilbert Ramirez saw its potential and contributed 
+      Not long after that, Gilbert Ramirez saw its potential and contributed 
       a low-level dissector to it.
     </para>
     <para>
@@ -397,7 +397,7 @@
 	<listitem>
 	  <para>
 	    The developers of Wireshark might improve your changes even more,
-		as there's always room for improvements. Or they may implement some 
+		as there's always room for improvement. Or they may implement some 
 		advanced things on top of your code, which can be useful for yourself
 		too.
 	  </para>
@@ -425,7 +425,7 @@
     <title>Reporting problems and getting help</title>
 	<para>
       If you have problems, or need help with Wireshark, there are several 
-      places that may be of interest to you (well, beside this guide of 
+      places that may be of interest to you (well, besides this guide of 
 	  course).
 	</para>
 
diff --git a/docbook/wsug_src/WSUG_chapter_io.xml b/docbook/wsug_src/WSUG_chapter_io.xml
index eda4bf51d9..d32236abf7 100644
--- a/docbook/wsug_src/WSUG_chapter_io.xml
+++ b/docbook/wsug_src/WSUG_chapter_io.xml
@@ -505,7 +505,7 @@
 	and in the file formats of some other protocol analyzers, so other tools 
 	can read the capture data.
     </para>
-	<warning><title>File formats have different time stamp accuracys!</title>
+	<warning><title>File formats have different time stamp accuracies!</title>
 	<para>
 	Saving from the currently used to a different file format may reduce the 
 	time stamp accuracy, see the <xref linkend="ChAdvTimestamps"/> for details.
diff --git a/docbook/wsug_src/WSUG_chapter_troubleshoot.xml b/docbook/wsug_src/WSUG_chapter_troubleshoot.xml
index ed4a876951..ecc0c5756c 100644
--- a/docbook/wsug_src/WSUG_chapter_troubleshoot.xml
+++ b/docbook/wsug_src/WSUG_chapter_troubleshoot.xml
@@ -8,7 +8,7 @@
     <para>
       Wireshark is a very useful tool for network troubleshooting, since it 
       contains a number of features that allow you to quickly focus on 
-      problems in your networkfor several reasons:
+      problems in your network for several reasons:
       <itemizedlist>
 	<listitem>
 	  <para>
@@ -54,7 +54,7 @@
 	  </para>
 	  <para>
 	    Because Wireshark can read many capture file formats, you can 
-	    capture using any conventient tool. One useful approach is 
+	    capture using any convenient tool. One useful approach is 
 	    to use <command>tcpdump</command> to capture on remote 
 	    systems and then copy the capture file to your system for 
 	    later analysis. For more details on capturing with 
@@ -83,7 +83,7 @@
   <section id="Ch04ROUSWI">
     <title>Capturing in the presence of switches and routers</title>
     <para>
-	In the old days of Ethernet, all network traffic was spreaded over one 
+	In the old days of Ethernet, all network traffic was spread over one 
 	"yellow" cable through the whole network. Capturing data was easy,
 	as all packets from the network could be captured using the 
 	"promiscuous mode" at any place in the network. The only devices blocking 
@@ -92,14 +92,14 @@
     </para>
     <para>
 	Then Ethernet wiring using hubs become the state of the art. As the hubs 
-	still spreaded the packets all over the network, things regarding 
+	still spaded the packets all over the network, things regarding 
 	capturing didn't changed.
     </para>
     <para>
 	At the next stage, Ethernet switches became widely available. This 
 	complicated things a lot. When capturing traffic on a computer connected 
 	to a switch, usually the switch will only forward packets to the computer, 
-	which are directed to it, or to all computers (broadcast's). It's much the 
+	which are directed to it, or to all computers (broadcasts). It's much the 
 	same like deactivating the promiscuous mode of the capturing network card.
     </para>
     <para>
diff --git a/docbook/wsug_src/WSUG_chapter_work.xml b/docbook/wsug_src/WSUG_chapter_work.xml
index 0c6c1420ea..53db2c5b7b 100644
--- a/docbook/wsug_src/WSUG_chapter_work.xml
+++ b/docbook/wsug_src/WSUG_chapter_work.xml
@@ -836,7 +836,7 @@ ip.len le 0x436
 		    <entry>Ethernet address (6 bytes)</entry>
 		    <entry><para>Separators can be a colon
 			(:), dot (.) or dash (-) and can have one or
-			two bytes between seperators:<programlisting>
+			two bytes between separators:<programlisting>
 eth.addr == ff:ff:ff:ff:ff:ff
 eth.addr == ff-ff-ff-ff-ff-ff
 eth.addr == ffff.ffff.ffff</programlisting></para></entry>
@@ -847,21 +847,15 @@ eth.addr == ffff.ffff.ffff</programlisting></para></entry>
 		  </row>
 		  <row>
 		    <entry>IPv6 address</entry>
-		    <entry>  </entry>
+		    <entry>ipv6.addr == ::1</entry>
 		  </row>
 		  <row>
-		    <entry>IPX network number</entry>
-		    <entry>  </entry>
+		    <entry>IPX address</entry>
+		    <entry>ipx.addr == 00000000.ffffffffffff</entry>
 		  </row>
 		  <row>
 		    <entry>String (text)</entry>
-		    <entry> </entry>
-		  </row>
-		  <row>
-		    <entry>
-		      Double-precision floating point number
-		    </entry>
-		    <entry>  </entry>
+		    <entry>http.request.uri == "http://www.wireshark.org/"</entry>
 		  </row>
 		</tbody>
 	      </tgroup>
diff --git a/docbook/wsug_src/WSUG_preface.xml b/docbook/wsug_src/WSUG_preface.xml
index 68e7767710..8009da86fb 100644
--- a/docbook/wsug_src/WSUG_preface.xml
+++ b/docbook/wsug_src/WSUG_preface.xml
@@ -26,7 +26,7 @@
   <para>
   This book will explain all the basics and also some of the advanced features 
   that Wireshark provides. As Wireshark has become a very complex program since 
-  the early days, not every feature of Wireshark might be explained in this 
+  the early days, not every feature of Wireshark may be explained in this 
   book. 
   </para>
   <para>
@@ -37,11 +37,10 @@
   </para>
   <para>
   By reading this book, you will learn how to install Wireshark, how to use the 
-  basic elements of the graphical user interface (like the menu) and what's 
-  behind some of the advanced features that are maybe not that obvious at first 
-  sight. It will 
-  hopefully guide you around some common problems that frequently appears for 
-  new (and sometimes even advanced) users of Wireshark.
+  basic elements of the graphical user interface (such as the menu) and what's 
+  behind some of the advanced features that are not always obvious at first 
+  sight. It will hopefully guide you around some common problems that
+  frequently appear for new (and sometimes even advanced) users of Wireshark.
   </para>
   </section>