improved wording guidelines

Author: mtrezza

CONTRIBUTING.md

@@ -207,11 +207,11 @@ Adding a new security check for your feature is easy and fast:
 #### Wording Guideline
 Consider the following when adding a new security check:
 - *Group.name*: The category name; ends without period as this is a headline.
-- *Check.title*: Is the positive hypothesis that should be checked; ends without period as this is a title.
+- *Check.title*: Is the positive hypothesis that should be checked (for example "Door locked" instead of "Door unlocked"); ends without period as this is a title.
 - *Check.warning*: The warning if the test fails; ends with period as this is a description.
 - *Check.solution*: The recommended solution if the test fails; ends with period as this is an instruction.
 - The wordings must not contain any sensitive information such as keys, as the security report may be exposed in logs.
-- The wordings should be concise and not contain verbose explanations. Remember that these phrases contribute to data traffic and are therefore a cost factor that can become significant when scaling up.
+- The wordings should be concise and not contain verbose explanations.
 - Do not use pronouns such as "you" or "your" because log files can have various readers with different roles. Do not use pronouns such as "I" or "me" because although we love it dearly, Parse Server is not a human.
 
 ### Parse Error