clean up

3 files changed, 27 insertions, 24 deletions

diff --git a/fml/doc/en/tutorial/message/chapter.sgml b/fml/doc/en/tutorial/message/chapter.sgml
index 4c2f7192..95cdb65d 100644
--- a/fml/doc/en/tutorial/message/chapter.sgml
+++ b/fml/doc/en/tutorial/message/chapter.sgml
@@ -1,11 +1,11 @@
 <!--
-   $FML$
+   $FML: chapter.sgml,v 1.1 2003/07/28 15:20:18 fukachan Exp $
    $jaFML: chapter.sgml,v 1.5 2003/04/15 14:51:42 fukachan Exp $
 -->
 
 <chapter id="mail.manipulation">
 	<title>
-	manipulate message (mail)
+	Manipulate message (mail message)
 	</title>
 
 <para>
@@ -14,7 +14,7 @@ See
 Mail::Message class
 </link>
 for the mail message object handling. Mail::Message class provides
-fundamental methods. Several message related modules e.g.
+fundamental methods. Several message handling modules e.g.
 Mail::Bounce, Mail::Delivery depend on this class.  
 </para>
 
@@ -31,7 +31,7 @@ A multipart mail consists of several parts.
 </para>
 
 <para>
-The mail delivery needs no detai of a message.
+The mail delivery needs not to know the detail of a message.
 But the filter system needs to know the structure of the message.
 </para>
 
@@ -41,11 +41,11 @@ These modules depend
 Mail::Message class
 </link>
 to know the message structure.
-For eample,  Mail::Bounce, Mail::Delivery et.al. uses this.
+For eample, Mail::Bounce, Mail::Delivery et.al. uses this.
 </para>
 
 <para>
-THe usage is as follows:
+The usage is as follows:
 <screen>
     my $fh  = new FileHandle $file;
     my $msg = Mail::Message->parse( { fd => $fh } );
@@ -93,7 +93,7 @@ class.
 <para>
 dummy.
 This is an adapter for MIME::Lite class.
-All thre request is forwarded to MIME::Lite class.
+All requests are forwarded to MIME::Lite class.
 </para>
 
 <para>
diff --git a/fml/doc/en/tutorial/message/discussion.sgml b/fml/doc/en/tutorial/message/discussion.sgml
index 3d4e48b2..0491d830 100644
--- a/fml/doc/en/tutorial/message/discussion.sgml
+++ b/fml/doc/en/tutorial/message/discussion.sgml
@@ -1,5 +1,5 @@
 <!--
-   $FML$
+   $FML: discussion.sgml,v 1.1 2003/07/29 12:13:55 fukachan Exp $
    $jaFML: discussion.sgml,v 1.4 2003/04/15 14:51:42 fukachan Exp $
 -->
 
@@ -9,10 +9,14 @@
 	</title>
 
 <para>
-fml needs to send back language dependent error mesages.
+Fml needs to send back language dependent error messages.
 How we should implement it ?
 </para>
 
+<para>
+(Below, just a discussion not implemation in fact.)
+</para>
+
 
 <!-- ===================================================== -->
 <sect2>
@@ -21,15 +25,15 @@ How we should implement it ?
 	</title>
 
 <para>
-In the case of &fml4;, call language dependent message converter like
-this:
+In the case of &fml4;, &fml4; call language dependent message
+converter like this:
 <screen>
    Mesg(*e, KEYWORD, DEFAULT MESSAGE, ARGUMENT);
 </screen>
 </para>
 
 <para>
-Mesg() searches the specified keyword in files
+Mesg() searches the specified keyword in files under
 /usr/local/fml/messages/Japanese/ directory. Each file contains
 messages with keywords to be substituted properly.
 </para>
@@ -50,9 +54,8 @@ For example, the keyword not_found matches not_found entry in
 	</title>
 
 <para>
-Hmm, which is better ? "One file has one keyword" and "one file for
-one category, so one file contains plural entries".
-I don't determine it.
+"One file has one keyword" and "one file for one category, so one file
+contains plural entries". Hmm, which is better? I don't determine it.
 </para>
 
 <sect3>
@@ -75,7 +78,7 @@ For example, the usage is as follows:
 <screen>
 printf(catgets(catd, 30,  4,  "%s: Internal match error.\n"), progname);
 </screen>
-Thie function uses se 30 and entry 4 in th local definition file such
+This function uses se 30 and entry 4 in the local definition file such
 as /usr/pkg/share/nls/ja_JP.EUC/PROGNAME.cat.
 </para>
 
@@ -88,7 +91,7 @@ as /usr/pkg/share/nls/ja_JP.EUC/PROGNAME.cat.
 
 <para>
 One problem is whether we should use locale or not ?
-By considering CUI e.g. makefml, it is better to use locale.
+In considering CUI e.g. makefml, it is better to use locale.
 For example, prepare
 <screen>
 /usr/local/lib/fml/$fml_version/messages/ja_JP.EUC/kern
@@ -100,8 +103,8 @@ For example, prepare
 </para>
 
 <para>
-Instead one file for one message may be useful.
-Especially we can customize only one message.
+Instead, one file for one message may be useful.
+Especially it is easy we can customize only one message.
 </para>
 
 <para>
@@ -136,7 +139,7 @@ This methods has the following problems:
 
 
 <para>
-Consider the example. In the latter case, 
+Consider an example. In the latter case, 
 the message module will be like this?
 <screen>
 sub not_found
diff --git a/fml/doc/en/tutorial/message/language.sgml b/fml/doc/en/tutorial/message/language.sgml
index 7e34be55..7b98a921 100644
--- a/fml/doc/en/tutorial/message/language.sgml
+++ b/fml/doc/en/tutorial/message/language.sgml
@@ -1,12 +1,12 @@
 <!--
-   $FML$
+   $FML: language.sgml,v 1.1 2003/07/29 12:13:55 fukachan Exp $
    $jaFML: language.sgml,v 1.5 2003/04/15 14:51:42 fukachan Exp $
 -->
 
 
 <sect1 id="message.nl">
 	<title>
-	message internationalization: 
+	Message internationalization: a
 	the usage of reply_message_nl()
 	</title>
 
@@ -30,7 +30,7 @@ This function uses the message template at
 </para>
 
 <para>
-$_arg_VARNAME in the message such as
+$_arg_VARNAME in the message template such as
 <screen>
 $_args_address
 </screen>
@@ -40,7 +40,7 @@ reply_mesage_nl().
 
 <para>
 Usual $VARIABLE is also expaned by replacing it with value of config.cf.
-For example, $ml_name is expanded to ML name defined in config.cf
+For example, $ml_name is expanded to ML name defined in config.cf.
 $_arg_ prefix is used for lexical scope variables to avoid
 conflicts against variables in config.cf.
 </para>