@redocly/recheck 0.15.0 → 2.58.1

package/presets/microsoft/PROVENANCE.md

@@ -33,9 +33,9 @@ Confirmed two independent ways:
 - The raw `LICENSE` file itself is the full CC BY 4.0 legal code.
 
 The site's Terms of Use (`https://learn.microsoft.com/en-us/legal/termsofuse`)
-explicitly defers to this: *"Certain documentation may be subject to
+explicitly defers to this: _"Certain documentation may be subject to
 explicit license terms separate from the terms contained here. To the
-extent the terms conflict, the explicit license terms control."*
+extent the terms conflict, the explicit license terms control."_
 
 **Bottom line, and the reason this matters for the preset:** CC-BY-4.0
 attribution is factually correct to ship, but every `link:` in `microsoft.ts`
@@ -91,35 +91,35 @@ rather than a complete test) is `warn`.
 
 ### Structural (heading, list, table, alt-text, link mechanics) — `error` unless noted
 
-| Rule id | Source URL | Quote | Verdict |
-|---|---|---|---|
-| `microsoft/heading-sentence-case` | [capitalization](https://learn.microsoft.com/en-us/style-guide/capitalization) | "Microsoft style uses sentence-style capitalization." | CONFIRMED |
-| `microsoft/capitalize-after-heading-colon` (`warn`) | [colons](https://learn.microsoft.com/en-us/style-guide/punctuation/colons) | "Always capitalize the word after the colon." | CONFIRMED, scoped to headings only — the mid-sentence-colon form is merely "Acceptable" per the guide's own table, not shipped |
-| `microsoft/no-trailing-punctuation` | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings) | "Don't end headings with a period." | CONFIRMED — default punctuation set (`.,;:` with `?` stripped) already matches Microsoft's own `?`-allowed/`!`-rarely exceptions with no override |
-| `microsoft/no-ampersand-in-headings` (`warn`) | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings) | "Don't use ampersands (&) or plus signs (+) in headings unless..." | CONFIRMED, `exceptions.lines` for `C++`/`A+`/`.NET`; `&` pattern excludes `&`/` `/`<`/`>`/`"`/numeric entities |
-| `microsoft/vs-in-headings` (`warn`) | [versus-vs](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/v/versus-vs) | "In headings, use the abbreviation vs., all lowercase." | CONFIRMED, scoped to `heading` |
-| `microsoft/versus-in-text` (`warn`) | same | "In text, spell out as versus." | CONFIRMED, scoped to `[paragraph, list-item, table.cell]` — two scoped rules with opposite directions so they don't fight each other |
-| `microsoft/no-multiple-blanks` | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings) | "Don't use extra line breaks to increase heading spacing." | CONFIRMED |
-| `microsoft/no-emphasis-as-heading` | [writing-all-abilities](https://learn.microsoft.com/en-us/style-guide/accessibility/writing-all-abilities) | "Use heading levels instead of text formatting to communicate... hierarchy." | CONFIRMED |
-| `microsoft/no-apostrophe-plural-decade` (`warn`) | [apostrophes](https://learn.microsoft.com/en-us/style-guide/punctuation/apostrophes) | "Don't use an apostrophe... to form the plural of a singular noun." | CONFIRMED, scoped to the unambiguous decade case (`1990's`); a bare `[A-Z]{2,}'s` (e.g. `API's`) is excluded — frequently a legitimate possessive |
-| `microsoft/article-before-acronym` (`warn`) | [acronyms](https://learn.microsoft.com/en-us/style-guide/acronyms) | "a DLL / an ISP / a URL / a SQL database" | CONFIRMED |
-| `microsoft/list-item-capital` | [lists](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists) | "Begin each item in a list with a capital letter." | CONFIRMED, custom-regex `capitalization` (not `$sentence`, which would overshoot) |
-| `microsoft/no-trailing-conjunction-list` (`warn`) | [lists](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists) | "Don't use semicolons, commas, or conjunctions... at the end of list items." | CONFIRMED |
-| `microsoft/no-ellipsis-column-header` (`warn`) | [tables](https://learn.microsoft.com/en-us/style-guide/scannable-content/tables) | "Don't use ellipses at the end of column headers." | CONFIRMED |
-| `microsoft/no-blank-table-cell` (`warn`) | [tables](https://learn.microsoft.com/en-us/style-guide/scannable-content/tables) | "Don't leave a cell blank or use an em dash. Instead, use Not applicable or None." | CONFIRMED, **em dash only** — the guide's other half ("don't leave a cell blank") is NOT enforced: a truly blank `table.cell` segment's content is the empty string, and every `pattern` token can only ever produce a zero-width match against `''`, which pattern.ts deliberately skips (no real text to report) — an architectural limit of the `pattern` assertion, not a missed narrowing pass. See the rule's doc comment in `config/presets/microsoft.ts` for the full reasoning and what a real fix would require (a token rule or an extractor-level change). The draft's original broader pattern also matched an en dash/hyphen, which the guide never names for this rule either. |
-| `microsoft/single-space-after-punctuation` (`warn`) | [periods](https://learn.microsoft.com/en-us/style-guide/punctuation/periods) + [top-10-tips](https://learn.microsoft.com/en-us/style-guide/top-10-tips-style-voice) | "Put one space, not two, after a period" — top-10-tips broadens to "periods, question marks, and colons" | CONFIRMED, widened scope per verifier F's note |
-| `microsoft/no-space-around-em-dash` (`warn`) | [dashes-hyphens](https://learn.microsoft.com/en-us/style-guide/punctuation/dashes-hyphens/) | "Don't use spaces around em dashes." | CONFIRMED, **narrowed to em dash only** — the en-dash rule has an explicit worked exception for UI timestamps/date ranges ("2:15 PM – 4:45 PM") a blind regex can't distinguish from the ordinary case; en-dash spacing is not enforced at all |
-| `microsoft/no-from-before-en-dash-range` (`warn`) | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers) | "Don't use from before a range indicated by an en dash." | CONFIRMED |
-| `microsoft/straight-quotes` (`warn`) | [quotation-marks](https://learn.microsoft.com/en-us/style-guide/punctuation/quotation-marks) | "Use straight quotation marks. Segoe Sans... does not have a curly quotation mark option." | CONFIRMED |
-| `microsoft/spell-out-ordinals` (`warn`) | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers) | "Always spell out ordinal numbers." | CONFIRMED |
-| `microsoft/ordinal-no-ly` (`warn`) | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers) | "Don't add -ly to an ordinal number, as in firstly or secondly." | CONFIRMED |
-| `microsoft/noon-midnight` (`warn`) | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers) | "Don't use numerals for 12:00. Use noon or midnight instead." | CONFIRMED |
-| `microsoft/no-alt-text` | [alternative-text](https://learn.microsoft.com/en-us/style-guide/accessibility/alternative-text) | "Add alt text to all images that convey important meaning." | CONFIRMED |
-| `microsoft/alt-text-length` (`warn`) | same | "Limit the length to 150 characters." | CONFIRMED — structural number |
-| `microsoft/alt-text-format` (`warn`) | same | "Begin alt text with a capital letter. End it with a period." | CONFIRMED, incomplete — the guide's own carve-out ("even if it's just a fragment, if doing so is practical for the image type") is not modeled; see "Known limitations" |
-| `microsoft/alt-text-generic-opener` (`warn`) | same | "Don't start alt text with 'Image.'" / "Don't start... with 'Button' or 'Link.'" | CONFIRMED — `Screenshot`/`Diagram`/`Photograph`/`Chart`/`Drawing` are prescribed openers, deliberately absent from the pattern |
-| `microsoft/alt-text-no-filename` (`warn`) | same | "Don't use the file name of an image as alt text." | CONFIRMED |
-| `microsoft/descriptive-link-text` | [urls-web-addresses](https://learn.microsoft.com/en-us/style-guide/urls-web-addresses) | "rather than a generic phrase like click here" | CONFIRMED |
+| Rule id                                             | Source URL                                                                                                                                                          | Quote                                                                                                    | Verdict                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `microsoft/heading-sentence-case`                   | [capitalization](https://learn.microsoft.com/en-us/style-guide/capitalization)                                                                                      | "Microsoft style uses sentence-style capitalization."                                                    | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/capitalize-after-heading-colon` (`warn`) | [colons](https://learn.microsoft.com/en-us/style-guide/punctuation/colons)                                                                                          | "Always capitalize the word after the colon."                                                            | CONFIRMED, scoped to headings only — the mid-sentence-colon form is merely "Acceptable" per the guide's own table, not shipped                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `microsoft/no-trailing-punctuation`                 | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings)                                                                                | "Don't end headings with a period."                                                                      | CONFIRMED — default punctuation set (`.,;:` with `?` stripped) already matches Microsoft's own `?`-allowed/`!`-rarely exceptions with no override                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `microsoft/no-ampersand-in-headings` (`warn`)       | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings)                                                                                | "Don't use ampersands (&) or plus signs (+) in headings unless..."                                       | CONFIRMED, `exceptions.lines` for `C++`/`A+`/`.NET`; `&` pattern excludes `&`/` `/`<`/`>`/`"`/numeric entities                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `microsoft/vs-in-headings` (`warn`)                 | [versus-vs](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/v/versus-vs)                                                               | "In headings, use the abbreviation vs., all lowercase."                                                  | CONFIRMED, scoped to `heading`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `microsoft/versus-in-text` (`warn`)                 | same                                                                                                                                                                | "In text, spell out as versus."                                                                          | CONFIRMED, scoped to `[paragraph, list-item, table.cell]` — two scoped rules with opposite directions so they don't fight each other                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `microsoft/no-multiple-blanks`                      | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings)                                                                                | "Don't use extra line breaks to increase heading spacing."                                               | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/no-emphasis-as-heading`                  | [writing-all-abilities](https://learn.microsoft.com/en-us/style-guide/accessibility/writing-all-abilities)                                                          | "Use heading levels instead of text formatting to communicate... hierarchy."                             | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/no-apostrophe-plural-decade` (`warn`)    | [apostrophes](https://learn.microsoft.com/en-us/style-guide/punctuation/apostrophes)                                                                                | "Don't use an apostrophe... to form the plural of a singular noun."                                      | CONFIRMED, scoped to the unambiguous decade case (`1990's`); a bare `[A-Z]{2,}'s` (e.g. `API's`) is excluded — frequently a legitimate possessive                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `microsoft/article-before-acronym` (`warn`)         | [acronyms](https://learn.microsoft.com/en-us/style-guide/acronyms)                                                                                                  | "a DLL / an ISP / a URL / a SQL database"                                                                | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/list-item-capital`                       | [lists](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists)                                                                                      | "Begin each item in a list with a capital letter."                                                       | CONFIRMED, custom-regex `capitalization` (not `$sentence`, which would overshoot)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `microsoft/no-trailing-conjunction-list` (`warn`)   | [lists](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists)                                                                                      | "Don't use semicolons, commas, or conjunctions... at the end of list items."                             | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/no-ellipsis-column-header` (`warn`)      | [tables](https://learn.microsoft.com/en-us/style-guide/scannable-content/tables)                                                                                    | "Don't use ellipses at the end of column headers."                                                       | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/no-blank-table-cell` (`warn`)            | [tables](https://learn.microsoft.com/en-us/style-guide/scannable-content/tables)                                                                                    | "Don't leave a cell blank or use an em dash. Instead, use Not applicable or None."                       | CONFIRMED, **em dash only** — the guide's other half ("don't leave a cell blank") is NOT enforced: a truly blank `table.cell` segment's content is the empty string, and every `pattern` token can only ever produce a zero-width match against `''`, which pattern.ts deliberately skips (no real text to report) — an architectural limit of the `pattern` assertion, not a missed narrowing pass. See the rule's doc comment in `config/presets/microsoft.ts` for the full reasoning and what a real fix would require (a token rule or an extractor-level change). The draft's original broader pattern also matched an en dash/hyphen, which the guide never names for this rule either. |
+| `microsoft/single-space-after-punctuation` (`warn`) | [periods](https://learn.microsoft.com/en-us/style-guide/punctuation/periods) + [top-10-tips](https://learn.microsoft.com/en-us/style-guide/top-10-tips-style-voice) | "Put one space, not two, after a period" — top-10-tips broadens to "periods, question marks, and colons" | CONFIRMED, widened scope per verifier F's note                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `microsoft/no-space-around-em-dash` (`warn`)        | [dashes-hyphens](https://learn.microsoft.com/en-us/style-guide/punctuation/dashes-hyphens/)                                                                         | "Don't use spaces around em dashes."                                                                     | CONFIRMED, **narrowed to em dash only** — the en-dash rule has an explicit worked exception for UI timestamps/date ranges ("2:15 PM – 4:45 PM") a blind regex can't distinguish from the ordinary case; en-dash spacing is not enforced at all                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `microsoft/no-from-before-en-dash-range` (`warn`)   | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers)                                                                                                    | "Don't use from before a range indicated by an en dash."                                                 | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/straight-quotes` (`warn`)                | [quotation-marks](https://learn.microsoft.com/en-us/style-guide/punctuation/quotation-marks)                                                                        | "Use straight quotation marks. Segoe Sans... does not have a curly quotation mark option."               | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/spell-out-ordinals` (`warn`)             | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers)                                                                                                    | "Always spell out ordinal numbers."                                                                      | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/ordinal-no-ly` (`warn`)                  | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers)                                                                                                    | "Don't add -ly to an ordinal number, as in firstly or secondly."                                         | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/noon-midnight` (`warn`)                  | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers)                                                                                                    | "Don't use numerals for 12:00. Use noon or midnight instead."                                            | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/no-alt-text`                             | [alternative-text](https://learn.microsoft.com/en-us/style-guide/accessibility/alternative-text)                                                                    | "Add alt text to all images that convey important meaning."                                              | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/alt-text-length` (`warn`)                | same                                                                                                                                                                | "Limit the length to 150 characters."                                                                    | CONFIRMED — structural number                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `microsoft/alt-text-format` (`warn`)                | same                                                                                                                                                                | "Begin alt text with a capital letter. End it with a period."                                            | CONFIRMED, incomplete — the guide's own carve-out ("even if it's just a fragment, if doing so is practical for the image type") is not modeled; see "Known limitations"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `microsoft/alt-text-generic-opener` (`warn`)        | same                                                                                                                                                                | "Don't start alt text with 'Image.'" / "Don't start... with 'Button' or 'Link.'"                         | CONFIRMED — `Screenshot`/`Diagram`/`Photograph`/`Chart`/`Drawing` are prescribed openers, deliberately absent from the pattern                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `microsoft/alt-text-no-filename` (`warn`)           | same                                                                                                                                                                | "Don't use the file name of an image as alt text."                                                       | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `microsoft/descriptive-link-text`                   | [urls-web-addresses](https://learn.microsoft.com/en-us/style-guide/urls-web-addresses)                                                                              | "rather than a generic phrase like click here"                                                           | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 
 ### Structural numbers (`warn`) — see the dedicated section below
 
@@ -127,36 +127,36 @@ rather than a complete test) is `warn`.
 
 ### Voice, contractions — `warn`
 
-| Rule id | Source URL | Quote | Verdict |
-|---|---|---|---|
-| `microsoft/use-contractions` | [use-contractions](https://learn.microsoft.com/en-us/style-guide/word-choice/use-contractions) + [top-10-tips](https://learn.microsoft.com/en-us/style-guide/top-10-tips-style-voice) | "Use contractions like it's, you'll, you're, we're, and let's." | CONFIRMED — the signature Microsoft rule and the sharpest voice difference from other guides. Every pair is a clean word-for-word contraction; `applyMatchCase` verified to handle sentence-initial capitalized matches correctly ("Do not" → "Don't"). |
-| `microsoft/no-awkward-contractions` | [use-contractions](https://learn.microsoft.com/en-us/style-guide/word-choice/use-contractions) | "Avoid ambiguous or awkward contractions, such as there'd, it'll, and they'd." | CONFIRMED |
-| `microsoft/contraction-consistency` | same | "don't use can't and cannot in the same UI." | CONFIRMED — textbook fit for first-seen-wins `consistency` |
-| `microsoft/no-weak-phrasing` | [top-10-tips](https://learn.microsoft.com/en-us/style-guide/top-10-tips-style-voice) | "Avoid weak phrasing like there is, there are, and there were." | CONFIRMED |
-| `microsoft/avoid-please` | [a-z/please](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/please) | "Avoid please except in situations where the customer is asked to do something inconvenient..." | CONFIRMED |
+| Rule id                             | Source URL                                                                                                                                                                            | Quote                                                                                           | Verdict                                                                                                                                                                                                                                                 |
+| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `microsoft/use-contractions`        | [use-contractions](https://learn.microsoft.com/en-us/style-guide/word-choice/use-contractions) + [top-10-tips](https://learn.microsoft.com/en-us/style-guide/top-10-tips-style-voice) | "Use contractions like it's, you'll, you're, we're, and let's."                                 | CONFIRMED — the signature Microsoft rule and the sharpest voice difference from other guides. Every pair is a clean word-for-word contraction; `applyMatchCase` verified to handle sentence-initial capitalized matches correctly ("Do not" → "Don't"). |
+| `microsoft/no-awkward-contractions` | [use-contractions](https://learn.microsoft.com/en-us/style-guide/word-choice/use-contractions)                                                                                        | "Avoid ambiguous or awkward contractions, such as there'd, it'll, and they'd."                  | CONFIRMED                                                                                                                                                                                                                                               |
+| `microsoft/contraction-consistency` | same                                                                                                                                                                                  | "don't use can't and cannot in the same UI."                                                    | CONFIRMED — textbook fit for first-seen-wins `consistency`                                                                                                                                                                                              |
+| `microsoft/no-weak-phrasing`        | [top-10-tips](https://learn.microsoft.com/en-us/style-guide/top-10-tips-style-voice)                                                                                                  | "Avoid weak phrasing like there is, there are, and there were."                                 | CONFIRMED                                                                                                                                                                                                                                               |
+| `microsoft/avoid-please`            | [a-z/please](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/please)                                                                                   | "Avoid please except in situations where the customer is asked to do something inconvenient..." | CONFIRMED                                                                                                                                                                                                                                               |
 
 ### US spelling, Latin abbreviations, simple words — `error` (mechanical, per the research's "ship at error" framing)
 
-| Rule id | Source URL | Quote | Verdict |
-|---|---|---|---|
-| `microsoft/us-spelling` | [use-us-spelling](https://learn.microsoft.com/en-us/style-guide/word-choice/use-us-spelling-avoid-non-english-words) | "use the US spelling. For example, use license, not licence." | CONFIRMED — a subset not already covered by `recheck/prose`'s `consistency` rule (behavior/color/license/organize) |
-| `microsoft/no-latin-abbreviations` | same | "Avoid Latin abbreviations for common English phrases." | CONFIRMED for e.g./i.e./viz./ergo/de facto/ad hoc/vis-a-vis. `via` deliberately dropped (see self-contradictions section) |
-| `microsoft/simple-words` | [use-simple-words](https://learn.microsoft.com/en-us/style-guide/word-choice/use-simple-words-concise-sentences) | "Choose simple verbs without modifiers." / "Don't use two or three words when one will do." | CONFIRMED |
-| `microsoft/leverage` | [avoid-jargon](https://learn.microsoft.com/en-us/style-guide/word-choice/avoid-jargon) | "using leverage to mean take advantage of" | CONFIRMED — split into its own rule so its `link:` points at the page that actually states it |
-| `microsoft/glyph` | same | "such as symbol instead of glyph" | CONFIRMED |
-| `microsoft/bucketize` | [dont-use-common-words](https://learn.microsoft.com/en-us/style-guide/word-choice/dont-use-common-words-in-new-ways) | "Don't create a new word from an existing word." | CONFIRMED |
-| `microsoft/impact-verb` (`warn`) | same | "Don't use verbs as nouns or nouns as verbs" | CONFIRMED, narrowly anchored to `impact` immediately followed by a specific object noun (performance/productivity/quality/reliability/availability/latency/throughput) — bare "impact" is also a common, correct noun ("the impact of this change") per verifier E's own caution |
-| `microsoft/the-ask` (`warn`) | [dont-use-common-words](https://learn.microsoft.com/en-us/style-guide/word-choice/dont-use-common-words-in-new-ways) | "respond to the request" vs. "respond to the ask" | CONFIRMED |
+| Rule id                            | Source URL                                                                                                           | Quote                                                                                       | Verdict                                                                                                                                                                                                                                                                          |
+| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `microsoft/us-spelling`            | [use-us-spelling](https://learn.microsoft.com/en-us/style-guide/word-choice/use-us-spelling-avoid-non-english-words) | "use the US spelling. For example, use license, not licence."                               | CONFIRMED — a subset not already covered by `recheck/prose`'s `consistency` rule (behavior/color/license/organize)                                                                                                                                                               |
+| `microsoft/no-latin-abbreviations` | same                                                                                                                 | "Avoid Latin abbreviations for common English phrases."                                     | CONFIRMED for e.g./i.e./viz./ergo/de facto/ad hoc/vis-a-vis. `via` deliberately dropped (see self-contradictions section)                                                                                                                                                        |
+| `microsoft/simple-words`           | [use-simple-words](https://learn.microsoft.com/en-us/style-guide/word-choice/use-simple-words-concise-sentences)     | "Choose simple verbs without modifiers." / "Don't use two or three words when one will do." | CONFIRMED                                                                                                                                                                                                                                                                        |
+| `microsoft/leverage`               | [avoid-jargon](https://learn.microsoft.com/en-us/style-guide/word-choice/avoid-jargon)                               | "using leverage to mean take advantage of"                                                  | CONFIRMED — split into its own rule so its `link:` points at the page that actually states it                                                                                                                                                                                    |
+| `microsoft/glyph`                  | same                                                                                                                 | "such as symbol instead of glyph"                                                           | CONFIRMED                                                                                                                                                                                                                                                                        |
+| `microsoft/bucketize`              | [dont-use-common-words](https://learn.microsoft.com/en-us/style-guide/word-choice/dont-use-common-words-in-new-ways) | "Don't create a new word from an existing word."                                            | CONFIRMED                                                                                                                                                                                                                                                                        |
+| `microsoft/impact-verb` (`warn`)   | same                                                                                                                 | "Don't use verbs as nouns or nouns as verbs"                                                | CONFIRMED, narrowly anchored to `impact` immediately followed by a specific object noun (performance/productivity/quality/reliability/availability/latency/throughput) — bare "impact" is also a common, correct noun ("the impact of this change") per verifier E's own caution |
+| `microsoft/the-ask` (`warn`)       | [dont-use-common-words](https://learn.microsoft.com/en-us/style-guide/word-choice/dont-use-common-words-in-new-ways) | "respond to the request" vs. "respond to the ask"                                           | CONFIRMED                                                                                                                                                                                                                                                                        |
 
 ### Bias-free, militaristic, derogatory language — `error` (sensitive category)
 
-| Rule id | Source URL | Quote | Verdict |
-|---|---|---|---|
-| `microsoft/bias-free-terms` | [bias-free](https://learn.microsoft.com/en-us/style-guide/bias-free-communication) | chairman→chair; mankind→humanity; manmade→synthetic; manpower→workforce; salesman→sales representative; DMZ→perimeter network | CONFIRMED. `master/slave` deliberately NOT included in this rule's pairs — it ships separately as `microsoft/master-slave`, see next row and the self-contradictions section |
-| `microsoft/master-slave` | [bias-free](https://learn.microsoft.com/en-us/style-guide/bias-free-communication) + [a-z/master-slave](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/master-slave) | "primary/subordinate ← master/slave" (bias-free); "Don't use master/slave. Use primary/replica or alternatives such as primary/secondary, principal/agent, controller/worker" (a-z) | CONFIRMED both pages ban the term; the two pages disagree only on the replacement — added in the task-10 fix wave as `pattern` (detection-only), naming both candidates in its message rather than shipping neither direction. See "Self-contradictions" |
-| `microsoft/cyberattack-spelling` | [militaristic-language](https://learn.microsoft.com/en-us/style-guide/militaristic-language) | "add cyber- in front of threat so it reads cyberthreat, all one word no space no hyphen" | CONFIRMED — spelling normalization only; the guide's separate "needs a qualifier in front of it" test is not mechanically decidable and is not enforced |
-| `microsoft/no-derogatory-slang` | [bias-free](https://learn.microsoft.com/en-us/style-guide/bias-free-communication) | "Don't use profane or derogatory terms, such as pimp or bitch." / "spirit animal" | CONFIRMED, detection-only (no safe fixed replacement for any of these) |
-| `microsoft/racial-ethnic-capitalization` | same | "Use title-style capitalization for Asian, Black and African American, Hispanic and Latinx..." | CONFIRMED, case-sensitive match (only genuinely-lowercase forms flagged); `white`/`multiracial` (which the guide says to LOWERCASE) deliberately excluded — a bare capitalized "White" collides constantly with unrelated proper nouns |
+| Rule id                                  | Source URL                                                                                                                                                                                           | Quote                                                                                                                                                                               | Verdict                                                                                                                                                                                                                                                  |
+| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `microsoft/bias-free-terms`              | [bias-free](https://learn.microsoft.com/en-us/style-guide/bias-free-communication)                                                                                                                   | chairman→chair; mankind→humanity; manmade→synthetic; manpower→workforce; salesman→sales representative; DMZ→perimeter network                                                       | CONFIRMED. `master/slave` deliberately NOT included in this rule's pairs — it ships separately as `microsoft/master-slave`, see next row and the self-contradictions section                                                                             |
+| `microsoft/master-slave`                 | [bias-free](https://learn.microsoft.com/en-us/style-guide/bias-free-communication) + [a-z/master-slave](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/master-slave) | "primary/subordinate ← master/slave" (bias-free); "Don't use master/slave. Use primary/replica or alternatives such as primary/secondary, principal/agent, controller/worker" (a-z) | CONFIRMED both pages ban the term; the two pages disagree only on the replacement — added in the task-10 fix wave as `pattern` (detection-only), naming both candidates in its message rather than shipping neither direction. See "Self-contradictions" |
+| `microsoft/cyberattack-spelling`         | [militaristic-language](https://learn.microsoft.com/en-us/style-guide/militaristic-language)                                                                                                         | "add cyber- in front of threat so it reads cyberthreat, all one word no space no hyphen"                                                                                            | CONFIRMED — spelling normalization only; the guide's separate "needs a qualifier in front of it" test is not mechanically decidable and is not enforced                                                                                                  |
+| `microsoft/no-derogatory-slang`          | [bias-free](https://learn.microsoft.com/en-us/style-guide/bias-free-communication)                                                                                                                   | "Don't use profane or derogatory terms, such as pimp or bitch." / "spirit animal"                                                                                                   | CONFIRMED, detection-only (no safe fixed replacement for any of these)                                                                                                                                                                                   |
+| `microsoft/racial-ethnic-capitalization` | same                                                                                                                                                                                                 | "Use title-style capitalization for Asian, Black and African American, Hispanic and Latinx..."                                                                                      | CONFIRMED, case-sensitive match (only genuinely-lowercase forms flagged); `white`/`multiracial` (which the guide says to LOWERCASE) deliberately excluded — a bare capitalized "White" collides constantly with unrelated proper nouns                   |
 
 **Note on the militaristic-language word bundle:** the broader "kill chain /
 blast radius / locked down / threat intel / defense-in-depth approach /
@@ -230,15 +230,15 @@ adjective-for-clause instead of verb-for-noun.
 
 ### UI verbs and checkbox/dialog terminology — `warn`
 
-| Rule id | Source URL | Quote | Verdict |
-|---|---|---|---|
-| `microsoft/no-click` | [describing-interactions-with-ui](https://learn.microsoft.com/en-us/style-guide/procedures-instructions/describing-interactions-with-ui) | "Don't use input-specific verbs, such as click or swipe." | CONFIRMED — **the single sharpest divergence from `recheck/google`**, which allows "click". Anchored with a negative lookbehind/lookahead to exclude the hyphen-joined compounds `double-click`/`right-click` (a real substring risk: `\bclick\b` DOES match inside "double-click" once a hyphen precedes it, since a hyphen is a non-word character) and the unrelated compounds `clickstream`/`clickthrough`. Verified via a dedicated fix-safety test. |
-| `microsoft/press-key-verb` | [a-z/hit](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/h/hit) | "Don't use press, depress, hit, or strike [to describe pressing a key]. Use select instead." | CONFIRMED, narrowly anchored to recognizable key-press phrasing (Enter/Tab/Esc/Delete/etc., or "the ... key") — bare "press"/"hit"/"strike" are far too polysemous (press releases, press charges, hit a milestone, strike a balance) to match unconditionally |
-| `microsoft/checkbox-verbs` | [describing-interactions-with-ui](https://learn.microsoft.com/en-us/style-guide/procedures-instructions/describing-interactions-with-ui) | "Clear \| Clearing the selection from a checkbox." | CONFIRMED for `uncheck`/`unmark`/`unselect` → `clear`. Bare `check`/`deselect` deliberately excluded: "check" is extremely polysemous, and "deselect"'s replacement differs by UI-element type ("clear" for checkboxes, "cancel the selection" elsewhere) in a way a blind swap can't resolve |
-| `microsoft/dialog-terminology` | [formatting-text-in-instructions](https://learn.microsoft.com/en-us/style-guide/procedures-instructions/formatting-text-in-instructions) | "Don't use pop-up window, dialog box, or dialogue box." | CONFIRMED |
-| `microsoft/mouse-over` | [mouse-and-mouse-interaction-terms](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/mouse-and-mouse-interaction-terms) | "Don't use mouse over or move the mouse pointer to." | CONFIRMED (conditionally OK for beginner-skill content per the same page — low risk for reference documentation) |
-| `microsoft/keyboard-shortcut-plus-spacing` | [formatting-text-in-instructions](https://learn.microsoft.com/en-us/style-guide/procedures-instructions/formatting-text-in-instructions) | "Don't put a space around the plus sign (+) in keyboard shortcuts." | CONFIRMED, detection-only — `swap` replacements are literal (Constraint 2), and the fix would need to reproduce whichever modifier key matched, which needs capture-group interpolation the engine does not support |
-| `microsoft/sign-in-sign-out` | [log-on-log-off](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/l/log-on-log-off) | "Don't use log in, login, log into, log on... unless it appears in the UI (and you're writing instructions)." | CONFIRMED, `fix: false` — "login"/"logon" are frequently used as NOUNS or adjectives ("the login page", "your login credentials"), where "sign in" (a verb phrase) does not slot in grammatically. The guide's exception is also a two-part test (UI match AND instructions context) neither this nor the research draft attempts to model — flagged here as a known limitation, not silently dropped |
+| Rule id                                    | Source URL                                                                                                                                                           | Quote                                                                                                         | Verdict                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `microsoft/no-click`                       | [describing-interactions-with-ui](https://learn.microsoft.com/en-us/style-guide/procedures-instructions/describing-interactions-with-ui)                             | "Don't use input-specific verbs, such as click or swipe."                                                     | CONFIRMED — **the single sharpest divergence from `recheck/google`**, which allows "click". Anchored with a negative lookbehind/lookahead to exclude the hyphen-joined compounds `double-click`/`right-click` (a real substring risk: `\bclick\b` DOES match inside "double-click" once a hyphen precedes it, since a hyphen is a non-word character) and the unrelated compounds `clickstream`/`clickthrough`. Verified via a dedicated fix-safety test. |
+| `microsoft/press-key-verb`                 | [a-z/hit](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/h/hit)                                                                        | "Don't use press, depress, hit, or strike [to describe pressing a key]. Use select instead."                  | CONFIRMED, narrowly anchored to recognizable key-press phrasing (Enter/Tab/Esc/Delete/etc., or "the ... key") — bare "press"/"hit"/"strike" are far too polysemous (press releases, press charges, hit a milestone, strike a balance) to match unconditionally                                                                                                                                                                                            |
+| `microsoft/checkbox-verbs`                 | [describing-interactions-with-ui](https://learn.microsoft.com/en-us/style-guide/procedures-instructions/describing-interactions-with-ui)                             | "Clear \| Clearing the selection from a checkbox."                                                            | CONFIRMED for `uncheck`/`unmark`/`unselect` → `clear`. Bare `check`/`deselect` deliberately excluded: "check" is extremely polysemous, and "deselect"'s replacement differs by UI-element type ("clear" for checkboxes, "cancel the selection" elsewhere) in a way a blind swap can't resolve                                                                                                                                                             |
+| `microsoft/dialog-terminology`             | [formatting-text-in-instructions](https://learn.microsoft.com/en-us/style-guide/procedures-instructions/formatting-text-in-instructions)                             | "Don't use pop-up window, dialog box, or dialogue box."                                                       | CONFIRMED                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `microsoft/mouse-over`                     | [mouse-and-mouse-interaction-terms](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/mouse-and-mouse-interaction-terms) | "Don't use mouse over or move the mouse pointer to."                                                          | CONFIRMED (conditionally OK for beginner-skill content per the same page — low risk for reference documentation)                                                                                                                                                                                                                                                                                                                                          |
+| `microsoft/keyboard-shortcut-plus-spacing` | [formatting-text-in-instructions](https://learn.microsoft.com/en-us/style-guide/procedures-instructions/formatting-text-in-instructions)                             | "Don't put a space around the plus sign (+) in keyboard shortcuts."                                           | CONFIRMED, detection-only — `swap` replacements are literal (Constraint 2), and the fix would need to reproduce whichever modifier key matched, which needs capture-group interpolation the engine does not support                                                                                                                                                                                                                                       |
+| `microsoft/sign-in-sign-out`               | [log-on-log-off](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/l/log-on-log-off)                                                      | "Don't use log in, login, log into, log on... unless it appears in the UI (and you're writing instructions)." | CONFIRMED, `fix: false` — "login"/"logon" are frequently used as NOUNS or adjectives ("the login page", "your login credentials"), where "sign in" (a verb phrase) does not slot in grammatically. The guide's exception is also a two-part test (UI match AND instructions context) neither this nor the research draft attempts to model — flagged here as a known limitation, not silently dropped                                                     |
 
 ## Excluded candidates
 
@@ -275,29 +275,29 @@ Fix wave B / Step 6.3: every row below now carries its own source URL(s) —
 the stated bar for this table is rule + URL + reason, and a reason without
 a citation isn't verifiable by a future reader.
 
-| Candidate | Why excluded | Source(s) |
-|---|---|---|
-| `deprecated` → `obsolete`; `user` → `customer`; `client` (a person) → `customer`; `utility` → `tool`; `cursor`; `machine` → `computer`; `start` (an app) → `open` | Each carries an explicit or de-facto developer/technical-audience carve-out that directly applies to Redocly's own documentation — see "Additional tier-boundary findings" above. | [d/deprecated](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/d/deprecated), [u/user-end-user](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/u/user-end-user), [c/client](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/client), [u/utility](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/u/utility), [mouse-mouse-interaction-terms](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/mouse-mouse-interaction-terms), [computer-device-terms](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/computer-device-terms), [o/open](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/o/open) |
-| `freeze`/`frozen` (as system-hang synonyms) | Sense-ambiguous: "freeze an account," "freeze a value," "deep freeze" are all common, unrelated, correct uses; the guide's own carve-out ("as a synonym for stop responding") names a specific sense a blind swap can't isolate. | [f/freeze-frozen](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/f/freeze-frozen) |
-| `header`/`head` → `heading`; `context menu` → `shortcut menu`; `disk` → `hard drive`; `directory` → `folder`; `field`/`entry field` → `box`; `attribute` (meaning property) → `property`; `issue` (meaning problem) → `problem` | Each has a common, correct, unrelated technical sense in API/developer documentation (HTTP header, context menu in a sample app, managed disk, working directory, JSON field, XML attribute, GitHub issue / "issue a token") that a blind match would corrupt. | [h/header](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/h/header), [c/context-menu](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/context-menu), [d/disk](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/d/disk), [d/directory](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/d/directory), [f/field](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/f/field), [a/attribute](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/a/attribute), [i/issue](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/i/issue) |
-| `radio button`, `scroll`, `Microsoft's` (possessive), x-multiplication, `shortcut key` | Tier-4/Tier-1 crossings — see Rule 0. | [r/radio-button](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/r/radio-button), [s/scroll](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/s/scroll), [m/microsoft](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/microsoft), [m/multiplication-sign](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/multiplication-sign), [keys-keyboard-shortcuts](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/keys-keyboard-shortcuts) |
-| `may` (ability modal) | Homograph collision with the proper noun "May" (the month) — `ignoreCase: true` (needed to catch sentence-initial "May") would flag "released in May 2024" as a modal verb. | [c/can-may](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/can-may) |
-| `that` (referring to people) → `who` | One of the most common words in English; only a small fraction of occurrences refer to people. A literal `swap` would be extraordinarily noisy; the guide's own quote scopes the objection to a use a `pattern`/`swap` can't isolate. | [w/who-vs-that](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/w/who-vs-that) |
-| `star` → `asterisk` | Ordinary English word (star rating, star performer) with a narrow, Microsoft-documented exception (OK for a phone-keypad key) a blanket swap would miss in both directions. | [keys-keyboard-shortcuts](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/keys-keyboard-shortcuts) |
-| `+` (plus sign, in text) | Single punctuation character; collides with `C++`, query strings, and ordinary arithmetic in code-adjacent prose. | [p/plus-sign](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/plus-sign) |
-| `field`, `attribute`, `issue` | See row above — TOO-RISKY for Redocly's schema/API documentation specifically. | (same as above) |
-| `foo`/`foobar`/`fubar` (as placeholders) | "OK to use... in content for a technical audience" — Redocly's docs qualify. | [f/foo-foobar-fubar](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/f/foo-foobar-fubar) |
-| `Internet Service Provider`/`Key Performance Indicator` (C20 illustrative pairs) | The general principle (lowercase spelled-out acronym forms) is CONFIRMED, but these specific phrase pairs were not independently re-quoted as live-page examples by any verifier — dropped rather than shipped on the author's own unverified guess. | [acronyms](https://learn.microsoft.com/en-us/style-guide/acronyms) (general principle only; no per-phrase page exists to cite) |
-| `API's`/`URL's`/`SDK's` → `APIs`/`URLs`/`SDKs` (C18) | The general "add lowercase s, not an apostrophe" principle is CONFIRMED, but a bare `[A-Z]{2,}'s` is frequently a legitimate POSSESSIVE ("the API's response"), not an attempted plural — verifier G's own note flags this exact ambiguity. Excluded entirely; only the unambiguous decade-plural case (`microsoft/no-apostrophe-plural-decade`) ships. | [acronyms](https://learn.microsoft.com/en-us/style-guide/acronyms) |
-| `property sheet`/`property page` → "dialog box or tab"; `application developer` → "software developer, web developer, developer, or programmer" | Multiple, meaningfully different acceptable replacements — no single canonical swap target can be chosen without guessing which the guide's authors intended for a given context. | [p/property-sheet-property-page](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/property-sheet-property-page), [a/application-developer-app-developer](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/a/application-developer-app-developer) |
-| Broader militaristic-language bundle (`kill chain`, `blast radius`, `locked down`, `threat intel`, `defense-in-depth approach`, `frontline analysts`, `first line of defense`) | See the note under "Bias-free, militaristic, derogatory language" above — content confirmed real, but no verifier independently quoted exact replacement text for each multi-word term, and the same page's "12 never-use terms" count was already shown to be wrong. | [militaristic-language](https://learn.microsoft.com/en-us/style-guide/militaristic-language) |
-| `corrupt`/`corrupted` (detection-only) | Considered as a `pattern` fallback after ruling out the `swap` to "damaged"; ultimately not shipped at all — the guide's own instruction ("offer help fixing it if possible") is a request for an empathetic, context-dependent rewrite, not a term to flag mechanically. | [c/corrupted](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/corrupted) |
-| C21 acronym first-mention expansion | See "Known limitations" #5. | [acronyms](https://learn.microsoft.com/en-us/style-guide/acronyms) |
-| Broader "spell out & / + / ~ in prose" (A9) | NOISY in developer docs outside heading/list-item/alt scope (query strings, HTML entities, code-adjacent `&&`); the one high-value case (ampersands in HEADINGS specifically) is already covered by `microsoft/no-ampersand-in-headings`. | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings) |
-| `no-possessive-product-names` (C16, "Don't use Microsoft's") | **Not shippable at all**, conditionally or not — see below. | [m/microsoft](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/microsoft) |
-| `SMB` → "small or medium-sized business" | Fix wave B / Step 4 drop, added here in fix wave C to give it a URL + reason row (it previously existed only in the narrative "Fix wave B / Step 4" prose below, which this table's own stated purpose — "why doesn't `recheck/microsoft` check X?" — doesn't cover). Bare, case-shouted acronym with a common, correct, unrelated technical sense in exactly Redocly's domain: SMB as the Server Message Block network protocol ("mount the SMB share"). No syntactic anchor distinguishes either sense — both are just the bare acronym in ordinary noun position. | [s/smb](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/s/smb) |
-| `SKU` → "subscription, edition, version, or tier" | Fix wave B / Step 4 drop, same table-completeness reason as `SMB` above. Common, correct, unrelated e-commerce/inventory sense ("the SKU field") with no syntactic anchor separating it from Microsoft's intended sense. Carries a second, independent hazard even where the guide's sense IS intended: the guide names FOUR acceptable alternatives, not one, so no single canonical swap target exists either. | [s/sku](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/s/sku) |
-| `terminate` → "close" | Fix wave B / Step 4 drop, same table-completeness reason as `SMB`/`SKU` above. "Terminate the instance/process/session/connection" is standard, correct cloud-infrastructure vocabulary throughout Redocly's own API-documentation domain (a genuine meaning change, not a false match: the guide's sense is "close an app or window"), and no reliable positional anchor separates that sense from the guide's UI sense the way `exit`'s determiner-based anchor does. | [t/terminate](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/t/terminate) |
+| Candidate                                                                                                                                                                                                                       | Why excluded                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Source(s)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deprecated` → `obsolete`; `user` → `customer`; `client` (a person) → `customer`; `utility` → `tool`; `cursor`; `machine` → `computer`; `start` (an app) → `open`                                                               | Each carries an explicit or de-facto developer/technical-audience carve-out that directly applies to Redocly's own documentation — see "Additional tier-boundary findings" above.                                                                                                                                                                                                                                                                                                                                                                                    | [d/deprecated](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/d/deprecated), [u/user-end-user](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/u/user-end-user), [c/client](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/client), [u/utility](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/u/utility), [mouse-mouse-interaction-terms](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/mouse-mouse-interaction-terms), [computer-device-terms](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/computer-device-terms), [o/open](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/o/open) |
+| `freeze`/`frozen` (as system-hang synonyms)                                                                                                                                                                                     | Sense-ambiguous: "freeze an account," "freeze a value," "deep freeze" are all common, unrelated, correct uses; the guide's own carve-out ("as a synonym for stop responding") names a specific sense a blind swap can't isolate.                                                                                                                                                                                                                                                                                                                                     | [f/freeze-frozen](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/f/freeze-frozen)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `header`/`head` → `heading`; `context menu` → `shortcut menu`; `disk` → `hard drive`; `directory` → `folder`; `field`/`entry field` → `box`; `attribute` (meaning property) → `property`; `issue` (meaning problem) → `problem` | Each has a common, correct, unrelated technical sense in API/developer documentation (HTTP header, context menu in a sample app, managed disk, working directory, JSON field, XML attribute, GitHub issue / "issue a token") that a blind match would corrupt.                                                                                                                                                                                                                                                                                                       | [h/header](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/h/header), [c/context-menu](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/context-menu), [d/disk](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/d/disk), [d/directory](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/d/directory), [f/field](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/f/field), [a/attribute](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/a/attribute), [i/issue](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/i/issue)                                                                                                           |
+| `radio button`, `scroll`, `Microsoft's` (possessive), x-multiplication, `shortcut key`                                                                                                                                          | Tier-4/Tier-1 crossings — see Rule 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | [r/radio-button](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/r/radio-button), [s/scroll](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/s/scroll), [m/microsoft](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/microsoft), [m/multiplication-sign](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/multiplication-sign), [keys-keyboard-shortcuts](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/keys-keyboard-shortcuts)                                                                                                                                                                                                                                      |
+| `may` (ability modal)                                                                                                                                                                                                           | Homograph collision with the proper noun "May" (the month) — `ignoreCase: true` (needed to catch sentence-initial "May") would flag "released in May 2024" as a modal verb.                                                                                                                                                                                                                                                                                                                                                                                          | [c/can-may](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/can-may)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `that` (referring to people) → `who`                                                                                                                                                                                            | One of the most common words in English; only a small fraction of occurrences refer to people. A literal `swap` would be extraordinarily noisy; the guide's own quote scopes the objection to a use a `pattern`/`swap` can't isolate.                                                                                                                                                                                                                                                                                                                                | [w/who-vs-that](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/w/who-vs-that)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `star` → `asterisk`                                                                                                                                                                                                             | Ordinary English word (star rating, star performer) with a narrow, Microsoft-documented exception (OK for a phone-keypad key) a blanket swap would miss in both directions.                                                                                                                                                                                                                                                                                                                                                                                          | [keys-keyboard-shortcuts](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/keys-keyboard-shortcuts)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `+` (plus sign, in text)                                                                                                                                                                                                        | Single punctuation character; collides with `C++`, query strings, and ordinary arithmetic in code-adjacent prose.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | [p/plus-sign](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/plus-sign)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `field`, `attribute`, `issue`                                                                                                                                                                                                   | See row above — TOO-RISKY for Redocly's schema/API documentation specifically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | (same as above)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `foo`/`foobar`/`fubar` (as placeholders)                                                                                                                                                                                        | "OK to use... in content for a technical audience" — Redocly's docs qualify.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | [f/foo-foobar-fubar](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/f/foo-foobar-fubar)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `Internet Service Provider`/`Key Performance Indicator` (C20 illustrative pairs)                                                                                                                                                | The general principle (lowercase spelled-out acronym forms) is CONFIRMED, but these specific phrase pairs were not independently re-quoted as live-page examples by any verifier — dropped rather than shipped on the author's own unverified guess.                                                                                                                                                                                                                                                                                                                 | [acronyms](https://learn.microsoft.com/en-us/style-guide/acronyms) (general principle only; no per-phrase page exists to cite)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `API's`/`URL's`/`SDK's` → `APIs`/`URLs`/`SDKs` (C18)                                                                                                                                                                            | The general "add lowercase s, not an apostrophe" principle is CONFIRMED, but a bare `[A-Z]{2,}'s` is frequently a legitimate POSSESSIVE ("the API's response"), not an attempted plural — verifier G's own note flags this exact ambiguity. Excluded entirely; only the unambiguous decade-plural case (`microsoft/no-apostrophe-plural-decade`) ships.                                                                                                                                                                                                              | [acronyms](https://learn.microsoft.com/en-us/style-guide/acronyms)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `property sheet`/`property page` → "dialog box or tab"; `application developer` → "software developer, web developer, developer, or programmer"                                                                                 | Multiple, meaningfully different acceptable replacements — no single canonical swap target can be chosen without guessing which the guide's authors intended for a given context.                                                                                                                                                                                                                                                                                                                                                                                    | [p/property-sheet-property-page](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/property-sheet-property-page), [a/application-developer-app-developer](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/a/application-developer-app-developer)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Broader militaristic-language bundle (`kill chain`, `blast radius`, `locked down`, `threat intel`, `defense-in-depth approach`, `frontline analysts`, `first line of defense`)                                                  | See the note under "Bias-free, militaristic, derogatory language" above — content confirmed real, but no verifier independently quoted exact replacement text for each multi-word term, and the same page's "12 never-use terms" count was already shown to be wrong.                                                                                                                                                                                                                                                                                                | [militaristic-language](https://learn.microsoft.com/en-us/style-guide/militaristic-language)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `corrupt`/`corrupted` (detection-only)                                                                                                                                                                                          | Considered as a `pattern` fallback after ruling out the `swap` to "damaged"; ultimately not shipped at all — the guide's own instruction ("offer help fixing it if possible") is a request for an empathetic, context-dependent rewrite, not a term to flag mechanically.                                                                                                                                                                                                                                                                                            | [c/corrupted](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/corrupted)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| C21 acronym first-mention expansion                                                                                                                                                                                             | See "Known limitations" #5.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [acronyms](https://learn.microsoft.com/en-us/style-guide/acronyms)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Broader "spell out & / + / ~ in prose" (A9)                                                                                                                                                                                     | NOISY in developer docs outside heading/list-item/alt scope (query strings, HTML entities, code-adjacent `&&`); the one high-value case (ampersands in HEADINGS specifically) is already covered by `microsoft/no-ampersand-in-headings`.                                                                                                                                                                                                                                                                                                                            | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `no-possessive-product-names` (C16, "Don't use Microsoft's")                                                                                                                                                                    | **Not shippable at all**, conditionally or not — see below.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | [m/microsoft](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/microsoft)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `SMB` → "small or medium-sized business"                                                                                                                                                                                        | Fix wave B / Step 4 drop, added here in fix wave C to give it a URL + reason row (it previously existed only in the narrative "Fix wave B / Step 4" prose below, which this table's own stated purpose — "why doesn't `recheck/microsoft` check X?" — doesn't cover). Bare, case-shouted acronym with a common, correct, unrelated technical sense in exactly Redocly's domain: SMB as the Server Message Block network protocol ("mount the SMB share"). No syntactic anchor distinguishes either sense — both are just the bare acronym in ordinary noun position. | [s/smb](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/s/smb)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `SKU` → "subscription, edition, version, or tier"                                                                                                                                                                               | Fix wave B / Step 4 drop, same table-completeness reason as `SMB` above. Common, correct, unrelated e-commerce/inventory sense ("the SKU field") with no syntactic anchor separating it from Microsoft's intended sense. Carries a second, independent hazard even where the guide's sense IS intended: the guide names FOUR acceptable alternatives, not one, so no single canonical swap target exists either.                                                                                                                                                     | [s/sku](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/s/sku)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `terminate` → "close"                                                                                                                                                                                                           | Fix wave B / Step 4 drop, same table-completeness reason as `SMB`/`SKU` above. "Terminate the instance/process/session/connection" is standard, correct cloud-infrastructure vocabulary throughout Redocly's own API-documentation domain (a genuine meaning change, not a false match: the guide's sense is "close an app or window"), and no reliable positional anchor separates that sense from the guide's UI sense the way `exit`'s determiner-based anchor does.                                                                                              | [t/terminate](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/t/terminate)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
 
 Every URL in the "Source(s)" column above was re-verified live (`curl`,
 HTTP 200) during this fix wave — see `sources.json` for the ones this
@@ -333,12 +333,12 @@ Redocly's own vocabulary, not something the Microsoft guide provides.
 
 ### NOT-ENFORCEABLE (real guide content, requires human judgment or structure Recheck doesn't have)
 
-| Candidate | Why excluded |
-|---|---|
-| V19-V22, V37-V39 (noun+verb contractions, active voice, subjunctive mood, verb-first sentences, modifier stacks, that/who omission, -ing word care) | Each requires POS tagging or grammatical-role judgment beyond regex/AST primitives. |
+| Candidate                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Why excluded                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| V19-V22, V37-V39 (noun+verb contractions, active voice, subjunctive mood, verb-first sentences, modifier stacks, that/who omission, -ing word care)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Each requires POS tagging or grammatical-role judgment beyond regex/AST primitives.                                                                                                                                                                                                                                                                                                                                                 |
 | C10 (second-level headings need ≥2 siblings), C11 (no two headings in a row), L4 (periods only on complete sentences), L5 (per-list punctuation consistency), L7 (list parallelism), T1 (table sentence-case — NOISY, reference tables are dense with identifiers/proper nouns), T4 ("Name" is a bad column header — NOISY, "Name" is genuinely correct in many API reference tables), T5/T6/T10 (table intro-sentence rules, minimum table dimensions), P3/P4/P6/P8/P9/P10-P12 (multiple-hyphens-for-dash, en-dash-for-minus, from/through ranges, closing-quote placement, mid-sentence colon rules, colon-before-block), N1/N2/N6/N7/N9/N11 (spell out 0-9, no sentence-initial numerals, no K/M/B abbreviation, comma grouping, spell out months, decimal leading zero) | Each is confirmed content, but every one carries either a documented exception too common to ignore (space-limited UI text, "if one item requires a numeral," page numbers/addresses/decimals) or needs structural context (paragraph→table/list/heading adjacency) Recheck's segment model doesn't expose — matching the research draft's own NOISY/NOT-ENFORCEABLE verdicts, independently re-confirmed rather than re-litigated. |
-| U5 (don't name the UI element type unless it adds clarity), U8 (file extensions lowercase / device names uppercase), U9 (bold not italic for work titles), A7 (directional terms as the only clue to location), W1-W4 (URL formatting/bare-URL rules) | "Unless it adds needed clarity" and "as the only clue" are judgment calls; the URL rules were separately judged too weakly cited (W4) or too noisy in a docs site full of real clickable links (W1/W2) to attribute to Microsoft specifically — available generically via `recheck/markdown`'s `no-bare-urls` if wanted. |
-| S1-S4 (link fragments, fenced-code-language, single-H1, consistent bullet/fence/emphasis/table-pipe style) | The research draft itself labels these "House rule; no Microsoft statement" — no live-page citation exists for any of them, so none ship under a Microsoft attribution (unlike `recheck/google`, whose equivalent structural rules ARE independently Google-cited). |
+| U5 (don't name the UI element type unless it adds clarity), U8 (file extensions lowercase / device names uppercase), U9 (bold not italic for work titles), A7 (directional terms as the only clue to location), W1-W4 (URL formatting/bare-URL rules)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "Unless it adds needed clarity" and "as the only clue" are judgment calls; the URL rules were separately judged too weakly cited (W4) or too noisy in a docs site full of real clickable links (W1/W2) to attribute to Microsoft specifically — available generically via `recheck/markdown`'s `no-bare-urls` if wanted.                                                                                                            |
+| S1-S4 (link fragments, fenced-code-language, single-H1, consistent bullet/fence/emphasis/table-pipe style)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | The research draft itself labels these "House rule; no Microsoft statement" — no live-page citation exists for any of them, so none ship under a Microsoft attribution (unlike `recheck/google`, whose equivalent structural rules ARE independently Google-cited).                                                                                                                                                                 |
 
 ## Deliberation and development history
 
@@ -358,13 +358,13 @@ research draft's config shipped five terms unconditionally at `error` while
 those SAME five also appeared, verbatim, on its own Tier-4 "never enforce"
 list:
 
-| Term | Live page carve-out |
-|---|---|
-| `execute` | "Don't use except to follow the UI. Use run instead." |
-| `reboot` | "If the UI or API uses reboot in a label... it's OK to refer to the label." |
-| `navigate` | "You don't need to find an alternative to navigation when it's the most precise word in the context." |
-| `ZIP Code` | "It's OK to use ZIP Code in content that's intended for a US audience only." |
-| `disjoint selection` | "Don't use... except for a technical audience, and only if the term appears in the UI or API." |
+| Term                 | Live page carve-out                                                                                   |
+| -------------------- | ----------------------------------------------------------------------------------------------------- |
+| `execute`            | "Don't use except to follow the UI. Use run instead."                                                 |
+| `reboot`             | "If the UI or API uses reboot in a label... it's OK to refer to the label."                           |
+| `navigate`           | "You don't need to find an alternative to navigation when it's the most precise word in the context." |
+| `ZIP Code`           | "It's OK to use ZIP Code in content that's intended for a US audience only."                          |
+| `disjoint selection` | "Don't use... except for a technical audience, and only if the term appears in the UI or API."        |
 
 None of the five ship. Their siblings sharing the exact same conditional
 sentence (`contiguous selection`, `nonadjacent selection`, `noncontiguous
@@ -372,13 +372,13 @@ selection` — same sentence as `disjoint selection`) are excluded too.
 
 #### The five additional mis-filed entries the corrections doc flagged for evaluation
 
-| Term | Carve-out found | Disposition |
-|---|---|---|
-| `shortcut key` | Bundled in the same Tier-1 row as `accelerator key, fast key, hot key, quick key, speed key`, but `keys-keyboard-shortcuts` grants it, alone, the identical developer-audience carve-out already accepted for `access key` (correctly Tier 4). | Removed from the row; `accelerator key`/`fast key`/`hot key`/`quick key`/`speed key` still ship (no carve-out for those). |
-| `radio button` | "Use radio button **only** in content for developers in which the API includes the term." | Excluded entirely. |
-| `scroll` | "It's OK to use scroll in content that teaches beginning skills." | Excluded entirely. |
-| x-multiplication (`x` → `×`) | "Use an asterisk (\*) **if you need to match the UI**" — Tier 4's own defining phrase, verbatim. Also SUBSTRING-RISK (bare `x` collides with `x-axis`/`x-ray`/`x-coordinate`, all hyphen-joined so `\bx\b` DOES match inside them). | Excluded entirely (double reason). |
-| `Microsoft's` (possessive ban) | "Exception: it's OK to use Microsoft's occasionally when referring to the company itself" — with the guide's own worked example, "Microsoft's privacy policies." | Excluded entirely — see "C16" above; not shippable at all, conditional or not (see reasoning). |
+| Term                           | Carve-out found                                                                                                                                                                                                                                | Disposition                                                                                                               |
+| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| `shortcut key`                 | Bundled in the same Tier-1 row as `accelerator key, fast key, hot key, quick key, speed key`, but `keys-keyboard-shortcuts` grants it, alone, the identical developer-audience carve-out already accepted for `access key` (correctly Tier 4). | Removed from the row; `accelerator key`/`fast key`/`hot key`/`quick key`/`speed key` still ship (no carve-out for those). |
+| `radio button`                 | "Use radio button **only** in content for developers in which the API includes the term."                                                                                                                                                      | Excluded entirely.                                                                                                        |
+| `scroll`                       | "It's OK to use scroll in content that teaches beginning skills."                                                                                                                                                                              | Excluded entirely.                                                                                                        |
+| x-multiplication (`x` → `×`)   | "Use an asterisk (\*) **if you need to match the UI**" — Tier 4's own defining phrase, verbatim. Also SUBSTRING-RISK (bare `x` collides with `x-axis`/`x-ray`/`x-coordinate`, all hyphen-joined so `\bx\b` DOES match inside them).            | Excluded entirely (double reason).                                                                                        |
+| `Microsoft's` (possessive ban) | "Exception: it's OK to use Microsoft's occasionally when referring to the company itself" — with the guide's own worked example, "Microsoft's privacy policies."                                                                               | Excluded entirely — see "C16" above; not shippable at all, conditional or not (see reasoning).                            |
 
 #### Additional tier-boundary findings made while authoring (beyond the ten above)
 
@@ -387,19 +387,19 @@ rows that were not individually named by the corrections doc but share the
 identical shape. Found by re-reading the verifier tables while authoring,
 not pre-flagged:
 
-| Term | Carve-out | Disposition |
-|---|---|---|
-| `deprecated` → `obsolete` | "Avoid in content for a **technical audience**. Don't use in content for a general audience." | **Excluded.** Redocly's docs are technical-audience API documentation, and "deprecated" is itself load-bearing OpenAPI vocabulary (the `deprecated: true` field). Shipping this unconditionally would misfire on Redocly's own domain, the same shape as `header`/`context menu`/`disk`/`directory` below. |
-| `and/or` → `or` | "Don't use **unless it helps you avoid lengthy, complex wording**." | Excluded (not in the shipped word list). |
-| `freeze`/`frozen` | "Don't use freeze **as a synonym for stop responding**" — i.e. only in that one sense; "freeze" has many unrelated senses (freeze an account, freeze a value). | Excluded from `az-state-failure`. **Correction (fix wave B / Step 9):** this row previously said "not verifier-flagged" — false. Verifier G:76 marks it `CONFIRMED (cond.)` with the exact quote above; the exclusion is a real, verifier-confirmed sense-ambiguity call (the same class as `marquee`, which verifier H explicitly calls "context-flipped"), not an unflagged author guess. |
-| `user` → `customer`/`person`/etc. | "It's OK to use user in content for **developers**." | Excluded — Redocly's docs are developer content, and "user" is one of the most common words in any documentation. |
-| `cursor` (as opposed to `insertion point`) | "Use cursor only for a **technical audience**." | Only `insertion point` → `pointer` ships (unconditional per the same page); bare `cursor` excluded. |
-| `machine` → `computer` | "It's OK to use machine in content for a **technical audience** and... virtualization." | Excluded — "virtual machine", "state machine", "build machine" are all extremely common in Redocly's domain. |
-| `foo, foobar, fubar` | "OK to use these words as placeholders... in content for a **technical audience**." | Excluded (Redocly's docs qualify). |
-| `client` (a person) → `customer` | Not marked `(cond.)` by the verifier — G:93 states it plainly ("Don't use client to refer to a person. Use customer instead."), no carve-out at all. | Excluded anyway (see the fix-wave-B note directly below — this is a considered "anchoring isn't reliable" call, not silent inference). |
-| `utility` → `tool` | Not marked `(cond.)` either — H:55 is also unconditional ("Use tool, not utility, to describe a feature..."). | Excluded anyway (same fix-wave-B note). |
-| `start` (an app) → `open` | Not marked `(cond.)` — G:89 bundles it with `launch` under one unconditional CONFIRMED row. The row bundles `launch, start (an app), boot`; "start" alone is one of the most common words in English with countless unrelated correct senses (start a server, start a request, from the start). | Excluded; only `launch` → `open` and `boot` → `turn on` ship from this row. |
-| `deinstall`, `machine`, `user`, `client`, `utility` cross-checked against Redocly's own domain vocabulary | — | See individual rows above. |
+| Term                                                                                                      | Carve-out                                                                                                                                                                                                                                                                                       | Disposition                                                                                                                                                                                                                                                                                                                                                                                 |
+| --------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deprecated` → `obsolete`                                                                                 | "Avoid in content for a **technical audience**. Don't use in content for a general audience."                                                                                                                                                                                                   | **Excluded.** Redocly's docs are technical-audience API documentation, and "deprecated" is itself load-bearing OpenAPI vocabulary (the `deprecated: true` field). Shipping this unconditionally would misfire on Redocly's own domain, the same shape as `header`/`context menu`/`disk`/`directory` below.                                                                                  |
+| `and/or` → `or`                                                                                           | "Don't use **unless it helps you avoid lengthy, complex wording**."                                                                                                                                                                                                                             | Excluded (not in the shipped word list).                                                                                                                                                                                                                                                                                                                                                    |
+| `freeze`/`frozen`                                                                                         | "Don't use freeze **as a synonym for stop responding**" — i.e. only in that one sense; "freeze" has many unrelated senses (freeze an account, freeze a value).                                                                                                                                  | Excluded from `az-state-failure`. **Correction (fix wave B / Step 9):** this row previously said "not verifier-flagged" — false. Verifier G:76 marks it `CONFIRMED (cond.)` with the exact quote above; the exclusion is a real, verifier-confirmed sense-ambiguity call (the same class as `marquee`, which verifier H explicitly calls "context-flipped"), not an unflagged author guess. |
+| `user` → `customer`/`person`/etc.                                                                         | "It's OK to use user in content for **developers**."                                                                                                                                                                                                                                            | Excluded — Redocly's docs are developer content, and "user" is one of the most common words in any documentation.                                                                                                                                                                                                                                                                           |
+| `cursor` (as opposed to `insertion point`)                                                                | "Use cursor only for a **technical audience**."                                                                                                                                                                                                                                                 | Only `insertion point` → `pointer` ships (unconditional per the same page); bare `cursor` excluded.                                                                                                                                                                                                                                                                                         |
+| `machine` → `computer`                                                                                    | "It's OK to use machine in content for a **technical audience** and... virtualization."                                                                                                                                                                                                         | Excluded — "virtual machine", "state machine", "build machine" are all extremely common in Redocly's domain.                                                                                                                                                                                                                                                                                |
+| `foo, foobar, fubar`                                                                                      | "OK to use these words as placeholders... in content for a **technical audience**."                                                                                                                                                                                                             | Excluded (Redocly's docs qualify).                                                                                                                                                                                                                                                                                                                                                          |
+| `client` (a person) → `customer`                                                                          | Not marked `(cond.)` by the verifier — G:93 states it plainly ("Don't use client to refer to a person. Use customer instead."), no carve-out at all.                                                                                                                                            | Excluded anyway (see the fix-wave-B note directly below — this is a considered "anchoring isn't reliable" call, not silent inference).                                                                                                                                                                                                                                                      |
+| `utility` → `tool`                                                                                        | Not marked `(cond.)` either — H:55 is also unconditional ("Use tool, not utility, to describe a feature...").                                                                                                                                                                                   | Excluded anyway (same fix-wave-B note).                                                                                                                                                                                                                                                                                                                                                     |
+| `start` (an app) → `open`                                                                                 | Not marked `(cond.)` — G:89 bundles it with `launch` under one unconditional CONFIRMED row. The row bundles `launch, start (an app), boot`; "start" alone is one of the most common words in English with countless unrelated correct senses (start a server, start a request, from the start). | Excluded; only `launch` → `open` and `boot` → `turn on` ship from this row.                                                                                                                                                                                                                                                                                                                 |
+| `deinstall`, `machine`, `user`, `client`, `utility` cross-checked against Redocly's own domain vocabulary | —                                                                                                                                                                                                                                                                                               | See individual rows above.                                                                                                                                                                                                                                                                                                                                                                  |
 
 **Fix wave B / Step 8 — these three are inference, not a documented guide
 exception, and that distinction matters.** Unlike `header`/`context
@@ -449,28 +449,28 @@ the developer/API-documentation audience Redocly serves. **None of the four
 ship**, unconditionally or otherwise — running this preset on Redocly's own
 docs must not flag any of them:
 
-| Term | Carve-out |
-|---|---|
-| `header` (meaning heading) → `heading` | Microsoft's own page confirms "it's OK to use header as a short form of file header, as in HTML header" — the standard, correct term for an HTTP/API request/response header throughout API documentation. |
-| `context menu` → `shortcut menu` | "Use context menu only in content for developers." |
-| `disk`/`fixed disk`/`hard disk`/`disk drive` → `hard drive` | "Use disk only in the context of Azure cloud storage and virtual machines" — extremely common, correct in cloud/infra API docs. |
-| `directory` → `folder` | "Use directory only in content for developers... to match the API" — CLI paths, working directory, root directory. |
+| Term                                                        | Carve-out                                                                                                                                                                                                  |
+| ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `header` (meaning heading) → `heading`                      | Microsoft's own page confirms "it's OK to use header as a short form of file header, as in HTML header" — the standard, correct term for an HTTP/API request/response header throughout API documentation. |
+| `context menu` → `shortcut menu`                            | "Use context menu only in content for developers."                                                                                                                                                         |
+| `disk`/`fixed disk`/`hard disk`/`disk drive` → `hard drive` | "Use disk only in the context of Azure cloud storage and virtual machines" — extremely common, correct in cloud/infra API docs.                                                                            |
+| `directory` → `folder`                                      | "Use directory only in content for developers... to match the API" — CLI paths, working directory, root directory.                                                                                         |
 
 `microsoft-clean.md` includes a paragraph using all four terms in exactly
 this developer sense, and the test suite asserts zero findings on it.
 
 ### Section 3 — wrong, inverted, and non-guidance entries corrected
 
-| Entry | Problem found | Resolution |
-|---|---|---|
-| `shaded` | **Inverted.** The draft bundled it into an avoid-term row (`gray, grayed out, dimmed, shaded, unavailable, disabled`); the live pages state Microsoft **recommends** "shaded" for the appearance of a checkbox representing a mixture of settings. | `shaded` does not appear anywhere in this preset, in either direction. **Nor does the rest of that row** — no `grayed out` or `dimmed` rule ships here either (an earlier revision of this table claimed one did; it never existed). `recheck/inclusive-language` covers `grayed out` → `unavailable`, sourced from Google. |
-| `boot` → `open` | Wrong direction AND target. Live page: *"Don't use as a verb. Use turn on to refer to turning on power to a device."* | Shipped separately as `boot` → `turn on` (`microsoft/az-lifecycle-verbs`), not bundled with `launch`/`open`. |
-| `corrupt`/`corrupted` → `damaged` | Not guidance — the source asks for an empathetic sentence **rewrite** ("Try to use a more empathetic statement... offer help"); its own worked example never uses "damaged". | Not shipped as a swap. (Detection-only was considered and also dropped for scope reasons — see "Excluded candidates".) |
-| `invalid` → `not valid` | Soft preference: *"Both terms are OK to use, but try to use more specific terms instead"* — a machine-translation-safety tip, not a "never use" rule. | Not shipped. |
-| "afflicted with" (Tier 2) | **Fabricated** — appears nowhere on the live `accessibility-terms` page; the actual Row 5 avoid-list is "Affected by, stricken with, suffers from, a victim of, an epileptic." | Not shipped anywhere. `affected by`/`stricken with`/`suffers from`/`a victim of` (the real Row 5 terms, minus "an epileptic", which needs a sentence rewrite no pattern/swap can safely target) ship in `microsoft/accessibility-terms`. |
-| `ToolTip` regex (Tier 3) | Config-mechanics bug: a shared `ignoreCase: true` flag on the combined "tool tip"/"ToolTip" pattern made the "ToolTip"-only branch also match the already-correct lowercase "tooltip". | `microsoft/tooltip-capitalization` ships as its OWN case-sensitive (`ignoreCase: false`) rule, separate from `microsoft/spelling-hyphenation`'s case-insensitive "tool tip" (spacing) pattern. |
-| Row-1452 "(all don't use)" bundle | **Under-shipped.** The draft filed the whole bundle as detection-only; six of its members have an explicit, single-value replacement stated on their own page. | `friendly name` → `display name`, `print queue`/`printer queue` → `list of documents`, `data record` → `record`, `e-form` → `form`, `upsize` → `scale up` ship in `microsoft/az-real-replacements` (plus `working memory`, `soft copy`, `print out`, `search and replace`, `target drive`/`target file`, which had replacements but weren't singled out by the corrections doc). `property sheet`/`property page` (multi-option: "dialog box or tab") and `application developer` (four very different alternatives: "software developer, web developer, developer, or programmer") are excluded — no single canonical replacement can be chosen without guessing which the guide's authors intended. |
-| Tier 2 accessibility table | **Three crossed pairings.** The draft merged two separate live rows into one, producing wrong swap targets: `handicapped` → `person with a disability` (wrong; that word belongs to Row 3, whose target is "person with limited mobility..."); `differently abled` → `person with a disability` (wrong; Row 9's target is "person with cognitive disabilities, developmental disabilities, learning disabilities, or dyslexia"). | See "Tier 2 design" below — resolved by shipping **detection-only**, sidestepping the wrong-target risk entirely rather than attempting to re-derive every row's exact target from partial verifier quotes. |
+| Entry                             | Problem found                                                                                                                                                                                                                                                                                                                                                                                                                    | Resolution                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `shaded`                          | **Inverted.** The draft bundled it into an avoid-term row (`gray, grayed out, dimmed, shaded, unavailable, disabled`); the live pages state Microsoft **recommends** "shaded" for the appearance of a checkbox representing a mixture of settings.                                                                                                                                                                               | `shaded` does not appear anywhere in this preset, in either direction. **Nor does the rest of that row** — no `grayed out` or `dimmed` rule ships here either (an earlier revision of this table claimed one did; it never existed). `recheck/inclusive-language` covers `grayed out` → `unavailable`, sourced from Google.                                                                                                                                                                                                                                                                                                                                                                           |
+| `boot` → `open`                   | Wrong direction AND target. Live page: _"Don't use as a verb. Use turn on to refer to turning on power to a device."_                                                                                                                                                                                                                                                                                                            | Shipped separately as `boot` → `turn on` (`microsoft/az-lifecycle-verbs`), not bundled with `launch`/`open`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `corrupt`/`corrupted` → `damaged` | Not guidance — the source asks for an empathetic sentence **rewrite** ("Try to use a more empathetic statement... offer help"); its own worked example never uses "damaged".                                                                                                                                                                                                                                                     | Not shipped as a swap. (Detection-only was considered and also dropped for scope reasons — see "Excluded candidates".)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `invalid` → `not valid`           | Soft preference: _"Both terms are OK to use, but try to use more specific terms instead"_ — a machine-translation-safety tip, not a "never use" rule.                                                                                                                                                                                                                                                                            | Not shipped.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| "afflicted with" (Tier 2)         | **Fabricated** — appears nowhere on the live `accessibility-terms` page; the actual Row 5 avoid-list is "Affected by, stricken with, suffers from, a victim of, an epileptic."                                                                                                                                                                                                                                                   | Not shipped anywhere. `affected by`/`stricken with`/`suffers from`/`a victim of` (the real Row 5 terms, minus "an epileptic", which needs a sentence rewrite no pattern/swap can safely target) ship in `microsoft/accessibility-terms`.                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `ToolTip` regex (Tier 3)          | Config-mechanics bug: a shared `ignoreCase: true` flag on the combined "tool tip"/"ToolTip" pattern made the "ToolTip"-only branch also match the already-correct lowercase "tooltip".                                                                                                                                                                                                                                           | `microsoft/tooltip-capitalization` ships as its OWN case-sensitive (`ignoreCase: false`) rule, separate from `microsoft/spelling-hyphenation`'s case-insensitive "tool tip" (spacing) pattern.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Row-1452 "(all don't use)" bundle | **Under-shipped.** The draft filed the whole bundle as detection-only; six of its members have an explicit, single-value replacement stated on their own page.                                                                                                                                                                                                                                                                   | `friendly name` → `display name`, `print queue`/`printer queue` → `list of documents`, `data record` → `record`, `e-form` → `form`, `upsize` → `scale up` ship in `microsoft/az-real-replacements` (plus `working memory`, `soft copy`, `print out`, `search and replace`, `target drive`/`target file`, which had replacements but weren't singled out by the corrections doc). `property sheet`/`property page` (multi-option: "dialog box or tab") and `application developer` (four very different alternatives: "software developer, web developer, developer, or programmer") are excluded — no single canonical replacement can be chosen without guessing which the guide's authors intended. |
+| Tier 2 accessibility table        | **Three crossed pairings.** The draft merged two separate live rows into one, producing wrong swap targets: `handicapped` → `person with a disability` (wrong; that word belongs to Row 3, whose target is "person with limited mobility..."); `differently abled` → `person with a disability` (wrong; Row 9's target is "person with cognitive disabilities, developmental disabilities, learning disabilities, or dyslexia"). | See "Tier 2 design" below — resolved by shipping **detection-only**, sidestepping the wrong-target risk entirely rather than attempting to re-derive every row's exact target from partial verifier quotes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 
 ### Self-contradictions — enforced in NEITHER direction (three), plus one escalated
 
@@ -481,12 +481,12 @@ the task-10 fix wave to ship detection-only — see the dedicated subsection
 below the table. Both citations for all four are recorded here regardless,
 per the task's instruction:
 
-| Case | Page A | Page B |
-|---|---|---|
-| **`%` vs. spelled-out "percent"** | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers) (`ms.date` 2022-05-13): "Use a numeral plus percent to specify a percentage." | [a-z/percent-percentage](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/percent-percentage) (`ms.date` 2023-11-15, newer): "Use the percent sign (\"%\") with numerals, rather than spelling out \"percent.\"" |
-| **`master/slave` replacement target** — ESCALATED, ships detection-only, see below | [bias-free](https://learn.microsoft.com/en-us/style-guide/bias-free-communication): "primary/subordinate ← master/slave" | [a-z/master-slave](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/master-slave): "Don't use master/slave. Use primary/replica or alternatives such as primary/secondary, principal/agent, controller/worker" — and separately rejects `primary/subordinate` as a synonym for parent/child. |
-| **`etc.`** | [use-us-spelling](https://learn.microsoft.com/en-us/style-guide/word-choice/use-us-spelling-avoid-non-english-words): "It's OK to use etc., in situations where space is limited." | [a-z/etc](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/e/etc): "Don't use. Instead be specific. When space is limited, use such as or like." |
-| **Forced line breaks** | [writing-all-abilities](https://learn.microsoft.com/en-us/style-guide/accessibility/writing-all-abilities): "Don't force line breaks... within sentences and paragraphs." | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings): "Break two-line headings carefully... (Shift + Enter inserts a manual line break)." |
+| Case                                                                               | Page A                                                                                                                                                                             | Page B                                                                                                                                                                                                                                                                                                                     |
+| ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`%` vs. spelled-out "percent"**                                                  | [numbers](https://learn.microsoft.com/en-us/style-guide/numbers) (`ms.date` 2022-05-13): "Use a numeral plus percent to specify a percentage."                                     | [a-z/percent-percentage](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/p/percent-percentage) (`ms.date` 2023-11-15, newer): "Use the percent sign (\"%\") with numerals, rather than spelling out \"percent.\""                                                                             |
+| **`master/slave` replacement target** — ESCALATED, ships detection-only, see below | [bias-free](https://learn.microsoft.com/en-us/style-guide/bias-free-communication): "primary/subordinate ← master/slave"                                                           | [a-z/master-slave](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/m/master-slave): "Don't use master/slave. Use primary/replica or alternatives such as primary/secondary, principal/agent, controller/worker" — and separately rejects `primary/subordinate` as a synonym for parent/child. |
+| **`etc.`**                                                                         | [use-us-spelling](https://learn.microsoft.com/en-us/style-guide/word-choice/use-us-spelling-avoid-non-english-words): "It's OK to use etc., in situations where space is limited." | [a-z/etc](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/e/etc): "Don't use. Instead be specific. When space is limited, use such as or like."                                                                                                                                               |
+| **Forced line breaks**                                                             | [writing-all-abilities](https://learn.microsoft.com/en-us/style-guide/accessibility/writing-all-abilities): "Don't force line breaks... within sentences and paragraphs."          | [headings](https://learn.microsoft.com/en-us/style-guide/scannable-content/headings): "Break two-line headings carefully... (Shift + Enter inserts a manual line break)."                                                                                                                                                  |
 
 Also note: `via` is dropped from the Latin-abbreviation swap list on
 verifier E's own recommendation ("Could not independently confirm 'via'
@@ -526,12 +526,12 @@ Shipping a `metric` rule under a Microsoft citation would misattribute an
 invented numeric mandate. Instead, this preset ships the guide's own real
 structural numbers:
 
-| Rule | Assertion | Guide's number | Source |
-|---|---|---|---|
-| `microsoft/paragraph-length` | `length`, `unit: sentences`, `max: 7` | "Three to seven lines is about the right length for a paragraph." | [scannable-content](https://learn.microsoft.com/en-us/style-guide/scannable-content/) |
-| `microsoft/list-length` | `list-length`, `min: 2, max: 7` | "at least two items but (if possible) no more than seven items" | [lists](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists) |
-| `microsoft/comma-density` | `occurrence`, pattern `,`, `max: 2`, `scope: sentence` | "If a sentence contains more than a comma or two and ending punctuation, consider rewriting it" | [punctuation](https://learn.microsoft.com/en-us/style-guide/punctuation/) |
-| `microsoft/alt-text-length` | `length`, `unit: characters`, `max: 150`, `scope: alt` | "Limit the length to 150 characters." | [alternative-text](https://learn.microsoft.com/en-us/style-guide/accessibility/alternative-text) |
+| Rule                         | Assertion                                              | Guide's number                                                                                  | Source                                                                                           |
+| ---------------------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
+| `microsoft/paragraph-length` | `length`, `unit: sentences`, `max: 7`                  | "Three to seven lines is about the right length for a paragraph."                               | [scannable-content](https://learn.microsoft.com/en-us/style-guide/scannable-content/)            |
+| `microsoft/list-length`      | `list-length`, `min: 2, max: 7`                        | "at least two items but (if possible) no more than seven items"                                 | [lists](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists)                   |
+| `microsoft/comma-density`    | `occurrence`, pattern `,`, `max: 2`, `scope: sentence` | "If a sentence contains more than a comma or two and ending punctuation, consider rewriting it" | [punctuation](https://learn.microsoft.com/en-us/style-guide/punctuation/)                        |
+| `microsoft/alt-text-length`  | `length`, `unit: characters`, `max: 150`, `scope: alt` | "Limit the length to 150 characters."                                                           | [alternative-text](https://learn.microsoft.com/en-us/style-guide/accessibility/alternative-text) |
 
 **Two deliberate deviations from the brief's literal numbers, both found
 empirically while building this preset's own clean fixture, both discussed
@@ -887,24 +887,24 @@ already-correct `favorite` spelling too) narrowed to `favourite` only.
 
 #### Step 4 — ~15 Tier-1 pairs no longer rewrite correct prose
 
-| Pair | Disposition | Reasoning |
-|---|---|---|
-| `SMB` → `small or medium-sized business` | **Dropped** | Homograph with the Server Message Block protocol, common in exactly Redocly's domain ("mount the SMB share"); no positional anchor distinguishes the senses. |
-| `SKU` → `edition` | **Dropped** | `SKU` is standard e-commerce/inventory vocabulary in API docs; also carried an independent ALL-CAPS-shout hazard (single-word replacement) and a multi-target guide quote (subscription/edition/version/tier). |
-| `terminate` → `close` | **Dropped** | "Terminate the instance/process/session" is standard, correct cloud-infrastructure vocabulary in Redocly's own domain — a genuine meaning change, not a false match, with no reliable anchor. |
-| `exit` → `close` | **Anchored, stays fixable** | Lookaround excludes preceding "the/an/no/emergency" and following "code/status/button/sign/strategy/interview/poll/ramp/velocity/row" (noun-compound senses). |
-| `launch` → `open` | **Anchored, stays fixable** | Excludes preceding "product/software/game/website/app/feature/rocket/mission" and following "date/event/party/window/site/pad/day/plan/schedule/announcement". |
-| `boot` → `turn on` | **Anchored, stays fixable** | Excludes following "disk/sector/loader/sequence/process/time/options/record/partition/menu/order/camera". |
-| `crash` → `fail` | **Moved to detection-only** (`az-state-failure-detect`) | G:73 gives a hardware/software target split ("fail" vs. "stop responding") a single `swap` replacement can't express; also anchored against "crash dump/report/log/course/test/site". |
-| `lock up` → `fail` | **Moved to detection-only** (`az-state-failure-detect`) | Same hardware/software split (G:77). |
-| `hangs`/`hang` → `stops responding`/`stop responding` | **Anchored, stays fixable** | Excludes "hang(s) on/up/around/out/together" (retain, end a call, loiter — unrelated phrasal verbs). |
-| `roman` → `regular type` | **Anchored, stays fixable** | Excludes the civilization/proper-noun sense ("Roman numerals/Empire/alphabet/calendar/..."), a homograph collision of the `aka`-inside-`Akamai` shape. |
-| `italics`/`italicized` → `italic` | **Moved to detection-only** (`microsoft/italic-as-noun`) | The guide's own rule ("use only as an adjective, not a noun") makes a direct swap ungrammatical in exactly the position the avoid-term occupies — the same class as `actionable`. |
-| `blade` → `pane` | **Anchored, stays fixable** | Excludes following "server(s)/enclosure/chassis/center(s)/centre(s)" (physical hardware sense). |
-| `beta` → `preview` | **Anchored, stays fixable** | Excludes following "distribution/function/coefficient/particle/blocker/decay" (statistical/physics/medical senses). |
-| `visit` → `go to` | **Anchored, stays fixable** | Excludes following "count(s)/duration/frequency/history/log/data" (analytics-metric noun sense). |
-| `in addition` → `also` | **Anchored, stays fixable** | Excludes following "to" (the standard, grammatically necessary preposition phrase "in addition to X", distinct from the guide's stand-alone-adverb target). |
-| `print out` → `print` | **Anchored, stays fixable** | Excludes following "of" (noun sense — "a print out of X" — distinct from the guide's verb-scoped rule). |
+| Pair                                                  | Disposition                                              | Reasoning                                                                                                                                                                                                      |
+| ----------------------------------------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `SMB` → `small or medium-sized business`              | **Dropped**                                              | Homograph with the Server Message Block protocol, common in exactly Redocly's domain ("mount the SMB share"); no positional anchor distinguishes the senses.                                                   |
+| `SKU` → `edition`                                     | **Dropped**                                              | `SKU` is standard e-commerce/inventory vocabulary in API docs; also carried an independent ALL-CAPS-shout hazard (single-word replacement) and a multi-target guide quote (subscription/edition/version/tier). |
+| `terminate` → `close`                                 | **Dropped**                                              | "Terminate the instance/process/session" is standard, correct cloud-infrastructure vocabulary in Redocly's own domain — a genuine meaning change, not a false match, with no reliable anchor.                  |
+| `exit` → `close`                                      | **Anchored, stays fixable**                              | Lookaround excludes preceding "the/an/no/emergency" and following "code/status/button/sign/strategy/interview/poll/ramp/velocity/row" (noun-compound senses).                                                  |
+| `launch` → `open`                                     | **Anchored, stays fixable**                              | Excludes preceding "product/software/game/website/app/feature/rocket/mission" and following "date/event/party/window/site/pad/day/plan/schedule/announcement".                                                 |
+| `boot` → `turn on`                                    | **Anchored, stays fixable**                              | Excludes following "disk/sector/loader/sequence/process/time/options/record/partition/menu/order/camera".                                                                                                      |
+| `crash` → `fail`                                      | **Moved to detection-only** (`az-state-failure-detect`)  | G:73 gives a hardware/software target split ("fail" vs. "stop responding") a single `swap` replacement can't express; also anchored against "crash dump/report/log/course/test/site".                          |
+| `lock up` → `fail`                                    | **Moved to detection-only** (`az-state-failure-detect`)  | Same hardware/software split (G:77).                                                                                                                                                                           |
+| `hangs`/`hang` → `stops responding`/`stop responding` | **Anchored, stays fixable**                              | Excludes "hang(s) on/up/around/out/together" (retain, end a call, loiter — unrelated phrasal verbs).                                                                                                           |
+| `roman` → `regular type`                              | **Anchored, stays fixable**                              | Excludes the civilization/proper-noun sense ("Roman numerals/Empire/alphabet/calendar/..."), a homograph collision of the `aka`-inside-`Akamai` shape.                                                         |
+| `italics`/`italicized` → `italic`                     | **Moved to detection-only** (`microsoft/italic-as-noun`) | The guide's own rule ("use only as an adjective, not a noun") makes a direct swap ungrammatical in exactly the position the avoid-term occupies — the same class as `actionable`.                              |
+| `blade` → `pane`                                      | **Anchored, stays fixable**                              | Excludes following "server(s)/enclosure/chassis/center(s)/centre(s)" (physical hardware sense).                                                                                                                |
+| `beta` → `preview`                                    | **Anchored, stays fixable**                              | Excludes following "distribution/function/coefficient/particle/blocker/decay" (statistical/physics/medical senses).                                                                                            |
+| `visit` → `go to`                                     | **Anchored, stays fixable**                              | Excludes following "count(s)/duration/frequency/history/log/data" (analytics-metric noun sense).                                                                                                               |
+| `in addition` → `also`                                | **Anchored, stays fixable**                              | Excludes following "to" (the standard, grammatically necessary preposition phrase "in addition to X", distinct from the guide's stand-alone-adverb target).                                                    |
+| `print out` → `print`                                 | **Anchored, stays fixable**                              | Excludes following "of" (noun sense — "a print out of X" — distinct from the guide's verb-scoped rule).                                                                                                        |
 
 #### Step 5 — the "CONFIRMED unconditional" comment corrected
 
@@ -916,17 +916,17 @@ contradicted it; each was moved to a `*-detect` `pattern` sibling,
 - **Moved to detection-only:** `quit`/`deinstall`/`reinitialize`
   (`az-lifecycle-verbs-detect`; G:88 multi-target, G:156/H:52 "(cond.)"),
   `crash`/`lock up` (`az-state-failure-detect`; Step 4), `bottom
-  left`/`bottom right` (`az-direction-layout-detect`; G:106, the
+left`/`bottom right` (`az-direction-layout-detect`; G:106, the
   BottomLeft/BottomRight API-property carve-out), `thank you`
   (`az-geography-detect`; H:62), `hierarchical menu`/`secondary
-  menu`/`running head`/`running foot` (`az-ui-nouns-detect`; G:146/H:93),
+menu`/`running head`/`running foot` (`az-ui-nouns-detect`; G:146/H:93),
   `pound sign` (`az-abbreviations-names-detect`; H:115).
 - **`fix: false`:** `left-hand`/`right-hand` (new rule
   `microsoft/left-hand-right-hand`; G:108 marks these DETECT-ONLY outright
   — no replacement is stated on the live page for the modifier sense, so
   shipping one fixable was itself the defect).
 - **Already detection-only, no change needed:** `backbone`/`natural user
-  interface` (G:187/G:190) already ship as `pattern` in
+interface` (G:187/G:190) already ship as `pattern` in
   `microsoft/az-no-replacement`. `indices` is excluded entirely (see Step
   5's own TOO-RISKY note below), so its math-carve-out marker (G:168) never
   reached a shipped pair either.
@@ -941,38 +941,38 @@ instead of unconditionally.
    (16 rules pre-wave, more after Step 4/5 added new rules) now cites the
    real, live, term-specific page for one of its pairs (verified via
    `curl`, HTTP 200, for every one — see the table below). `microsoft/
-   mouse-over`'s slug carried a spurious "-and-"
+mouse-over`'s slug carried a spurious "-and-"
    (`mouse-and-mouse-interaction-terms`, 404) corrected to
    `mouse-mouse-interaction-terms` (200) — verifier G's own fetch log
    named the correct slug at G:200; the verifier never cited the broken
    form itself.
 
-   | Rule | New link slug |
-   |---|---|
-   | `spelling-hyphenation` | `e/email` |
-   | `az-case-only` | `i/internet-intranet-extranet` |
-   | `az-verb-able` | `b/blacklist` |
-   | `az-state-failure` | `h/hang` |
-   | `az-state-failure-detect` | `c/crash` |
-   | `az-lifecycle-verbs` | `b/boot` |
-   | `az-lifecycle-verbs-detect` | `q/quit` |
-   | `az-judgment-words` | `f/finalize` |
-   | `az-geography` | `f/far-east` |
-   | `az-geography-detect` | `t/thanks-thank-you` |
-   | `az-direction-layout` | `f/far-left-far-right` |
-   | `az-direction-layout-detect` | `b/bottom-left-bottom-right` |
-   | `left-hand-right-hand` | `l/left-leftmost-left-hand` |
-   | `az-ui-nouns` | `b/blade` |
-   | `az-ui-nouns-detect` | `h/hierarchical-menu` |
-   | `az-typography` | `r/roman` |
-   | `az-filesystem` | `c/child-folder` |
-   | `az-grammar-usage` | `a/as-well-as` |
-   | `az-abbreviations-names` | `h/hexadecimal` |
-   | `az-abbreviations-names-detect` | `n/number-sign` |
-   | `az-navigation` | `v/visit` |
-   | `bookmark-favorite` | `b/bookmark` |
-   | `az-no-replacement` | `b/black-box` |
-   | `az-real-replacements` | `f/friendly-name` |
+   | Rule                            | New link slug                  |
+   | ------------------------------- | ------------------------------ |
+   | `spelling-hyphenation`          | `e/email`                      |
+   | `az-case-only`                  | `i/internet-intranet-extranet` |
+   | `az-verb-able`                  | `b/blacklist`                  |
+   | `az-state-failure`              | `h/hang`                       |
+   | `az-state-failure-detect`       | `c/crash`                      |
+   | `az-lifecycle-verbs`            | `b/boot`                       |
+   | `az-lifecycle-verbs-detect`     | `q/quit`                       |
+   | `az-judgment-words`             | `f/finalize`                   |
+   | `az-geography`                  | `f/far-east`                   |
+   | `az-geography-detect`           | `t/thanks-thank-you`           |
+   | `az-direction-layout`           | `f/far-left-far-right`         |
+   | `az-direction-layout-detect`    | `b/bottom-left-bottom-right`   |
+   | `left-hand-right-hand`          | `l/left-leftmost-left-hand`    |
+   | `az-ui-nouns`                   | `b/blade`                      |
+   | `az-ui-nouns-detect`            | `h/hierarchical-menu`          |
+   | `az-typography`                 | `r/roman`                      |
+   | `az-filesystem`                 | `c/child-folder`               |
+   | `az-grammar-usage`              | `a/as-well-as`                 |
+   | `az-abbreviations-names`        | `h/hexadecimal`                |
+   | `az-abbreviations-names-detect` | `n/number-sign`                |
+   | `az-navigation`                 | `v/visit`                      |
+   | `bookmark-favorite`             | `b/bookmark`                   |
+   | `az-no-replacement`             | `b/black-box`                  |
+   | `az-real-replacements`          | `f/friendly-name`              |
 
    All 60 distinct URLs this preset's rules now cite were verified live
    (`curl -A "Mozilla/5.0..."`) at HTTP 200 as of 2026-07-30.
@@ -1016,13 +1016,13 @@ polysemous for any anchor to meaningfully narrow).
 
 - `case-preserve.ts`'s "KNOWN EDGE" note claimed no shipped pair hit the
   hyphen/dot-joined-replacement shouting gap — false; `spelling-
-  hyphenation`'s `ecommerce`→`e-commerce`/`elearning`→`e-learning`/
+hyphenation`'s `ecommerce`→`e-commerce`/`elearning`→`e-learning`/
   `ebook`→`e-book` all do (comment corrected, no behavior change).
 - `az-case-only`'s claim that all 17 pairs would "silently no-op" was
   verified against the live `applyMatchCase` function directly (not
   re-reasoned by eye): true for only 7 (`Internet`, `Intranet`,
   `Extranet`, `Euro`, `WWW`, `Registry`, `Spam`). The other 10 (`Big
-  Data`, `Dark Mode`, `darkmode`, `Devops`, `devops`, `bluetooth`,
+Data`, `Dark Mode`, `darkmode`, `Devops`, `devops`, `bluetooth`,
   `boolean`, `Javascript`, `javascript`, `World Wide Web`) now ship
   fixable in a new rule, `microsoft/az-case-fixable`, instead of
   reporting forever for no reason.
@@ -1053,18 +1053,18 @@ one rule family nobody had named (`az-grammar-usage`) and found two more
 corrupting pairs — both marked plain `CONFIRMED` by a verifier, with the
 correct quote attached:
 
-- `as well as` → `and`: a/as-well-as says *"Don't use as a synonym for
-  and"* — a caution against treating the two as interchangeable, not an
+- `as well as` → `and`: a/as-well-as says _"Don't use as a synonym for
+  and"_ — a caution against treating the two as interchangeable, not an
   instruction to replace the text.
 - `or greater`/`or higher`/`or lower` → `or later`/`or earlier`:
-  g/greater-better and h/higher scope this to *"identifying multiple
-  versions of programs or apps"* — a version-number rule, not a
+  g/greater-better and h/higher scope this to _"identifying multiple
+  versions of programs or apps"_ — a version-number rule, not a
   general-magnitude rule.
 
 #### The root cause, restated precisely
 
-A `CONFIRMED` verdict means *the live page genuinely discusses this term*.
-It does **not** mean *a blind textual substitution of that term is safe*.
+A `CONFIRMED` verdict means _the live page genuinely discusses this term_.
+It does **not** mean _a blind textual substitution of that term is safe_.
 Those are two different properties, and this task's verification passes
 (E/F/G/H/accessibility) only ever checked the first one. Fixing the two
 named pairs without addressing the conflation would have left the rest of
@@ -1085,18 +1085,18 @@ all HTTP 200.
 
 **10 pairs reclassified** from fixable to detection-only or `fix: false`:
 
-| Pair | Rule (before → after) | Guidance shape (live quote) | Why unsafe as a blind swap |
-|---|---|---|---|
-| `as well as` → `and` | `az-grammar-usage` → `az-grammar-usage-detect` (`pattern`) | "Don't use **as a synonym for** and." | Caution against conflation, not an instruction to replace — "As well as being fast, the API is reliable." → "And being fast, the API is reliable." is not grammatical; "and" can't head a sentence the way a subordinating phrase can. |
-| `or greater` → `or later` | `az-grammar-usage` → `az-grammar-usage-detect` | "Don't use greater or better to mean or later **when identifying multiple versions of programs or apps**." | Scoped to version numbers; "a score of 80 or greater" → "a score of 80 or later" is nonsensical for a magnitude. |
-| `or higher` → `or later` | `az-grammar-usage` → `az-grammar-usage-detect` | Same page, PLUS: "It's OK to use higher to refer to **display resolution**. Don't use higher to refer to **processor speed**. Use **faster** instead." | Scoped to version numbers AND multi-target (resolution: unchanged; processor speed: "faster"; version: "later") — no single literal replacement covers all three senses the live page itself names. |
-| `or lower` → `or earlier` | `az-grammar-usage` → `az-grammar-usage-detect` | "Don't use **to indicate product version numbers**. Use earlier instead." | Same version-number scoping; "lower" is an ordinary magnitude word (price, temperature, priority) in every other context. |
-| `leverage`/`leveraging`/`leveraged` → `use`/`using`/`used` | `microsoft/leverage`, `fix: false` | "Don't use **as a verb** to mean take advantage of. Use take advantage of, use, or **another more appropriate word or phrase**." | Verb-sense-scoped AND multiple-alternatives. "Leverage"/"leveraged" are also common, correct nouns/adjectives this page never addresses ("financial leverage", "a highly leveraged company", "a leveraged buyout") — unlike `impact-verb`, there's no small enumerable set of following objects to anchor on (leverage takes almost any direct object), so detection-only is the fallback, not an abandoned first attempt. |
-| `glyph` → `symbol` | `microsoft/glyph`, `fix: false` | "Don't use to refer generically to a graphic... on a button, on an icon, or in a message box. Use symbol instead. **It's OK to use glyph in a technical discussion of fonts and characters.**" | Context-scoped exactly like the developer-audience carve-outs already excluded for `header`/`disk`/`directory`/`context menu` — font/Unicode documentation (plausible in Redocly's own docs) uses "glyph" as a precise technical term this page's objection doesn't cover, and no anchor tells "technical discussion of fonts" apart from the generic-icon sense. |
-| `de facto` → `in practice` | `no-latin-abbreviations` → `no-latin-abbreviations-detect` (`pattern`) | use-us-spelling's ONLY sentence: "Avoid non-English words or phrases, **such as** de facto or ad hoc." | No replacement given at all — an example list of avoid-terms, not a "use Y instead of X" table row (unlike `e.g./i.e./viz./ergo`, which come from this same page's own table). "in practice" was the author's own reasonable-sounding guess. |
-| `ad hoc` → `as needed` | `no-latin-abbreviations` → `no-latin-abbreviations-detect` | Same sentence as `de facto`. | Same — no replacement stated. |
-| `vis-a-vis` → `compared with` | `no-latin-abbreviations` → `no-latin-abbreviations-detect` | **Not named on any fetched page at all** — confirmed via a live 404 on `v/vis-a-vis`. | Not just "no replacement given" — the term itself isn't sourced anywhere; "compared with" is entirely the author's own invention. |
-| `visit` → `go to` | `az-navigation` → `az-navigation-detect` (`pattern`) | "use go to in **most cases**... It's OK to use visit... if you're using a tone that's meant to imply [a suggestion, or browsing]." Worked example: "**Visit** the product website to learn about offerings..." | The live page's own approved example uses "visit" — a blind fix would rewrite Microsoft's own sanctioned usage. Also a second, independent hazard the wave-B anchor never covered: "visit" preceded by an article ("Schedule a visit", "during my visit") is a common noun sense the noun-**compound** anchor (which only excluded specific FOLLOWING words) never excluded — "Schedule a go to with the doctor" is not English. |
+| Pair                                                       | Rule (before → after)                                                  | Guidance shape (live quote)                                                                                                                                                                                    | Why unsafe as a blind swap                                                                                                                                                                                                                                                                                                                                                                                                       |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `as well as` → `and`                                       | `az-grammar-usage` → `az-grammar-usage-detect` (`pattern`)             | "Don't use **as a synonym for** and."                                                                                                                                                                          | Caution against conflation, not an instruction to replace — "As well as being fast, the API is reliable." → "And being fast, the API is reliable." is not grammatical; "and" can't head a sentence the way a subordinating phrase can.                                                                                                                                                                                           |
+| `or greater` → `or later`                                  | `az-grammar-usage` → `az-grammar-usage-detect`                         | "Don't use greater or better to mean or later **when identifying multiple versions of programs or apps**."                                                                                                     | Scoped to version numbers; "a score of 80 or greater" → "a score of 80 or later" is nonsensical for a magnitude.                                                                                                                                                                                                                                                                                                                 |
+| `or higher` → `or later`                                   | `az-grammar-usage` → `az-grammar-usage-detect`                         | Same page, PLUS: "It's OK to use higher to refer to **display resolution**. Don't use higher to refer to **processor speed**. Use **faster** instead."                                                         | Scoped to version numbers AND multi-target (resolution: unchanged; processor speed: "faster"; version: "later") — no single literal replacement covers all three senses the live page itself names.                                                                                                                                                                                                                              |
+| `or lower` → `or earlier`                                  | `az-grammar-usage` → `az-grammar-usage-detect`                         | "Don't use **to indicate product version numbers**. Use earlier instead."                                                                                                                                      | Same version-number scoping; "lower" is an ordinary magnitude word (price, temperature, priority) in every other context.                                                                                                                                                                                                                                                                                                        |
+| `leverage`/`leveraging`/`leveraged` → `use`/`using`/`used` | `microsoft/leverage`, `fix: false`                                     | "Don't use **as a verb** to mean take advantage of. Use take advantage of, use, or **another more appropriate word or phrase**."                                                                               | Verb-sense-scoped AND multiple-alternatives. "Leverage"/"leveraged" are also common, correct nouns/adjectives this page never addresses ("financial leverage", "a highly leveraged company", "a leveraged buyout") — unlike `impact-verb`, there's no small enumerable set of following objects to anchor on (leverage takes almost any direct object), so detection-only is the fallback, not an abandoned first attempt.       |
+| `glyph` → `symbol`                                         | `microsoft/glyph`, `fix: false`                                        | "Don't use to refer generically to a graphic... on a button, on an icon, or in a message box. Use symbol instead. **It's OK to use glyph in a technical discussion of fonts and characters.**"                 | Context-scoped exactly like the developer-audience carve-outs already excluded for `header`/`disk`/`directory`/`context menu` — font/Unicode documentation (plausible in Redocly's own docs) uses "glyph" as a precise technical term this page's objection doesn't cover, and no anchor tells "technical discussion of fonts" apart from the generic-icon sense.                                                                |
+| `de facto` → `in practice`                                 | `no-latin-abbreviations` → `no-latin-abbreviations-detect` (`pattern`) | use-us-spelling's ONLY sentence: "Avoid non-English words or phrases, **such as** de facto or ad hoc."                                                                                                         | No replacement given at all — an example list of avoid-terms, not a "use Y instead of X" table row (unlike `e.g./i.e./viz./ergo`, which come from this same page's own table). "in practice" was the author's own reasonable-sounding guess.                                                                                                                                                                                     |
+| `ad hoc` → `as needed`                                     | `no-latin-abbreviations` → `no-latin-abbreviations-detect`             | Same sentence as `de facto`.                                                                                                                                                                                   | Same — no replacement stated.                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `vis-a-vis` → `compared with`                              | `no-latin-abbreviations` → `no-latin-abbreviations-detect`             | **Not named on any fetched page at all** — confirmed via a live 404 on `v/vis-a-vis`.                                                                                                                          | Not just "no replacement given" — the term itself isn't sourced anywhere; "compared with" is entirely the author's own invention.                                                                                                                                                                                                                                                                                                |
+| `visit` → `go to`                                          | `az-navigation` → `az-navigation-detect` (`pattern`)                   | "use go to in **most cases**... It's OK to use visit... if you're using a tone that's meant to imply [a suggestion, or browsing]." Worked example: "**Visit** the product website to learn about offerings..." | The live page's own approved example uses "visit" — a blind fix would rewrite Microsoft's own sanctioned usage. Also a second, independent hazard the wave-B anchor never covered: "visit" preceded by an article ("Schedule a visit", "during my visit") is a common noun sense the noun-**compound** anchor (which only excluded specific FOLLOWING words) never excluded — "Schedule a go to with the doctor" is not English. |
 
 `hot link` (same `az-navigation` rule) and `e.g./i.e./viz./ergo` (same
 `no-latin-abbreviations` rule) were audited alongside their reclassified
@@ -1110,11 +1110,11 @@ real but incomplete — the guidance shape was correctly identified as
 sense-scoped, but the exclusion list didn't cover every common noun/idiom
 sense:
 
-| Pair | Rule | Gap found | Fix |
-|---|---|---|---|
-| `hang`/`hangs` → `stop(s) responding` | `az-state-failure` | Exclusion list (`on/up/around/out/together`) missed "get the hang **of** it" (a knack, not a system), "hang **in** there"/"hang **tight**"/"hang **loose**"/"hang **fire**" (encouragement/waiting idioms), and the literal suspension sense ("hangs **from** the ceiling"/"hangs **over** the door"). | Added `of/in/tight/loose/fire/from/over` to the exclusion list. Not exhaustive — "hang" is as broad a word as `crash`/`lock up`, which were moved to detection-only in wave B for the identical breadth reason — but this closes the specific gap a plausible Redocly onboarding sentence ("Once you get the hang of the API...") would have hit. |
-| `print out` → `print` | `az-real-replacements` | The noun-compound anchor only excluded "print out **of** X" — "Keep the print out safe"/"Attach the print out to the ticket" (a determiner-preceded noun, no "of" following) still corrupted to "Keep the print safe"/"Attach the print to the ticket" (register shift toward "print" = photograph). | Added a negative lookbehind excluding a preceding determiner/possessive (`a/an/the/this/that/your/my/its/his/her/their/our`) — the verb sense is never preceded by a determiner directly. |
-| `click`/`clicks` → `select(s)` | `no-click` | The live page's ban is verb-scoped ("Avoid this **verb**"); the anchor excluded hyphen-joined compounds and letter-adjacent compounds (`double-click`, `clickstream`) but not the ordinary noun sense ("click count", "clicks per session") — plausible in analytics/UI-event documentation, exactly Redocly's domain. | Added a follow-word exclusion for noun-compound risk (`count(s)/rate(s)/event(s)/tracking/data/metrics/history/id(s)/per`). Residual, accepted risk (not anchored): the live page's own carve-out "OK to use click when you need to describe mouse actions specifically" isn't mechanically detectable — same class as `hex`'s mechanical-fastener sense, low practical likelihood in Redocly's API-documentation domain. |
+| Pair                                  | Rule                   | Gap found                                                                                                                                                                                                                                                                                                              | Fix                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| ------------------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `hang`/`hangs` → `stop(s) responding` | `az-state-failure`     | Exclusion list (`on/up/around/out/together`) missed "get the hang **of** it" (a knack, not a system), "hang **in** there"/"hang **tight**"/"hang **loose**"/"hang **fire**" (encouragement/waiting idioms), and the literal suspension sense ("hangs **from** the ceiling"/"hangs **over** the door").                 | Added `of/in/tight/loose/fire/from/over` to the exclusion list. Not exhaustive — "hang" is as broad a word as `crash`/`lock up`, which were moved to detection-only in wave B for the identical breadth reason — but this closes the specific gap a plausible Redocly onboarding sentence ("Once you get the hang of the API...") would have hit.                                                                         |
+| `print out` → `print`                 | `az-real-replacements` | The noun-compound anchor only excluded "print out **of** X" — "Keep the print out safe"/"Attach the print out to the ticket" (a determiner-preceded noun, no "of" following) still corrupted to "Keep the print safe"/"Attach the print to the ticket" (register shift toward "print" = photograph).                   | Added a negative lookbehind excluding a preceding determiner/possessive (`a/an/the/this/that/your/my/its/his/her/their/our`) — the verb sense is never preceded by a determiner directly.                                                                                                                                                                                                                                 |
+| `click`/`clicks` → `select(s)`        | `no-click`             | The live page's ban is verb-scoped ("Avoid this **verb**"); the anchor excluded hyphen-joined compounds and letter-adjacent compounds (`double-click`, `clickstream`) but not the ordinary noun sense ("click count", "clicks per session") — plausible in analytics/UI-event documentation, exactly Redocly's domain. | Added a follow-word exclusion for noun-compound risk (`count(s)/rate(s)/event(s)/tracking/data/metrics/history/id(s)/per`). Residual, accepted risk (not anchored): the live page's own carve-out "OK to use click when you need to describe mouse actions specifically" isn't mechanically detectable — same class as `hex`'s mechanical-fastener sense, low practical likelihood in Redocly's API-documentation domain. |
 
 #### Bug fix found during the audit (not a substitution-safety issue — a detection bug)
 
@@ -1242,7 +1242,7 @@ wrong under `--fix` twice:
    corruption strings above pass axis 1 (each guide page states a plain
    "use Y instead of X" rule) and fail on axis 2 — `DMZ` is also the
    Korean border zone; `the ask` is also the bid/ask market term; `home
-   directory` always means the Unix `$HOME` sense in the corrupted
+directory` always means the Unix `$HOME` sense in the corrupted
    sentence, and the guide's "root directory" target is a genuinely
    different concept (the filesystem's `/`, not a per-user directory);
    `unmark` collides with no listed acceptable alternative for non-
@@ -1252,7 +1252,7 @@ wrong under `--fix` twice:
 3. **The posture**: auto-fix is retained **only** where a replacement
    cannot be wrong — the same word, normalized (spelling, hyphenation,
    casing, or a non-standard written form of the identical word). A pair
-   that substitutes a *different* word or phrase — even one that always
+   that substitutes a _different_ word or phrase — even one that always
    looks safe, like `alright` → `OK` — moves to detection-only, because
    "this one looks safe" is exactly the per-pair judgement call that
    produced three rounds of misses. Mechanical classification, not
@@ -1267,12 +1267,12 @@ is a whole-RULE flag, not per-pair, so a mixed bundle has to split). The
 16 rules that remain fixable are exhaustively enumerated with before/after
 fix output in the fix-posture report; four representative examples:
 
-| Rule | Pair | Why it stays fixable |
-|---|---|---|
-| `microsoft/us-spelling` | `centre` → `center` | Spelling variant of the identical word (the brief's own textbook example). |
-| `microsoft/spelling-hyphenation` | `e-mail` → `email` | Hyphenation of the identical word. |
-| `microsoft/az-case-fixable` | `javascript` → `JavaScript` | Casing of the identical token; empirically re-verified against `applyMatchCase` this wave (case-sensitive matching means an ALL-CAPS input like `JAVASCRIPT` can never reach these keys in the first place, so the ALL-CAPS-shout no-op class `az-case-only` exists to avoid doesn't recur here). |
-| `microsoft/az-grammar-usage` | `broadcasted` → `broadcast` | Non-standard inflection of the identical word (the guide's own irregular past tense), the same class as "alot" → "a lot". |
+| Rule                             | Pair                        | Why it stays fixable                                                                                                                                                                                                                                                                              |
+| -------------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `microsoft/us-spelling`          | `centre` → `center`         | Spelling variant of the identical word (the brief's own textbook example).                                                                                                                                                                                                                        |
+| `microsoft/spelling-hyphenation` | `e-mail` → `email`          | Hyphenation of the identical word.                                                                                                                                                                                                                                                                |
+| `microsoft/az-case-fixable`      | `javascript` → `JavaScript` | Casing of the identical token; empirically re-verified against `applyMatchCase` this wave (case-sensitive matching means an ALL-CAPS input like `JAVASCRIPT` can never reach these keys in the first place, so the ALL-CAPS-shout no-op class `az-case-only` exists to avoid doesn't recur here). |
+| `microsoft/az-grammar-usage`     | `broadcasted` → `broadcast` | Non-standard inflection of the identical word (the guide's own irregular past tense), the same class as "alot" → "a lot".                                                                                                                                                                         |
 
 Two rules flipped for a reason found DURING this wave, not named in the
 brief:
@@ -1288,7 +1288,7 @@ brief:
   each has to be checked against the actual function, not just the shape
   of the rule.
 - **`MSFT` → `Microsoft` (`az-abbreviations-names`) moved to detection-only
-  for a fix-*mechanism* defect, not a word-choice one.** `MSFT` is
+  for a fix-_mechanism_ defect, not a word-choice one.** `MSFT` is
   virtually always written all-caps (it's a stock ticker); with
   `ignoreCase: true`, `applyMatchCase`'s ALL-CAPS branch shouts a
   single-word replacement, so the "fix" would produce `"MICROSOFT"` (wrong
@@ -1399,12 +1399,12 @@ this preset, plus 5 `consistency` pairs left untouched — 118 total; the
 parallel sweep in `recheck/google` is documented in that preset's own
 PROVENANCE.md) was checked against question 3. This preset's flips:
 
-| Rule | Pair(s) flipped | Real proper noun that collides |
-|---|---|---|
-| `microsoft/usa-abbreviation` | `USA`/`U.S.A.`/`U.S.` -> `US` (all 3) | "USA Gymnastics" (US national governing body), "U.S. Bank" (top-10 US bank), "U.S.A. Track and Field" (national governing body), "U.S. Steel" — named brief case. |
-| `microsoft/us-spelling` | `centre`/`centres` -> `center`/`centers` | "Bell Centre" (Montreal Canadiens' arena, official English spelling) and "Centre County, Pennsylvania" (a real US county whose OWN official name keeps the British "re"). |
-| `microsoft/us-spelling` | `catalogue`/`catalogues` -> `catalog`/`catalogs` | "Catalogue of Life" (a real, commonly-cited global species database whose own name is spelled with the British "ue"). |
-| `microsoft/az-case-fixable` | `boolean` -> `Boolean` | Not proper-noun (question 2, found during this sweep): lowercase `boolean` is the REQUIRED spelling of the OpenAPI/JSON Schema type name (`"type": "boolean"`) — exactly Redocly's own domain — and auto-capitalizing it would corrupt extremely common, completely correct schema prose. |
+| Rule                         | Pair(s) flipped                                  | Real proper noun that collides                                                                                                                                                                                                                                                            |
+| ---------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `microsoft/usa-abbreviation` | `USA`/`U.S.A.`/`U.S.` -> `US` (all 3)            | "USA Gymnastics" (US national governing body), "U.S. Bank" (top-10 US bank), "U.S.A. Track and Field" (national governing body), "U.S. Steel" — named brief case.                                                                                                                         |
+| `microsoft/us-spelling`      | `centre`/`centres` -> `center`/`centers`         | "Bell Centre" (Montreal Canadiens' arena, official English spelling) and "Centre County, Pennsylvania" (a real US county whose OWN official name keeps the British "re").                                                                                                                 |
+| `microsoft/us-spelling`      | `catalogue`/`catalogues` -> `catalog`/`catalogs` | "Catalogue of Life" (a real, commonly-cited global species database whose own name is spelled with the British "ue").                                                                                                                                                                     |
+| `microsoft/az-case-fixable`  | `boolean` -> `Boolean`                           | Not proper-noun (question 2, found during this sweep): lowercase `boolean` is the REQUIRED spelling of the OpenAPI/JSON Schema type name (`"type": "boolean"`) — exactly Redocly's own domain — and auto-capitalizing it would corrupt extremely common, completely correct schema prose. |
 
 **4 pairs swept out of the 113 live `swap` pairs, all moved to a
 detection-only sibling rather than anchored** — `microsoft/us-spelling`
@@ -1434,6 +1434,7 @@ round of anchor-then-leak was not worth it for pairs this marginal.
 `fix: false` was preferred over an anchor for every pair this wave found.
 
 #### `aka` was misclassified, not newly found unsafe (recorded here for
+
 cross-reference; the pair itself lives in `recheck/google`)
 
 Expanding an abbreviation into a phrase is a substitution, not a
@@ -1491,7 +1492,7 @@ RISING hit rate after three rounds of narrowing, spanning every category
 the three axes above treated as clean:
 
 - **Spelling**, believed the safest category of all: Hemingway's real,
-  correctly spelled published title *A Moveable Feast* is corrected to "A
+  correctly spelled published title _A Moveable Feast_ is corrected to "A
   Movable Feast" by this preset's own `microsoft/az-grammar-usage`'s
   `moveable` → `movable` pair — a genuine same-word normalization by every
   axis above (axis 1 passes, axis 2 finds no unrelated sense, axis 3 finds
@@ -1513,10 +1514,8 @@ the three axes above treated as clean:
 
 Full round-5 acceptance evidence (these sentences and more, run through
 `--fix` twice and confirmed byte-identical) lives in
-`src/config/__tests__/preset-detection-only-acceptance.test.ts`, plus the
-per-preset regression suites in `preset-microsoft.test.ts` and
-`preset-google-fix-wave-c.test.ts` (both rewritten by this change to assert
-"unchanged" where they used to assert a real rewrite). The `consistency`
+`src/config/__tests__/presets.test.ts` (the "detection-only" contract), plus the
+per-preset suites in `preset-microsoft.test.ts` and `preset-google.test.ts`. The `consistency`
 engine bug this same change fixed — `it's`/`it is` collapsing into one
 meaning via first-seen-wins, live since Phase 1 and reproduced exactly by
 this preset's `microsoft/contraction-consistency` rule with
@@ -1528,9 +1527,9 @@ preset.
 
 #### The conclusion this decision rests on
 
-A rule's *category* — spelling, hyphenation, casing, word-choice — does not
-predict fix-safety at this scale. A style guide states *intent* ("use X to
-mean Y"); a `swap`/`consistency`/`pattern` rule matches *tokens* (literal
+A rule's _category_ — spelling, hyphenation, casing, word-choice — does not
+predict fix-safety at this scale. A style guide states _intent_ ("use X to
+mean Y"); a `swap`/`consistency`/`pattern` rule matches _tokens_ (literal
 text, regardless of the grammatical role or referent that text has in a
 given sentence). That gap is not closable by inventing a fourth, fifth, or
 sixth axis: axis 1 (guidance-shape) closed the space of pairs where the