From a25d95a8c4f443886e55b24c97d4bbee1d87283d Mon Sep 17 00:00:00 2001
From: Zen <250477360+ZenPZero@users.noreply.github.com>
Date: Sat, 14 Feb 2026 14:42:24 -0500
Subject: [PATCH] io: clarify the behavior of `AsyncWriteExt::shutdown()`
 (#7908)

---
 tokio/src/io/util/async_write_ext.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tokio/src/io/util/async_write_ext.rs b/tokio/src/io/util/async_write_ext.rs
index db4400bb7..9bdc49748 100644
--- a/tokio/src/io/util/async_write_ext.rs
+++ b/tokio/src/io/util/async_write_ext.rs
@@ -1294,8 +1294,8 @@ cfg_io_util! {
         /// async fn shutdown(&mut self) -> io::Result<()>;
         /// ```
         ///
-        /// Similar to [`flush`], all intermediately buffered is written to the
-        /// underlying stream. Once the operation completes, the caller should
+        /// Similar to [`flush`], all intermediately buffered content is written to
+        /// the underlying stream. Once the operation completes, the caller should
         /// no longer attempt to write to the stream. For example, the
         /// `TcpStream` implementation will issue a `shutdown(Write)` sys call.
         ///