more spellchecking

Author: Vladimir Kotal

file-api.tex

@@ -762,13 +762,13 @@
 command.  See the manual page.
 \item \emph{Metadata} is information about the file -- access mode, access
 times, length, owner, group, etc.  Metadata does \emsl{not} include the file
-data itself, neither the filename as the file data can be accesses through
+data itself, neither the file name as the file data can be accesses through
 several different hard links and those hardlinks are in the data of directories.
 In other words, metadata is data about the actual file data.
 \item Metadata can be read even when the process has no rights to read the file
 data.
 \item These functions do not provide file descriptor flags or flags from the
-system file table.  These functions are about file information as stored on some
+system file table. These functions are about file information as stored on some
 mountable media.
 \item \texttt{st\_ctime} is not the creation time but the change time -- the
 last modification of the inode.

network.tex

@@ -187,7 +187,7 @@
 \item \emph{domain} -- ,,where the communication will take place'': 
     \begin{itemize}
     \item \texttt{AF\_UNIX} \dots{} local communication within a host, its
-    address is a filename.  Also \texttt{AF\_LOCAL}.
+    address is a file name. Also \texttt{AF\_LOCAL}.
     \item \texttt{AF\_INET}, \texttt{AF\_INET6} \dots{} internet communication,
     the address is an IP address and port pair
     \end{itemize}

signals.tex

@@ -156,7 +156,7 @@
 \begin{itemize}
 \item Creating a core dump means to store the contents of the process virtual
 address space to a file.  Usually such file has a word \texttt{core} in its
-filename.  Some systems, e.g. macOS, may not generate core dumps by default even
+file name. Some systems, e.g. macOS, may not generate core dumps by default even
 if its for signals with default core dump action.
 \item Most of the signals implicitly terminate the process, some create a core
 dump on top of that to enable a post-mortem analysis.

synchro.tex

@@ -243,11 +243,12 @@
 \item Dekker's solution is presented as a first solution to the problem of
 mutual exclusion of 2 processes, without having to apply the mechanism of
 strict alternation, i.e. if second process does not express will to enter
-critical section, the first can enter how many times it wants (and vice versa).
+critical section, the first can enter how many times it wants
+(and ifdef([[[NOSPELLCHECK]]], [[[vice versa]]])).
 Dekker's solution is not trivial, compare it with 16 year younger
 Peterson solution, e.g. on \texttt{en.wikipedia.org}.
 \item We are not going to deal with theoretical algorithms or compare hardware
-mechanisms used by the kernel. Instead we are going to focus on the use of 
+mechanisms used by the kernel. Instead we are going to focus on the use of
 file level locking (which use the atomicity of some file operations)
 and special synchronization primitives offered by the kernel.
 \end{itemize}
@@ -561,7 +562,8 @@
 The same process is unlocking (incrementing the value) and locking
 (decrementing the value).
 \item In general, the increment operation can be done by different process
-than the one which performed the decrement operation (and vice versa).
+than the one which performed the decrement operation (and
+ifdef([[[NOSPELLCHECK]]], [[[vice versa]]])).
 The mutexes work differently, see page \pageref{MUTEXES}.
 \end{itemize}
 

sys-v-semaphores.tex

@@ -159,8 +159,8 @@
 Linux the key is determined using the combination of 16-bit inode number, 8 bits
 of \texttt{id} and 8 bits of minor device number. Same key is returned if the
 inode numbers have the same 16 lower bits.
-\item If unrelated processes need to use the same semaphore, \emsl{the filename
-used for the key needs to be agreed on beforehand.}
+\item If unrelated processes need to use the same semaphore,
+\emsl{the file name used for the key needs to be agreed on beforehand.}
 \item \label{SEM_FIXED_RACE_C} Example: \example{race/sem-fixed-race.c}
 (this is the \example{race/race.c} example from page \pageref{RACE_C} fixed
 with semaphores)

unix_dict.txt

@@ -374,3 +374,4 @@ versioning
 startup
 GCC
 AMD
+multi