summaryrefslogtreecommitdiff
path: root/docs/source/internal
diff options
context:
space:
mode:
authorAnthony Sottile <asottile@umich.edu>2020-09-20 19:15:15 -0700
committerAnthony Sottile <asottile@umich.edu>2020-09-20 19:16:10 -0700
commit2fe70dda6b6327b00f318e121016f3ca372461c2 (patch)
treec4a2ea2bae5e8570c7110633f9b2be8959bad089 /docs/source/internal
parent93209ffac9f7dd5a1bdf2f3a01409d18339554a5 (diff)
downloadflake8-2fe70dda6b6327b00f318e121016f3ca372461c2.tar.gz
fix a few small spelling issues
found via `pre-commit try-repo https://github.com/codespell-project/codespell --all-files`
Diffstat (limited to 'docs/source/internal')
-rw-r--r--docs/source/internal/checker.rst2
-rw-r--r--docs/source/internal/index.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/source/internal/checker.rst b/docs/source/internal/checker.rst
index d11117c..35eac0e 100644
--- a/docs/source/internal/checker.rst
+++ b/docs/source/internal/checker.rst
@@ -5,7 +5,7 @@
In |Flake8| 2.x, |Flake8| delegated check running to pep8. In 3.0 |Flake8|
takes on that responsibility. This has allowed for simpler
handling of the ``--jobs`` parameter (using :mod:`multiprocessing`) and
-simplified our fallback if something goes awry with concurency.
+simplified our fallback if something goes awry with concurrency.
At the lowest level we have a |FileChecker|. Instances of |FileChecker| are
created for *each* file to be analyzed by |Flake8|. Each instance, has a copy
of all of the plugins registered with setuptools in the ``flake8.extension``
diff --git a/docs/source/internal/index.rst b/docs/source/internal/index.rst
index 9e31d0b..a6a203b 100644
--- a/docs/source/internal/index.rst
+++ b/docs/source/internal/index.rst
@@ -4,7 +4,7 @@
While writing |Flake8| 3.0, the developers attempted to capture some reasoning
and decision information in internal documentation meant for future developers
-and maintaners. Most of this information is unnecessary for users and plugin
+and maintainers. Most of this information is unnecessary for users and plugin
developers. Some of it, however, is linked to from the plugin development
documentation.