Skip to content

Commit

Permalink
fix a couple of typos in synopsis
Browse files Browse the repository at this point in the history
  • Loading branch information
CaselIT authored Jun 26, 2024
1 parent 2463cee commit 90cef50
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/build/synopsis.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down Expand Up @@ -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::

Expand Down

0 comments on commit 90cef50

Please sign in to comment.