Skip to content

Commit f0144ae

Browse files
committed
typos in IntoFuture docs
1 parent 5fb8a39 commit f0144ae

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

library/core/src/future/into_future.rs

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ use crate::future::Future;
22

33
/// Conversion into a `Future`.
44
///
5-
/// By implementing `Intofuture` for a type, you define how it will be
5+
/// By implementing `IntoFuture` for a type, you define how it will be
66
/// converted to a future.
77
///
88
/// # `.await` desugaring
@@ -29,7 +29,7 @@ use crate::future::Future;
2929
/// When implementing futures manually there will often be a choice between
3030
/// implementing `Future` or `IntoFuture` for a type. Implementing `Future` is a
3131
/// good choice in most cases. But implementing `IntoFuture` is most useful when
32-
/// implementing "async builder" types, which allows the type to be modified
32+
/// implementing "async builder" types, which allow their values to be modified
3333
/// multiple times before being `.await`ed.
3434
///
3535
/// ```rust

0 commit comments

Comments
 (0)