style-lookup

To resolve technical documentation style conflicts, apply Google developer documentation style first and fall back to Chicago Manual of Style only when Google guidance is silent. You receive a structured ruling with a recommendation, rationale, suggested edit, and consistency note.

The best way to get a defensible editorial style ruling is to provide a specific style question or sample text. The system evaluates it against Google developer documentation style and Chicago Manual of Style, returning a source-backed recommendation and suggested edit.

You can use this to enforce consistency for inclusive language, terminology, capitalization, punctuation, and formatting across technical documents. It provides structured guidance to help editors apply rulings consistently throughout their content.

Google developer documentation style does not override Chicago Manual of Style for every decision. Google style is applied first as the primary authority, but Chicago Manual of Style is used as a fallback specifically when Google guidance is silent on the issue.

To arbitrate punctuation and capitalization choices in developer documentation, submit the text or question. The system checks Google developer documentation style first, then Chicago Manual of Style, outputting a structured recommendation and consistency note.

You should not rely on automated editorial style rulings when your organization mandates a custom style guide or a primary style authority other than Google developer documentation style or Chicago Manual of Style, as this system specifically prioritizes those two sources.