# Out of date: How to write for SF.gov [We’ve moved our guidance for SF.gov](https://sfgovdt.jira.com/wiki/spaces/SFGOV/pages/1810038785/Writing%2Bfor%2BSF.gov%2Bstyle%2Bguide). This page is out of date. Everything on SF.gov must be written at or below a 5th-grade reading level. Writing simply avoids discrimination and misunderstanding. It helps all San Franciscans use our site. You can paste your text into the [Hemingway Editor](http://www.hemingwayapp.com/) to check readability. To give [feedback on this guide, leave comments on the GoogleDoc](https://docs.google.com/document/d/108sQRXffEFEbzSKvht3EoiR4yO9W2vb-Z2eF6Cd6pVo/edit?usp=sharing). We'll make changes to this guide based on discussions on the doc. For visual design guidance, refer to [our branding style guide](https://sfdigitalservices.gitbook.io/branding-style-guide/). Email if you have questions. --- # 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://sfdigitalservices.gitbook.io/style-guide/master.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.