about summary refs log tree commit diff
diff options
context:
space:
mode:
authorDan Gohman <dev@sunfishcode.online>2022-06-08 08:26:56 -0700
committerGitHub <noreply@github.com>2022-06-08 08:26:56 -0700
commite89ec68d5db9aa58b8170b351e730d45304c812b (patch)
treed450aa9fb51725fb9cff57c2ba9baa0166674dac
parent7656e085e3d056f0f0f35a9112727478a848350f (diff)
downloadrust-e89ec68d5db9aa58b8170b351e730d45304c812b.tar.gz
rust-e89ec68d5db9aa58b8170b351e730d45304c812b.zip
Update library/std/src/os/unix/io/mod.rs
Co-authored-by: Mara Bos <m-ou.se@m-ou.se>
-rw-r--r--library/std/src/os/unix/io/mod.rs5
1 files changed, 2 insertions, 3 deletions
diff --git a/library/std/src/os/unix/io/mod.rs b/library/std/src/os/unix/io/mod.rs
index 8935f303081..0a9c95fd409 100644
--- a/library/std/src/os/unix/io/mod.rs
+++ b/library/std/src/os/unix/io/mod.rs
@@ -46,9 +46,8 @@
 //!
 //! ## What about `/proc/self/mem` and similar OS features?
 //!
-//! Some platforms have special files, such as `/proc/self/mem`, which is a
-//! filesystem path that can be opened, producing a file descriptor that, when
-//! read from or written to, reads and writes the process's memory. These reads
+//! Some platforms have special files, such as `/proc/self/mem`, which 
+//! provide read and write access to the process's memory. Such reads
 //! and writes happen outside the control of the Rust compiler, so they do not
 //! uphold Rust's memory safety guarantees.
 //!