explicitely->explicitly

src/qtgui/main.cpp

@@ -172,7 +172,7 @@ static const char usage [] =
 "     -f : the query will be interpreted as a filename search\n"
 "     -l : the query will be interpreted as a query language string (default)\n"
 "     -t : terminal display: no gui. Results go to stdout. MUST be given\n"
-"          explicitely as -t (not ie, -at), and -q <query> MUST\n"
+"          explicitly as -t (not ie, -at), and -q <query> MUST\n"
 "          be last on the command line if this is used.\n"
 ;
 static void

src/rcldb/searchdata.h

@@ -64,7 +64,7 @@ class SearchDataClause;
 
   This is why the clauses also have an AND/OR/... type. 
 
-  A phrase clause could be added either explicitely or using double quotes:
+  A phrase clause could be added either explicitly or using double quotes:
   {SCLT_PHRASE, [this is a phrase]} or as {SCLT_XXX, ["this is a phrase"]}
 
  */

src/utils/mimeparse.cpp

@@ -54,7 +54,7 @@ using namespace std;
 //    headertype: value [; paramname=paramvalue] ...
 //
 // Value and paramvalues can be quoted strings, and there can be
-// comments too. Note that RFC2047 is explicitely forbidden for
+// comments too. Note that RFC2047 is explicitly forbidden for
 // parameter values (RFC2231 must be used), but I have seen it used
 // anyway (ie: thunderbird 1.0)
 //

src/utils/mimeparse.h

@@ -84,7 +84,7 @@ extern bool qp_decode(const string& in, string &out, char esc = '=');
  *
  * Example input:  Some words =?iso-8859-1?Q?RE=A0=3A_Smoke_Tests?= more input
  * 
- * Note that MIME parameter values are explicitely NOT to be encoded with
+ * Note that MIME parameter values are explicitly NOT to be encoded with
  * this encoding which is only for headers like Subject:, To:. But it
  * is sometimes used anyway...
  *