===================================================================
RCS file: /home/cvs/OpenXM/doc/issac2000/openxm-stackmachines.tex,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -p -r1.4 -r1.5
--- OpenXM/doc/issac2000/openxm-stackmachines.tex	2000/01/07 09:56:08	1.4
+++ OpenXM/doc/issac2000/openxm-stackmachines.tex	2000/01/07 10:22:41	1.5
@@ -1,19 +1,19 @@
-% $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.3 2000/01/03 04:27:52 takayama Exp $
+% $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.4 2000/01/07 09:56:08 ohara Exp $
 
 \section{OpenXM Stack machines}   (Tamura)
 
 In OpenXM specification, all servers are stack machines.
 These are called OpenXM stack machines.
 When a server ox\_xyz gets an OX data message,
-it translates the data into its own object and push the object
-on the stack.
+it translates the data into an object of its local mathematical system 
+and push the object on the stack.
 The translation scheme together with definitions of 
 mathematical operations
-of the system ox\_xyz is called the {\it phrase dictionary} of
+of the system ox\_xyz is called the {\it PhraseBook} of
 ox\_xyz following the OpenMath specification.
 
 Any OX command message starts with the int32 tag OX\_COMMAND.
-The body is OX stack machine operation code expressed by int32.
+The body is OpenXM stack machine operation code expressed by int32.
 The codes are listed below.
 \begin{verbatim}
 #define SM_popSerializedLocalObject               258