# Make it scannable When busy developers read technical content, they often quickly **scan** through to find what they’re interested in. Here are some things you can do to help with that. * **Don’t be wordy**: Remove excess words and say things concisely. To do this, here are [tons of great tips](https://procomm.ieee.org/communication-resources-for-engineers/style/write-clearly-and-concisely/). * **Keep paragraphs short**: Keep paragraphs nice and short (1-3 sentences max) for easy reading/scannability. * **Break into short sections**: Break your article into sections with section headings, too. Don’t let sections get too long. Readers appreciate opportunities to take a rest! * **Descriptive section headings**: Headings should be short and descriptive, covering what’s inside the section (such as “Drawing Arcs”), rather than something “funny” (like “Launching the Arc-Capacitor”). This makes it easier to scan. * **Use lists**: Whenever you’re describing a list of terms and definitions, rather than using paragraphs, put the content in an ordered or bulleted list. Use the format \[bolded term]: definition - just like you see in this list! --- # 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://playbook.wednesday.is/communications/content/processes/articles/first-draft/make-it-scannable.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.