fix spelling

Author: Vladimir Kotal

files.tex

@@ -17,7 +17,7 @@
 metadata, etc.
 \item Each filesystem has a specific structure type it uses, for example
 \texttt{ext4} (Linux specific), \texttt{XFS} (used on Linux but coming from SGI
-IRIX), \texttt{JFS} (used on Linux but came from IBM AIX), \texttt{ufs} (BSD
+IRIX), \texttt{JFS} (used on Linux but came from IBM AIX), \texttt{UFS} (BSD
 systems), \texttt{FAT32} (Win), \texttt{ZFS} (Solaris born, then ported to other
 systems), \texttt{APFS} (macOS and iOS since 2017), etc.  A filesystem can be
 either used on local or remote storage, and in case of a remote storage network

history.tex

@@ -198,7 +198,7 @@
 the 4.xBSD versioning scheme. It was common that rather write its own code, the
 Berkeley developers looked around first for what is already done. In this way
 BSD took virtual memory from Mach or NFS-compatible code developed on one
-canadian university.
+Canadian university.
 %\item (1988) 4.3BSD-Tahoe had already the kernel code split into architecture
 %dependent and independent.
 %\item (1989) \emph{Networking Release 1}, first freely distributable code from

network.tex

@@ -1065,7 +1065,7 @@
 addresses, i.e. it will be able to accept connections for both address families
 on the same socket. The remote address of IPv4 clients will be represented as
 \emph{IPv4-mapped IPv6 address}, (i.e. it contains embedded IPv4 address, e.g.
-napø. \texttt{::FFFF:78.128.192.1}).
+e.g. \texttt{::FFFF:78.128.192.1}).
 \item Note that it is mostly not necessary to cast to the \texttt{sockaddr}
 structure. The only exception is the \texttt{accept} call.
 For the \texttt{accept} call the \texttt{sockaddr\_storage} is used which is

synchro.tex

@@ -435,7 +435,7 @@
 release the lock however that will never happen. Next possibility is deadlock
 of single process that is reading from a pipe after forgetting to close
 the write end of the pipe. If there is no one else that has the pipe open,
-the read will block because the all file desriptor copies of the write end are
+the read will block because the all file descriptor copies of the write end are
 not closed and therefore the end of file cannot happen until the reading process
 closed the write end however it cannot do it because it is blocked.
 in \texttt{read} syscall:
@@ -469,7 +469,7 @@
 \sltitle{IPC}
 \begin{itemize}
 \item \emsl{IPC} stands for \emph{Inter-Process Communication}
-\item between processes \emsl{in single system}, e.g. does not inlude
+\item between processes \emsl{in single system}, e.g. does not include
 network communication.
 \item \emsl{semaphores} \dots{} used for process synchronization
 \item \emsl{shared memory} \dots{} passing data between processes,

unix_dict.txt

@@ -619,3 +619,29 @@ rdlock
 rwlock
 wrlock
 trywrlock
+SIGABRT
+stty
+tcsetattr
+SIGPOLL
+WIFEXITED
+COFF
+PROT
+ASYNC
+Salus
+seteuid
+pageout
+sched
+setpriority
+UFS
+readlink
+bss
+proc
+pmap
+nanosleep
+strace
+mkfile
+fallocate
+RESETHAND
+DFL
+NODEFER
+IGN