Author: pete.muir(a)jboss.org Date: 2008-03-28 06:32:17 -0400 (Fri, 28 Mar 2008) New Revision: 7728 Modified: branches/Seam_2_0/doc/Seam_Reference_Guide/en/Tutorial.xml trunk/doc/reference/en/modules/tutorial.xml Log: JBSEAM-2786 Modified: branches/Seam_2_0/doc/Seam_Reference_Guide/en/Tutorial.xml =================================================================== --- branches/Seam_2_0/doc/Seam_Reference_Guide/en/Tutorial.xml 2008-03-28 01:52:14 UTC (rev 7727) +++ branches/Seam_2_0/doc/Seam_Reference_Guide/en/Tutorial.xml 2008-03-28 10:32:17 UTC (rev 7728) @@ -264,7 +264,7 @@ </example> <para> The most important things to notice in this example are the <literal>@Name</literal> and <literal>@Scope</literal> annotations. These annotations establish that this class is a Seam component. </para> - <para> We'll see below that the properties of our <literal>User</literal> class are bound to + <para> We'll see below that the properties of our <literal>User</literal> class are bound directly to JSF components and are populated by JSF during the update model values phase. We don't need any tedious glue code to copy data back and forth between the JSP pages and the entity bean domain model. </para> @@ -337,7 +337,7 @@ <calloutlist> <callout arearefs="registration-stateless-annotation"> <para> The EJB standard <literal>@Stateless</literal> annotation marks this class as - stateless session bean. </para> + a stateless session bean. </para> </callout> <callout arearefs="registration-in-annotation"> <para> The <link linkend="in-annotation"> @@ -357,7 +357,7 @@ <callout arearefs="registration-action-listener"> <para> The action listener method uses the standard EJB3 <literal>EntityManager</literal> API to interact with the database, and returns the - JSF outcome. Note that, since this is a sesson bean, a transaction is automatically + JSF outcome. Note that, since this is a session bean, a transaction is automatically begun when the <literal>register()</literal> method is called, and committed when it completes. </para> </callout> Modified: trunk/doc/reference/en/modules/tutorial.xml =================================================================== --- trunk/doc/reference/en/modules/tutorial.xml 2008-03-28 01:52:14 UTC (rev 7727) +++ trunk/doc/reference/en/modules/tutorial.xml 2008-03-28 10:32:17 UTC (rev 7728) @@ -261,7 +261,7 @@ <para> The most important things to notice in this example are the <literal>@Name</literal> and <literal>@Scope</literal> annotations. These annotations establish that this class is a Seam component. </para> - <para> We'll see below that the properties of our <literal>User</literal> class are bound to + <para> We'll see below that the properties of our <literal>User</literal> class are bound directly to JSF components and are populated by JSF during the update model values phase. We don't need any tedious glue code to copy data back and forth between the JSP pages and the entity bean domain model. </para> @@ -333,7 +333,7 @@ <calloutlist> <callout arearefs="registration-stateless-annotation"> <para> The EJB standard <literal>@Stateless</literal> annotation marks this class as - stateless session bean. </para> + a stateless session bean. </para> </callout> <callout arearefs="registration-in-annotation"> <para> The <link linkend="in-annotation"> @@ -353,7 +353,7 @@ <callout arearefs="registration-action-listener"> <para> The action listener method uses the standard EJB3 <literal>EntityManager</literal> API to interact with the database, and returns the - JSF outcome. Note that, since this is a sesson bean, a transaction is automatically + JSF outcome. Note that, since this is a session bean, a transaction is automatically begun when the <literal>register()</literal> method is called, and committed when it completes. </para> </callout>