Bug 106386 Correct misspellings in source code

patch by unknown@simplemachines.org r=timeless rs=brendan

diff --git a/Bugzilla/User.pm b/Bugzilla/User.pm
index 0cca45682f6472e649644bfae33ef4db03fd995c..d35077a4bf27828aaa62964ffa87c703320cd9fb 100644 (file)
--- a/Bugzilla/User.pm
+++ b/Bugzilla/User.pm
@@ -1488,7 +1488,7 @@ the page footer, and C<0> otherwise.
 
 =item C<identity>
 
-Retruns a string for the identity of the user. This will be of the form
+Returns a string for the identity of the user. This will be of the form
 C<name E<lt>emailE<gt>> if the user has specified a name, and C<email>
 otherwise.
 

diff --git a/contrib/README.Mailif b/contrib/README.Mailif
index 8b66044388f2418272277abb424b427d6c4be1fa..0c65cef83e56d2cc70f3892d3a2603be1034952d 100644 (file)
--- a/contrib/README.Mailif
+++ b/contrib/README.Mailif
@@ -54,7 +54,7 @@ Search the script after 'default' - you find some default-Settings for bug
 reports, which are used, if the sender did not send a field for it. The defaults
 should be checked and changed.
 
-Thats hopefully all, we will come up with any configuration file or something.
+That's hopefully all, we will come up with any configuration file or something.
 
 
 If your mail works, your script will insert mails from now on.

diff --git a/contrib/bug_email.pl b/contrib/bug_email.pl
index 98b8d157e2340d12d8f9fa7d9037d8fde917a26c..6844fa279e5b561a7d940bd4ffba67ef928b9826 100755 (executable)
--- a/contrib/bug_email.pl
+++ b/contrib/bug_email.pl
@@ -38,7 +38,7 @@
 #
 # You need to work with bug_email.pl the MIME::Parser installed.
 # 
-# $Id: bug_email.pl,v 1.29 2005/08/26 23:11:32 bugreport%peshkin.net Exp $
+# $Id: bug_email.pl,v 1.30 2005/11/25 19:47:38 timeless%mozdev.org Exp $
 ###############################################################
 
 # 02/12/2000 (SML)
@@ -193,7 +193,7 @@ sub horLine( )
 # Check if $Name is in $GroupName
 
 # This is no more CreateBugs group, so I'm using this routine to just determine if the user is
-# in the database.  Eventually, here should be a seperate routine or renamed, or something (SML)
+# in the database.  Eventually, here should be a separate routine or renamed, or something (SML)
 sub CheckPermissions {
     my ($GroupName, $Name) = @_;
     
@@ -451,7 +451,7 @@ sub FetchAllSQLData( )
 # 0 - Its an error, but bugzilla can process the bug. The user should
 #     handle that as a warning.
 # 
-# 1 - Its a real bug. Bugzilla cant store the bug. The mail has to be
+# 1 - It's a real bug. Bugzilla can't store the bug. The mail has to be
 #     resent.
 # 
 # 2 - Permission error: The user does not have the permission to send
@@ -465,7 +465,7 @@ sub BugMailError($ $ )
 {
     my ( $errflag, $text ) = @_;
 
-    # On permission error, dont sent all other Errors back -> just quit !
+    # On permission error, don't sent all other Errors back -> just quit !
     if( $errflag == 2 ) {            # Permission-Error
         Reply( $SenderShort, $Message_ID, "Bugzilla Error", "Permission denied.\n\n" .
                "You do not have the permissions to create a new bug. Sorry.\n" );
@@ -677,7 +677,7 @@ sub extractControls( $ )
         }
     }
 
-    # thats it.
+    # that's it.
     return( $backbody );
 }
 

diff --git a/contrib/bugmail_help.html b/contrib/bugmail_help.html
index a2f89f260402df7254ca303b4d6dc9668732cffc..1b43cd2b564d96cafe0c0d831b2061703f45af4f 100644 (file)
--- a/contrib/bugmail_help.html
+++ b/contrib/bugmail_help.html
@@ -39,7 +39,7 @@ You receive a reply mail with the new bug-ID if your request was ok.
 If not, you get a mail with 
 some help on the bugmail system and a specific analysis of your request.
 <P>
