Skip to content

Commit a17f718

Browse files
committed
improve wording
1 parent 7de17c5 commit a17f718

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

synchro.tex

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -93,8 +93,8 @@
9393
\end{enumerate}
9494
\item Note that synchronization problems may surface only after the program is
9595
run on multiprocessor(core) machine or on more processors than what is used when
96-
development. However, given that nowadays you have a few CPUs even on a
97-
low-level laptop, it is easier to test such scenarios than in the past.
96+
development. Given that nowadays even a low-level laptop has multiple CPU
97+
cores, it is easier to test such scenarios than in the past.
9898
\end{itemize}
9999

100100
%%%%%
@@ -252,7 +252,7 @@
252252
Peterson solution, e.g. on Wikipedia.
253253
\item We are not going to deal with theoretical algorithms or compare hardware
254254
mechanisms used by the kernel. Instead we are going to focus on the use of
255-
file level locking (which use the atomicity of some file operations)
255+
file level locking (which builds on the atomicity of some file operations)
256256
and special synchronization primitives offered by the kernel.
257257
\item note that ``signalling'' here has nothing to do with Unix signals. It's
258258
confusing though.

0 commit comments

Comments
 (0)