Index: doc/tutorial2.html
===================================================================
diff -u -rbe3ba45f303ed61511b034e73e0bba5d10d10982 -rf934951db464db1a6f39ac98290ecde17a466cd7
--- doc/tutorial2.html	(.../tutorial2.html)	(revision be3ba45f303ed61511b034e73e0bba5d10d10982)
+++ doc/tutorial2.html	(.../tutorial2.html)	(revision f934951db464db1a6f39ac98290ecde17a466cd7)
@@ -441,9 +441,9 @@
 Stack empty!
 </pre>
 
-Note that the definition of Saftey can be used not only for instances
+Note that the definition of Safety can be used not only for instances
 of the class <tt>Stack</tt>, but for arbitrary objects supporting the
-same interface.  We can as well use <tt>Saftey</tt> to create a new
+same interface.  We can as well use <tt>Safety</tt> to create a new
 class <tt>SafeStack</tt>. In this case, all instances of
 <tt>SafeStack</tt> have the safety property defined above.
 
@@ -592,12 +592,12 @@
 <pre CLASS="code">
   SoccerTeam <tt>method</tt> newPlayer args {
     <it># we create a new player who is part of the soccer team</it>
-    <it># "eval" is needed to pass the provided arguments seperately to the call of new</it>
+    <it># "eval" is needed to pass the provided arguments separately to the call of new</it>
     <tt>eval</tt> Player <tt>new</tt> -childof [<tt>self</tt>] $args
   }
 </pre>
 <p>
-A player can be transfered to another team. The player object does
+A player can be transferred to another team. The player object does
 not change internally (e.g. the playerRole stays the same). Therefore we
 <tt>move</tt> it to the destination team.
 </p>
@@ -609,7 +609,7 @@
       <it># But we only remove matching playernames of type "Player". We do</it>
       <it># not want to remove another club member type who has the same</it>
       <it># name.</it>
-      <tt>if</tt>{[$player info is type Player] && [$player name] eq $playername} {
+      <tt>if</tt>{[$player info has type Player] && [$player name] eq $playername} {
         <it># We simply 'move' the player object to the destination team.</it>
         <it># Again we use a unique autoname in the new scope</it>
         $player <tt>move</tt> ${destinationTeam}::[$destinationTeam <tt>autoname</tt> player%02d]
@@ -629,7 +629,7 @@
   SoccerTeam <tt>method</tt> printPlayers {} {
     <tt>puts</tt> "Players of ${:name}:"
     <tt>foreach</tt> m [<tt>:info</tt> children] {
-      <tt>if</tt> {[$m info is type Player]} {<tt>puts</tt> "  [$m name]"}
+      <tt>if</tt> {[$m info has type Player]} {<tt>puts</tt> "  [$m name]"}
     }
   }
 </pre>
@@ -776,7 +776,7 @@
 <pre CLASS="code">
   <tt>Class</tt> TransferObserver {
     <tt>:method</tt> transferPlayer {pname destinationTeam} {
-      <tt>puts</tt> "Player '$pname' is transfered to Team '[$destinationTeam name]'"
+      <tt>puts</tt> "Player '$pname' is transferred to Team '[$destinationTeam name]'"
       <tt>next</tt>
     }
   }
@@ -920,7 +920,7 @@
 intrinsic changes of object properties (in contrast to extrinsic
 properties e.g. modeled through roles and implemented through
 per-object and per-class mixins <a href="#xotcl-mixin">[Neumann and
-Zdun 1999c]</a> ) . These changes can be achieved without loosing the
+Zdun 1999c]</a> ) . These changes can be achieved without losing the
 object's identity, its inner state, and its per-object behavior (methods
 and mixins).
 </P>
@@ -1816,7 +1816,7 @@
 dynamics is the changing of the relationship between object and
 class. This means, objects can also change their class dynamically at
 run-time. This feature may be used to model a life-cycle of an object,
-without loosing the object's identity, inner state or
+without losing the object's identity, inner state or
 per-object-specializations through procs. The <tt>class</tt> instance
 method enables this functionality.
 </P>