fixed various typos

svn path=/trunk/; revision=10220

5 files changed, 44 insertions, 43 deletions

diff --git a/help/capture_filters.txt b/help/capture_filters.txt
index 204c41d8af..b269d9dfba 100644
--- a/help/capture_filters.txt
+++ b/help/capture_filters.txt
@@ -8,8 +8,8 @@ Note: This capture filter language is different from the one used for the Ethere
 
 -------------------------------------------------
 
-Some common examples:
----------------------
+Some common examples
+--------------------
 Example Ethernet: capture all traffic to and from the Ethernet address 08:00:08:15:ca:fe
 
 ether host 08:00:08:15:ca:fe
@@ -30,8 +30,8 @@ Beware: if you capture TCP/IP traffic with the primitives "host" or "port", you
 
 -------------------------------------------------
 
-Capture Filter Syntax:
-----------------------
+Capture Filter Syntax
+---------------------
 The following is a short description of the capture filter language syntax. For a further reference, have a look at: http://www.tcpdump.org/tcpdump_man.html
 
 A capture filter takes the form of a series of primitive expressions, connected by conjunctions (and/or) and optionally preceeded by not:
@@ -46,7 +46,7 @@ This primitive allows you to filter on a host IP address or name. You can option
 
 ether [src|dst] host <ehost>
 
-This primitive allows you to filter on Ethernet host addresses. You can optionally includethe keyword src|dst between the keywords ether and host to specify that you are only interested in source or destination addresses. If these are not present, packets where the specified address appears in either the source or destination address will be selected.
+This primitive allows you to filter on Ethernet host addresses. You can optionally include the keyword src|dst between the keywords ether and host to specify that you are only interested in source or destination addresses. If these are not present, packets where the specified address appears in either the source or destination address will be selected.
 
 gateway host <host>
 
@@ -54,7 +54,7 @@ This primitive allows you to filter on packets that used host as a gateway. That
 
 [src|dst] net <net> [{mask <mask>}|{len <len>}]
 
-This primitive allows you to filter on network numbers. You can optionally preceed this primitive with the keyword src|dst to specify that you are only interested in a source or destination network. If neither of these are present, packets will be selected that have the specified network in either the source or destination address. In addition, you can specify either the netmask or the CIDR prefix for the network if they are different from your own.
+This primitive allows you to filter on network numbers. You can optionally preceed this primitive with the keyword src|dst to specify that you are only interested in a source or destination network. If neither of these are present, packets will be selected that have the specified network in either the source or destination address. In addition, you can specify either the netmask or the CIDR (Classless Inter-Domain Routing) prefix for the network if they are different from your own.
 
 [tcp|udp] [src|dst] port <port>
 
diff --git a/help/capturing.txt b/help/capturing.txt
index 9d0877ef22..3c553ebe4e 100644
--- a/help/capturing.txt
+++ b/help/capturing.txt
@@ -29,9 +29,9 @@ Filtering options
 
 Storing options
 ---------------
--File: you can choose the file to which captured data will be written. If you don't enter something here a temporary file will be used.
+-File: You can choose the file to which captured data will be written. If you don't enter something here a temporary file will be used.
 
--Use ring buffer: Instead of using a single capture file, multiple files will be created. The generated filenames will contain a incrementing number and the start time of the capture. For example, if you choose "/foo.cap" in the "File" field, files like "/foo_00001_20040205110102.cap", "/foo_00002_20040205110102.cap", ... will be created.
+-Use ring buffer: Instead of using a single capture file, multiple files will be created. The generated filenames will contain an incrementing number and the start time of the capture. For example, if you choose "/foo.cap" in the "File" field, files like "/foo_00001_20040205110102.cap", "/foo_00002_20040205110102.cap", ... will be created.
 This feature can be useful if you do long term capturing, as working with a single capture file of several GB usually isn't very fast.
 
 Stop condition options
@@ -40,12 +40,12 @@ These three fields should be obvious; the capture process will be automatically
 
 Display while capturing options
 -------------------------------
