X-Git-Url: https://vcs.fsf.org/?a=blobdiff_plain;f=doc%2Fmime.txt;h=39eb3cbe60e8c81986dd3d4643f38d9a3836c0bd;hb=03dc576b115b1d93bebea357c7f7b282fd5046f4;hp=7c5d316a500ab8011309c2bbaf63da37747b06dd;hpb=24fc5dd2a66bd6fa6c3885f0222b87379b5644b1;p=squirrelmail.git

diff --git a/doc/mime.txt b/doc/mime.txt
index 7c5d316a..39eb3cbe 100644
--- a/doc/mime.txt
+++ b/doc/mime.txt
@@ -8,7 +8,7 @@ works and how it parses a MIME encoded message.
 
 Object Structure
 ----------------
-There are two objects that are used: "message" and "msg_header".  here is a
+There are two objects that are used: "message" and "msg_header".  Here is a
 brief overview of what each object contains.
 
 msg_header
@@ -43,7 +43,7 @@ Getting the Structure
 ---------------------
 Previously (version 0.4 and below), SquirrelMail handled all the parsing of
 the email message.  It would read the entire message in, search for 
-boundaries, and created an array similar to the $message object discribed
+boundaries, and create an array similar to the $message object described
 above.  This was very inefficient.
 
 Currently, all the parsing of the body of the message takes place on the
@@ -78,7 +78,7 @@ NOTE:  SquirrelMail passes the MIME Torture Test written by Mark
 
 Getting the Body
 ----------------
-Once all of the structure of the message has been read into the $message
+Once all the structure of the message has been read into the $message
 object, we then need to display the body of one entity.  There are a number
 of ways we decide which entity to display at a certain time, and I won't go
 into that here.  
@@ -105,4 +105,4 @@ The code in mime.php is pretty well documented, so you might want to poke
 around there as well to find out more details of how this works.
 
 If you have questions about this, please direct them to our mailing list:
-squirrelmail-list@sourceforge.net
+squirrelmail-users@sourceforge.net