-Please dont refuse to send one or two wrong mails, you will get all the information 
+Please don't refuse to send one or two wrong mails, you will get all the information 
 you need in the replies, and <I>only</I> in the mail replies. The information on this
 page, concerning available products, versions and so on, is not dynamicly generated and 
 may  be old therefore.
@@ -91,23 +91,23 @@ hopefully valid value.
        <TR>
                <TD>@rep_platform</TD>
                <TD>The desired platform</TD>
-               <TD>no.<br>If you dont give a value, this field is set to <I>All</I>.</TD>
+               <TD>no.<br>If you don't give a value, this field is set to <I>All</I>.</TD>
        </TR>
        <TR>
                <TD>@bug_severity</TD>
                <TD>The severity of the bug</TD>
-               <TD>no. <br> If you dont give a value, this field is set to 
+               <TD>no. <br> If you don't give a value, this field is set to 
                <I>normal</I></TD>
        </TR>
        <TR>
                <TD>@priority</TD>
                <TD>The priority of the bug</TD>
-               <TD>no.<br>If you dont give a value, this field is set to <I>P3</I></TD>
+               <TD>no.<br>If you don't give a value, this field is set to <I>P3</I></TD>
        </TR>
        <TR>
                <TD>@op_sys</TD>
                <TD>The operating system</TD>
-               <TD>no.<br>If you dont give a value, this field is set to <I>Linux</I>.</TD>
+               <TD>no.<br>If you don't give a value, this field is set to <I>Linux</I>.</TD>
        </TR>
        <TR>
                <TD>@assigned_to</TD>
@@ -150,7 +150,7 @@ Give string values for the most keys above. Some keywords  require special value
 <ol>
 <li>E-Mail adresses: If you want to set the qa-contact, specify a email-adress for @qa_contact. The email must be known by bugzilla of course.</li>
 <li>Listvalues: Most of the values have to be one of a list of valid values. Try by sending
-a mail and read the reply. Skip fields if you dont get help for them unless you dont know
+a mail and read the reply. Skip fields if you don't get help for them unless you don't know
 which values you may choose.</li>
 <li>free Text: The descriptions may be free text. </li>
 <li>Special: The field groupset may be specified in different in three different kinds:
@@ -181,7 +181,7 @@ Some of the values must be choosen from a list:<br>
 <p>
 
 After you have specified the required keywords and maybe some other value, you may 
-describe your bug. You dont need  a keyword for starting your bug description. All 
+describe your bug. You don't need  a keyword for starting your bug description. All 
 text which follows the keyword block is handled as long description of the bug.
 <p>
 
@@ -198,7 +198,7 @@ the attachment in bugzilla.
 
 <H1><A NAME="examplemail">Example Mail</A></H1>
 
-See the example of the mail <b>body</b> (Dont forget to specify the short description
+See the example of the mail <b>body</b> (Don't forget to specify the short description
 in the mail subject):<hr><pre>
 
   @product      = Bugzilla

diff --git a/contrib/gnatsparse/gnatsparse.py b/contrib/gnatsparse/gnatsparse.py
index b317b240d187631d4314d4ff1a6ad39dd356a4b1..5315ee8b0b17a4448a0113a28d71ec7ab880c7dd 100755 (executable)
--- a/contrib/gnatsparse/gnatsparse.py
+++ b/contrib/gnatsparse/gnatsparse.py
@@ -270,7 +270,7 @@ def load_responsible(fname):
     rfp.close()
 
 def split_csl(list):
-    """ Split a comma seperated list """
+    """ Split a comma separated list """
     newlist = re.split(r"""\s*,\s*""", list)
     return newlist
 

diff --git a/process_bug.cgi b/process_bug.cgi
index e56793fcd63f14e25c44e17d4c126252556e624f..77496f2a38952b5ef0dab3354b316becc4d49e64 100755 (executable)
--- a/process_bug.cgi
+++ b/process_bug.cgi
@@ -341,7 +341,7 @@ if (((defined $cgi->param('id') && $cgi->param('product') ne $oldproduct)
             my %defaults;
             # We set the defaults to these fields to the old value,
             # if its a valid option, otherwise we use the default where
-            # thats appropriate
+            # that's appropriate
             $vars->{'versions'} = $::versions{$prod};
             if ($vok) {
                 $defaults{'version'} = $cgi->param('version');