===================================================================
RCS file: /home/cvs/OpenXM/doc/issac2000/openxm-stackmachines.tex,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -p -r1.12 -r1.13
--- OpenXM/doc/issac2000/openxm-stackmachines.tex	2000/01/17 01:23:41	1.12
+++ OpenXM/doc/issac2000/openxm-stackmachines.tex	2000/01/17 08:06:15	1.13
@@ -1,4 +1,4 @@
-% $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.11 2000/01/16 06:39:39 takayama Exp $
+% $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.12 2000/01/17 01:23:41 takayama Exp $
 
 \section{OpenXM Stack machines}\label{sec:ox-stackmachines}
 
@@ -20,7 +20,7 @@ Here,
 {\tt OX\_DATA} stands for {\tt OX\_DATA} header and 
 {\tt (CMO\_ZZ,1)} is a body standing for $1$ expressed 
 by the CMO.
-The server tranlates {\tt (CMO\_ZZ, 1)} to its internal object of
+The server translates {\tt (CMO\_ZZ, 1)} to its internal object of
 the integer  $1$
 and pushes the object onto the stack.
 
@@ -90,12 +90,12 @@ error([8,fctr : invalid argument])
 
 OpenXM server won't send error messages to the client
 except when it receives a {\tt SM\_pop*} command.
-OX stackmachines work in the asynchronous mode which is similar 
+OX stack machines work in the asynchronous mode which is similar 
 to X servers.
 For servers of graphic and sound applications, 
 it may be an advantageous feature.
 It is also possible to emulate RPC and a web server for MCP \cite{iamc} 
-on our asynchronous OX stackmachines.
+on our asynchronous OX stack machines.