From 7dcac97d0b9a0e993b842c6d678511921c7a370f Mon Sep 17 00:00:00 2001 From: Jane Lusby Date: Tue, 11 Aug 2020 10:22:40 -0700 Subject: [PATCH] Update book/src/dev/rfcs/XXXX-asynchronous-script-verification.md Co-authored-by: Deirdre Connolly --- book/src/dev/rfcs/XXXX-asynchronous-script-verification.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/src/dev/rfcs/XXXX-asynchronous-script-verification.md b/book/src/dev/rfcs/XXXX-asynchronous-script-verification.md index 7a5019e8..6fd281c2 100644 --- a/book/src/dev/rfcs/XXXX-asynchronous-script-verification.md +++ b/book/src/dev/rfcs/XXXX-asynchronous-script-verification.md @@ -106,7 +106,7 @@ In the first category, our state is presented to the rest of the application as a `Buffer`ed `tower::Service`. The `Buffer` wrapper allows shared access to a service using an actor model, moving the service to be shared into a worker task and passing messages to it over an multi-producer single-consumer -(mpsc) channel. The worker task recieves messages and makes `Service::call`s. +(mpsc) channel. The worker task receives messages and makes `Service::call`s. The `Service::call` method returns a `Future`, and the service is allowed to decide how much work it wants to do synchronously (in `call`) and how much work it wants to do asynchronously (in the `Future` it returns).