diff --git a/docs/pages/interfaces.rst b/docs/pages/interfaces.rst
index 8daf38b0e..d83ceca2d 100644
--- a/docs/pages/interfaces.rst
+++ b/docs/pages/interfaces.rst
@@ -575,7 +575,7 @@ do not have type aliases for one type argument in a form of ``ResultLike1``.
 Why does ``Mappable1`` exists and ``ResultLike1`` does not?
 
 Because ``Mappable1`` does make sense.
-But, ``ResultLike1`` requiers at least two (value and error) types to exist.
+But, ``ResultLike1`` requires at least two (value and error) types to exist.
 The same applies for ``ReaderLike1`` and ``ReaderResultLike1``
 and ``ReaderResultLike2``.
 
diff --git a/returns/primitives/reawaitable.py b/returns/primitives/reawaitable.py
index 7093be7ce..2db1b0b6e 100644
--- a/returns/primitives/reawaitable.py
+++ b/returns/primitives/reawaitable.py
@@ -16,7 +16,7 @@ class ReAwaitable(object):
     Allows to write coroutines that can be awaited multiple times.
 
     It works by actually caching the ``await`` result and reusing it.
-    So, in reallity we still ``await`` once,
+    So, in reality we still ``await`` once,
     but pretending to do it multiple times.
 
     Why is that required? Because otherwise,