From ac6063d27d43968251ad2a6e6d88d0160f63ca00 Mon Sep 17 00:00:00 2001 From: Timothy Date: Tue, 2 Apr 2024 09:53:48 +0800 Subject: [PATCH] fix a typo in status_quo.md --- src/vision/submitted_stories/status_quo.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/vision/submitted_stories/status_quo.md b/src/vision/submitted_stories/status_quo.md index 71dc633b..8be24009 100644 --- a/src/vision/submitted_stories/status_quo.md +++ b/src/vision/submitted_stories/status_quo.md @@ -36,7 +36,7 @@ Rust strives to be a language that brings together performance, productivity, an
Making hard choices from a complex ecosystem from the start -The problems begin from the very first moment a user starts to try out async Rust. The async Rust support in Rust itself is very basic, consisting only of the core Future mechanism. Everything else -- including the basic async runtimes themselves -- lives in user space. This means that users must make a number of choices rom the very beginning: +The problems begin from the very first moment a user starts to try out async Rust. The async Rust support in Rust itself is very basic, consisting only of the core Future mechanism. Everything else -- including the basic async runtimes themselves -- lives in user space. This means that users must make a number of choices from the very beginning: * what runtime to use * [Barbara makes their first foray into async](status_quo/barbara_makes_their_first_steps_into_async.md)