diff --git a/mistral/engine/actions.py b/mistral/engine/actions.py
index d7ba33dcf..64624f82e 100644
--- a/mistral/engine/actions.py
+++ b/mistral/engine/actions.py
@@ -567,7 +567,7 @@ class WorkflowAction(Action):
         )
 
         # If the parent has a root_execution_id, it must be a sub-workflow. So
-        # we should propogate that ID down. Otherwise the parent must be the
+        # we should propagate that ID down. Otherwise the parent must be the
         # root execution and we should use the parents ID.
         root_execution_id = parent_wf_ex.root_execution_id or parent_wf_ex.id
 
diff --git a/releasenotes/notes/make_integrity_checker_work_with_batches-56c1cd94200d4c38.yaml b/releasenotes/notes/make_integrity_checker_work_with_batches-56c1cd94200d4c38.yaml
index 52ef30393..201f2f532 100644
--- a/releasenotes/notes/make_integrity_checker_work_with_batches-56c1cd94200d4c38.yaml
+++ b/releasenotes/notes/make_integrity_checker_work_with_batches-56c1cd94200d4c38.yaml
@@ -1,7 +1,7 @@
 ---
 fixes:
   - |
-    Workflow execution integrity checker mechanism was too agressive in case
+    Workflow execution integrity checker mechanism was too aggressive in case
     of big workflows that have many task executions in RUNNING state at the
     same time. The mechanism was selecting them all in one query and calling
     "on_action_complete" for each of them within a single DB transaction.