Update peps/pep-0800.rst

Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>

Author: JelleZijlstra

peps/pep-0800.rst

@@ -145,7 +145,7 @@ provide more precise type information to users.
 As a concrete example, a possible implementation of assignability with intersection types could be that
 given an intersection type ``A & B``, a type ``C`` is assignable to it if ``C`` is assignable to at least one of
 ``A`` and ``B``, and overlaps with all of ``A`` and ``B``. ("Overlaps" here means that at least one runtime value could exist
-that would be a member of both types. That is, ``A`` and ``B`` overlap if ``A & B`` is inhabited.) The second part of therule ensures that ``str`` is not assignable to a type like ``int & Any``: while ``str`` is assignable to ``Any``,
+that would be a member of both types. That is, ``A`` and ``B`` overlap if ``A & B`` is inhabited.) The second part of the rule ensures that ``str`` is not assignable to a type like ``int & Any``: while ``str`` is assignable to ``Any``,
 it does not overlap with ``int``. But of course, we can only know that ``str`` and ``int`` do not overlap if we know
 that both classes are solid bases.