more pipe wording

Author: Vladimir Kotal

proc.tex

@@ -918,16 +918,16 @@
 \begin{itemize}
 \item creates an \emph{unnamed pipe} and allocates a pair of file descriptors
     \begin{itemize}
-    \item \texttt{fildes[0]} \dots{} for reading from a pipe
-    \item \texttt{fildes[1]} \dots{} for writing to a pipe
+    \item \texttt{fildes[0]} \dots{} for reading from the pipe
+    \item \texttt{fildes[1]} \dots{} for writing to the pipe
     \end{itemize}
 \item the system makes sure that:
     \begin{itemize}
     \item producer blocks on writing if the pipe is full
     \item consumer blocks on reading if the pipe is empty
     \end{itemize}
-\item consumer gets \texttt{EOF} (i.e. \texttt{read()} returns
-\texttt{0}) only if all copies of \texttt{fildes[1]} are closed.
+\item consumer gets \texttt{EOF} (i.e. \texttt{read()} on \texttt{fildes[0]}
+returns \texttt{0}) only if all copies of \texttt{fildes[1]} are closed.
 \item \emph{named pipe} (i.e. FIFO, see \funnm{mkfifo}) works the same way.
 The difference is that any process (modulo permissions) can use it.
 \end{itemize}