summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--CHANGES.md2
-rw-r--r--docs/documentation.md2
-rw-r--r--src/tests/documentation.py2
3 files changed, 3 insertions, 3 deletions
diff --git a/CHANGES.md b/CHANGES.md
index 36a5877..f76724b 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -32,7 +32,7 @@ lacking dunder attributes, like `dict.__setitem__`.
## 5.0.7 (2021-04-14)
The decorator module was not passing correctly the defaults inside the
-`*args` tuple, thanks to Dan Shult for the fix. Also fixed some mispellings
+`*args` tuple, thanks to Dan Shult for the fix. Also fixed some misspellings
in the documentation and integrated codespell in the CI, thanks to
Christian Clauss.
diff --git a/docs/documentation.md b/docs/documentation.md
index fa3145f..cc92eb9 100644
--- a/docs/documentation.md
+++ b/docs/documentation.md
@@ -1492,7 +1492,7 @@ with ``functools.singledispatch``, the assertion will break: ``g`` will return
will insert the ``Container`` class right before ``S``.
Notice that here I am not making any bold claim such as "the standard
-library algorithm is wrong and my algorithm is right" or viceversa. It
+library algorithm is wrong and my algorithm is right" or vice versa. It
just point out that there are some subtle differences. The only way to
understand what is really happening here is to scratch your head by
looking at the implementations. I will just notice that
diff --git a/src/tests/documentation.py b/src/tests/documentation.py
index b2794d4..bbbe562 100644
--- a/src/tests/documentation.py
+++ b/src/tests/documentation.py
@@ -1171,7 +1171,7 @@ with ``functools.singledispatch``, the assertion will break: ``g`` will return
will insert the ``Container`` class right before ``S``.
Notice that here I am not making any bold claim such as "the standard
-library algorithm is wrong and my algorithm is right" or viceversa. It
+library algorithm is wrong and my algorithm is right" or vice versa. It
just point out that there are some subtle differences. The only way to
understand what is really happening here is to scratch your head by
looking at the implementations. I will just notice that