From 5611cce6f0b03b5bcf0fcd4f230abf7d1f645b1e Mon Sep 17 00:00:00 2001 From: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Date: Fri, 8 Apr 2022 17:08:36 +0900 Subject: [PATCH] Prepared Brand page for new blockquotes (#5012) Updated existing use of blockquotes in preparation for the new styling. See https://github.com/fleetdm/fleet/pull/5009 --- handbook/brand.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/handbook/brand.md b/handbook/brand.md index 72f9e1d51f..43b6aec5a3 100644 --- a/handbook/brand.md +++ b/handbook/brand.md @@ -18,11 +18,11 @@ At Fleet, our voice and tone should be clear, simple, friendly, and inspiring - 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.* +- *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.* +- *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. @@ -38,18 +38,18 @@ For Fleet the product, we say either *“Fleet”* or *“Fleet for osquery”*. ### 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. In **sentence case**, we write titles as if they were sentences. For example: -> **A**sk questions about your servers, containers, and laptops running **L**inux, **W**indows, and macOS +- **A**sk questions about your servers, containers, and laptops running **L**inux, **W**indows, and macOS As we are using sentence case, only the first word of a heading and subheading is capitalized. However, if a word in the sentence would normally be capitalized (e.g. a [proper noun](https://www.grammarly.com/blog/proper-nouns/?&utm_source=google&utm_medium=cpc&utm_campaign=11862361094&utm_targetid=dsa-1233402314764&gclid=Cj0KCQjwg7KJBhDyARIsAHrAXaFwpnEyL9qrS4z1PEAgFwh3RXmQ24zmwmowAyOQbHngsI8W_F730aAaArrwEALw_wcB&gclsrc=aw.ds),) these words should also be capitalized in the heading. > Note the capitalization of _“macOS”_ in the example above. Although this is a proper noun, macOS uses its own style guide from Apple, that we adhere to. ### How use osquery in sentences and headings Osquery should always be written in lowercase, unless used to start a sentence or heading. For example: -> _Open source software, built on **o**squery._ +- _Open source software, built on **o**squery._ or -> _**O**squery and Fleet provide structured, convenient access to information about your devices._ +- _**O**squery and Fleet provide structured, convenient access to information about your devices._ ## Brand resources