From OKANO Takayoshi via bug #5442: Fix typos in documentation

svn path=/trunk/; revision=35038

9 files changed, 13 insertions, 13 deletions

diff --git a/docbook/GPL_appendix.xml b/docbook/GPL_appendix.xml
index fe42b38abb..3260cf464e 100644
--- a/docbook/GPL_appendix.xml
+++ b/docbook/GPL_appendix.xml
@@ -2,9 +2,9 @@
 <appendix id="AppGPL">
 <!-- $Id$ -->
   <title>This Document's License (GPL)</title>
-  <para>As with the original licence and documentation distributed
+  <para>As with the original license and documentation distributed
     with Wireshark, this document is covered by the GNU General Public
-    Licence (GNU GPL).</para>
+    License (GNU GPL).</para>
 
   <para>If you haven't read the GPL before, please do so. It
     explains all the things that you are allowed to do with this
diff --git a/docbook/wsdg_src/WSDG_chapter_tools.xml b/docbook/wsdg_src/WSDG_chapter_tools.xml
index 568793b985..336d1cdf33 100644
--- a/docbook/wsdg_src/WSDG_chapter_tools.xml
+++ b/docbook/wsdg_src/WSDG_chapter_tools.xml
@@ -1548,7 +1548,7 @@ written by Larry Wall and Paul Eggert]]>
     your Internet connection might use an HTTP proxy. Some Internet
     providers use such a proxy and it is common in many company
     networks today. Wireshark's setup script will try to discover
-    your proxy settings automatically, but you you may need to set
+    your proxy settings automatically, but you may need to set
     the environment variable HTTP_PROXY by hand before using wget.
     For example, if you are behind proxy.com which is listening on
     port 8080, you have to set it to something like:</para>
diff --git a/docbook/wsluarm.xml b/docbook/wsluarm.xml
index 53d9939e93..b8654d27db 100644
--- a/docbook/wsluarm.xml
+++ b/docbook/wsluarm.xml
@@ -155,7 +155,7 @@ do
 		end
 	end
 
-	-- using this function we register our fuction
+	-- using this function we register our function
 	-- to be called when the user selects the Tools->Test->Packets menu
 	register_menu("Test/Packets", menuable_tap, MENU_TOOLS)
 end
diff --git a/docbook/wsug_src/WSUG_app_files.xml b/docbook/wsug_src/WSUG_app_files.xml
index cb85ee663b..5e49ccfac2 100644
--- a/docbook/wsug_src/WSUG_app_files.xml
+++ b/docbook/wsug_src/WSUG_app_files.xml
@@ -577,7 +577,7 @@ c0-a8-1c-00      CEO
 		  substitution in the "location" value. For example, if
 		  the database section contains
 		  <programlisting>
-locatoin = http://www.example.com/proto?cookie=${cookie}&amp;path=${PATH}
+location = http://www.example.com/proto?cookie=${cookie}&amp;path=${PATH}
 		  </programlisting>
 		  then setting
 		  <programlisting>
@@ -628,7 +628,7 @@ version=1
 url_template=http://${language}.wikipedia.org/wiki/${PATH}
 
 # Substitution data for the location template.
-# Each occurence of the keys below in the locaton template will be
+# Each occurence of the keys below in the location template will be
 # substituted with their corresponding values. For example, "${license}"
 # in the URL template above will be replaced with the value of "license"
 # below.
diff --git a/docbook/wsug_src/WSUG_app_tools.xml b/docbook/wsug_src/WSUG_app_tools.xml
index b67ecb8e37..1cc8b6fb84 100644
--- a/docbook/wsug_src/WSUG_app_tools.xml
+++ b/docbook/wsug_src/WSUG_app_tools.xml
@@ -675,7 +675,7 @@ Miscellaneous:
     <para>
       Text2pcap also allows the user to read in dumps of application-level
       data, by inserting dummy L2, L3 and L4 headers before each packet.
