--- a/docs/yatexe.tex	Thu May 27 16:37:44 2010 +0900
+++ b/docs/yatexe.tex	Thu May 27 20:02:32 2010 +0900
@@ -5,7 +5,7 @@
 
 @iftex
 @c @syncodeindex fn cp
-@c Last modified Thu May 27 16:25:29 2010 on firestorm
+@c Last modified Thu May 27 18:04:10 2010 on firestorm
 @syncodeindex vr cp
 @end iftex
 
@@ -195,9 +195,13 @@
 the cursor on the line of error message and type @kbd{SPACE} key.  This
 makes the cursor move to corresponding source line.
 
-  Since @kbd{[prefix] tr} pastes the region into the file
-@file{texput.tex} in the current directory, you should be careful of
-overwriting.  The method of specification of the region is shown in the
+  YaTeX-typeset-region invoked by @kbd{[prefix] tr} call typesetter
+for region.  The region is specified by standard point and mark, or
+by @code{%#BEGIN} and @code{%#END} marks.  Selected region will be
+copied to the temporary file @file{texput.tex} with the same preamble
+as the main file of current editing sources.  Be sure to put
+all local macro settings in preamble, not after @code{\begin{document}}.
+  The method of specification of the region is shown in the
 section @xref{%#notation}.
 
   The documentclass  for typeset-region is the same as that of editing
@@ -207,8 +211,12 @@
   The @kbd{[prefix] te} key automatically marks current inner environment
 or inner math mode and then call typeset-region with marked region.  This
 is convenient to quick view of current tabular environment or current
-editing formulas.  Keeping previewer window for @file{texput.dvi} is
-handy for debugging.
+editing formulas.  Keeping previewer window for @file{texput.dvi} is handy
+for debugging.  Since @kbd{[prefix] te} selects the inner-most environment
+as region, it is not suitable for partial typesetting of doubly or more
+composed environment.  If you want to do partial typesetting for a nested
+environment, use @kbd{[prefix] tr} for static-region, which is described
+in the section @xref{%#notation}.
 
 @node Calling previewer, Printing out, Calling typesetter, Typesetting
 @comment  node-name,  next,  previous,  up