diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8913d4636b..ad6e6ef8bc 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -29,7 +29,7 @@ Also, regarding the Sonic Pi development process:
 - We prefer an issue ticket to be raised as soon as possible when a new bug is discovered (ideally within 48 hours)
 - When someone intends to start work on an issue or new feature:
   - They check first that no-one else intends to (or has already done) work on it, via the [Issues page](https://github.com/sonic-pi-net/sonic-pi/issues) or [the Sonic Pi features project board](https://github.com/orgs/sonic-pi-net/projects/1)
-  - If the issue or feature is freely available for work, the person who intends to start work on it mentions this publically somewhere (for issues, leaving a message on the ticket requesting to be assigned to it, and for new features, mentioning it in any of the places we gather as a [community](COMMUNITY.md))
+  - If the issue or feature is freely available for work, the person who intends to start work on it mentions this publicly somewhere (for issues, leaving a message on the ticket requesting to be assigned to it, and for new features, mentioning it in any of the places we gather as a [community](COMMUNITY.md))
 
 ## Ideal process for contributing with code
 1. Familiarise yourself with the part(s) of the code that you wish to contribute towards if necessary. We're always happy to answer questions about the Sonic Pi code!