summaryrefslogtreecommitdiff
path: root/src/unistd.rs
diff options
context:
space:
mode:
authorRyan Zoeller <rtzoeller@rtzoeller.com>2021-12-26 20:14:50 -0600
committerRyan Zoeller <rtzoeller@rtzoeller.com>2021-12-26 20:14:50 -0600
commit57f41a8898e80f220d231136e26193db77388c03 (patch)
tree8a064d923e45614a21b8a8cb9bd3029b9fdfca87 /src/unistd.rs
parenta392647f450f88bf4a162135712ea023e8da3b1a (diff)
downloadnix-57f41a8898e80f220d231136e26193db77388c03.zip
Fix typos
Diffstat (limited to 'src/unistd.rs')
-rw-r--r--src/unistd.rs6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/unistd.rs b/src/unistd.rs
index 01f35215..7aa1cffe 100644
--- a/src/unistd.rs
+++ b/src/unistd.rs
@@ -204,8 +204,8 @@ impl ForkResult {
/// Create a new child process duplicating the parent process ([see
/// fork(2)](https://pubs.opengroup.org/onlinepubs/9699919799/functions/fork.html)).
///
-/// After calling the fork system call (successfully) two processes will
-/// be created that are identical with the exception of their pid and the
+/// After successfully calling the fork system call, a second process will
+/// be created which is identical to the original except for the pid and the
/// return value of this function. As an example:
///
/// ```
@@ -225,7 +225,7 @@ impl ForkResult {
/// }
/// ```
///
-/// This will print something like the following (order indeterministic). The
+/// This will print something like the following (order nondeterministic). The
/// thing to note is that you end up with two processes continuing execution
/// immediately after the fork call but with different match arms.
///