about summary refs log tree commit diff
path: root/src/libstd/sync
diff options
context:
space:
mode:
authorCorey Farwell <coreyf@rwell.org>2017-03-19 10:18:20 -0400
committerGitHub <noreply@github.com>2017-03-19 10:18:20 -0400
commitd8c8e01038eaf1d52c97af6aee7a6e7e03ad5c94 (patch)
tree2ecf19e2471ec2ebc05e75f4ce30572667b75cf2 /src/libstd/sync
parent969e625a19694da7ec0956d2eb2d505d89f527f9 (diff)
parentec8ecf4f9d06f7e034180a6c56f33a6f800dd1e2 (diff)
downloadrust-d8c8e01038eaf1d52c97af6aee7a6e7e03ad5c94.tar.gz
rust-d8c8e01038eaf1d52c97af6aee7a6e7e03ad5c94.zip
Rollup merge of #40611 - ScottAbbey:patch-1, r=GuillaumeGomez
Fix typo in mutex.rs docs

This seems to match other uses of "be accessed" in the document.
Diffstat (limited to 'src/libstd/sync')
-rw-r--r--src/libstd/sync/mutex.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstd/sync/mutex.rs b/src/libstd/sync/mutex.rs
index 48d8d34dbe0..d79be2944c9 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