From 7d1d90fb377aeeaf7913b054398e5ced46e7a620 Mon Sep 17 00:00:00 2001
From: LukeMathWalker <20745048+LukeMathWalker@users.noreply.github.com>
Date: Fri, 17 May 2024 11:19:57 +0200
Subject: [PATCH] Reword `MutexGuard` explanation.

---
 book/src/07_threads/14_sync.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/book/src/07_threads/14_sync.md b/book/src/07_threads/14_sync.md
index 76fb83d..b6b3f6c 100644
--- a/book/src/07_threads/14_sync.md
+++ b/book/src/07_threads/14_sync.md
@@ -14,7 +14,7 @@ For example: `MutexGuard` is not `Send`, but it is `Sync`.
 
 It isn't `Send` because the lock must be released on the same thread that acquired it, therefore we don't 
 want `MutexGuard` to be dropped on a different thread.  
-But it is `Sync`, because that has no impact on where the lock is released.
+But it is `Sync`, because giving a `&MutexGuard` to another thread has no impact on where the lock is released.
 
 ## `Send` doesn't imply `Sync`