about summary refs log tree commit diff
diff options
context:
space:
mode:
authorDylan DPC <99973273+Dylan-DPC@users.noreply.github.com>2022-09-10 18:56:07 +0530
committerGitHub <noreply@github.com>2022-09-10 18:56:07 +0530
commit33d54c4f737a99e8acdec1377fc0f105ad24635d (patch)
treed193e3a00216030f7b5bb59880ec3aef928343b8
parent2386ed99628972bebdf85ea1dbc1d1f41b442111 (diff)
parent1933b74dbdd598edd3e54fcbf1d8b236ed5e82fc (diff)
downloadrust-33d54c4f737a99e8acdec1377fc0f105ad24635d.tar.gz
rust-33d54c4f737a99e8acdec1377fc0f105ad24635d.zip
Rollup merge of #101606 - akhi3030:patch-1, r=Dylan-DPC
doc: fix minor typo
-rw-r--r--library/std/src/thread/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/std/src/thread/mod.rs b/library/std/src/thread/mod.rs
index a17185b6f70..ceea6986e33 100644
--- a/library/std/src/thread/mod.rs
+++ b/library/std/src/thread/mod.rs
@@ -116,7 +116,7 @@
 //! Threads are able to have associated names for identification purposes. By default, spawned
 //! threads are unnamed. To specify a name for a thread, build the thread with [`Builder`] and pass
 //! the desired thread name to [`Builder::name`]. To retrieve the thread name from within the
-//! thread, use [`Thread::name`]. A couple examples of where the name of a thread gets used:
+//! thread, use [`Thread::name`]. A couple of examples where the name of a thread gets used:
 //!
 //! * If a panic occurs in a named thread, the thread name will be printed in the panic message.
 //! * The thread name is provided to the OS where applicable (e.g., `pthread_setname_np` in