diff --git a/docs/pages/future.rst b/docs/pages/future.rst
index d85e9b0d..0eb3662d 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 7d90aaae..f6a4e4c4 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