Punctuation and emphasis

Punctuation should clarify the relationships between words. Preserve literal punctuation in labels, quotations, identifiers, and code. Apply the prose rules only to the surrounding writing.

Commas and colons

Use a serial comma in a list of three or more items: “files, folders, and presets.” Use commas to mark introductory phrases or separate clauses when they make the structure clearer. Do not insert a comma between a subject and its verb.

A colon introduces an explanation, consequence, or list. What follows should complete the promise before it: “Choose a destination: a folder or a connected device.” Keep the first word after a colon lowercase unless it begins a quotation, is a proper name, or has another independent reason for a capital.

A semicolon can join closely related independent clauses or separate complicated list items. Use one when it improves the sentence; split the sentence when the relationship is easier to understand that way. The number of commas is a review signal, not a limit on sentence structure.

Dashes, hyphens, and parentheses

Prefer a colon when it states the relationship directly. If a dash is needed in running prose, put a space on each side. Do not use dashes to decorate a noun with vague praise. A dash that changes direction or carries a useful aside can remain when it suits the register.

Use hyphens to clarify compound modifiers, such as read-only file, and preserve established technical spellings. An adverb ending in -ly usually needs no hyphen before its adjective. Avoid suspended compounds when spelling out both terms makes them easier to read: “left-aligned or right-aligned text.”

Parentheses hold a useful qualification or aside. Keep them when the detail belongs with the statement but should not interrupt its main line. If the qualification determines whether an instruction is safe or applicable, state it directly instead of treating it as an aside.

Use mathematical symbols for mathematical meanings; see technical notation. Never replace an operator or a command-line hyphen with typographic punctuation.

Quotations and literal input

Use typographic quotation marks in ordinary prose, and straight marks where code or exact input requires them. Preserve the wording and meaningful punctuation of a direct quotation. Put sentence punctuation outside a quoted label or code span when it is not part of that label or input.

Use an ellipsis character for an intentional omission or pause in prose. Do not use it to conceal missing information. Literal code and syntax summaries keep their required characters, including three periods when those are part of the notation. Omitted code must be clearly identified as omitted, not presented as runnable.

Keep punctuation in the surrounding text's style unless it belongs to the formatted element. For example, the period after Example.otf is not part of the filename.

Headings, lists, and emphasis

Headings and short labels normally have no ending period. A real question keeps its question mark. Complete sentences in lists take periods; short noun phrases usually do not. Keep comparable items consistent without turning every fragment into a sentence.

Use emphasis to identify something the reader must notice, not to compensate for an unclear sentence. The mechanics page distinguishes interface labels, code, and prose emphasis. Marketing examples may emphasize an action as part of their register; that does not make bold the default for every important noun.

Exclamation marks depend on register and context. They are unusual in reference prose and inappropriate in a limitation or an error message. A verified marketing example or a warm announcement can retain one when it earns its place. Do not add or remove punctuation merely to meet a numerical quota.