fix translation

Author: Vladimir Kotal

file-api.tex

@@ -1065,7 +1065,7 @@
 running the process would have had access to a file if it was not for the SUID
 privileges.  However, there is an inherent security hole in this approach.
 The test and the subsequent action on the file is not an atomic operation.  An
-attacker could possibly unlink the file and immediatelly symlink it to a
+attacker could possibly unlink the file and immediately symlink it to a
 different file to what it actually had no rights to manipulate with.  If the
 timing is right, the SUID process will operate on that other file.  The correct
 solution is not to use the \texttt{access} call but return to the real UID/GID
@@ -1104,7 +1104,7 @@
 \item Only the owner of a file can change its mode.  Mode like
 \texttt{rw-rw-rw-} has nothing to do with that.
 \item In some implementations it was possible to pass the file ownership to
-someone else.  Today this is usually not allowed.  Just think aobut how you
+someone else.  Today this is usually not allowed.  Just think about how you
 could work around a per-user filesystem quota with this.
 \end{itemize}
 

intro.tex

@@ -367,7 +367,7 @@
 \item \label{POSIX4} A book that did not fit the slide and covers topics outside
 of the scope of this class: Gall\-meis\-ter, B. R.: \emsl{POSIX.4 Programmers
 Guide: Programming for the Real World}, O'Reilly; 1st edition, 1995.  A great
-book on real-time POSIX extensions with a beatiful cover.  See also pages
+book on real-time POSIX extensions with a beautiful cover.  See also pages
 \pageref{REALTIMEEXTENSIONS} a \pageref{SIGWAITINFO}.
 \item[\ldots] Go to Amazon and search for ``unix''.  If you ever buy anything,
 always check whether there is a newer edition of the same book.  Note that they

network.tex

@@ -18,7 +18,7 @@
 \begin{description}
 \item[UUCP (UNIX-to-UNIX Copy Program)] -- first application for communication
 between UNIX systems connected directly or via modems, in Version~7 UNIX (1978)
-\item[sokety (sockets)] -- introduced in 4.1aBSD (1982); socket is one end of a
+\item[sockets] -- introduced in 4.1aBSD (1982); socket is one end of a
 bidirectional communication channel created between two processes either on the
 same computer or across a network.
 \item[TLI (Transport Layer Interface)] -- SVR3 (1987); API providing network

proc.tex

@@ -29,7 +29,7 @@
     \item stack
     \end{itemize}
 \item \texttt{text} and \texttt{data} sections are saved in executable file
-\item The sections for inicialized and non-initialized variables and heap are
+\item The sections for initialized and non-initialized variables and heap are
 considered as data
 \item It is also possible to connect segments of shared memory
 (\texttt{shmat}) or files (\texttt{mmap}) into the address space.

signals.tex

@@ -188,7 +188,7 @@
 \texttt{SIGBUS} & bus error, eg. wrong alignment (core) \\
 \texttt{SIGFPE} & floating point exception (core) \\
 \texttt{SIGILL} & illegal instructions (core) \\
-\texttt{SIGSEGV} & sigmentation violation (core) \\
+\texttt{SIGSEGV} & segmentation violation (core) \\
 \texttt{SIGPIPE} & write on a pipe with no reader (exit) \\
 \texttt{SIGSYS} & non-existent system call invoked (core) \\
 \texttt{SIGXCPU} & CPU time limit exceeded (core) \\

threads.tex

@@ -346,7 +346,7 @@
 \item Any thread can wait for another thread, not just the one that created it.
 \item We recommend to always check the return value of \funnm{pthread\_join}()
 to make sure you wait for the right thread.  If you use an incorrect thread ID,
-the funtion returns immediatelly with an error.
+the funtion returns immediately with an error.
 \item In contrast to waiting for processes to finish, \emsl{one cannot wait for
 any thread to finish}.  The rationale is that since there is not parent--child
 relation, it was not deemed necessary.  However, some system provide that

unix_dict.txt

@@ -440,3 +440,104 @@ SIGCHLD
 SIGKILL
 sigwait
 sig
+uid
+blksize
+blocksize
+atime
+mtime
+ctime
+DSYNC
+NOCTTY
+EAGAIN
+RGID
+EGID
+SGID
+XFS
+UFS
+ZFS
+ACLs
+getpwnam
+getpwuid
+mknod
+NSS
+DNS
+NIS
+LDAP
+nsswitch
+EINTR
+unlink
+getegid
+getgroups
+getuid
+geteuid
+VM
+getcwd
+fchdir
+chroot
+chrooted
+sandboxing
+SIGTERM
+SIGQUIT
+SIGCONT
+SIGSTOP
+SIGTSTP
+SIGTTIN
+SIGTTOU
+SIGTSTP
+SIGSTOP
+SIGPROF
+setitimer
+SIGVTALRM
+shmat
+SIGBUS
+sigbus
+AUTOGROW
+userspace
+msync
+munmap
+mprotect
+GETLK
+SETLK
+SETLKW
+GETFL
+fstat
+waitpid
+WNOHANG
+WUNTRACED
+WCONTINUED
+WIFCONTINUED
+execv
+execle
+execl
+execve
+execlp
+EOF
+WEXITSTATUS
+WIFSIGNALED
+WTERMSIG
+WIFSTOPPED
+WSTOPSIG
+dlclose
+dlerror
+dynlib
+RTLD
+SIGTRAP
+SIGURG
+sigaction
+sigaddset
+sigdelset
+sigemptyset
+sigfillset
+sigismember
+sigpending
+sigset
+Peterka
+mem
+kmem
+tty
+symlink's
+SIGSYS
+SIGXCPU
+SIGXFSZ
+SIGFPE
+SIGILL

user-access.tex

@@ -395,7 +395,7 @@
 \verb#size_t#, \verb#pid_t#, etc.  In general, these are integer types and you
 can often find them in the \texttt{/usr/inc{}lude/sys/types.h} header file.
 \item Solaris has the \texttt{pcred} command that provides process
-idenfitication information in a simple form:
+identification information in a simple form:
 
 \begin{verbatim}
 $ pcred 5464
@@ -494,13 +494,12 @@
 \item The root user can in some systems create cycle in directory structure
 however that might confuse file system traversal tools; hence the cyclical
 structure is not used much. Symbolic links to directories work everywhere.
-\item Named pipes (see page \pageref{MKFIFO}) can be used between processes that
-do not have ''family'' relationship.  They work as unnamed pipes otherwise.
+\item Named pipes (see page \pageref{MKFIFO}) can be used between processes
+that do not have ''family'' relationship.  They work as unnamed pipes otherwise.
 \item The sockets noticed above are in the UNIX domain, i.e. they serve for
 communication within one system. The INET domain sockets, used for network
-communication (see page \pageref{NETWORKING}) are not visible in the file system. 
-jednoho systému. Sokety z domény INET, pøes které probíhá sí»ová komunikace,
-se v systému souborù neobjevují. Sí»ová komunikace zaèíná na stranì
+communication (see page \pageref{NETWORKING}) are not visible in the file
+system.
 \item Debuggers use process images available through \texttt{/proc}.
 On many Unix-like systems the \texttt{/proc} tree contains information about
 kernel and running processes in the form of text files.  However, some systems,