Adding note about coordinated disclosure (#4007)

* Adding note about coordinated disclosure

@mike-j-thomas Not sure exactly *where* in the document I should've put this. If you have 5 minutes to comment on this PR I'll adjust it!

* Updated as per Mike's comments

Put in the right section and updated

* Update brand.md

* Update handbook/brand.md

* Update brand.md

Re-added Guillaume's previous suggestion to voice and tone guidelines.

Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>

handbook/brand.md

@@ -10,6 +10,8 @@
 
 - **Manage risk, not fear**. Educate users about security threats positively. Risk management is smart, but focusing on fear can lead to poor decisions. We NEVER use fear as a communication and marketing tactic. 
 
+- **Consider the meaning of words**. We never want to offend people or sound judgemental. Industry jargon that was once commonly used may now be considered offensive and should be avoided.
+
 ### What would Mr Rogers say?
 
 At Fleet, our voice and tone should be clear, simple, friendly, and inspiring - like [Mr. Rogers](https://en.wikipedia.org/wiki/Fred_Rogers) who had a deep understanding of these communication values.
@@ -24,6 +26,8 @@ becomes...
 
 By Mr Rogering our writing we can emphasize positivity, optimism and encourage our readers to succeed. The example above also considers sentence flow and use of synonyms to reduce repetition.
 
+Another example to consider is industry jargon that may now be inappropriate. While the term *"responsible vulnerability disclosure"* has been used for decades, it supposes that people who use a different process are *irresponsible*. Using *coordinated disclosure* is a more positive way to discuss the issue.
+
 ## Voice and tone guidelines
 
 ### How to use our name