aboutsummaryrefslogtreecommitdiffstats
path: root/docbook
diff options
context:
space:
mode:
authorBill Meier <wmeier@newsguy.com>2008-08-13 16:44:18 +0000
committerBill Meier <wmeier@newsguy.com>2008-08-13 16:44:18 +0000
commit0b499492f73f9696b609b571dbd633935f59e8f3 (patch)
tree9577f3588630c040f0c929a7d3b365da5cc65215 /docbook
parent895df0eeeac068f9e689b81d9c4ec4112a7fa49d (diff)
Fix various minor typos and spelling errors
svn path=/trunk/; revision=26008
Diffstat (limited to 'docbook')
-rw-r--r--docbook/wsdg_src/WSDG_chapter_dissection.xml8
-rw-r--r--docbook/wsdg_src/WSDG_chapter_env_intro.xml6
-rw-r--r--docbook/wsdg_src/WSDG_chapter_quick_setup.xml6
-rw-r--r--docbook/wsdg_src/WSDG_chapter_sources.xml10
-rw-r--r--docbook/wsdg_src/WSDG_chapter_tools.xml4
-rw-r--r--docbook/wsdg_src/WSDG_chapter_userinterface.xml4
-rw-r--r--docbook/wsdg_src/WSDG_chapter_works.xml2
7 files changed, 20 insertions, 20 deletions
diff --git a/docbook/wsdg_src/WSDG_chapter_dissection.xml b/docbook/wsdg_src/WSDG_chapter_dissection.xml
index e01418543b..3637e2d0e2 100644
--- a/docbook/wsdg_src/WSDG_chapter_dissection.xml
+++ b/docbook/wsdg_src/WSDG_chapter_dissection.xml
@@ -908,7 +908,7 @@ static gint *ett[] =
You also cannot assume that a TCP packet contains only one application layer message
and that the message header is at the start of your TCP payload.
More than one messages can be transmitted in one TCP packet,
- so that a message can start at an abitrary position.
+ so that a message can start at an arbitrary position.
</para>
<para>
@@ -963,7 +963,7 @@ static guint get_foo_message_len(packet_info *pinfo, tvbuff_t *tvb, int offset)
<para>
The parameters <parameter>tvb</parameter>, <parameter>pinfo</parameter> and <parameter>tree</parameter>
are just handed over to <function>tcp_dissect_pdus()</function>.
- The 4th parameter is a flag to indicate if the data should be reassebled or not. This could be set
+ The 4th parameter is a flag to indicate if the data should be reassembled or not. This could be set
according to a dissector preference as well.
Parameter 5 indicates how much data has at least to be available to be able to determine the length
of the foo message.
@@ -982,7 +982,7 @@ static guint get_foo_message_len(packet_info *pinfo, tvbuff_t *tvb, int offset)
<para>
A tap is basically a way of allowing other items to see whats happening as
a protocol is dissected. A tap is registered with the main program, and
- then called on each dissection. Some arbritary protocol specific data
+ then called on each dissection. Some arbitrary protocol specific data
is provided with the routine that can be used.
</para>
<para>
@@ -999,7 +999,7 @@ static int foo_tap = -1;
struct FooTap {
gint packet_type;
- gint priorty;
+ gint priority;
...
};
...
diff --git a/docbook/wsdg_src/WSDG_chapter_env_intro.xml b/docbook/wsdg_src/WSDG_chapter_env_intro.xml
index d939969c7a..8f1e6e58ee 100644
--- a/docbook/wsdg_src/WSDG_chapter_env_intro.xml
+++ b/docbook/wsdg_src/WSDG_chapter_env_intro.xml
@@ -157,7 +157,7 @@
<section><title>Open Source Software</title>
<para>
Wireshark is an open source software project, and is released under
- the <ulink url="&GPLWebsite;">GNU General Public Licence</ulink> (GPL).
+ the <ulink url="&GPLWebsite;">GNU General Public License</ulink> (GPL).
You can freely use Wireshark on any number of computers you like, without
worrying about license keys or fees or such. In addition, all source
code is freely available under the GPL. Because of that, it is very easy
@@ -508,7 +508,7 @@
<varlistentry><term><command>wireshark-bugs</command></term>
<listitem>
<para>
- This list is for Wireshark developers. Everytime a change to the bug
+ This list is for Wireshark developers. Every time a change to the bug
database occurs, a mail to this mailing list is generated.
If you want to be notified about all the changes to the bug
database, join this list. Details about the bug database can be
@@ -519,7 +519,7 @@
<varlistentry><term><command>wireshark-commits</command></term>
<listitem>
<para>
- This list is for Wireshark developers. Everytime a change to the SVN
+ This list is for Wireshark developers. Every time a change to the SVN
repository is checked in, a mail to this mailing list is generated.
If you want to be notified about all the changes to the SVN
repository, join this list. Details about the SVN repository can be
diff --git a/docbook/wsdg_src/WSDG_chapter_quick_setup.xml b/docbook/wsdg_src/WSDG_chapter_quick_setup.xml
index 1a82bf4a07..76ddebe34d 100644
--- a/docbook/wsdg_src/WSDG_chapter_quick_setup.xml
+++ b/docbook/wsdg_src/WSDG_chapter_quick_setup.xml
@@ -239,7 +239,7 @@
<xref linkend="ChToolsMSChain" />!</para>
<para>
<superscript>2</superscript>International Windows might use
- different values here, e.g. a german version uses
+ different values here, e.g. a German version uses
C:/Programme - take this also in account where C:\Program
Files appears elsewhere</para>
</section>
@@ -274,9 +274,9 @@
<xref linkend="ChToolsMSChain" />!</para>
<para>
<superscript>2</superscript>International Windows might use
- different values here, e.g. a german version uses
+ different values here, e.g. a German version uses
C:/Programme - take this also in account where C:\Program
- Files appears elsewhereNote: You need to repeat steps 1 - 4
+ Files appears elsewhere. Note: You need to repeat steps 1 - 4
each time you open a new cmd.exe!</para>
</section>
<section id="ChToolsWin32Verify">
diff --git a/docbook/wsdg_src/WSDG_chapter_sources.xml b/docbook/wsdg_src/WSDG_chapter_sources.xml
index e9d8bb4f2e..906301f999 100644
--- a/docbook/wsdg_src/WSDG_chapter_sources.xml
+++ b/docbook/wsdg_src/WSDG_chapter_sources.xml
@@ -37,7 +37,7 @@
Subversion repository located at a server at the wireshark.org domain.
</para>
<para>
- To qoute the Subversion book about "What is Subversion?":
+ To quote the Subversion book about "What is Subversion?":
</para>
<para>
<quote>Subversion is a free/open-source version control system. That is,
@@ -98,7 +98,7 @@
separate from the main repository.
It may take several minutes for committed changes to appear in the
public repository - so please be patient for a few minutes if you
- desperately need a code change that was commited to the repository
+ desperately need a code change that was committed to the repository
very recently.
</para>
@@ -688,7 +688,7 @@ Index: file.h
<tbody>
<row>
<entry>-N</entry>
- <entry>Add new files when used in conjuction with -r.</entry>
+ <entry>Add new files when used in conjunction with -r.</entry>
</row>
<row>
<entry>-r</entry>
@@ -885,7 +885,7 @@ Index: file.h
another patch.
</para></listitem>
<listitem><para>
- You don't get any reponse to your patch (even after a few days or so).
+ You don't get any response to your patch (even after a few days or so).
Possible reason: your patch might simply get lost, as all core
maintainers were busy at that time and forgot to look at your patch.
Simply send a mail asking if the patch was forgotten or if someone is
@@ -1108,7 +1108,7 @@ $Id&#36;
<para>
The RPM is built using rpmbuild (http://www.rpm.org/), which comes as standard on many flavours of Linux, including
Red Hat and Fedora. The process creates a clean build environment in <filename>packaging/rpm/BUILD</filename> every
- time the RPM is built. The settings controlling the build are in <filename>packaging/rpm/SPECS/wireshark.spec.in</filename>. After editing the settings in this file, <filename>./configure</filename> must be run again in the wireshark direcrory to generate the actual specification script.
+ time the RPM is built. The settings controlling the build are in <filename>packaging/rpm/SPECS/wireshark.spec.in</filename>. After editing the settings in this file, <filename>./configure</filename> must be run again in the wireshark directory to generate the actual specification script.
</para>
<warning><title>Warn!</title><para>
The SPEC file contains settings for the <filename>configure</filename> used to set the RPM build environment. These are
diff --git a/docbook/wsdg_src/WSDG_chapter_tools.xml b/docbook/wsdg_src/WSDG_chapter_tools.xml
index 3a623239b0..a1d57a1ef5 100644
--- a/docbook/wsdg_src/WSDG_chapter_tools.xml
+++ b/docbook/wsdg_src/WSDG_chapter_tools.xml
@@ -1086,7 +1086,7 @@ Stop.]]>
available.</para>
<para>You can get it free of charge at:
<ulink url="http://www.microsoft.com/whdc/devtools/debugging/default.mspx" /> (as
- links to microsoft pages change from time to time, search
+ links to Microsoft pages change from time to time, search
for "Debugging Tools" at their page if this link should be
outdated).</para>
</section>
@@ -1153,7 +1153,7 @@ Copyright (C) 2005 Free Software Foundation, Inc.]]>
<ulink url="http://python.org/download/" />to download the
latest stable release. You can download a setup there, which
will install the python system typically into
- <filename>C:\Python25</filename> or similiar.</para>
+ <filename>C:\Python25</filename> or similar.</para>
<para>After correct installation, typing at the command
line prompt (cmd.exe) - this must be entered in the Python
directory, the installer won't set the PATH:</para>
diff --git a/docbook/wsdg_src/WSDG_chapter_userinterface.xml b/docbook/wsdg_src/WSDG_chapter_userinterface.xml
index 132dafeb86..0ca6258f32 100644
--- a/docbook/wsdg_src/WSDG_chapter_userinterface.xml
+++ b/docbook/wsdg_src/WSDG_chapter_userinterface.xml
@@ -40,7 +40,7 @@
finished)
</para></listitem>
</itemizedlist>
- This chapter is focussed on the Wireshark frontend, and especially on
+ This chapter is focused on the Wireshark frontend, and especially on
the GTK specific things.
</para>
</section>
@@ -85,7 +85,7 @@
</para>
<para>
GTK 1.x was the first major release. Today there are 1.2.x and 1.3.x
- versions "in the wild", with only very limitted differences in the API.
+ versions "in the wild", with only very limited differences in the API.
</para>
<para>
Advantages (compared to GTK 2.x):
diff --git a/docbook/wsdg_src/WSDG_chapter_works.xml b/docbook/wsdg_src/WSDG_chapter_works.xml
index 00eba62482..adc656b755 100644
--- a/docbook/wsdg_src/WSDG_chapter_works.xml
+++ b/docbook/wsdg_src/WSDG_chapter_works.xml
@@ -14,7 +14,7 @@
<section id="ChWorksOverview">
<title>Overview</title>
<para>
- The following will give you a simplified overview of Wiresharks function blocks:
+ The following will give you a simplified overview of Wireshark's function blocks:
<figure id="ChWorksFigOverview">
<title>
<application>Wireshark</application> function blocks.