docs(lib): fix some typos (#2818)
Signed-off-by: cuishuang <imcusg@gmail.com>
This commit is contained in:
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user