From c2c99463720e758d5aa0bdcea19dc5b3dd67292c Mon Sep 17 00:00:00 2001 From: Joseph Crail Date: Mon, 9 Jun 2014 00:00:52 -0400 Subject: Fix more misspelled comments and strings. --- src/libnative/io/pipe_win32.rs | 2 +- src/libnative/io/process.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'src/libnative/io') diff --git a/src/libnative/io/pipe_win32.rs b/src/libnative/io/pipe_win32.rs index 45b12aa7007..b097bde2ad8 100644 --- a/src/libnative/io/pipe_win32.rs +++ b/src/libnative/io/pipe_win32.rs @@ -50,7 +50,7 @@ //! it sounded like named pipes just weren't built for this kind of interaction, //! and the suggested solution was to use overlapped I/O. //! -//! I don't realy know what overlapped I/O is, but my basic understanding after +//! I don't really know what overlapped I/O is, but my basic understanding after //! reading about it is that you have an external Event which is used to signal //! I/O completion, passed around in some OVERLAPPED structures. As to what this //! is, I'm not exactly sure. diff --git a/src/libnative/io/process.rs b/src/libnative/io/process.rs index 97b227ae1d8..d8486cb9f09 100644 --- a/src/libnative/io/process.rs +++ b/src/libnative/io/process.rs @@ -923,7 +923,7 @@ fn waitpid(pid: pid_t, deadline: u64) -> IoResult { // Register a new SIGCHLD handler, returning the reading half of the // self-pipe plus the old handler registered (return value of sigaction). // - // Be sure to set up the self-pipe first because as soon as we reigster a + // Be sure to set up the self-pipe first because as soon as we register a // handler we're going to start receiving signals. fn register_sigchld() -> (libc::c_int, c::sigaction) { unsafe { -- cgit 1.4.1-3-g733a5