about summary refs log tree commit diff
path: root/src/libstd/sync
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2018-02-16 15:56:50 +0100
committerMatthias Krüger <matthias.krueger@famsik.de>2018-02-17 17:38:49 +0100
commit4452446292086d9c92ea709eea61a31cedb55e22 (patch)
tree261a9b2a1b4fb4468673a71fbe774ee84527599f /src/libstd/sync
parentb298607864b76ea6b7b7a4b8bb482472f1604c8d (diff)
downloadrust-4452446292086d9c92ea709eea61a31cedb55e22.tar.gz
rust-4452446292086d9c92ea709eea61a31cedb55e22.zip
fix more typos found by codespell.
Diffstat (limited to 'src/libstd/sync')
-rw-r--r--src/libstd/sync/rwlock.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libstd/sync/rwlock.rs b/src/libstd/sync/rwlock.rs
index 2edf02efc47..f7fdedc0d21 100644
--- a/src/libstd/sync/rwlock.rs
+++ b/src/libstd/sync/rwlock.rs
@@ -24,8 +24,8 @@ use sys_common::rwlock as sys;
 /// typically allows for read-only access (shared access).
 ///
 /// In comparison, a [`Mutex`] does not distinguish between readers or writers
-/// that aquire the lock, therefore blocking any threads waiting for the lock to
-/// become available. An `RwLock` will allow any number of readers to aquire the
+/// that acquire the lock, therefore blocking any threads waiting for the lock to
+/// become available. An `RwLock` will allow any number of readers to acquire the
 /// lock as long as a writer is not holding the lock.
 ///
 /// The priority policy of the lock is dependent on the underlying operating