From: Georg Brandl <georg@python.org>
Date: Fri, 10 Jun 2005 19:55:35 +0000 (+0000)
Subject: Clarify docs about os.popen[234].
X-Git-Tag: v2.5a0~1710
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=debd3710b6a15323ee03b4e3a21d3ba536d7e79b;p=python

Clarify docs about os.popen[234].
---

diff --git a/Doc/lib/libos.tex b/Doc/lib/libos.tex
index 2d0327f55d..517bddca59 100644
--- a/Doc/lib/libos.tex
+++ b/Doc/lib/libos.tex
@@ -354,7 +354,7 @@ Availability: Macintosh, \UNIX, Windows.
 \end{funcdesc}
 
 
-For each of these \function{popen()} variants, if \var{bufsize} is
+For each of the following \function{popen()} variants, if \var{bufsize} is
 specified, it specifies the buffer size for the I/O pipes.
 \var{mode}, if provided, should be the string \code{'b'} or
 \code{'t'}; on Windows this is needed to determine whether the file
@@ -366,7 +366,7 @@ which case arguments will be passed directly to the program without shell
 intervention (as with \function{os.spawnv()}). If \var{cmd} is a string it will
 be passed to the shell (as with \function{os.system()}).
 
-These methods do not make it possible to retrieve the return code from
+These methods do not make it possible to retrieve the exit status from
 the child processes.  The only way to control the input and output
 streams and also retrieve the return codes is to use the
 \class{Popen3} and \class{Popen4} classes from the \refmodule{popen2}