about summary refs log tree commit diff
path: root/src/libstd/ffi
diff options
context:
space:
mode:
authorAlexis Hunt <lexer@google.com>2018-01-10 17:58:00 -0500
committerAlexis Hunt <lexer@google.com>2018-01-10 17:58:00 -0500
commit9d9504a27c240f3e04bec95e382f8130282cca36 (patch)
treee8b1d795a1f3c61aaa9387afa8a25d668047933d /src/libstd/ffi
parentf62f774035735a06c880c48c0b9017fcc0577e33 (diff)
Fix typo.
Diffstat (limited to 'src/libstd/ffi')
-rw-r--r--src/libstd/ffi/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstd/ffi/mod.rs b/src/libstd/ffi/mod.rs
index a75596351e4..a37a5e8ae82 100644
--- a/src/libstd/ffi/mod.rs
+++ b/src/libstd/ffi/mod.rs
@@ -53,7 +53,7 @@
 //! terminator, so the buffer length is really `len+1` characters.
 //! Rust strings don't have a nul terminator; their length is always
 //! stored and does not need to be calculated. While in Rust
-//! accessing a string's length is a O(1) operation (becasue the
+//! accessing a string's length is a O(1) operation (because the
 //! length is stored); in C it is an O(length) operation because the
 //! length needs to be computed by scanning the string for the nul
 //! terminator.