Updated Communicating as Fleet (#3802)

* Updated Communicating as Fleet

I have made a start to our Communicating as Fleet style guide. It's not perfect. Feedback welcome.

* Update handbook/growth.md

* Update handbook/growth.md

handbook/growth.md

@@ -43,7 +43,21 @@ A browser compatibility check of [fleetdm.com](https://fleetdm.com/) should be c
 
 - **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. 
 
-## Voice and grammar guidelines
+### 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.
+
+Consider the example tweets below. What would Mr. Rogers say?
+
+> *Distributed workforces aren’t going anywhere anytime soon. **It’s past time** to **start engaging meaningfully** with your **workforce** and **getting them** to work with your security team instead of around them.*
+ 
+becomes...
+
+> *Distributed workforces aren’t going anywhere anytime soon, **so it’s a great time** to **engage** with your **crew** and **help them** to work with your security team instead of around them.*
+
+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.
+
+## Voice and tone guidelines
 
 ### How to write headings & subheadings
 Fleet uses **sentence case** capitalization for all headings across Fleet EE, fleetdm.com, our documentation, and our social media channels.