From 78de9b63c0e655c13e671fafb3548532a4614bf9 Mon Sep 17 00:00:00 2001 From: David Brochart Date: Mon, 23 Sep 2024 21:43:53 +0200 Subject: [PATCH] Fix typo --- docs/pages/future.rst | 4 ++-- docs/pages/pipeline.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/pages/future.rst b/docs/pages/future.rst index d85e9b0d7..0eb3662da 100644 --- a/docs/pages/future.rst +++ b/docs/pages/future.rst @@ -34,7 +34,7 @@ So, you have to turn you function into async one. And all callers of this function in async functions. And all their callers. This is really hard to model. -When you code has two types of uncomposable +When your code has two types of uncomposable functions you increase your mental complexity by extreme levels. Instead, you can use ``Future`` container, @@ -54,7 +54,7 @@ it allows you to model async interactions in a sync manner: ... return Future(first()).bind_awaitable(second) Now we can compose async functions and maintaining a sync context! -It is also possible run a ``Future`` +It is also possible to run a ``Future`` with regular tools like ``asyncio.run`` or ``anyio.run``: .. code:: python diff --git a/docs/pages/pipeline.rst b/docs/pages/pipeline.rst index 7d90aaaee..f6a4e4c47 100644 --- a/docs/pages/pipeline.rst +++ b/docs/pages/pipeline.rst @@ -113,7 +113,7 @@ It might be later used with multiple values: >>> assert pipeline(2) == '2B' -It is also might be useful to compose containers together: +It also might be useful to compose containers together: .. code:: python