diff --git a/editions/tw5.com/tiddlers/community/Contributing.tid b/editions/tw5.com/tiddlers/community/Contributing.tid
index 3e55a0a7f..332467405 100644
--- a/editions/tw5.com/tiddlers/community/Contributing.tid
+++ b/editions/tw5.com/tiddlers/community/Contributing.tid
@@ -20,7 +20,7 @@ PRs must meet these minimum requirements before they can be considered for mergi
 * The title of the PR should be written in the imperative mood. See below
 * Adequate explanation in the body of the PR for the motivation and implementation of the change. Focus on the //why// and //what//, rather than the //how//
 * PRs must be self-contained. Although they can link to material elsewhere, everything needed to understand the intention of the PR should be included
-* Any visual changes introuced by the PR should be noted and illustrated with before/after screenshots
+* Any visual changes introduced by the PR should be noted and illustrated with before/after screenshots
 * Documentation as appropriate for end-users or developers
 * Observe the coding style
 * Read the developers documentation