Skip to content

Commit b352205

Browse files
author
Vladimir Kotal
committed
fix wording
1 parent 4ef87b8 commit b352205

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

file-api.tex

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -961,7 +961,8 @@
961961
\item put maximum of \emph{\texttt{bufsz}} bytes from the symlink target path
962962
to \texttt{\emph{buf}}
963963
\item returns the number of bytes written to \texttt{\emph{buf}}.
964-
\item \texttt{\emph{buf}} is \emsl{not} terminated by \verb#'\0'#
964+
\item The path written to \texttt{\emph{buf}} is \emsl{not} terminated
965+
by \verb#'\0'#
965966
\end{itemize}
966967
\end{slide}
967968

@@ -971,8 +972,8 @@
971972
\item Calling \texttt{unlink} on a hardlink will not release the file data if
972973
other hardlinks exists. You can delete the symlink's target in which case you
973974
end up with a \emph{broken link}.
974-
\item \texttt{readlink} is useful in the situation where you want to \texttt{unlink}
975-
the symlink's target.
975+
\item \texttt{readlink} is useful in the situation where you want to
976+
\texttt{unlink} the symlink's target.
976977
\item \emph{\texttt{bufsz}} is typically set as 1 byte less than the buffer
977978
size to accommodate the terminating \texttt{NULL} character.
978979
\item See \example{readlink/readlink.c} and fix the problem therein.

0 commit comments

Comments
 (0)