about summary refs log tree commit diff
path: root/src/libstd/sys/redox/ext
diff options
context:
space:
mode:
authorGuillaume Gomez <guillaume1.gomez@gmail.com>2017-08-13 11:03:11 +0200
committerGitHub <noreply@github.com>2017-08-13 11:03:11 +0200
commitbc6659a8fef000c96665f6ba8d6ddcd1ef89623b (patch)
tree7887050320d236b12a5d5ec4e36eb535108ba922 /src/libstd/sys/redox/ext
parent9191fe1ef4228ccfa6d573f9546f1e315b433960 (diff)
parent3ab86fbab281ca059731c31fa2aee5d9afc7e6dc (diff)
downloadrust-bc6659a8fef000c96665f6ba8d6ddcd1ef89623b.tar.gz
rust-bc6659a8fef000c96665f6ba8d6ddcd1ef89623b.zip
Rollup merge of #43814 - Eijebong:fix_typos2, r=petrochenkov
Fix some typos

Follow up of #43794

If refined my script a little bit and found some more.
Diffstat (limited to 'src/libstd/sys/redox/ext')
-rw-r--r--src/libstd/sys/redox/ext/fs.rs2
-rw-r--r--src/libstd/sys/redox/ext/process.rs2
2 files changed, 2 insertions, 2 deletions
diff --git a/src/libstd/sys/redox/ext/fs.rs b/src/libstd/sys/redox/ext/fs.rs
index 9a0d1e06da3..5d4edc2cf92 100644
--- a/src/libstd/sys/redox/ext/fs.rs
+++ b/src/libstd/sys/redox/ext/fs.rs
@@ -121,7 +121,7 @@ pub trait OpenOptionsExt {
     #[stable(feature = "fs_ext", since = "1.1.0")]
     fn mode(&mut self, mode: u32) -> &mut Self;
 
-    /// Pass custom flags to the `flags` agument of `open`.
+    /// Pass custom flags to the `flags` argument of `open`.
     ///
     /// The bits that define the access mode are masked out with `O_ACCMODE`, to
     /// ensure they do not interfere with the access mode set by Rusts options.
diff --git a/src/libstd/sys/redox/ext/process.rs b/src/libstd/sys/redox/ext/process.rs
index c59524974bf..e68e180acf1 100644
--- a/src/libstd/sys/redox/ext/process.rs
+++ b/src/libstd/sys/redox/ext/process.rs
@@ -47,7 +47,7 @@ pub trait CommandExt {
     /// # Notes
     ///
     /// This closure will be run in the context of the child process after a
-    /// `fork`. This primarily means that any modificatons made to memory on
+    /// `fork`. This primarily means that any modifications made to memory on
     /// behalf of this closure will **not** be visible to the parent process.
     /// This is often a very constrained environment where normal operations
     /// like `malloc` or acquiring a mutex are not guaranteed to work (due to