From 3455435afd0f8601f511e692eba43e275c0dd56b Mon Sep 17 00:00:00 2001
From: A1-Mathematik <42889536+A1-Mathematik@users.noreply.github.com>
Date: Mon, 22 Nov 2021 21:37:00 +0100
Subject: [PATCH] Fix typo: RecursiveLock to ReentrantLock (#43192)

---
 base/condition.jl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/base/condition.jl b/base/condition.jl
index d5f2277eac863..69caf4a4cec3d 100644
--- a/base/condition.jl
+++ b/base/condition.jl
@@ -34,7 +34,7 @@ assert_havelock(l::AbstractLock, tid::Nothing) = concurrency_violation()
 This struct does not implement a real lock, but instead
 pretends to be always locked on the original thread it was allocated on,
 and simply ignores all other interactions.
-It also does not synchronize tasks; for that use a real lock such as [`RecursiveLock`](@ref).
+It also does not synchronize tasks; for that use a real lock such as [`ReentrantLock`](@ref).
 This can be used in the place of a real lock to, instead, simply and cheaply assert
 that the operation is only occurring on a single cooperatively-scheduled thread.
 It is thus functionally equivalent to allocating a real, recursive, task-unaware lock