From 4b308b44e1d8204702f6912dda4dfc404aa2a87d Mon Sep 17 00:00:00 2001 From: Cristi Cobzarenco Date: Wed, 7 Oct 2015 23:11:25 +0100 Subject: typos: fix a grabbag of typos all over the place --- src/libstd/sys/windows/mod.rs | 4 ++-- src/libstd/sys/windows/mutex.rs | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'src/libstd/sys/windows') diff --git a/src/libstd/sys/windows/mod.rs b/src/libstd/sys/windows/mod.rs index 04bb5e5ea38..85f5d4e5884 100644 --- a/src/libstd/sys/windows/mod.rs +++ b/src/libstd/sys/windows/mod.rs @@ -75,8 +75,8 @@ fn to_utf16_os(s: &OsStr) -> Vec { v } -// Many Windows APIs follow a pattern of where we hand the a buffer and then -// they will report back to us how large the buffer should be or how many bytes +// Many Windows APIs follow a pattern of where we hand a buffer and then they +// will report back to us how large the buffer should be or how many bytes // currently reside in the buffer. This function is an abstraction over these // functions by making them easier to call. // diff --git a/src/libstd/sys/windows/mutex.rs b/src/libstd/sys/windows/mutex.rs index 277c3d14c0e..b770156582d 100644 --- a/src/libstd/sys/windows/mutex.rs +++ b/src/libstd/sys/windows/mutex.rs @@ -22,7 +22,7 @@ //! more details. //! //! 3. While CriticalSection is fair and SRWLock is not, the current Rust policy -//! is there there are no guarantees of fairness. +//! is that there are no guarantees of fairness. //! //! The downside of this approach, however, is that SRWLock is not available on //! Windows XP, so we continue to have a fallback implementation where -- cgit 1.4.1-3-g733a5