[hibernate-commits] Hibernate SVN: r20021 - core/trunk/entitymanager/src/main/docbook/en/modules.

[hibernate-commits at lists.jboss.org]

Author: epbernard
Date: 2010-07-23 12:42:36 -0400 (Fri, 23 Jul 2010)
New Revision: 20021

Modified:
   core/trunk/entitymanager/src/main/docbook/en/modules/configuration.xml
Log:
HHH-5408 Change wording on "What is hibernate-jpa-2.0-api-x.y.z.jar" to suit Oracle

Lance asked us to adjust some details on how we use the word TCK. Basically better not use the word, it's too complicated :(

Modified: core/trunk/entitymanager/src/main/docbook/en/modules/configuration.xml
===================================================================
--- core/trunk/entitymanager/src/main/docbook/en/modules/configuration.xml	2010-07-23 16:41:23 UTC (rev 20020)
+++ core/trunk/entitymanager/src/main/docbook/en/modules/configuration.xml	2010-07-23 16:42:36 UTC (rev 20021)
@@ -66,12 +66,14 @@
       </itemizedlist></para>
 
     <note>
-      <title>What is hibernate-jpa-2.0-api-x.y.z.jar</title>
+      <title>What is hibernate-jpa-2.0-api-x.y.z.jar?</title>
 
-      <para>This is the JAR containing the JPA 2.0 API, it is fully compliant
-      with the spec and passed the TCK signature test. You typically don't
-      need it when you deploy your application in a Java EE 6 application
-      server (like JBoss AS 6 for example).</para>
+      <para>This is the JAR containing the JPA 2.0 API, it provides all the
+      interfaces and concrete classes that the specification defines as public
+      API. Said otherwise, you can use this JAR to bootstrap any JPA provider
+      implementation. Note that you typically don't need it when you deploy
+      your application in a Java EE 6 application server (like JBoss AS 6 for
+      example).</para>
     </note>
 
     <para>Alternatively, if you use Maven, add the following