kvserver: fix incorrect comment information

Release note: None
cockroachdb · Jun 2, 2022 · 3bdc450 · 3bdc450
1 parent 5a54758
commit 3bdc450
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/pkg/kv/kvserver/concurrency/lock/locking.proto b/pkg/kv/kvserver/concurrency/lock/locking.proto
@@ -101,7 +101,7 @@ enum Strength {
   //
   // To avoid this potential deadlock problem, an Upgrade lock can be used in
   // place of a Shared lock. Upgrade locks are not compatible with any other
-  // form of locking. As with Shared locks, the lock holder of a Shared lock
+  // form of locking. As with Shared locks, the lock holder of an Upgrade lock
   // on a key is only allowed to read from the key while the lock is held.
   // This resolves the deadlock scenario presented above because only one of
   // the transactions would have been able to acquire an Upgrade lock at a

diff --git a/pkg/kv/kvserver/concurrency/lock_table.go b/pkg/kv/kvserver/concurrency/lock_table.go
@@ -40,7 +40,7 @@ const (
 	_ waitKind = iota
 
 	// waitFor indicates that the request is waiting on another transaction to
-	// to release its locks or complete its own request. waitingStates with this
+	// release its locks or complete its own request. waitingStates with this
 	// waitKind will provide information on who the request is waiting on. The
 	// request will likely want to eventually push the conflicting transaction.
 	waitFor