Last of the spelling fixed

cde/programs/dtmail/libDtMail/Common/IO.C

@@ -931,7 +931,7 @@ struct vmount   **vmountpp)     /* place to tell where buffer is */
 /*
  * perform the QUERY mntctl - if it returns > 0, that is the
  * number of vmount structures in the buffer.  If it returns
- * -1, an error occured.  If it returned 0, then look in
+ * -1, an error occurred.  If it returned 0, then look in
  * first word of buffer for needed size.
  */
         if ((nmounts = mntctl(MCTL_QUERY, size, (caddr_t)vm)) > 0) {

cde/programs/dtmail/libDtMail/Common/libDtMail.msg

@@ -21,7 +21,7 @@ $quote "
 
 $set 1 libDtMail API set
 $ // DTME_NoError
-1 "No error occured."
+1 "No error occurred."
 
 $ // DTME_AlreadyLocked
 2 "The folder is locked by another session."

cde/programs/dtmail/libDtMail/RFC/MIMEBodyPart.C

@@ -631,7 +631,7 @@ MIMEBodyPart::loadBody(DtMailEnv & error)
 // March 25, 1997
 // The Content-Disposition field has been designated as the primary 
 // header field for transmitting file names.  See RFC 1806.  Therefore
-// the algorithm has bee updated as follows.
+// the algorithm has been updated as follows.
 //
 // 1. DtMail checks the following headers for the "filename" for a body part:
 //	o The "filename" parameter of the "Content-Disposition" header field.

cde/programs/dtmail/libDtMail/RFC/RFCBodyPart.C

@@ -234,13 +234,13 @@ RFCBodyPart::getContents(DtMailEnv & error,
     if (description) {
 	// getDescription should not be passed a DtMailEnv object.
 	// Neither implementation of getDescription (MIME or V3)
-	// sets the error before returning.  Besides being unneccessary,
+	// sets the error before returning.  Besides being unnecessary,
 	// it requires the caller of getDescription to check the error
 	// status upon its return.
 	//
 	*description = getDescription(error);
 	if (error.isSet()) {
-	    // don't care about the error condition returned by getDescription
+	    // Don't care about the error condition returned by getDescription
 	    // because it returns a valid string no matter what error
 	    // condition occurs.
 	    error.clear();

cde/programs/dtmail/libDtMail/RFC/RFCMailBox.C

@@ -2482,7 +2482,7 @@ RFCMailBox::ThreadNewMailEntry(void * client_data)
     //
     while(info->object_valid->state()) {
 
-	// The following sequence is a little wierd, but here is why.
+	// The following sequence is a little weird, but here is why.
 	// We need to sleep for the ping interval. We can be awaken
 	// early however if the thread catches a signal. The main
 	// thread will send a SIGTERM from the mail box destructor

cde/programs/dtmail/libDtMail/RFC/RFCMailValues.C

@@ -378,7 +378,7 @@ RFCValue::toDate(void)
     }
 
     // There are usually no more than 6 tokens in an RFC date. We will
-    // have a few extras just in case we are given a wierd string.
+    // have a few extras just in case we are given a weird string.
     const char *token_begin[12];
     const char *token_end[12];
     int	n_tokens = 0;