-      Possiblities include inserting headers such as Ethernet, Ethernet + IP,
+      Possibilities include inserting headers such as Ethernet, Ethernet + IP,
       Ethernet + IP + UDP, or Ethernet + Ip + TCP before each packet.
       This allows Wireshark or any other full-packet decoder to handle these dumps.
     </para>
@@ -834,7 +834,7 @@ Miscellaneous:
 	</listitem>
 	<listitem>
 	  <para>
-	    omniidl from the the omniORB package must be available. See
+	    omniidl from the omniORB package must be available. See
 	    <ulink url="http://omniorb.sourceforge.net/"/>
 	  </para>
 	</listitem>
diff --git a/docbook/wsug_src/WSUG_chapter_capture.xml b/docbook/wsug_src/WSUG_chapter_capture.xml
index 9917f72645..e5fce1ae1f 100644
--- a/docbook/wsug_src/WSUG_chapter_capture.xml
+++ b/docbook/wsug_src/WSUG_chapter_capture.xml
@@ -745,7 +745,7 @@ wireshark -i eth0 -k
       </section>
       <section><title>Remote Capture Settings</title>
       <para>
-	  The remote capture can be furhter fine tuned to match your situation.
+	  The remote capture can be further fine tuned to match your situation.
 	  The <command>Remote Settings</command> button gives you this option.
 	  It pops up the dialog shown in
 	  <xref linkend="ChCapInterfaceRemoteSettingsDialog"/>.
diff --git a/docbook/wsug_src/WSUG_chapter_customize.xml b/docbook/wsug_src/WSUG_chapter_customize.xml
index 89682c227d..6a9b336172 100644
--- a/docbook/wsug_src/WSUG_chapter_customize.xml
+++ b/docbook/wsug_src/WSUG_chapter_customize.xml
@@ -205,7 +205,7 @@ Miscellaneous:
 	  <listitem>
 	    <para>
 	      Win32 only: set capture buffer size (in MB, default is 1MB). This
-		  is used by the the capture driver to buffer packet data until that
+		  is used by the capture driver to buffer packet data until that
 		  data can be written to disk. If you encounter packet drops while
 		  capturing, try to increase this size.
 	    </para>
diff --git a/docbook/wsug_src/WSUG_chapter_io.xml b/docbook/wsug_src/WSUG_chapter_io.xml
index ea78712127..689422668f 100644
--- a/docbook/wsug_src/WSUG_chapter_io.xml
+++ b/docbook/wsug_src/WSUG_chapter_io.xml
@@ -719,7 +719,7 @@
     character dump). Any hex numbers in this text are also ignored. An offset of zero
     is indicative of starting a new packet, so a single text file with a series of
     hexdumps can be converted into a packet capture with multiple packets. Packets may
-    be preseded by a timestamp. These are interpreted according to the format
+    be preceded by a timestamp. These are interpreted according to the format
     given. If not the first packet is timestamped with the current time the import
     takes place. Multiple packets are read in with timestamps differing by one
     microsecond each. In general, short of these restrictions, Wireshark is pretty
@@ -821,7 +821,7 @@
       <para>
       Here you can select which type of frames you are importing. This all depends on
       from what type of medium the dump to import was taken. It lists all types that 
-      Wirshark understands, so as to pass the capture file contents to the right dissector.
+      Wireshark understands, so as to pass the capture file contents to the right dissector.
       </para>
       </listitem>
     </varlistentry>
diff --git a/docbook/wsug_src/WSUG_chapter_statistics.xml b/docbook/wsug_src/WSUG_chapter_statistics.xml
index f2b9fb3d05..2a75e7a900 100644
--- a/docbook/wsug_src/WSUG_chapter_statistics.xml
+++ b/docbook/wsug_src/WSUG_chapter_statistics.xml
@@ -649,7 +649,7 @@
         <listitem>
         <para>
             <command>Endpoint distinction:</command> Use MAC addresses or IP
-            time-to-live values to determine connection enpoints.
+            time-to-live values to determine connection endpoints.
         </para>
         </listitem>
         <listitem>