summaryrefslogtreecommitdiff
path: root/absl/synchronization
diff options
context:
space:
mode:
authorGravatar Abseil Team <absl-team@google.com>2022-04-22 15:00:05 -0400
committerGravatar dinord <dino.radakovich@gmail.com>2022-04-22 15:05:02 -0400
commit731d4021ae94450c66627e71767c92f378065ae9 (patch)
tree0f59ffb54e8c6e22aea31e6c069c515e198c9bd5 /absl/synchronization
parent7c6608d0dbe43cf9bdf7f77787bc6bc89cc42f8b (diff)
Fix typo: "a the condition" -> "a condition".
PiperOrigin-RevId: 443723710 Change-Id: Ic39b0cf2b289efa9cd9434616949dd08a1a35117
Diffstat (limited to 'absl/synchronization')
-rw-r--r--absl/synchronization/mutex.cc6
1 files changed, 3 insertions, 3 deletions
diff --git a/absl/synchronization/mutex.cc b/absl/synchronization/mutex.cc
index 8f25e3dd..821047fd 100644
--- a/absl/synchronization/mutex.cc
+++ b/absl/synchronization/mutex.cc
@@ -2510,9 +2510,9 @@ void CondVar::Remove(PerThreadSynch *s) {
// before calling Mutex::UnlockSlow(), the Mutex code might be re-entered (via
// the logging code, or via a Condition function) and might potentially attempt
// to block this thread. That would be a problem if the thread were already on
-// a the condition variable waiter queue. Thus, we use the waitp->cv_word
-// to tell the unlock code to call CondVarEnqueue() to queue the thread on the
-// condition variable queue just before the mutex is to be unlocked, and (most
+// a condition variable waiter queue. Thus, we use the waitp->cv_word to tell
+// the unlock code to call CondVarEnqueue() to queue the thread on the condition
+// variable queue just before the mutex is to be unlocked, and (most
// importantly) after any call to an external routine that might re-enter the
// mutex code.
static void CondVarEnqueue(SynchWaitParams *waitp) {