From b7bfe04b2d003d08f6ac450f41d7f221cb87f129 Mon Sep 17 00:00:00 2001 From: Joseph Crail Date: Tue, 2 Sep 2014 01:35:58 -0400 Subject: Fix spelling errors and capitalization. --- src/librustrt/args.rs | 2 +- src/librustrt/c_str.rs | 2 +- src/librustrt/local_ptr.rs | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) (limited to 'src/librustrt') diff --git a/src/librustrt/args.rs b/src/librustrt/args.rs index 6ac36f8b856..4c444036e1d 100644 --- a/src/librustrt/args.rs +++ b/src/librustrt/args.rs @@ -14,7 +14,7 @@ //! the processes `argc` and `argv` arguments to be stored //! in a globally-accessible location for use by the `os` module. //! -//! Only valid to call on linux. Mac and Windows use syscalls to +//! Only valid to call on Linux. Mac and Windows use syscalls to //! discover the command line arguments. //! //! FIXME #7756: Would be nice for this to not exist. diff --git a/src/librustrt/c_str.rs b/src/librustrt/c_str.rs index d68fef30622..000def0cc3b 100644 --- a/src/librustrt/c_str.rs +++ b/src/librustrt/c_str.rs @@ -19,7 +19,7 @@ string types are *not* null terminated. The other problem with translating Rust strings to C strings is that Rust strings can validly contain a null-byte in the middle of the string (0 is a -valid unicode codepoint). This means that not all Rust strings can actually be +valid Unicode codepoint). This means that not all Rust strings can actually be translated to C strings. # Creation of a C string diff --git a/src/librustrt/local_ptr.rs b/src/librustrt/local_ptr.rs index ef56cd3b1da..8ce12a5157d 100644 --- a/src/librustrt/local_ptr.rs +++ b/src/librustrt/local_ptr.rs @@ -107,10 +107,10 @@ pub mod compiled { // efficient sequence of instructions. This also involves dealing with fun // stuff in object files and whatnot. Regardless, it turns out this causes // trouble with green threads and lots of optimizations turned on. The - // following case study was done on linux x86_64, but I would imagine that + // following case study was done on Linux x86_64, but I would imagine that // other platforms are similar. // - // On linux, the instruction sequence for loading the tls pointer global + // On Linux, the instruction sequence for loading the tls pointer global // looks like: // // mov %fs:0x0, %rax -- cgit 1.4.1-3-g733a5