--Update List of packets in real time: Using this will show the captured packets immediately on the main screen.
+-Update list of packets in real time: Using this will show the captured packets immediately on the main screen.
 Please note: this will slow down capturing, so increased packet drops might appear.
 
 -Automatic scrolling in live capture: This will scroll the "Packet List" automatically to the latest captured packet, when the "Update List of packets in real time" option is used.
 
--Name resolution: perform the corresponding name resolution while capturing
+-Name resolution: perform the corresponding name resolution while capturing.
 
 
 
@@ -55,7 +55,7 @@ When your network traffic is high, you might need to take some steps to ensure E
 
 When Etheral cannot keep up, packets are dropped. To help avoid this as much as possible:
 
-a) Don't use the "Update List of packets in real time" option (see above). This has a significant performance penalty.
+a) Don't use the "Update list of packets in real time" option (see above). This has a significant performance penalty.
 
 b) Close other programs that might slow down your system, such as virus scanner software, server processes, etc.
 
@@ -73,10 +73,10 @@ Long term capturing
 -------------------
 By "Long term capturing", it's meant to capture data from a network for several hours or even days. Long term capturing will usually result in huge capture files, being hundreds of MB's or even several GB's in size!
 
-Before doing a long term capture, get familiar with the options to use for it, as you might not get what you desire. Doing a long term capture not getting the results needed, is usually wasting a lot of time ;-)
+Before doing a long term capture, get familiar with the options to use for it, as you might not get what you desire. Doing a long term capture not getting the results needed, is usually wasting a lot of time. ;-)
 
 Rules of thumb for this task:
--Use the ring buffer feature when you expect very large capture files
--Don't use the "Update list of packets in real time" option
--Set an appropriate capture filter, when you are only interested in some special packets from the net
+-Use the ring buffer feature when you expect very large capture files.
+-Don't use the "Update list of packets in real time" option.
+-Set an appropriate capture filter, when you are only interested in some special packets from the net.
 
diff --git a/help/display_filters.txt b/help/display_filters.txt
index 0614a03ab2..b3f2c21a35 100644
--- a/help/display_filters.txt
+++ b/help/display_filters.txt
@@ -2,9 +2,9 @@ Filtering packets while viewing
 -------------------------------
 After capturing packets or loading some network traffic from a file, Ethereal will display the packet data immediately on the screen.
 
-Using display filters, you can choose which packets should (not) be shown on the screen. This is useful to reduce the "noice" usually on the network, showing only the packets you want to. So you can concentrate on the things you are really interested in. 
+Using display filters, you can choose which packets should (not) be shown on the screen. This is useful to reduce the "noise" usually on the network, showing only the packets you want to. So you can concentrate on the things you are really interested in. 
 
-The display filter will not affect the data captured, it will only select for you which packets of the captured data are displayed on the screen.
+The display filter will not affect the data captured, it will only select which packets of the captured data are displayed on the screen.
 
 Everytime you change the filter string, all packets will be reread from the capture file (or from memory), and processed by the display filter "machine". Packet by packet, this "machine" is asked, if this particular packet should be shown or not.
 
@@ -14,8 +14,8 @@ Note: This display filter language is different from the one used for the Ethere
 
 -------------------------------------------------
 
-Some common examples:
----------------------
+Some common examples
+--------------------
 Example Ethernet: display all traffic to and from the Ethernet address 08.00.08.15.ca.fe
 
 eth.addr==08.00.08.15.ca.fe
@@ -36,5 +36,6 @@ Beware: The filter string builds a logical expression, which must be true to sho
 
 -------------------------------------------------
 
-Hints:
+Hint
+----
 Filtering can lead to side effects, which are sometimes not obvious at first sight. Example: If you capture TCP/IP traffic with the primitive "ip", you will not see the ARP traffic belonging to it, as this is a lower protocol layer than IP!
diff --git a/help/getting_started.txt b/help/getting_started.txt
index b997a4b96a..379646a7f6 100644
--- a/help/getting_started.txt
+++ b/help/getting_started.txt
@@ -21,7 +21,7 @@ Many of the features available in the menu will also be on the main toolbar.
 
 First capture file
 ------------------
