From Ville Skyttä: Spelling Fixes

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9591


svn path=/trunk/; revision=54387

2 files changed, 5 insertions, 5 deletions

diff --git a/help/capture_filters.txt b/help/capture_filters.txt
index 27b5154ace..a238f7d936 100644
--- a/help/capture_filters.txt
+++ b/help/capture_filters.txt
@@ -34,7 +34,7 @@ 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:
+A capture filter takes the form of a series of primitive expressions, connected by conjunctions (and/or) and optionally preceded by not:
 
 [not] primitive [and|or [not] primitive ...]
 
@@ -42,7 +42,7 @@ A primitive is simply one of the following:
 
 [src|dst] host <host>
 
-This primitive allows you to filter on a host IP address or name. You can optionally preceed the primitive with the keyword src|dst to specify that you are only interested in source or destination addresses. If these are not present, packets where the specified address appears as either the source or the destination address will be selected.
+This primitive allows you to filter on a host IP address or name. You can optionally precede the primitive with the keyword src|dst to specify that you are only interested in source or destination addresses. If these are not present, packets where the specified address appears as either the source or the destination address will be selected.
 
 ether [src|dst] host <ehost>
 
@@ -54,11 +54,11 @@ 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 (Classless Inter-Domain Routing) prefix for the network if they are different from your own.
+This primitive allows you to filter on network numbers. You can optionally precede 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>
 
-This primitive allows you to filter on TCP and UDP port numbers. You can optionally preceed this primitive with the keywords src|dst and tcp|udp which allow you to specify that you are only interested in source or destination ports and TCP or UDP packets respectively. The keywords tcp|udp must appear before src|dst.
+This primitive allows you to filter on TCP and UDP port numbers. You can optionally precede this primitive with the keywords src|dst and tcp|udp which allow you to specify that you are only interested in source or destination ports and TCP or UDP packets respectively. The keywords tcp|udp must appear before src|dst.
 If these are not specified, packets will be selected for both the TCP and UDP protocols and when the specified address appears in either the source or destination port field.
 
 less|greater <length>
diff --git a/help/display_filters.txt b/help/display_filters.txt
index 97a6e6dfef..28303ff04e 100644
--- a/help/display_filters.txt
+++ b/help/display_filters.txt
@@ -6,7 +6,7 @@ Using display filters, you can choose which packets should (not) be shown on the
 
 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.
+Every time 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.
 
 Wireshark offers a very powerful display filter language for this. It can be used for a wide range of purposes, from simply: "show only packets from a specific IP address", or on the other hand, to very complex filters like: "find all packets where a special application specific flag is set".