--- a/xml/510connectbotmonitor.in	Thu Nov 08 11:59:30 2018 -0800
+++ b/xml/510connectbotmonitor.in	Sun Apr 28 14:45:56 2019 -0700
@@ -19,7 +19,7 @@
 
     <refentry id="x@PACKAGE@.1">
         <refentryinfo>
-            <date>2015-05-01</date>
+            <date>2019-04-28</date>
             <author>
                 <firstname>Carl</firstname>
                 <surname>Byington</surname>
@@ -42,8 +42,7 @@
             <title>Build method</title>
             <para>
                 This is an android project with no native code, so
-                "android update project -p . -t android-16; ant debug"
-                should build cleanly.
+                "make docs; make builder style=release" should build cleanly.
             </para>
         </refsect1>
 
@@ -77,9 +76,9 @@
             <para>
                 The messages exchanged between the terminal emulator and the
                 terminal monitor are arrays of uint16 values in network byte
-                order. Each message starts with a uint16 message byte length,
-                followed by that many bytes of data. Note that the message length
-                will always be even. The next uint16 contains the message
+                order. Each message starts with a uint16 message length,
+                followed by that many uint16 values.
+                The next uint16 contains the message
                 command value, and the remaining uint16 values are the arguments
                 if any for that command.
             </para>
@@ -139,7 +138,7 @@
                 and the second argument is the column number (0..79).
                 That is followed by the field value, a sequence of uint16
                 character codes from the screen buffer. The field
-                covers N columns, where N = (message length - 4) / 2.
+                covers N columns, where N = (message length - 4).
                 When sent from the monitor to the emulator, this causes
                 the emulator to send the field codes to the host (for async
                 modes) or to set the specified field contents (for block modes).
@@ -192,6 +191,13 @@
                 in block mode (tn5250) sessions. Those commands do trigger CURSORMOVE
                 updates in async mode (telnet, ssh) sessions.
             </para>
+
+            <para>
+                SAYSTRING = 12 (TE -> Monitor). The first argument is nonzero if
+                any current speech should be flushed. The second argument is nonzero
+                if this speech should be synchronous. That is followed by uint16
+                character codes to be spoken.
+            </para>
         </refsect1>
 
         <refsect1 id='synchronization.1'>