docs: fix typos

Author: kianmeng

docs/ISSUES.md

@@ -48,7 +48,7 @@ An optional step when triaging is to adjust the title once more information is
 known. Sometimes an issue starts as a question, and through discussion, it
 turns out to be a feature request, or a bug report. In those cases, the title
 should be changed from a question, and the title should be a succict action to
-be taken. For example, a question about an non-existant configuration option
+be taken. For example, a question about an non-existent configuration option
 may be reworded to "Add option to Client to do Zed".
 
 ### Mentoring

docs/ROADMAP.md

@@ -82,7 +82,7 @@ of `http` and `hyper` are prepared for that, there's two potential problems.
 - New HTTP versions
   - HTTP/3 will require a new transport abstraction. It's not as simple as just using some
     `impl AsyncRead + AsyncWrite`. While HTTP/2 bundled the concept of stream creation internally,
-    and thus could be managed wholy on top of a read-write transport, HTTP/3 is different. Stream
+    and thus could be managed wholly on top of a read-write transport, HTTP/3 is different. Stream
     creation is shifted to the QUIC protocol, and HTTP/3 needs to be able to use that directly.
   - This means the existing `Connection` types for both client and server will not be able to
     accept a QUIC transport so we can add HTTP/3 support.

src/common/io/rewind.rs

@@ -60,7 +60,7 @@ where
                 // TODO: There should be a way to do following two lines cleaner...
                 buf.put_slice(&prefix[..copy_len]);
                 prefix.advance(copy_len);
-                // Put back whats left
+                // Put back what's left
                 if !prefix.is_empty() {
                     self.pre = Some(prefix);
                 }

src/proto/h1/conn.rs

@@ -586,7 +586,7 @@ where
         }
     }
 
-    // Fix keep-alives when Connection: keep-alive header is not present
+    // Fix keep-alive when Connection: keep-alive header is not present
     fn fix_keep_alive(&mut self, head: &mut MessageHead<T::Outgoing>) {
         let outgoing_is_keep_alive = head
             .headers

src/proto/h1/role.rs

@@ -949,7 +949,7 @@ impl Http1Transaction for Client {
                         #[cfg(feature = "ffi")]
                         let reason = {
                             let reason = res.reason.unwrap();
-                            // Only save the reason phrase if it isnt the canonical reason
+                            // Only save the reason phrase if it isn't the canonical reason
                             if Some(reason) != status.canonical_reason() {
                                 Some(Bytes::copy_from_slice(reason.as_bytes()))
                             } else {

src/proto/h2/server.rs

@@ -143,7 +143,7 @@ where
             #[cfg(feature = "runtime")]
             keep_alive_timeout: config.keep_alive_timeout,
             // If keep-alive is enabled for servers, always enabled while
-            // idle, so it can more aggresively close dead connections.
+            // idle, so it can more aggressively close dead connections.
             #[cfg(feature = "runtime")]
             keep_alive_while_idle: true,
         };
@@ -264,7 +264,7 @@ where
                         let reason = err.h2_reason();
                         if reason == Reason::NO_ERROR {
                             // NO_ERROR is only used for graceful shutdowns...
-                            trace!("interpretting NO_ERROR user error as graceful_shutdown");
+                            trace!("interpreting NO_ERROR user error as graceful_shutdown");
                             self.conn.graceful_shutdown();
                         } else {
                             trace!("abruptly shutting down with {:?}", reason);