diff --git a/README.md b/README.md
index c8d67d4..aa4f1fc 100644
--- a/README.md
+++ b/README.md
@@ -119,13 +119,13 @@ If no `dry_run` parameter is passed in, the run will be started in Rainforest.
 ## Rerunning failed tests
 If your Rainforest run fails due to a ["non-bug"](https://rainforest.engineering/2021-01-20-shipping-faster-orb/) (your testing environment might have had a hiccup, or a test might have needed to be tweaked, etc), then rather than make code changes and then run your full testing suite once more, you'll instead want to rerun just the tests that failed. The Rainforest QA GitHub Action uses GitHub [caching](https://docs.github.com/en/actions/advanced-guides/caching-dependencies-to-speed-up-workflows) to know when a workflow is [being rerun](https://docs.github.com/en/actions/managing-workflow-runs/re-running-workflows-and-jobs). It will then automatically rerun only the tests which failed in the previous run.
 
-## Running multiple Rainforest runs from a single workflow using `worklow_call`
+## Running multiple Rainforest runs from a single workflow using `workflow_call`
 The Rainforest QA GitHub Action cannot detect on its own when it is being called multiple times in a single workflow through an intermediary reusable workflow. This means that the second invocation will attempt to rerun the run created by the first invocation, which will fail if that run has no failed tests to rerun. In order to avoid this situation, set the `cache_key` parameter to a distinct value in each invocation:
 
 ```yml
 # reusable workflow
 on:
-  worklow_call:
+  workflow_call:
     inputs:
       cache_key:
         type: string