about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-07-14 10:05:21 +0200
committerGitHub <noreply@github.com>2024-07-14 10:05:21 +0200
commitdba010d7faa095139e244a0453c9d078564bda7f (patch)
tree35bc34efcd624ea8762bbd12a2f45a9ab055a9f1
parentbef29c0a8f0fd1ccf3df2a4758e98b53d0635eaf (diff)
parent99a5964b737bd78b471cca5da39e0d0f54e9eb36 (diff)
downloadrust-dba010d7faa095139e244a0453c9d078564bda7f.tar.gz
rust-dba010d7faa095139e244a0453c9d078564bda7f.zip
Rollup merge of #127704 - workingjubilee:fixup-better-than, r=ChrisDenton
Fix minor typos in std::process doc on Win argv
-rw-r--r--library/std/src/process.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/library/std/src/process.rs b/library/std/src/process.rs
index f351dab78dc..fc86578a5ff 100644
--- a/library/std/src/process.rs
+++ b/library/std/src/process.rs
@@ -96,9 +96,9 @@
 //! child processes must agree on how the commandline string is encoded.
 //!
 //! Most programs use the standard C run-time `argv`, which in practice results
-//! in consistent argument handling. However some programs have their own way of
+//! in consistent argument handling. However, some programs have their own way of
 //! parsing the commandline string. In these cases using [`arg`] or [`args`] may
-//! result in the child process seeing a different array of arguments then the
+//! result in the child process seeing a different array of arguments than the
 //! parent process intended.
 //!
 //! Two ways of mitigating this are: