* doc/README.jaxp: Fix typos.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@131893 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/libjava/classpath/ChangeLog b/libjava/classpath/ChangeLog
index d5dc614..2d87adc 100644 (file)
--- a/libjava/classpath/ChangeLog
+++ b/libjava/classpath/ChangeLog
@@ -1,3 +1,7 @@
+2008-01-27  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
+
+       * doc/README.jaxp: Fix typos.
+
 2008-01-24  Tom Tromey  <tromey@redhat.com>
 
        * resource/gnu/classpath/tools/native2ascii/messages.properties

diff --git a/libjava/classpath/doc/README.jaxp b/libjava/classpath/doc/README.jaxp
index ec88132..afafb08 100644 (file)
--- a/libjava/classpath/doc/README.jaxp
+++ b/libjava/classpath/doc/README.jaxp
@@ -155,7 +155,7 @@ To enable the various GNU JAXP factories, set the following system properties
 When using libxmlj, the libxmlj shared library must be available.
 In general it is picked up by the runtime using GNU Classpath. If not you
 might want to try adding the directory where libxmlj.so is installed
-(by default ${prefix}/lib/classpath/) with ldconfig or specifing in the
+(by default ${prefix}/lib/classpath/) with ldconfig or specifying in the
 LD_LIBRARY_PATH environment variable. Additionally, you may need to specify
 the location of your shared libraries to the runtime environment using the
 java.library.path system property.
@@ -174,7 +174,7 @@ Update: it may be possible to make libxmlj thread-safe nonetheless
 using thread context variables.
 
 Update: thread context variables have been introduced. This is very
-untested though, libxmll therefore still has the single thread
+untested though, libxmlj therefore still has the single thread
 bottleneck.