(Network): Say what stopped datagram connections do.

diff --git a/lispref/processes.texi b/lispref/processes.texi
index d0b77b7c0184288999ab2ed69a9a5d2a4b2650a0..af4304588341fb0d3e654a8a33872cade74b9847 100644 (file)
--- a/lispref/processes.texi
+++ b/lispref/processes.texi
@@ -1507,11 +1507,12 @@ subprocess.  @xref{Process Information}.
 process, being stopped means not accepting new connections.  (Up to 5
 connection requests will be queued for when you resume the server; you
 can increase this limit, unless it is imposed by the operating
-systems.)  For a network connection, being stopped means not
+systems.)  For a network stream connection, being stopped means not
 processing input (any arriving input waits until you resume the
-connection).  You can use the function @code{process-command} to
-determine whether a network connection or server is stopped; a
-non-@code{nil} value means yes.
+connection).  For a datagram connection, some number of packets may be
+queued but input may be lost.  You can use the function
+@code{process-command} to determine whether a network connection or
+server is stopped; a non-@code{nil} value means yes.
 
 @defun open-network-stream name buffer-or-name host service
 This function opens a TCP connection, and returns a process object