Typo: "dead lock" --> "deadlock"

diff --git a/Doc/lib/libos.tex b/Doc/lib/libos.tex
index af8871cda4c1f324dc6b9cd1f666922c55673274..5a0df45ca2ba7e4657cb32345adfea9ef788c982 100644 (file)
--- a/Doc/lib/libos.tex
+++ b/Doc/lib/libos.tex
@@ -331,7 +331,7 @@ streams and also retrieve the return codes is to use the
 \class{Popen3} and \class{Popen4} classes from the \refmodule{popen2}
 module; these are only available on \UNIX.
 
-For a discussion of possible dead lock conditions related to the use
+For a discussion of possible deadlock conditions related to the use
 of these functions, see ``\ulink{Flow Control
 Issues}{popen2-flow-control.html}''
 (section~\ref{popen2-flow-control}).

diff --git a/Doc/lib/libpopen2.tex b/Doc/lib/libpopen2.tex
index 83b85abc4bf75ae99488188e280934c0c9bc3148..41a7e8e514cf4ec52535e06ffa63be8736d9a196 100644 (file)
--- a/Doc/lib/libpopen2.tex
+++ b/Doc/lib/libpopen2.tex
@@ -129,7 +129,7 @@ module equivalents).
 
 When reading output from a child process that writes a lot of data to
 standard error while the parent is reading from the child's standard
-out, a dead lock can occur.  A similar situation can occur with other
+out, a deadlock can occur.  A similar situation can occur with other
 combinations of reads and writes.  The essential factors are that more
 than \constant{_PC_PIPE_BUF} bytes are being written by one process in
 a blocking fashion, while the other process is reading from the other