Author: nico.ben
Date: 2009-01-07 16:38:08 -0500 (Wed, 07 Jan 2009)
New Revision: 9889
Modified:
trunk/doc/Seam_Reference_Guide/en-US/Tutorial.xml
Log:
Corrected error
Modified: trunk/doc/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- trunk/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-01-07 17:53:32 UTC (rev 9888)
+++ trunk/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-01-07 21:38:08 UTC (rev 9889)
@@ -1949,7 +1949,7 @@
<para>The numberguess example also contains Giveup and Cheat buttons.
You should be able to
trace the pageflow state for both actions relatively easily. Pay
particular attention
- to the <literal>cheat</literal> transtition, which loads a
sub-process to handle that flow.
+ to the <literal>cheat</literal> transition, which loads a
sub-process to handle that flow.
Although it's
overkill for this application, it does demonstrate how complex pageflows
can be broken down into
smaller parts to make them easier to understand.