typos in IntoFuture docs

This commit is contained in:
KaDiWa4 2022-06-19 17:07:38 +02:00
parent 5fb8a39266
commit f0144aea74
No known key found for this signature in database
GPG Key ID: 0B52AE391C674CE5

View File

@ -2,7 +2,7 @@
/// Conversion into a `Future`. /// Conversion into a `Future`.
/// ///
/// By implementing `Intofuture` for a type, you define how it will be /// By implementing `IntoFuture` for a type, you define how it will be
/// converted to a future. /// converted to a future.
/// ///
/// # `.await` desugaring /// # `.await` desugaring
@ -29,7 +29,7 @@
/// When implementing futures manually there will often be a choice between /// When implementing futures manually there will often be a choice between
/// implementing `Future` or `IntoFuture` for a type. Implementing `Future` is a /// implementing `Future` or `IntoFuture` for a type. Implementing `Future` is a
/// good choice in most cases. But implementing `IntoFuture` is most useful when /// good choice in most cases. But implementing `IntoFuture` is most useful when
/// implementing "async builder" types, which allows the type to be modified /// implementing "async builder" types, which allow their values to be modified
/// multiple times before being `.await`ed. /// multiple times before being `.await`ed.
/// ///
/// ```rust /// ```rust