# Our Voice ### When we write and we speak, we want others to feel like they’ve been heard. Like what they say matters, and that we’ve taken them seriously. When others speak, we furrow our brow and listen. We want anyone to feel comfortable bringing their problems to us, and confident that we’d never pass judgment — because we wouldn’t. We choose our words deliberately and would never be caught shouting … unless it was to let someone know they dropped their wallet. **Keep it simple** Always use a short sentence over a long, stuffy one. Same with words. **Front-load the meaning** To be ultra clear, begin paragraphs with the most important thing. For example, rather than Slack someone a long story that ends with a request, we’ll start with the request — “Do you have 30 minutes to help?” — and work back. **Write like you talk** If you wouldn’t say it in casual conversation to a friend, find simpler wording. **Check your facts** With a complex subject like the Honeyland game, it's important to get facts correct when publishing them. Make sure that what you're putting out is accurate to the game. **Write in active voice** Say, “I checked the facts,” not, “The facts were checked by me.” **Always edit** Never submit something unless you’ve read through it yourself. **Eliminate jargon where possible** To the best of your ability, avoid using industry-specific words and jargon that may confuse or mislead newcomers. Honeyland is an inclusive game for people of all life experiences and backgrounds. **Reframe negative statements to be positive** For example, turn “no shipping fee” into “free shipping.” It’s shorter, more accurate, and more upbeat. **Check your homonyms and homophones** These are words that are pronounced the same but spelled differently. E.g. “they’re” and “their.” **When in doubt, delete “that”** “That” tends to get overused. If you can delete it and a sentence reads the same, please do. \ **Double-check all pronouns** If it’s not clear what your “it” or “that” is referring to, bring the noun up again. \ **Be specific** Is it a river or is it the Nile? Is it a truck or is it an eighteen-wheeler? Specificity paints the picture. \ **Hyphenate modifiers** --- # Agent Instructions: 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: ``` GET https://brand.honey.land/written-style-guidelines/copywriting-style-guide-for-honeyland/our-voice.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.