From c1e032fa9451dd50a69cf572cd80dcdbe6591d2e Mon Sep 17 00:00:00 2001
From: Isaiah Becker-Mayer <ibeckermayer@gmail.com>
Date: Thu, 23 Jun 2022 10:15:09 -0400
Subject: [PATCH] sync: clarify Cond.Wait documentation

The previous wording was unclear and seemingly contradictory.
---
 src/sync/cond.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/sync/cond.go b/src/sync/cond.go
index cbf5ba6071..cc927adf58 100644
--- a/src/sync/cond.go
+++ b/src/sync/cond.go
@@ -53,7 +53,7 @@ func NewCond(l Locker) *Cond {
 // Wait locks c.L before returning. Unlike in other systems,
 // Wait cannot return unless awoken by Broadcast or Signal.
 //
-// Because c.L is not locked when Wait first resumes, the caller
+// Because c.L is not locked while Wait is waiting, the caller
 // typically cannot assume that the condition is true when
 // Wait returns. Instead, the caller should Wait in a loop:
 //