===================================================================
RCS file: /home/cvs/OpenXM/doc/ascm2001p/openxm-stackmachines.tex,v
retrieving revision 1.2
retrieving revision 1.4
diff -u -p -r1.2 -r1.4
--- OpenXM/doc/ascm2001p/openxm-stackmachines.tex	2001/06/20 05:42:47	1.2
+++ OpenXM/doc/ascm2001p/openxm-stackmachines.tex	2001/06/21 03:09:46	1.4
@@ -1,4 +1,4 @@
-% $OpenXM: OpenXM/doc/ascm2001p/openxm-stackmachines.tex,v 1.1 2001/06/19 07:32:58 noro Exp $
+% $OpenXM: OpenXM/doc/ascm2001p/openxm-stackmachines.tex,v 1.3 2001/06/21 00:15:34 takayama Exp $
 
 \section{OpenXM Stack machines}\label{sec:ox-stackmachines}
 
@@ -25,7 +25,7 @@ and pushes the object onto the stack.
 
 If the server gets an {\it OX command} message, then the server 
 executes the command.
-Any OX command message starts with the int32 tag OX\_COMMAND.
+Any OX command message starts with the int32 tag {\tt OX\_COMMAND}.
 The body is a stack machine operation code expressed by int32.
 %The codes are listed below \cite{ox-rfc-100}.
 %\begin{verbatim}
@@ -87,8 +87,9 @@ instead of a result of the computation.
 %error([8,fctr : invalid argument])
 %\end{verbatim}
 
-OpenXM server won't send error messages to the client
-except when it receives a {\tt SM\_pop*} command.
+OpenXM server does not send error messages to the client
+except when it receives a {\tt SM\_pop*} command, 
+which is a request to pop data from the stack and to write it to the client.
 OX stack machines work in the asynchronous mode which is similar 
 to X servers.
 %For servers of graphic and sound applications,