Update CONTRIBUTING.md

Co-authored-by: aplaice <plaice.adam+github@gmail.com>

Author: axelboc

CONTRIBUTING.md

@@ -437,7 +437,7 @@ The recommended structure, which can of course be tweaked and expanded as needed
 
 Here are som additional guidelines:
 
-- If the upgrade is non-trivial, make sure to grab users attention with bold text, emojis, etc. at the top of the release notes.
+- If the upgrade is non-trivial, make sure to grab users' attention with bold text, emojis, etc. at the top of the release notes.
 - Don't write release notes from a contributor's point of view (i.e. one bullet point per pull request/commit/issue), but from a user's point of view (i.e. one bullet point per meaningful change). Indeed, it's common for one change to span multiple pull requests (e.g. new translation followed by various corrections), and it sometimes happens that multiple changes are done with a single pull request.
 - Be as specific as possible, for instance by mentioning the country name of the affected note, except when a lot of notes are affected by similar minor changes (like when a lot of typos/mistranslations are fixed in a specific language).
 - Always link to relevant issues and pull requests with the `#` syntax.