Fix some typos.

diff --git a/doc/README.win32 b/doc/README.win32
index 4131529d98bc177b9600e43ec2f07cdb1af154b0..3ffb3b6f91705d189d52b66b61d940ce407773d8 100644 (file)
--- a/doc/README.win32
+++ b/doc/README.win32
@@ -153,7 +153,7 @@ http://bugzilla.openwatcom.org/show_bug.cgi?id=664), so You are warned.
 Incremental Collection
 ----------------------
 There is some support for incremental collection.  By default, the
-collector chooses between explicit page protection, anf GetWriteWatch-based
+collector chooses between explicit page protection, and GetWriteWatch-based
 write tracking automatically, depending on the platform.
 
 The former is slow and interacts poorly with a debugger.

diff --git a/doc/gcdescr.html b/doc/gcdescr.html
index 68448e6146f1ea41f6b87893218df96f95ed4d93..be83c1d1549b241e50d810049426cd4fcf3367a2 100644 (file)
--- a/doc/gcdescr.html
+++ b/doc/gcdescr.html
@@ -558,7 +558,7 @@ accomplished with <TT># define</tt>'s in <TT>gc.h</tt>
 (really <TT>gc_pthread_redirects.h</tt>), or optionally
 by using ld's function call wrapping mechanism under Linux.
 <P>
-Recent versions of the collector support several facilites to enhance
+Recent versions of the collector support several facilities to enhance
 the processor-scalability and thread performance of the collector.
 These are discussed in more detail <A HREF="scale.html">here</a>.
 We briefly outline the data approach to thread-local allocation in the
@@ -572,7 +572,7 @@ The free list arrays associated
 with each thread are only used to satisfy requests for objects that
 are  both very small, and belong to one of a small number of well-known
 kinds.  These currently include "normal" and pointer-free objects.
-Depending onthe configuration, "gcj" objects may also be included.
+Depending on the configuration, "gcj" objects may also be included.
 <P>
 Thread-local free list entries contain either a pointer to the first
 element of a free list, or they contain a counter of the number of

diff --git a/doc/gcinterface.html b/doc/gcinterface.html
index c78f6a9e86eab809f79e9a7a7c113ff302041509..ea6dfc5e1af1bdda588d09e10dad5e2da871ac16 100644 (file)
--- a/doc/gcinterface.html
+++ b/doc/gcinterface.html
@@ -133,7 +133,7 @@ that write to the garbage collected heap.
 <DD>
 Replace the default procedure used by the collector to print warnings.
 The collector
-may otherwise write to sterr, most commonly because GC_malloc was used
+may otherwise write to stderr, most commonly because GC_malloc was used
 in a situation in which GC_malloc_ignore_off_page would have been more
 appropriate.  See <A HREF="http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gch.txt">gc.h</a> for details.
 <DT> <B> void GC_REGISTER_FINALIZER(...) </b>

diff --git a/doc/scale.html b/doc/scale.html
index 3d976ea41b36c3a7b6e30fae80027b0829824933..b9de2e40e380c523d977a15dfbc354931231d220 100644 (file)
--- a/doc/scale.html
+++ b/doc/scale.html
@@ -158,7 +158,7 @@ the client using either one or two marker threads, and running
 one or two client threads.  Note that the client uses thread local
 allocation exclusively.  With -DTHREAD_LOCAL_ALLOC the collector
 switches to a locking strategy that is better tuned to less frequent
-lock acquisition.  The standard allocation primitives thus peform
+lock acquisition.  The standard allocation primitives thus perform
 slightly worse than without -DTHREAD_LOCAL_ALLOC, and should be
 avoided in time-critical code.
 <P>