[hibernate-commits] Hibernate SVN: r11307 - trunk/HibernateExt/shards/doc/reference/en/modules.

Author: max.ross Date: 2007-03-19 19:08:21 -0400 (Mon, 19 Mar 2007) New Revision: 11307 Modified: trunk/HibernateExt/shards/doc/reference/en/modules/limitations.xml Log: fix typose Modified: trunk/HibernateExt/shards/doc/reference/en/modules/limitations.xml =================================================================== --- trunk/HibernateExt/shards/doc/reference/en/modules/limitations.xml 2007-03-19 22:43:03 UTC (rev 11306) +++ trunk/HibernateExt/shards/doc/reference/en/modules/limitations.xml 2007-03-19 23:08:21 UTC (rev 11307) @@ -7,7 +7,7 @@ In order to speed-up the initial release of Hibernate Shards, some parts of the Hibernate API that we rarely use were left unimplemented. Of course things that we rarely used are probably critical for some applications, so if we've left you out in the cold - we apologize. We're committed to getting the rest of the api implemented quickly. For details on which + we apologize. We're committed to getting the rest of the API implemented quickly. For details on which methods were not implemented, please see the Javadoc for <classname>ShardedSessionImpl</classname>, <classname>ShardedCriteriaImpl</classname>, and <classname>ShardedQueryImpl</classname>. </para> @@ -115,7 +115,7 @@ <classname>StatefulInterceptorFactory</classname> implements this interface, Hibernate Shards will provide the <classname>Interceptor</classname> with a reference to the real (shard-specific) <classname>Session</classname> once the factory constructs it. This way your - <classname>Interceptor</classname> can safely and accurately interact with a speicific shard. Here's an example: + <classname>Interceptor</classname> can safely and accurately interact with a specific shard. Here's an example: <programlisting><![CDATA[ public class MyStatefulInterceptor implements Interceptor, RequiresSession { private Session session; @@ -196,7 +196,7 @@ <para>We have a number of ideas about how to make this easy to deal with but we have not yet implemented any of them. In the short term, we think your best bet is to either not create object relationships between - sharded entities and replicated entities. In otherwords, just model the relationship like + sharded entities and replicated entities. In other words, just model the relationship like you would if you weren't using an OR Mapping tool. We know this is clunky and annoying. We'll take care of it soon. </para>