diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index a24e3de78f9d3d1a6db18a4cc9a15a510b394e67..96dd9c944b59dd882c2af0a7a9bb4266f2f13305 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -92,3 +92,6 @@ repos:
     rev: v2.3.0
     hooks:
       - id: codespell
+        args:
+          - "-L"
+          - "anull,Cruzer"
diff --git a/content/pep-621-and-setuptools.rst b/content/pep-621-and-setuptools.rst
index 90e9bb3c1ae9a4dbe08486b79a52fe5b72e2d41a..7e2f5950f3dd42c35070441f50f20b359221e217 100644
--- a/content/pep-621-and-setuptools.rst
+++ b/content/pep-621-and-setuptools.rst
@@ -17,7 +17,7 @@ Why?
 
 - Avoid having a plethora of Python package managers installed. This is more
   noticeable when some are wrappers or replacements of virtualenv and then you
-  need to insall them globally.
+  need to install them globally.
 
 - With Setuptools you keep close to the state of `PEP 621
   <https://peps.python.org/pep-0621/>`_ and your :code:`pyproject.toml` generic
@@ -29,7 +29,7 @@ Why not?
 
 - You need a very recent version of Setuptools. At the time of writing this
   post I didn't find a distribution that had a new enough version of Setuptools
-  pacakged.
+  packaged.
 
 - You need a supported version of Python. Currently this means Python 3.7 or
   later.
diff --git a/content/spam_me.rst b/content/spam_me.rst
index 7d239a21657d8d73a3fcba0684d1bad899f705f3..a3aa3bbd21ff3f758ca520c36efa13b6825a9bbb 100644
--- a/content/spam_me.rst
+++ b/content/spam_me.rst
@@ -14,7 +14,7 @@ in place for such things.
 
 A few months went by and I remembered that project and started to play around
 with receiving such messages but sending them from a webpage. The outcome is
-`shore.co.il/spam <https://www.shore.co.il/spam>`_. I'm annnouncing this on my
+`shore.co.il/spam <https://www.shore.co.il/spam>`_. I'm announcing this on my
 blog as I'm actually interested to see if I get any spam this way. The desktop
 side of things is in this `rcfiles commit
 <https://git.shore.co.il/nimrod/rcfiles/-/commit/1e912443df1d8066f074a4addb1b443ada9ee36e>`_
diff --git a/content/tf-project-structure.rst b/content/tf-project-structure.rst
index ec1978d06ff598e14a4ae8a26176f4635bb06e83..4b9b527aa29289459a5db355045a4f1a69904b48 100644
--- a/content/tf-project-structure.rst
+++ b/content/tf-project-structure.rst
@@ -145,7 +145,7 @@ think that if you read it all you would see that I think that there are better
 and easier ways. You can compare Terragrunt to a badly managed Terraform project
 and find that it helps you. But when you compare to it one that uses the suggested
 convention, it makes things more difficult, doesn't deliver on the promise of
-keeping your code DRY and promotes bad habbits.
+keeping your code DRY and promotes bad habits.
 
 I didn't plan on reviewing Terragrunt until I used it. Terragrunt makes life
 less enjoyable. It has a convoluted workflow locally (with those bloody git