about summary refs log tree commit diff
path: root/library/std/src
diff options
context:
space:
mode:
authorDan Gohman <dev@sunfishcode.online>2022-06-07 09:53:26 -0700
committerGitHub <noreply@github.com>2022-06-07 09:53:26 -0700
commitfbb59e706287525a9157edc65944030f9cd251fd (patch)
treebbc383a083878379634fc8b3841ebac49053cde5 /library/std/src
parent5ae95fa89a87a643ec74d5c164246146c8188228 (diff)
downloadrust-fbb59e706287525a9157edc65944030f9cd251fd.tar.gz
rust-fbb59e706287525a9157edc65944030f9cd251fd.zip
Update library/std/src/os/unix/io/mod.rs
Co-authored-by: Sean Stangl <sean.stangl@gmail.com>
Diffstat (limited to 'library/std/src')
-rw-r--r--library/std/src/os/unix/io/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/std/src/os/unix/io/mod.rs b/library/std/src/os/unix/io/mod.rs
index d2c5f741324..73cb3d31a7b 100644
--- a/library/std/src/os/unix/io/mod.rs
+++ b/library/std/src/os/unix/io/mod.rs
@@ -56,7 +56,7 @@
 //! and read from or written to must be `unsafe`? No. Rust's safety guarantees
 //! only cover what the program itself can do, and not what entities outside
 //! the program can do to it. `/proc/self/mem` is considered to be such an
-//! external entity, along with debugggers and people with physical access to
+//! external entity, along with debuggers and people with physical access to
 //! the hardware. This is true even in cases where the program is controling
 //! the external entity.
 //!