diff --git a/.github/ISSUE_TEMPLATE/z_release_patch.md b/.github/ISSUE_TEMPLATE/z_release_patch.md
index c15311e421..d89566bbe3 100644
--- a/.github/ISSUE_TEMPLATE/z_release_patch.md
+++ b/.github/ISSUE_TEMPLATE/z_release_patch.md
@@ -39,7 +39,7 @@ If all is good, then in 24h, I will start the release. Thanks!
     - [ ] Manually document any known migration steps and known issues.
     - [ ] Add a link to the new release page in the [Release Notes](https://docs.communityhealthtoolkit.org/core/releases/#release-notes) section.
     - [ ] Assign the PR to:
-        - A develoer
+        - A developer
         - An SRE to review and confirm the documentation on upgrade instructions and breaking changes is sufficient
 - [ ] Create a release in GitHub from the release branch so it shows up under the [Releases tab](https://github.com/medic/cht-core/releases) with the naming convention `<major>.<minor>.<patch>`, and change the Target dropdown to the release branch (eg: `4.4.x`). This will create the git tag automatically. Ensure the release notes PR above is merged. Link to the release notes in the description of the release.
 - [ ] Confirm the release build completes successfully and the new release is available on the [market](https://staging.dev.medicmobile.org/_couch/builds_4/_design/builds/_view/releases). Make sure that the document has new entry with `id: medic:medic:<major>.<minor>.<patch>`