Index: doc/next-tutorial/next-tutorial.txt
===================================================================
diff -u -N -ra11d866d48c3ced35ec09fe74ddc12b58b6ef928 -r308645320ba8b2d4fa4d34b07ab8b6bf6c353738
--- doc/next-tutorial/next-tutorial.txt	(.../next-tutorial.txt)	(revision a11d866d48c3ced35ec09fe74ddc12b58b6ef928)
+++ doc/next-tutorial/next-tutorial.txt	(.../next-tutorial.txt)	(revision 308645320ba8b2d4fa4d34b07ab8b6bf6c353738)
@@ -500,7 +500,7 @@
 Stack create s4 {
 
   #
-  # Create a stack with a object-specific method
+  # Create a stack with an object-specific method
   # to check the type of entries
   #
 
@@ -1271,7 +1271,7 @@
 +baz+ defined on the object +o1+. An object method is defined
 via +object method+.
 
-Note that we can define a object method that shadows (redefines)
+Note that we can define an object method that shadows (redefines)
 for this object methods provided from classes.
 
 [[xmp-object-applicable1]]
@@ -1536,8 +1536,8 @@
 
 The invocation flag +-local+ means that the method has to be resolved
 from the same place, where the current method is defined. Since the
-current method is defined as a object method, +foo+ is resolved as
-a object method. The effect is that the mixin definitions are
+current method is defined as an object method, +foo+ is resolved as
+an object method. The effect is that the mixin definitions are
 ignored. The invocation flag +-local+ was already introduced in the
 section about method protection, where it was used to call _private_
 methods.