Unify the documentation layout and conventions

[glopesdev]

The documentation had drifted on four axes at once: how a page is laid out on disk, how its path is spelled, how its title relates to its navigation label, and which word names which idea. This converges each on a single rule. A page is a flat file whose name is its URL segment, a path is a noun naming its subject, a title is sentence case and mirrors its label, and a term carries one sense.

Structure

Example pages move from a directory each holding an index.md to flat files under docs/examples, with their scripts as flat siblings. Under use_directory_urls a flat device-info.md and a device-info/index.md produce the same /examples/device-info/, so the layout simplifies at no cost to the published paths. Removing the examples index page makes Examples a section label rather than a page, matching API.

Folders and files are renamed for their subject rather than for an operation, so get_info becomes device-info and create_device_module becomes registers-from-schema. URL segments use hyphens and Python filenames keep underscores, each separator used for what it means.

The trade-off between a generated package and a runtime module moves out of the schema example into docs/articles/device-modules.md, which now names and defines the device module term used throughout the rest of the documentation.

Navigation

The nav runs Introduction, Examples, Guides, API. Introduction replaces Home, matching the toolkit site. The articles/ path is kept for consistency with every other DocFX site in the organization, while the section label reads Guides.

Prose

Page titles and navigation labels are sentence case and mirror each other so they cannot drift. No heading opens with an -ing form, which both the Google and Microsoft style guides advise against, with Contributing the one entrenched exception.

reach was carrying four senses across the docs, the READMEs and the tests: accessing a register, a register passed as an argument, targeting a session folder, and arriving at a code branch. Each now takes the verb that fits it. Over-long sentences are split, anthropomorphisms and stranded verbs are rewritten, and stray parentheses and semicolons give way to plain sentences.

Tests

Test names drop articles, test docstrings become comments, and two functions follow the vocabulary above.