Update README.md

processing · Nov 25, 2024 · 25c066c · 25c066c
1 parent 2153a8e
commit 25c066c
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/README.md b/README.md
@@ -19,7 +19,7 @@ If you're interested in *using* Processing, head over to the [download page](htt
 For assistance with your own sketches, projects, or code, please post your question on the Processing forum: https://discourse.processing.org/. Our community is full of experienced developers and knowledgeable users who are eager to help. Before you post, please take a moment to read the [guidelines on asking questions](https://discourse.processing.org/t/guidelines-asking-questions/2147) to make sure you get the best possible help. We’re incredibly grateful for the support and knowledge shared by everyone on the forum over the years.
 
 ## Contributing to Processing
-Processing is a labor of love, built over decades by people who believed in this community and genuinely enjoyed contributing to it. It’s easy to assume Processing is “just that way,” but everything you see here is the result of collective effort. If you want to fix a bug that’s been bothering you or give back to the project in other ways, you’re in the right place! 
+Processing is a labor of love, built over decades by people who believed in this community and genuinely enjoyed contributing to it. It’s easy to assume Processing is “just that way,” but everything you see here is the result of collective effort. If you want to fix a bug that’s been bothering you or give back to the project in other ways, you’re in the right place! For detailed guidelines on how to contribute, please see our [CONTRIBUTING.md](CONTRIBUTING.md).
 
 We understand that contributing to open source can be intimidating, but mistakes are part of learning—and we are all learners here. We do not assume knowledge or imply that somebody should already know any particular thing. Whether you’re a newcomer or an expert, your knowledge and contributions are valuable. Never hesitate to ask questions, open an issue, a pull request, or write a comment. We also encourage you to step in if you can: reply to issues, review PRs, or help out in whatever way feels right for you.