docs(lib): fix some typos (#2818)

Signed-off-by: cuishuang <imcusg@gmail.com>

docs/CODE_OF_CONDUCT.md

@@ -4,7 +4,7 @@
 
 - Don't be mean.
 - Insulting anyone is prohibited.
-- Harrassment of any kind is prohibited.
+- Harassment of any kind is prohibited.
 - If another person feels uncomfortable with your remarks, stop it.
 - If a moderator deems your comment or conduct as inappropriate, stop it.
 - Disagreeing is fine, but keep it to technical arguments. Never attack the person.

docs/TENETS.md

@@ -30,7 +30,7 @@ important than **Correct** or **Fast**:
 
 - Say an individual were to bring forward a contribution that makes hyper more
   correct, or faster, perhaps fixing some serious bug. But in doing so, they
-  also insulted people, harrassed other contributors or users, or shamed
+  also insulted people, harassed other contributors or users, or shamed
   everyone for the previous code. They felt their contribution was "invaluable".
   We would not accept such a contribution, instead banning the user and
   rewriting the code amongst the kind collaborators of the project.

src/client/conn.rs

@@ -494,7 +494,7 @@ where
     ///
     /// This setting is configured by the server peer by sending the
     /// [`SETTINGS_ENABLE_CONNECT_PROTOCOL` parameter][2] in a `SETTINGS` frame.
-    /// This method returns the currently acknowledged value recieved from the
+    /// This method returns the currently acknowledged value received from the
     /// remote.
     ///
     /// [1]: https://datatracker.ietf.org/doc/html/rfc8441#section-4

src/ext.rs

@@ -179,7 +179,7 @@ impl OriginalHeaderOrder {
     // is needed to compile. Once ffi is stablized `no_run` should be removed
     // here.
     /// This returns an iterator that provides header names and indexes
-    /// in the original order recieved.
+    /// in the original order received.
     ///
     /// # Examples
     /// ```no_run

src/ffi/task.rs

@@ -32,7 +32,7 @@ pub struct hyper_executor {
     /// The executor of all task futures.
     ///
     /// There should never be contention on the mutex, as it is only locked
-    /// to drive the futures. However, we cannot gaurantee proper usage from
+    /// to drive the futures. However, we cannot guarantee proper usage from
     /// `hyper_executor_poll()`, which in C could potentially be called inside
     /// one of the stored futures. The mutex isn't re-entrant, so doing so
     /// would result in a deadlock, but that's better than data corruption.