osmocom
/
wireshark
14
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Some cleanup for Chapters 5 & 6: typos, spelling and minor rewording/additions. 

svn path=/trunk/; revision=22842
This commit is contained in:
Bill Meier 2007-09-11 14:36:09 +00:00
parent 7e1692e230
commit 3cada3d2cb
2 changed files with 25 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docbook/wsug_src/WSUG_chapter_io.xml
View File

@ -76,7 +76,7 @@
<para>
The appearance of this dialog depends on the system and GTK+ toolkit
version used. However, the functionality remains basically the same
on either system.
on any particular system.
</para>
</note>
@ -137,12 +137,12 @@
</listitem>
</itemizedlist>
<tip><title>Save a lot of time on huge capture files!</title>
<tip><title>Save a lot of time loading huge capture files!</title>
<para>
You can change the display filter and name resolution settings later
while viewing the packets.
However, for huge capture files it can take a significant amount of
extra time changing these settings later, so in such situations it can
However, loading huge capture files can take a significant amount of
extra time if these settings are changed later, so in such situations it can
be a good idea to set at least the filter in advance here.
</para>
</tip>
@ -306,7 +306,7 @@
<listitem><para>Catapult DCT2000 .out files</para></listitem>
</itemizedlist>
</para>
<note><title>Open a file may fail due to invalid packet types!</title>
<note><title>Opening a file may fail due to invalid packet types!</title>
<para>
It may not be possible to read some formats dependent on the packet types
captured. Ethernet captures are usually supported for most file formats,
@ -346,7 +346,7 @@
<para>
The appearance of this dialog depends on the system and GTK+ toolkit
version used. However, the functionality remains basically the same
on either system.
on any particular system.
</para>
</note>
@ -507,7 +507,7 @@
</para>
<warning><title>File formats have different time stamp accuracies!</title>
<para>
Saving from the currently used to a different file format may reduce the
Saving from the currently used file format to a different format may reduce the
time stamp accuracy, see the <xref linkend="ChAdvTimestamps"/> for details.
</para>
</warning>
@ -702,8 +702,8 @@
</para>
<para>
To find the files of a file set, Wireshark scans the directory where the
currently loaded file resides and scans for files matching the same filename
pattern (prefix and suffix) than the currently loaded file.
currently loaded file resides and scans for files matching the filename
pattern (prefix and suffix) of the currently loaded file.
</para>
<para>
This simple mechanism usually works well, but has its drawbacks. If several
@ -1057,8 +1057,8 @@
<listitem>
<para>
<command>Output to file:</command> specifies that printing
be done to a file, which name is entered in the field or selected
using the browse button.
be done to a file, using the filename entered in the field or selected
with the browse button.
</para>
<para>
This field is where you enter the <command>file</command> to

27
docbook/wsug_src/WSUG_chapter_work.xml
View File

@ -35,7 +35,7 @@
<para>
In addition, you can view individual packets in a separate window as
shown in <xref linkend="ChWorkPacketSepView"/>. Do this by selecting the
packet you are interested in the packet list pane, and then
packet in which you are interested in the packet list pane, and then
select "Show Packet in New Windows" from the Display menu. This
allows you to easily compare two or even more packets.
<figure id="ChWorkPacketSepView">
@ -446,7 +446,6 @@
<para>
Prepare and apply a display filter based on the currently
selected item.
name.
</para>
</entry>
</row>
@ -581,8 +580,8 @@
</itemizedlist>
</para>
<para>
To select packets based on protocol type, simply type the protocol you
are interested in in the <command>Filter:</command> field in the filter
To select packets based on protocol type, simply type the protocol in which you
are interested in the <command>Filter:</command> field in the filter
toolbar of the Wireshark window and press enter to initiate
the filter. <xref linkend="ChWorkTCPFilter"/> shows an example of what
happens when you type <command>tcp</command> in the filter field.
@ -636,8 +635,8 @@
<section id="ChWorkBuildDisplayFilterSection">
<title>Building display filter expressions</title>
<para>
Wireshark provides a simple but powerful display filter language that you
can build quite complex filter expressions with. You can compare
Wireshark provides a simple but powerful display filter language that allows you
to build quite complex filter expressions. You can compare
values in packets as well as combine expressions into more
specific expressions. The following sections provide more
information on doing this.
@ -997,7 +996,9 @@ eth.src[1-2] == 00:83
<para>
Select a protocol field from the protocol field tree.
Every protocol with filterable fields is listed at the
top level. By clicking on the "+" next to a protocol name
top level. (You can search for a particular protocol
entry by entering the first few letters of the protocol name).
By clicking on the "+" next to a protocol name
you can get a list of the field names available for filtering
for that protocol.
</para>
@ -1125,7 +1126,7 @@ eth.src[1-2] == 00:83
<listitem>
<para>
You can select a filter from this list (which will fill in the
filter name and filter string in the fields down the bottom of the
filter name and filter string in the fields down at the bottom of the
dialog box).
</para>
</listitem>
@ -1252,12 +1253,12 @@ eth.src[1-2] == 00:83
</itemizedlist>
</para>
<para>
The value to be found will by syntax checked while you type it in. If the
syntax check of your value succeeded, the background of the entry field
The value to be found will be syntax checked while you type it in. If the
syntax check of your value succeeds, the background of the entry field
will turn green, if it fails, it will turn red.
</para>
<para>
You can choose the direction to be searched for:
You can choose the search direction:
<itemizedlist>
<listitem>
<para><command>Up</command></para>
@ -1274,8 +1275,8 @@ eth.src[1-2] == 00:83
</section>
<section><title>The "Find Next" command</title>
<para>
"Find Next" will continue searching with the same options like in the last
"Find Packet" run.
"Find Next" will continue searching with the same options used in the last
"Find Packet".
</para>
</section>
<section><title>The "Find Previous" command</title>