From a74e1b110c1e8b7a33f7db52f9714ca42dca4eb5 Mon Sep 17 00:00:00 2001 From: I Hsin Cheng Date: Fri, 5 Apr 2024 14:57:31 +0800 Subject: [PATCH] Fix typo Correct "ctions" to "actions". --- concurrency-primer.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/concurrency-primer.tex b/concurrency-primer.tex index 45e7657..6eba19a 100644 --- a/concurrency-primer.tex +++ b/concurrency-primer.tex @@ -855,7 +855,7 @@ \subsection{Acquire and release} We have just examined the acquire and release operations in the context of the lock example from \secref{lock-example}. You can think of them as ``one-way'' barriers: an acquire operation permits other reads and writes to move past it, but only in a $before \to after$ direction. -A release works the opposite manner, allowing ctions to move in an $after \to before$ direction. +A release works the opposite manner, allowing actions to move in an $after \to before$ direction. On \textsc{Arm} and other weakly-ordered architectures, this enables us to eliminate one of the memory barriers in each operation, such that