From: nisikimi <nisikimi>
Date: Thu, 30 Apr 2009 04:34:45 +0000 (+0000)
Subject: *** empty log message ***
X-Git-Tag: REL-1-5-5~13
X-Git-Url: http://git.chise.org/gitweb/?a=commitdiff_plain;h=717f1feee5d6be43d590110fd5d385f12adc6403;p=m17n%2Fm17n-db.git

*** empty log message ***
---

diff --git a/FORMATS/IM-tut.txt b/FORMATS/IM-tut.txt
index 45fae17..793e727 100644
--- a/FORMATS/IM-tut.txt
+++ b/FORMATS/IM-tut.txt
@@ -231,11 +231,12 @@ method before explaining how it works.
 @endverbatim
 
 Let's see what happens when the user types the key sequence \<a\> \<b\> \< \>.
-Upon \<a\>, "A" is committed and the state shifts to [[non-upcase]].
+Upon \<a\>, "A" is inserted into the buffer and the state shifts to [[non-upcase]].
 So, the next \<b\> is handled in the [[non-upcase]] state.
 As it matches a
-rule in the map [[lower]], "b" is inserted in the preedit buffer and it
-is committed explicitly by the "commit" command in BRANCH-ACTION.  After
+rule in the map [[lower]], "b" is inserted in the preedit buffer and characters in the 
+buffer ("Ab")
+are committed explicitly by the "commit" command in BRANCH-ACTION.  After
 that, the input method is still in the [[non-upcase]] state.  So the next \< \>
 is also handled in [[non-upcase]].  For this time, no rule in this state
 matches it.  Thus the branch [[(nil (shift init))]] is selected and the