diff options
| author | ScottAbbey <ScottAbbey@users.noreply.github.com> | 2017-03-17 13:27:13 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-03-17 13:27:13 -0500 |
| commit | ec8ecf4f9d06f7e034180a6c56f33a6f800dd1e2 (patch) | |
| tree | 81700853017f87ed664b769b7f5b1b46441f870f /src/libstd | |
| parent | 9fae0405e9b4667f4f06101efca154b0ff76bf0a (diff) | |
| download | rust-ec8ecf4f9d06f7e034180a6c56f33a6f800dd1e2.tar.gz rust-ec8ecf4f9d06f7e034180a6c56f33a6f800dd1e2.zip | |
Fix typo in mutex.rs docs
This seems to match other uses of "be accessed" in the document.
Diffstat (limited to 'src/libstd')
| -rw-r--r-- | src/libstd/sync/mutex.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstd/sync/mutex.rs b/src/libstd/sync/mutex.rs index 97b84d59218..483d0ef752d 100644 --- a/src/libstd/sync/mutex.rs +++ b/src/libstd/sync/mutex.rs @@ -132,7 +132,7 @@ unsafe impl<T: ?Sized + Send> Sync for Mutex<T> { } /// An RAII implementation of a "scoped lock" of a mutex. When this structure is /// dropped (falls out of scope), the lock will be unlocked. /// -/// The data protected by the mutex can be access through this guard via its +/// The data protected by the mutex can be accessed through this guard via its /// [`Deref`] and [`DerefMut`] implementations. /// /// This structure is created by the [`lock()`] and [`try_lock()`] methods on |
