X-Git-Url: http://www.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Ffiltering_en-3.html;h=b14c853a78911ffacc7149e130a6d58db8e3fbbf;hb=cba7a181d14123afcf0c18149002526b8c463889;hp=aed01525ff1177c4dd9255325af3cf12ced7f4e2;hpb=60048475ad0657400d2f148da9aab566734e6645;p=spider.git

diff --git a/html/filtering_en-3.html b/html/filtering_en-3.html
index aed01525..b14c853a 100644
--- a/html/filtering_en-3.html
+++ b/html/filtering_en-3.html
@@ -19,10 +19,10 @@
 </H2>
 
 <P>A spot filter is one rule (a one line spot filter) or multiple rules (multiple 
-line spot filters) that a user can setup with-in DXSpider to control which 
+line spot filters) that a user can setup within DXSpider to control which 
 specific spot(s) are received at the shack console.  These configurable 
 filters/rules reside on the DXSpider node and are stored along with the user's 
-other information. Filters can be likened to a car wash . . . . . like cars; 
+other information. Filters can be likened to a car wash . . . . . like cars, 
 information goes in one end dirty, gets washed and comes out the other end 
 cleaned.</P>
 
@@ -41,7 +41,7 @@ down the drain to the infamous "bit-bucket."  </P>
 <H2><A NAME="ss3.2">3.2</A> <A HREF="filtering_en.html#toc3.2">How can filters be used? </A>
 </H2>
 
-<P>For example, let's say our local user has never owned a microphone in this life 
+<P>For example, let's say our local user has never owned a microphone in his life 
 and definitely doesn't want to see any of those useless SSB spots. Our user 
 simply sets up a basic filter to reject any SSB spots before they reach the 
 user's console.  Similarly, it's now the ARRL CW DX contest weekend, so not only