From 90cef50c3ecb8880aa1580a566b0d0c2c4698080 Mon Sep 17 00:00:00 2001 From: Federico Caselli Date: Wed, 26 Jun 2024 10:21:16 +0200 Subject: [PATCH] fix a couple of typos in synopsis --- docs/build/synopsis.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/build/synopsis.rst b/docs/build/synopsis.rst index 55ea2e2..1c4934d 100644 --- a/docs/build/synopsis.rst +++ b/docs/build/synopsis.rst @@ -81,7 +81,7 @@ within ``send_receive_logic()`` - that code is only a pass through, receiving data to and from an opaque implementation. Must we convert **all** our code everywhere that acts as "pass through" to use ``async`` ``await``? -With awaitlet, we dont have to. awaitlet provides a **functional form +With awaitlet, we don't have to. awaitlet provides a **functional form of the Python await call**, which can be invoked from non-async functions, within an overall asyncio context. We can port our program above by: @@ -254,9 +254,9 @@ The ``value`` passed in becomes the **return value of the awaitlet() call**:: and we are then back in the hosted function with an awaitable having proceeded and its return value passed back from the :func:`.awaitlet` call. -The loop continues; each time ``context.dead`` is False, we know that +The loop continues; each time ``context.dead`` is ``False``, we know that ``result`` is yet another Python awaitable. Once ``context.dead`` is -True, then we know the function completed; we return the result! +``True``, then we know the function completed; we return the result! .. sourcecode::