Update contributing.md
Few mistakes and a link to #maintainer-guidelines
@@ -65,12 +65,14 @@ This describes the overall steps to your first code contribution in OpenRefine.
- Make changes to the code to fix the issue. When you change the backend code, it's conveniant to also write one or more tests in Java to demonstrate the fix. You can imitate existing tests of comparable functionalities for that.
-- We now have [functional tests](#functional-tests). These are built with Cypress. They mimic a human user in front of a Chrome browser. If you change has a meaningful impact on the user interface, a functional test should probably be written.
+- We now have [functional tests](#functional-tests). These are built with Cypress. They mimic a human user in front of a Chrome browser. If your change has a meaningful impact on the user interface, a functional test should probably be written.
- If you made Java changes, run linting to make sure they conform to our code style, with `mvn formatter:format`.
-- commit your changes, using a message that contains one of the special words "closes" and "fixes" which are detected by Github, followed by the issue number, e.g. "closes #1234" or "fixes #1234", this will link the commit to the issue you are working on.
+- Commit your changes, using a message that contains one of the special words "closes" and "fixes" which are detected by Github, followed by the issue number, e.g. "closes #1234" or "fixes #1234", this will link the commit to the issue you are working on.
-- push your branch to your fork and create a pull request for it, explaining the approach you have used, any design decisions you have made.
+- Push your branch to your fork and create a pull request for it, explaining the approach you have used, any design decisions you have made.
Thank you!
+
+For more information, there is also the [Maintainer Guidelines](#maintainer-guidelines) section.
