Source: https://developers.google.com/style/philosophy\n\n# Philosophy of this style guide
Stay organized with collections
Save and categorize content based on your preferences.\n\n- Home\n- Products\n- Style\n\n\n## Page Summary\n\n- This style guide documents the preferred writing style for this organization's content, focusing on internal consistency rather than setting industry standards.\n- It does not aim to be a comprehensive writing guide or replace existing style guides, primarily focusing on stylistic choices rather than basic writing principles.\n- While it prioritizes conciseness over detailed explanations, the guide occasionally provides rationale for specific choices, particularly concerning accessibility and localization.\n- Users are expected to act ethically and legally regarding documentation, regardless of whether they have read the guidelines.\n- This guide is subject to change and doesn't limit the organization's ability to modify its documentation.\n\nThis style guide documents the preferred writing style for this organization's content, focusing on internal consistency rather than setting industry standards.\n\nIt does not aim to be a comprehensive writing guide or replace existing style guides, primarily focusing on stylistic choices rather than basic writing principles.\n\nWhile it prioritizes conciseness over detailed explanations, the guide occasionally provides rationale for specific choices, particularly concerning accessibility and localization.\n\nUsers are expected to act ethically and legally regarding documentation, regardless of whether they have read the guidelines.\n\nThis guide is subject to change and doesn't limit the organization's ability to modify its documentation.\n\nThis document discusses some of the principles and philosophy behind this
style guide.\n\n\n## Intended purpose\n\nThis style guide codifies and records our style decisions and describes our
house style. The guide doesn't claim to be objectively correct.\n\nThis guide is not intended to do the following:\n\n- Provide an industry documentation standard.\n- Compete with other well-known style guides.\n- Replace another style guide that you already follow.\n- Provide a complete set of basic writing guidelines.\n- Provide legal advice. For legal advice, consult a lawyer.\n\nNote: Two disclaimers:\n\n- The guidance in this style guide doesn't limit the changes that Google can
make to its documentation.\n- If you don't read a given guideline, then you are still responsible for
behaving ethically and lawfully with regard to documentation.\n\n\n## Explanation of reasons for guidelines\n\nWe generally don't explain the reasoning behind most of our guidelines. We
have a couple of reasons for that:\n\n- Many of our decisions are driven by accessibility, localization,
globalization, and ease of understanding. Giving those reasons as explanations
everywhere they apply would be repetitive.\n- Often, a given guideline is one good option among several; in those cases,
we sometimes just chose one option for consistency.\n- Too much explanation can clutter up a page. Readers most often want a
brief answer to a specific question, rather than a detailed explanation.\n\nThat said, we recognize that it's sometimes useful to know why we made a
given choice, so we've started to include occasional explanations in the What's new page.\n