diff --git a/.github/workflows/basic.yml b/.github/workflows/basic.yml
index 64f1d1139..7b3dd61c4 100644
--- a/.github/workflows/basic.yml
+++ b/.github/workflows/basic.yml
@@ -129,4 +129,4 @@ jobs:
         runs-on: ubuntu-latest
         steps:
         - uses: actions/checkout@v4
-        - uses: crate-ci/typos@v1.28.4
+        - uses: crate-ci/typos@v1.29.4
diff --git a/.github/workflows/extra.yml b/.github/workflows/extra.yml
index 2f95a4ea7..3565768c5 100644
--- a/.github/workflows/extra.yml
+++ b/.github/workflows/extra.yml
@@ -181,4 +181,4 @@ jobs:
         runs-on: ubuntu-latest
         steps:
         - uses: actions/checkout@v4
-        - uses: crate-ci/typos@v1.28.4
+        - uses: crate-ci/typos@v1.29.4
diff --git a/docs/tutorials/executor_forces_tutorial.rst b/docs/tutorials/executor_forces_tutorial.rst
index 914edaf2a..1c2c3ecd0 100644
--- a/docs/tutorials/executor_forces_tutorial.rst
+++ b/docs/tutorials/executor_forces_tutorial.rst
@@ -380,7 +380,7 @@ Running forces application with input file
 Many applications read an input file instead of being given parameters directly on the run line.
 
 forces_simple_with_input_file_ directory contains a variant of this example, where a templated
-input file is parametized for each evaluation.
+input file is parameterized for each evaluation.
 
 This requires **jinja2** to be installed::