Bump codespell from 2.1.0 to 2.2.1 (#139)

* Bump codespell from 2.1.0 to 2.2.1

Bumps [codespell](https://github.com/codespell-project/codespell) from 2.1.0 to 2.2.1.
- [Release notes](https://github.com/codespell-project/codespell/releases)
- [Commits](codespell-project/codespell@v2.1.0...v2.2.1)

---
updated-dependencies:
- dependency-name: codespell
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

* Fix spelling errors

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: paul.profizi <[email protected]>

Author: dependabot[bot]

ansys/dpf/post/misc_results.py

@@ -1,4 +1,4 @@
-"""This module contains all the miscallenous results."""
+"""This module contains all the miscellaneous results."""
 
 from ansys.dpf.core import Operator as _Operator
 from ansys.dpf.core import locations

docs/source/conf.py

@@ -90,7 +90,7 @@
     "examples_dirs": ["../../examples/"],
     # path where to save gallery generated examples
     "gallery_dirs": ["examples"],
-    # Patter to search for example files
+    # Pattern to search for example files
     "filename_pattern": r"\.py",
     # Remove the "Download all examples" button from the top level gallery
     "download_all_examples": False,

docs/source/contributing.rst

@@ -104,7 +104,7 @@ Consider the following general coding paradigms when contributing:
    guidelines, and always provide a for simple use cases for the new
    features.
 
-3. **Test it**. Since Python is an interperted language, if it's not
+3. **Test it**. Since Python is an interpreted language, if it's not
    tested, it's probably broken.  At the minimum, include unit tests
    for each new feature within the ``tests`` directory.  Ensure that
    each new method, class, or function has reasonable (>90%) coverage.

requirements/requirements_style.txt

@@ -1,2 +1,2 @@
 flake8==5.0.4
-codespell==2.1.0
+codespell==2.2.1