From 00d10c22f831f7d4508444f17a84e19319eaf36b Mon Sep 17 00:00:00 2001
From: Zen <250477360+ZenPZero@users.noreply.github.com>
Date: Mon, 16 Feb 2026 05:51:10 -0500
Subject: [PATCH] task: fix two typos (#7913)

---
 tokio/src/task/blocking.rs | 2 +-
 tokio/src/task/mod.rs      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tokio/src/task/blocking.rs b/tokio/src/task/blocking.rs
index dbd6edaae..bac50a565 100644
--- a/tokio/src/task/blocking.rs
+++ b/tokio/src/task/blocking.rs
@@ -96,7 +96,7 @@ cfg_rt! {
     /// asynchronously.  When you run CPU-bound code using `spawn_blocking`, you
     /// should keep this large upper limit in mind. When running many CPU-bound
     /// computations, a semaphore or some other synchronization primitive should be
-    /// used to limit the number of computation executed in parallel. Specialized
+    /// used to limit the number of computations executed in parallel. Specialized
     /// CPU-bound executors, such as [rayon], may also be a good fit.
     ///
     /// This function is intended for non-async operations that eventually finish on
diff --git a/tokio/src/task/mod.rs b/tokio/src/task/mod.rs
index ebd3a1bce..b46d696eb 100644
--- a/tokio/src/task/mod.rs
+++ b/tokio/src/task/mod.rs
@@ -180,7 +180,7 @@
 //! #### `spawn_blocking`
 //!
 //! The `task::spawn_blocking` function is similar to the `task::spawn` function
-//! discussed in the previous section, but rather than spawning an
+//! discussed in the previous section, but rather than spawning a
 //! _non-blocking_ future on the Tokio runtime, it instead spawns a
 //! _blocking_ function on a dedicated thread pool for blocking tasks. For
 //! example: