Ethereal-dev: [Ethereal-dev] Minor typos

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Gisle Vanem" <giva@xxxxxxxxx>
Date: Wed, 5 May 2004 17:14:50 +0200
Some typos in the doc/*.pod files.

Not sure about the lack of hyphenation;
should that be "time-stamp" (not "timestamp) and
"multi-cast", "filter-string" etc?

BTW. "Filterable" doesn't sound right. There must be a better
word for this.

--gv
--- ethereal-2004-05-05/doc/tethereal.pod	Sat May 01 23:33:44 2004
+++ doc/tethereal.pod	Wed May 05 16:51:11 2004
@@ -145,7 +145,7 @@
 pane in B<Ethereal>), although if it's printing packets as it captures
 them, rather than printing packets from a saved capture file, it won't
 print the "frame number" field.  If the B<-V> flag is specified, it
-prints intead a protocol tree, showing all the fields of all protocols
+prints instead a protocol tree, showing all the fields of all protocols
 in the packet.

 When writing packets to a file, B<Tethereal>, by default, writes the
@@ -350,7 +350,7 @@
 normally used when piping a live capture to a program or script, so that
 output for a packet shows up as soon as the packet is seen and
 dissected, it should work just as well as true line-buffering.  We do
-this as a workaround for a deficiency in the Microsoft Visual C++ C
+this as a work-around for a deficiency in the Microsoft Visual C++ C
 library.)

 This may be useful when piping the output of B<Tethereal> to another
@@ -689,7 +689,7 @@

 Count ITU-T H.225 messages and their reasons. In the first column you get a
 list of H.225 messages and H.225 message reasons, which occur in the current
-capture file. The number of occurences of each message or reason is displayed
+capture file. The number of occurrences of each message or reason is displayed
 in the second column.

 Example: use B<-z h225,counter>.
@@ -720,7 +720,7 @@
 B<-z> sip,stat[I<,filter>]

 This option will activate a counter for SIP messages. You will get the number
-of occurences of each SIP Method and of each SIP Status-Code. Additionally you
+of occurrences of each SIP Method and of each SIP Status-Code. Additionally you
 also get the number of resent SIP Messages (only for SIP over UDP).

 Example: use B<-z sip,stat>.
--- ethereal-2004-05-05/doc/ethereal.pod	Tue May 04 01:47:59 2004
+++ doc/ethereal.pod	Wed May 05 17:10:26 2004
@@ -428,7 +428,7 @@
 If the optional filterstring is provided, the stats will only be calculated
 on those calls that match that filter.
 Example: use B<-z "smb,srt,ip.addr==1.2.3.4"> to only collect stats for
-SMB packets echanged by the host at IP address 1.2.3.4 .
+SMB packets exchanged by the host at IP address 1.2.3.4 .

 B<-z> fc,srt[,I<filter>]

@@ -466,7 +466,7 @@
 If the optional filterstring is provided, the stats will only be calculated
 on those calls that match that filter.
 Example: use B<-z "ldap,srt,ip.addr==10.1.1.1"> to only collect stats for
-LDAP packets echanged by the host at IP address 10.1.1.1 .
+LDAP packets exchanged by the host at IP address 10.1.1.1 .

 The only LDAP command that are currently implemented and the stats will be available for are:
 BIND
@@ -523,7 +523,7 @@

 Count ITU-T H.225 messages and their reasons. In the first column you get a
 list of H.225 messages and H.225 message reasons, which occur in the current
-capture file. The number of occurences of each message or reason is displayed
+capture file. The number of occurrences of each message or reason is displayed
 in the second column.

 Example: use B<-z h225,counter>.
@@ -555,7 +555,7 @@
 B<-z> sip,stat[I<,filter>]

 This option will activate a counter for SIP messages. You will get the number
-of occurences of each SIP Method and of each SIP Status-Code. Additionally you
+of occurrences of each SIP Method and of each SIP Status-Code. Additionally you
 also get the number of resent SIP Messages (only for SIP over UDP).

 Example: use B<-z sip,stat>.
@@ -650,7 +650,7 @@
 displayed in the packet list pane.  Display filters will not affect or
 hide these packets.

-If there is a column displayed for "Culmulative Bytes" this counter will
+If there is a column displayed for "Cumulative Bytes" this counter will
 be reset at every Time Reference packet.

 =item Edit:Time Reference:Find Next
@@ -740,7 +740,7 @@

 =over

-=item How Colorization Works
+=item How Colorisation Works

 Packets are colored according to a list of color filters. Each filter
 consists of a name, a filter expression and a coloration. A packet is
@@ -902,7 +902,7 @@

 Create a display filter, or add to the display filter strip at the
 bottom, a display filter based on the data currently highlighted in the
-packe details, and apply the filter.
+packet details, and apply the filter.

 If that data is a field that can be tested in a display filter
 expression, the display filter will test that field; otherwise, the
@@ -1021,7 +1021,7 @@

 Below the drawing area and the scrollbar are the controls.  On the
 bottom left there will be five similar sets of controls to control each
-induvidual graph such as "Display:<button>" which button will toggle
+individual graph such as "Display:<button>" which button will toggle
 that individual graph on/off.  If <button> is ticked, the graph will be
 displayed.  "Color:<color>" which is just a button to show which color
 will be used to draw that graph (color is only available in Gtk2
@@ -1054,7 +1054,7 @@
 interval will be in the drawing area.  The default is 5 pixels per tick.

 "Y-scale:" controls the max value for the y-axis.  Default value is
-"auto" which means that B<Ethereal> will try to adjust the maxvalue
+"auto" which means that B<Ethereal> will try to adjust the max-value
 automatically.

 "advanced..." If Unit:advanced...  is selected the window will display
@@ -1065,7 +1065,7 @@

 The following restrictions apply to type and field combinations:
 SUM: available for all types of integers and will calculate the SUM of all
-	occurences of this field in teh capture. Note that some field can
+	occurrences of this field in teh capture. Note that some field can
 	occur multiple times in the same packet and then all instances will
 	be summed up.
 	Example: 'tcp.len' which will count the amount of payload data
@@ -1073,7 +1073,7 @@
 COUNT: available for all field types. This will COUNT the number of times
 	a certain field occurs in each interval. Note that some fields
 	may occur multiple times in each packet and if that is the case
-	then each instance willb e counted independently and COUNT
+	then each instance will be counted independently and COUNT
 	will be greater than the number of packets.
 MAX: available for all integer and relative time fields. This will calculate
 	the max seen integer/time value seen for the field during the interval.
@@ -1097,14 +1097,14 @@


 Example of advanced:
-Display how the average packetsize from host a.b.c.d changes over time.
+Display how the average packet-size from host a.b.c.d changes over time.

 Set first graph to   filter:ip.addr==a.b.c.d&&frame.pkt_len  Calc:AVG frame.pkt_len


 LOAD:
 The LOAD io-stat type is very different from anything you have ever seen
-before! While the response times themself as plotted by MIN,MAX,AVG are
+before! While the response times themselves as plotted by MIN,MAX,AVG are
 indications on the Server load (which affects the Server response time),
 the LOAD measurement measures the Client LOAD.
 What this measures is how much workload the client generates,
@@ -1254,7 +1254,7 @@

 Count ITU-T H.225 messages and their reasons. In the first column you get a
 list of H.225 messages and H.225 message reasons, which occur in the current
-capture file. The number of occurences of each message or reason will be displayed
+capture file. The number of occurrences of each message or reason will be displayed
 in the second column.
 This window opened will update in semi-real time to reflect changes when
 doing live captures or when reading new capture files into B<Ethereal>.
@@ -1265,7 +1265,7 @@

 =item Statistics:SIP

-Activate a counter for SIP messages. You will get the number of occurences of each
+Activate a counter for SIP messages. You will get the number of occurrences of each
 SIP Method and of each SIP Status-Code. Additionally you also get the number of
 resent SIP Messages (only for SIP over UDP).