> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/resources/brand-guide/editorial-style-guide.md). # Editorial Style Guide - [Voice and Tone](https://guide.techfleet.org/resources/brand-guide/editorial-style-guide/voice-and-tone.md): This section covers how to portray the proper voice and tone with the Tech Fleet Brand. - [Editorial Writing](https://guide.techfleet.org/resources/brand-guide/editorial-style-guide/editorial-writing.md): This section covers the mechanics of how we write. It ensures our writing is clear, consistent, and respectful of all people. - [Interface Copywriting](https://guide.techfleet.org/resources/brand-guide/editorial-style-guide/interface-copywriting.md): Because we build digital products and experiences, we need rules for how we write interface copy. Our UX content must meet WCAG 2.1 AA and WCAG 2.2 AA standards. Here are the guidelines. - [Channel-Specific Guidelines](https://guide.techfleet.org/resources/brand-guide/editorial-style-guide/channel-specific-guidelines.md): Different platforms require different approaches, but our core identity remains the same. Use these guidelines to adapt our voice and visuals to specific channels. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guide.techfleet.org/resources/brand-guide/editorial-style-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.