summaryrefslogtreecommitdiff
path: root/doc/hacking.texinfo
diff options
context:
space:
mode:
authorTom Tromey <tromey@redhat.com>2004-03-24 20:25:35 +0000
committerTom Tromey <tromey@redhat.com>2004-03-24 20:25:35 +0000
commite8b0391c21c44c9499301b0c650d7e8a42982da3 (patch)
tree0213faec38fa32f528e7ec4a7fcf3ad63a9bf1b9 /doc/hacking.texinfo
parent0d905abbf254fbfde8e5066c9a9cb2230ea13fe7 (diff)
downloadclasspath-e8b0391c21c44c9499301b0c650d7e8a42982da3.tar.gz
* doc/hacking.texinfo (Serialization): Typo.
Diffstat (limited to 'doc/hacking.texinfo')
-rw-r--r--doc/hacking.texinfo2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/hacking.texinfo b/doc/hacking.texinfo
index d240eddb5..607ebbc14 100644
--- a/doc/hacking.texinfo
+++ b/doc/hacking.texinfo
@@ -641,7 +641,7 @@ same serial #, because their .class files differ. However, once you
have a .class file, its serial # is unique, and the computation will
give the same result no matter what platform you execute on.
-Serialzation compatibility can be tested using tools provided with
+Serialization compatibility can be tested using tools provided with
@uref{http://www.kaffe.org/~stuart/japi/,Japitools}. These
tools can test binary serialization compatibility and also provide
information about unknown serialized formats by writing these in XML