[hibernate-commits] Hibernate SVN: r18981 - core/trunk/documentation/manual/src/main/docbook/en-US/content.

[hibernate-commits at lists.jboss.org]

Author: stliu
Date: 2010-03-10 17:20:03 -0500 (Wed, 10 Mar 2010)
New Revision: 18981

Modified:
   core/trunk/documentation/manual/src/main/docbook/en-US/content/architecture.xml
   core/trunk/documentation/manual/src/main/docbook/en-US/content/performance.xml
   core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml
   core/trunk/documentation/manual/src/main/docbook/en-US/content/query_sql.xml
   core/trunk/documentation/manual/src/main/docbook/en-US/content/session_api.xml
Log:
HHH-5000 correct duplicate words in document

Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/architecture.xml
===================================================================
--- core/trunk/documentation/manual/src/main/docbook/en-US/content/architecture.xml	2010-03-10 22:13:09 UTC (rev 18980)
+++ core/trunk/documentation/manual/src/main/docbook/en-US/content/architecture.xml	2010-03-10 22:20:03 UTC (rev 18981)
@@ -362,7 +362,7 @@
 
         <para>
             The first two implementations provide a "one session - one database transaction" programming
-            model. This is also also known and used as <emphasis>session-per-request</emphasis>. The beginning
+            model. This is also known and used as <emphasis>session-per-request</emphasis>. The beginning
             and end of a Hibernate session is defined by the duration of a database transaction.
             If you use programmatic transaction demarcation in plain JSE without JTA, you are advised to
             use the Hibernate <literal>Transaction</literal> API to hide the underlying transaction system

Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/performance.xml
===================================================================
--- core/trunk/documentation/manual/src/main/docbook/en-US/content/performance.xml	2010-03-10 22:13:09 UTC (rev 18980)
+++ core/trunk/documentation/manual/src/main/docbook/en-US/content/performance.xml	2010-03-10 22:20:03 UTC (rev 18981)
@@ -1156,7 +1156,7 @@
             <important>
                 <para>
                     If you configure your underlying cache implementation to use expiry or
-                    timeouts is is very important that the cache timeout of the underlying
+                    timeouts is very important that the cache timeout of the underlying
                     cache region for the UpdateTimestampsCache be set to a higher value than
                     the timeouts of any of the query caches.  In fact, we recommend that the
                     the UpdateTimestampsCache region not be configured for expiry at all.  Note,

Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml
===================================================================
--- core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml	2010-03-10 22:13:09 UTC (rev 18980)
+++ core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml	2010-03-10 22:20:03 UTC (rev 18981)
@@ -169,7 +169,7 @@
         <para>
             SQL functions can be referenced in many ways by users.  However, not all databases
             support the same set of functions.  Hibernate, provides a means of mapping a
-            <emphasis>logical</emphasis> function name to a a delegate which knows how to render
+            <emphasis>logical</emphasis> function name to a delegate which knows how to render
             that particular function, perhaps even using a totally different physical function call.
             <important>
                 <para>

Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/query_sql.xml
===================================================================
--- core/trunk/documentation/manual/src/main/docbook/en-US/content/query_sql.xml	2010-03-10 22:13:09 UTC (rev 18980)
+++ core/trunk/documentation/manual/src/main/docbook/en-US/content/query_sql.xml	2010-03-10 22:20:03 UTC (rev 18981)
@@ -363,7 +363,7 @@
               </row>
 
               <row>
-                <entry>All properties of the the collection</entry>
+                <entry>All properties of the collection</entry>
 
                 <entry><literal>{[aliasname].*}</literal></entry>
 

Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/session_api.xml
===================================================================
--- core/trunk/documentation/manual/src/main/docbook/en-US/content/session_api.xml	2010-03-10 22:13:09 UTC (rev 18980)
+++ core/trunk/documentation/manual/src/main/docbook/en-US/content/session_api.xml	2010-03-10 22:20:03 UTC (rev 18981)
@@ -105,7 +105,7 @@
         <title>Making objects persistent</title>
 
         <para>
-            Newly instantiated instances of a a persistent class are considered 
+            Newly instantiated instances of a persistent class are considered 
             <emphasis>transient</emphasis> by Hibernate. We can make a transient 
             instance <emphasis>persistent</emphasis> by associating it with a 
             session: