Index: doc/Class.3
===================================================================
diff -u -r6e30c5541188221b5d2a64a624212c342d1a51f1 -rf817725e88751339be58485d579241a0b97e15b9
--- doc/Class.3	(.../Class.3)	(revision 6e30c5541188221b5d2a64a624212c342d1a51f1)
+++ doc/Class.3	(.../Class.3)	(revision f817725e88751339be58485d579241a0b97e15b9)
@@ -1221,7 +1221,7 @@
 with an empty argument list\&.
 .PP
 Object destruction, such as triggered by an application-level
-\fBdestroy\fR call (5), is finalized by \fB__dealloc\fR offerd by
+\fBdestroy\fR call (5), is finalized by \fB__dealloc\fR offered by
 \fBnx::Class\fR\&.
 .PP
 In the following, the three built-in procedures ---
Index: doc/Class.man
===================================================================
diff -u -r5a44ade20d030bbe3fc3b19b0edc226e5d5e8c1b -rf817725e88751339be58485d579241a0b97e15b9
--- doc/Class.man	(.../Class.man)	(revision 5a44ade20d030bbe3fc3b19b0edc226e5d5e8c1b)
+++ doc/Class.man	(.../Class.man)	(revision f817725e88751339be58485d579241a0b97e15b9)
@@ -427,7 +427,7 @@
 [list_end]
 
 Object destruction, such as triggered by an application-level
-[method destroy] call (5), is finalized by [method {__dealloc}] offerd by
+[method destroy] call (5), is finalized by [method {__dealloc}] offered by
 [cmd nx::Class]. 
 
 [para]
Index: doc/tutorial2.html
===================================================================
diff -u -r3d145fa523334bae381b61747a7c6178021e78d3 -rf817725e88751339be58485d579241a0b97e15b9
--- doc/tutorial2.html	(.../tutorial2.html)	(revision 3d145fa523334bae381b61747a7c6178021e78d3)
+++ doc/tutorial2.html	(.../tutorial2.html)	(revision f817725e88751339be58485d579241a0b97e15b9)
@@ -4125,7 +4125,7 @@
 <p>Every object in XOTcl is realized as a Tcl command. If nested
 objects are created, these commands are available as object specific
 methods.  So, instead of calling the contained rectangle r1 via the
-fully qualfied name <tt>::r0::r1</tt>, one can use <tt>r0
+fully qualified name <tt>::r0::r1</tt>, one can use <tt>r0
 r1</tt>. This is exactly the same situation as it arises, when e.g. a
 global Tcl proc <tt>proc o1 {} {...}</tt> and an XOTcl object o1
 (created via <tt>Object o1</tt>) is created. Both commands cannot
@@ -4222,7 +4222,7 @@
 method should be prefixed with the specified string (to avoid name
 clashes), <tt>-earlybinding</tt> means that the function pointer of
 the specified command (callee) is take at invocation time (should only
-be done for (built-in) commands inplemented in C), and
+be done for (built-in) commands implemented in C), and
 <tt>-default</tt> provides a means for providing default methods when
 none are specified.</p>
 
Index: library/xotcl/doc/tutorial.html
===================================================================
diff -u -r2352fb1a509bd00ec49c9677798caad6bfec4d71 -rf817725e88751339be58485d579241a0b97e15b9
--- library/xotcl/doc/tutorial.html	(.../tutorial.html)	(revision 2352fb1a509bd00ec49c9677798caad6bfec4d71)
+++ library/xotcl/doc/tutorial.html	(.../tutorial.html)	(revision f817725e88751339be58485d579241a0b97e15b9)
@@ -4024,7 +4024,7 @@
 <p>Every object in XOTcl is realized as a Tcl command. If nested
 objects are created, these commands are available as object specific
 methods.  So, instead of calling the contained rectangle r1 via the
-fully qualfied name <tt>::r0::r1</tt>, one can use <tt>r0
+fully qualified name <tt>::r0::r1</tt>, one can use <tt>r0
 r1</tt>. This is exactly the same situation as it arises, when e.g. a
 global Tcl proc <tt>proc o1 {} {...}</tt> and an XOTcl object o1
 (created via <tt>Object o1</tt>) is created. Both commands cannot
@@ -4121,7 +4121,7 @@
 method should be prefixed with the specified string (to avoid name
 clashes), <tt>-earlybinding</tt> means that the function pointer of
 the specified command (callee) is take at invocation time (should only
-be done for (built-in) commands inplemented in C), and
+be done for (built-in) commands implemented in C), and
 <tt>-default</tt> provides a means for providing default methods when
 none are specified.</p>