Author: hardy.ferentschik
Date: 2008-08-28 03:05:45 -0400 (Thu, 28 Aug 2008)
New Revision: 15141

Modified:
 annotations/trunk/doc/reference/en/modules/entity.xml
Log:
Fixed a typo on the docs.

Modified: annotations/trunk/doc/reference/en/modules/entity.xml
===================================================================
--- annotations/trunk/doc/reference/en/modules/entity.xml  2008-08-25 08:48:44 UTC (rev 15140)
+++ annotations/trunk/doc/reference/en/modules/entity.xml  2008-08-28 07:05:45 UTC (rev 15141)
@@(protected) @@
    <para>By default, when Hibernate cannot resolve the association because
    the expected associated element is not in database (wrong id on the
    association column), an exception is raised by Hibernate. This might be
-    inconvenient for lecacy and badly maintained schemas. You can ask
+    inconvenient for legacy and badly maintained schemas. You can ask
    Hibernate to ignore such elements instead of raising an exception using
    the <literal>@(protected)
    on a <literal>@(protected)),

_______________________________________________
hibernate-commits mailing list
hibernate-commits@(protected)
https://lists.jboss.org/mailman/listinfo/hibernate-commits