Author: smukhina
Date: 2009-03-19 19:44:16 -0400 (Thu, 19 Mar 2009)
New Revision: 14276
Modified:
trunk/hibernatetools/docs/reference/en/modules/codegen.xml
trunk/hibernatetools/docs/reference/en/modules/plugins.xml
trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-359 - spelling and validation is checked
Modified: trunk/hibernatetools/docs/reference/en/modules/codegen.xml
===================================================================
--- trunk/hibernatetools/docs/reference/en/modules/codegen.xml 2009-03-19 23:44:07 UTC
(rev 14275)
+++ trunk/hibernatetools/docs/reference/en/modules/codegen.xml 2009-03-19 23:44:16 UTC
(rev 14276)
@@ -353,7 +353,7 @@
</emphasis> attributes, unless you are defining a class without
bi-directional
associations.</para>
- <para>We recomend instead to add the <emphasis>
+ <para>We recommend instead to add the <emphasis>
<property>meta</property>
</emphasis> attributes at the property level:</para>
Modified: trunk/hibernatetools/docs/reference/en/modules/plugins.xml
===================================================================
--- trunk/hibernatetools/docs/reference/en/modules/plugins.xml 2009-03-19 23:44:07 UTC
(rev 14275)
+++ trunk/hibernatetools/docs/reference/en/modules/plugins.xml 2009-03-19 23:44:16 UTC
(rev 14276)
@@ -806,7 +806,7 @@
</entry>
<entry>
- <para>A table that has a multi-colum primary key a
<composite-id>
+ <para>A table that has a multi-column primary key a
<composite-id>
mapping will always be created. If this option is enabled and there are
matching
foreign-keys each key column is still considered a 'basic'
scalar (string, long,
etc.) instead of a reference to an entity. If you disable this option
a
Modified: trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml
===================================================================
--- trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml 2009-03-19
23:44:07 UTC (rev 14275)
+++ trunk/hibernatetools/docs/reference/en/modules/reverseengineering.xml 2009-03-19
23:44:16 UTC (rev 14276)
@@ -61,13 +61,13 @@
<hibernate-reverse-engineering>
<type-mapping>
- <!-- jdbc-type is name fom java.sql.Types -->
+ <!-- jdbc-type is name for java.sql.Types -->
<sql-type jdbc-type="VARCHAR" length='20'
hibernate-type="SomeUserType" />
<sql-type jdbc-type="VARCHAR" length='1'
hibernate-type="yes_no" />
- <!-- length, scale and precision can be used to specify the mapping precisly -->
+ <!-- length, scale and precision can be used to specify the mapping precisely -->
<sql-type jdbc-type="NUMERIC" precision='1'
hibernate-type="boolean" />
<!-- the type-mappings are ordered. This mapping will be consulted last,
- thus overriden by the previous one if precision=1 for the column -->
+ thus overridden by the previous one if precision=1 for the column -->
<sql-type jdbc-type="NUMERIC" hibernate-type="long" />
</type-mapping>