-The first thing you probably want to do is look at some captured network data/packets:
+The first thing you probably want to do is look at some captured network data/packets.
 This can be achieved by two methods:
 
 -open an already existing capture file
@@ -83,6 +83,6 @@ Conclusion
 ----------
 There are a lot more features than described here. Just have a look at the menus to see them all. :-)
 
-For more information about Ethereal, see: "http://www.ethereal.com". You can get a users' guide and other useful information there.
+For more information about Ethereal, see: "http://www.ethereal.com". You can get a user's guide and other useful information there.
 
 We hope this helped you with the first steps of using Ethereal and that you will enjoy using this program.
diff --git a/help/well_known.txt b/help/well_known.txt
index a71db2e82b..976d0f40bd 100644
--- a/help/well_known.txt
+++ b/help/well_known.txt
@@ -3,48 +3,48 @@ Well known things
 Following is a simple selection of well known numbers, useful when working with Ethereal. This is not intended to replace comprehensive network documentation.
 
 
-Ethernet addresses [RFC 1700]:
-------------------------------
+Ethernet addresses [RFC 1700]
+-----------------------------
 ff:ff:ff:ff:ff:ff Broadcast, send to all nodes
 
-Ethernet type field:
---------------------
+Ethernet type field
+-------------------
  0 -   45 invalid
 46 - 1500 length field (Ethernet-II)
    0x0800 IP(V4), internet protocol version 4
    0x0806 ARP, address resolution protocol
    0x8137 IPX, internet packet exchange (Novell)
 
-IP addresses:
--------------
+IP addresses
+------------
 127.0.0.0 - 127.255.255.255 local loopback, should never appear on the network
 224.0.0.0 - 239.255.255.255 multicasting [RFC1112], transmission to a host group
             255.255.255.255 limited Broadcast, send to all nodes
 
-IP private addresses [RFC 1597]:
---------------------------------
+IP private addresses [RFC 1597]
+-------------------------------
 The following IP addresses will not be routed, and should be used for private networks:
    10.0.0.0 -  10.255.255.255 private in Class A
  172.16.0.0 -  172.31.255.255 private in Class B
 192.168.0.0 - 192.168.255.255 private in Class C
 
-IP address classes:
--------------------
+IP address classes
+------------------
   0.1.0.0 - 126.0.0.0       Class A
 128.0.0.0 - 191.255.0.0     Class B
 192.0.1.0 - 223.255.255.0   Class C
 224.0.0.0 - 239.255.255.255 Class D
 240.0.0.0 - 247.255.255.255 Class E
 
-IP protocols:
--------------
- 1 ICMP internet control message protocol v 4
- 6 TCP  transmission control protocol
-17 UDP  user datagram protocol
-58 ICMPv6 internet control message protocol v 6
+IP protocols
+------------
+ 1 ICMP 		internet control message protocol v 4
+ 6 TCP  		transmission control protocol
+17 UDP  		user datagram protocol
+58 ICMPv6 		internet control message protocol v 6
 
-TCP/UDP ports [RFC 1700]:
--------------------------
+TCP/UDP ports [RFC 1700]
+------------------------
   20 FTP-data   file transfer protocol
   21 FTP-ctrl   file transfer protocol
   22 SSH        secure shell
@@ -71,8 +71,8 @@ TCP/UDP ports [RFC 1700]:
 
 
 
-RFC References:
----------------
+RFC References
+--------------
 ARP     RFC  826 "An Ethernet Address Resolution Protocol"
 BOOTP   RFC  951 "BOOTSTRAP PROTOCOL (BOOTP)"
 CSLIP   RFC 1144 "Compressing TCP/IP Headers for Low-Speed Serial Links"
@@ -109,4 +109,4 @@ TELNET  RFC 1700 see: TELNET OPTIONS
 TFTP    RFC  783 "THE TFTP PROTOCOL (REVISION 2)"
 
 RFC 1166 "INTERNET NUMBERS" list of assigned IP addresses
-RFC 1700 "ASSIGNED NUMBERS" Various assigned numbers, e.g. TCP/UDP ports
+RFC 1700 "ASSIGNED NUMBERS" various assigned numbers, e.g. TCP/UDP ports