Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 42

Adjust DRI for content style guide and add guidance about how to use fleets (#9869)

Browse source
This commit is contained in:
Mike McNeil 2023-02-15 23:44:55 -06:00 committed by GitHub
parent 7fb3526919
commit 6a1a6f48c2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
handbook/marketing/content-style-guide.md
View file

@ -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.
<meta name="maintainedBy" value="chris-mcgillicuddy">
<meta name="maintainedBy" value="jarodreyes">
<meta name="title" value="Content style guide">