From 6a1a6f48c2dce0f4abd851c0de168487a4b80394 Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Wed, 15 Feb 2023 23:44:55 -0600 Subject: [PATCH] Adjust DRI for content style guide and add guidance about how to use fleets (#9869) --- handbook/marketing/content-style-guide.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/handbook/marketing/content-style-guide.md b/handbook/marketing/content-style-guide.md index 535b1aab2d..d2727c5102 100644 --- a/handbook/marketing/content-style-guide.md +++ b/handbook/marketing/content-style-guide.md @@ -46,6 +46,10 @@ For Fleet the product, we say either “Fleet” or “Fleet for osquery.” Employees are “Fleeties.” +#### Capitalizing "fleets" + +When talking about a group of devices or virtual servers, use "fleet" or "fleets" (lowercase). When talking about the product or company, use "Fleet" (capitalized). + #### Capitalizing osquery Osquery should always be written in lowercase unless used to start a sentence or heading: @@ -283,5 +287,5 @@ You don’t need to wait until a change has been made to write a new doc. Starti Writing about how to use a new feature puts you in the shoes of the user. If something seems complicated, you have the opportunity to improve it — before committing a line of code. - +