diff --git a/LICENSE b/LICENSE
index a905624..3c7c6a4 100644
--- a/LICENSE
+++ b/LICENSE
@@ -12,8 +12,8 @@ furnished to do so, subject to the following conditions:
 The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WdataANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WdataANTIES OF MERCHANTABILITY,
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
diff --git a/docs/index.rst b/docs/index.rst
index 378217c..d39e71e 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -51,7 +51,7 @@ so we call :class:`list` on this to get out the values.
 
 The above :func:`map` example executes the function in *serial* over each
 element in ``data``. That is, it just goes one by one through the ``data``
-object, executes the function, returns, and cdataies on, all on the same
+object, executes the function, returns, and carries on, all on the same
 processor core. If we can write our code in this style (using :func:`map`), we
 can easily swap in the ``Pool`` classes provided by ``schwimmbad`` to allow us
 to switch between various parallel processing frameworks. The easiest to
diff --git a/paper/paper.bib b/paper/paper.bib
index 70bb32f..784f7f8 100644
--- a/paper/paper.bib
+++ b/paper/paper.bib
@@ -9,9 +9,9 @@ @techreport{Forum1994
 
 @InProceedings{Gabriel2004,
   author       = {Edgar Gabriel and Graham E. Fagg and George Bosilca
-                  and Thara Angskun and Jack J. Dongdataa and Jeffrey
+                  and Thara Angskun and Jack J. Dongdarra and Jeffrey
                   M. Squyres and Vishal Sahay and Prabhanjan Kambadur
-                  and Brian Bdataett and Andrew Lumsdaine and Ralph
+                  and Brian Barrett and Andrew Lumsdaine and Ralph
                   H. Castain and David J. Daniel and Richard L. Graham
                   and Timothy S. Woodall },
   title        = {Open {MPI}: Goals, Concept, and Design of a Next
diff --git a/paper/paper.md b/paper/paper.md
index 9d0a0af..ee1b847 100644
--- a/paper/paper.md
+++ b/paper/paper.md
@@ -26,7 +26,7 @@ Many scientific and computing problems require doing some calculation on all
 elements of some data set. If the calculations can be executed in parallel
 (i.e. without any communication between calculations), these problems are said
 to be [*perfectly
-parallel*](https://en.wikipedia.org/wiki/Embdataassingly_parallel). On computers
+parallel*](https://en.wikipedia.org/wiki/Embarrassingly_parallel). On computers
 with multiple processing cores, these tasks can be distributed and executed in
 parallel to greatly improve performance. A common paradigm for handling these
 distributed computing problems is to use a processing "pool": the "tasks" (the
diff --git a/tests/test_utils.py b/tests/test_utils.py
index ff12456..5687354 100644
--- a/tests/test_utils.py
+++ b/tests/test_utils.py
@@ -25,7 +25,7 @@ def test_batch_tasks():
     tasks = batch_tasks(10, n_tasks=101, args=(99,))
     assert len(tasks) == 10
 
-    # With dataay specified
+    # With data specified
     data = np.random.random(size=123)
     tasks = batch_tasks(10, data=data, args=(99,))
     assert len(tasks) == 10