docs/CONTRIBUTING.md: Change formulation examples to discourage verbatim copying.

Co-authored-by: Eero Tamminen <eero.t.tamminen@intel.com>

diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
index 719f18b6204ed5dd488836f40097bc82f362f9bd..a2c51dab731cca176885785ea4b1f1ad569b5508 100644 (file)
--- a/docs/CONTRIBUTING.md
+++ b/docs/CONTRIBUTING.md
@@ -103,7 +103,8 @@ beginning of the line. To give the reader context for the information, the text
 should start with "${name} plugin" when making changes to a plugin, and
 "collectd" for the core daemon changes. Other common contexts are "Build
 system", and "Documentation". Use past tense and passive voice the for
-remainder, e.g. "a bug has been fixed", "a feature has been added".
+remainder, e.g. "a bug <describe impact> has been fixed", "a feature
+<describe impact> has been added".
 
 Some PRs should be excluded from the release notes, e.g. changes to project
 internal documentation (such as this file). Those changes are not interesting