[db-jdo] 06/43: JDO-356 Update README.txt

[cl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

clr pushed a commit to branch origin/2.0.1
in repository https://gitbox.apache.org/repos/asf/db-jdo.git

commit ba68ae75ad9e4d98d8a152b7d15e7d0b14789c3a
Author: Craig L Russell <cl...@apache.org>
AuthorDate: Fri Mar 31 23:31:40 2006 +0000

    JDO-356 Update README.txt
---
 README.txt | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.txt b/README.txt
index b8f2933..07a29f5 100644
--- a/README.txt
+++ b/README.txt
@@ -1,4 +1,4 @@
-This is the release candidate 1 of the JDO 2 project. It includes
+This is the official release of the JDO 2 project. It includes
 the JDO 2.0 TCK and its dependencies:
 
 - api20 contains source to build jdo.jar, which defines the JDO API version 2.0
@@ -16,7 +16,7 @@ and to execute the TCK. You can download maven from
 http://maven.apache.org/start/download.html
 
 Note that maven uses the user.home system property for the location
-of the maven local repostitory: ${user.home}/.maven/repository.
+of the maven local repository: ${user.home}/.maven/repository.
 Under Windows this system property is C:\Documents and Settings\<user> 
 no matter what the HOME variable is set to. As a workaround you may set the 
 system property by adding -Duser.home=%HOME% to the environment variable 
@@ -34,7 +34,7 @@ agreement, download 'File System Service Provider, 1.2 Beta 3' and then unpack
 the downloaded zip. It includes the jars fscontext.jar and providerutil.jar.
 
 - JPOX
-The Reference Implementation for JDO 2.0 is JPOX. The tck20 subproject 
+The Reference Implementation for JDO 2.0 is JPOX 1.1.0. The tck20 subproject 
 automatically downloads the JPOX jar files via maven configuration.
 
 - derby
@@ -70,10 +70,10 @@ execute goals.
 Running the TCK
 -------
 
-This version of the TCK is almost final.  
+This version of the TCK is final.  
 
 In the tck20 project, run "maven build" to build the tck.  This will 
-compile, enhance, install the schemas, and run all the tests on all 
+compile, enhance, install the schemas, and run all the tests on the RI on all 
 supported databases and identitytypes.
 
 You may use the following custom goals and command line options