fix spelling

Author: Vladimir Kotal

file-api.tex

@@ -1044,7 +1044,7 @@
 \texttt{int \funnm{access}(const char *\emph{path}, int \emph{amode});}
 \begin{itemize}
 \item checks whether the calling process can access the file \emph{path}
-\item \emph{amode} is an OR-combination of contants 
+\item \emph{amode} is an OR-combination of constants
     \begin{itemize}
     \item \verb#R_OK# \dots{} read permission test
     \item \verb#W_OK# \dots{} write permission test

proc.tex

@@ -464,7 +464,7 @@
 \end{description}
 \begin{itemize}
 \item To get information about running processes programatically is possible
-using non-standar API (e.g. the \texttt{libproc} library on Solarisu built
+using non-standar API (e.g. the \texttt{libproc} library on Solaris built
 on top of the \texttt{procfs} filesystem that is mounted under \texttt{/proc}).
 \item Note that using \texttt{getppid} value to check if parent exited is not
 portable (commonly \texttt{init} has pid 1 however this is not true in many

signals.tex

@@ -240,7 +240,7 @@
 You can check \example{signals/catch-SIGSEGV.c}. More information and another
 example can be found on page \pageref{THREADS_SIGWAIT}.
 \item Note: if the standard specifies any behavior as \emph{undefined}, it means
-the specification does not state what should happend and that whatever happens
+the specification does not state what should happen and that whatever happens
 does not violate the standard.  So, if you trigger such a behavior and your
 computer burns down or even flies off to the Moon, possibly still in flames,
 that does not violate the standard either.

synchro.tex

@@ -161,7 +161,7 @@
 records can be interleaved.
 \item only single process can write.
 \item other processes read data from the log file.
-\item while reading record that is being written inconsitent data is retrived.
+\item while reading record that is being written inconsitent data is retrieved.
 \item while writing, it is not possible to read. If no process is writing,
 multiple processes can read simultaneously.
 \end{itemize}

threads.tex

@@ -1,7 +1,7 @@
 changequote([[[, ]]])
 
 \pagebreak
-\pdfbookmark[0]{threads and their synchronization}{vlakna}
+\pdfbookmark[0]{threads and their synchronization}{threads}
 
 \begin{slide}
 \sltitle{Contents}

unix_dict.txt

@@ -645,3 +645,28 @@ RESETHAND
 DFL
 NODEFER
 IGN
+setsockopt
+getpeername
+socklen
+getipnodebyname
+getipnodebyaddr
+getipnode
+gethostbyaddr
+pton
+ntop
+proto
+getprotobyname
+getservbyname
+getservbyport
+getservent
+OSPF
+GRE
+recvfrom
+addrinfo
+addrlen
+socktype
+ai
+execvpe
+procfs
+lockfile
+lockfiles

user-access.tex

@@ -437,7 +437,7 @@
 \item If a process with UID~==~0 wants to change its identity, it has to call
 \texttt{setgid} first and then \texttt{setgroups}. Only after that it can call
 \texttt{setuid}. Any other ordering would mean that the process would lack the
-rights to perform the opearation in question, e.g. once \texttt{setuid} returns
+rights to perform the operation in question, e.g. once \texttt{setuid} returns
 it would not have the rights to perform \texttt{setgid} and \texttt{setgroups}.
 \item \texttt{setgroups} is not part of UNIX~98 or UNIX~03.
 \item RUID/EUID are saved in the kernel process structure and also in the so