clean up

1 files changed, 22 insertions, 19 deletions

diff --git a/fml/doc/en/tutorial/virtual/chapter.sgml b/fml/doc/en/tutorial/virtual/chapter.sgml
index 84cca9a1..90a18be0 100644
--- a/fml/doc/en/tutorial/virtual/chapter.sgml
+++ b/fml/doc/en/tutorial/virtual/chapter.sgml
@@ -1,34 +1,35 @@
 <!--
-   $FML$
+   $FML: chapter.sgml,v 1.1 2003/07/27 15:04:27 fukachan Exp $
    $jaFML: chapter.sgml,v 1.2 2003/04/15 14:51:47 fukachan Exp $
 -->
 
 <chapter id="virtualdomain">
 	<title>
-	virtual domain handling
+	Virtual domain handling
 	</title>
 
 <para>
 It is difficult to handle virtual domains and the default domain in
-same ways.
+the same way.
 </para>
 
 <para>
-We user "user@domain" form for the ML name if it is an ML of a virtual
-domain. For example, for a virtual domain, use makefml like this
+You can use "user@domain" as an argument if needed, for example,
+ambiguous. So, use "user@domain" form for the ML name if it is an ML
+of a virtual domain. For example, for a virtual domain, use makefml
+like this
 <screen>
 % makefml newml mlname@virtualdomain
 </screen>
-but both syntaxes are ok for the default domain.
+but both syntaxes are acceptable for the default domain.
 <screen>
 % makefml newml mlname@defaultdomain
 % makefml newml mlname
 </screen>
-fml treats these properly as could as possible but fml needs some
-hints such as the ml home directory information.
-You need to prepare /usr/local/etc/fml/virtual file for a hint on
-domain to directory mappings.
-This file name is $virtual_maps in main.cf.
+Fml treats these properly as could as possible. But fml needs some
+hints such as ml home directory information. You need to prepare
+/usr/local/etc/fml/virtual file for a hint on mappping between domain
+and directory. This file name is defined as $virtual_maps in main.cf.
 </para>
 
 
@@ -38,12 +39,14 @@ This file name is $virtual_maps in main.cf.
 	</title>
 
 <para>
-It is easy. Prepare
+It is easy in use.
+Edit
 <link linkend="install.virtual">
-/etc/fml/virtual
+/usr/local/etc/fml/virtual
 </link>
-file. 
-After that, use "user@domain" form in makefml for virtual domains.
+file and define it as $virtual_maps in main.cf. 
+After that, you can use "user@domain" form in makefml arguments 
+in handling virtual domains.
 <screen>
 makefml newml	ML@virtualdomain
 makefml add	ML@virtualdomain	address
@@ -55,7 +58,7 @@ accpetable.
 
 <para>
 When you use CGI, you need not to use user@domain syntax 
-since the url of config.cgi includes the domain name.
+since config.cgi knows the domain name the cgi handles.
 <screen>
 http://lists/~fml/cgi-bin/fml/$domain/admin/config.cgi
 </screen>
@@ -63,9 +66,9 @@ http://lists/~fml/cgi-bin/fml/$domain/admin/config.cgi
 
 <warning>
 <para>
-The domain name is hard-coded within config.cgi.  makefml inject the
-domain name in creating config.cgi when "makefml newml" runs.
-config.cgi does not resolve its domain by URL.
+The domain name is hard-coded within config.cgi since makefml injects
+the domain name in creating config.cgi when "makefml newml" runs.
+"config.cgi" does not resolve its domain by URL.
 </para>
 </warning>