[seam-commits] Seam SVN: r10715 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US.

[seam-commits at lists.jboss.org]

Author: manaRH
Date: 2009-04-29 03:12:52 -0400 (Wed, 29 Apr 2009)
New Revision: 10715

Modified:
   branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Framework.xml
Log:
JBSEAM-4155 - fixed typos in documentation

Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Framework.xml
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Framework.xml	2009-04-29 06:37:07 UTC (rev 10714)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Framework.xml	2009-04-29 07:12:52 UTC (rev 10715)
@@ -330,7 +330,7 @@
 			event when a transaction succeeds (a call to <literal>persist()</literal>, 
 			<literal>update()</literal> or <literal>remove()</literal> succeeds).  By observing 
 			this event we can refresh our queries when the underlying entities are changed.  If
-			we only want to refresh certain queries when a particular entity is persited, 
+			we only want to refresh certain queries when a particular entity is persisted, 
 			updated or removed we can observe the 
 			<literal>org.jboss.seam.afterTransactionSuccess.&lt;name&gt;</literal> 
 			event (where <literal>&lt;name&gt;</literal> is the name of the entity).
@@ -533,7 +533,7 @@
       <para>
          Unfortunately Query objects don't work well with 
          <emphasis>join fetch</emphasis> queries - the use of pagination with
-         these queries is not recomended, and you'll have to implement your own
+         these queries is not recommended, and you'll have to implement your own
          method of calculating the total number of results (by overriding 
          <literal>getCountEjbql()</literal>.
       </para>