Rollup merge of #126138 - wbk:patch-1, r=lqd

Fix typo in docs for std::pin

1 files changed, 1 insertions, 1 deletions

diff --git a/library/core/src/pin.rs b/library/core/src/pin.rs
index d8fc3b7177f..0d2aa3070a1 100644
--- a/library/core/src/pin.rs
+++ b/library/core/src/pin.rs
@@ -184,7 +184,7 @@
 //! requires at least a level of pointer indirection each time a new object is added to the mix
 //! (and, practically, a heap allocation).
 //!
-//! Although there were other reason as well, this issue of expensive composition is the key thing
+//! Although there were other reasons as well, this issue of expensive composition is the key thing
 //! that drove Rust towards adopting a different model. It is particularly a problem
 //! when one considers, for example, the implications of composing together the [`Future`]s which
 //! will eventually make up an asynchronous task (including address-sensitive `async fn` state