diff --git a/.claude/skills/microsoft-writing-style-guide/LICENSE b/.claude/skills/microsoft-writing-style-guide/LICENSE
new file mode 100644
index 000000000..6d0b3e7ba
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 msbrettorg
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/.claude/skills/microsoft-writing-style-guide/LICENSE-CONTENT b/.claude/skills/microsoft-writing-style-guide/LICENSE-CONTENT
new file mode 100644
index 000000000..e056e7c3e
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/LICENSE-CONTENT
@@ -0,0 +1,395 @@
+Attribution 4.0 International
+
+=======================================================================
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and
+does not provide legal services or legal advice. Distribution of
+Creative Commons public licenses does not create a lawyer-client or
+other relationship. Creative Commons makes its licenses and related
+information available on an "as-is" basis. Creative Commons gives no
+warranties regarding its licenses, any material licensed under their
+terms and conditions, or any related information. Creative Commons
+disclaims all liability for damages resulting from their use to the
+fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and
+conditions that creators and other rights holders may use to share
+original works of authorship and other material subject to copyright
+and certain other rights specified in the public license below. The
+following considerations are for informational purposes only, are not
+exhaustive, and do not form part of our licenses.
+
+     Considerations for licensors: Our public licenses are
+     intended for use by those authorized to give the public
+     permission to use material in ways otherwise restricted by
+     copyright and certain other rights. Our licenses are
+     irrevocable. Licensors should read and understand the terms
+     and conditions of the license they choose before applying it.
+     Licensors should also secure all rights necessary before
+     applying our licenses so that the public can reuse the
+     material as expected. Licensors should clearly mark any
+     material not subject to the license. This includes other CC-
+     licensed material, or material used under an exception or
+     limitation to copyright. More considerations for licensors:
+	wiki.creativecommons.org/Considerations_for_licensors
+
+     Considerations for the public: By using one of our public
+     licenses, a licensor grants the public permission to use the
+     licensed material under specified terms and conditions. If
+     the licensor's permission is not necessary for any reason--for
+     example, because of any applicable exception or limitation to
+     copyright--then that use is not regulated by the license. Our
+     licenses grant only permissions under copyright and certain
+     other rights that a licensor has authority to grant. Use of
+     the licensed material may still be restricted for other
+     reasons, including because others have copyright or other
+     rights in the material. A licensor may make special requests,
+     such as asking that all changes be marked or described.
+     Although not required by our licenses, you are encouraged to
+     respect those requests where reasonable. More_considerations
+     for the public: 
+	wiki.creativecommons.org/Considerations_for_licensees
+
+=======================================================================
+
+Creative Commons Attribution 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree
+to be bound by the terms and conditions of this Creative Commons
+Attribution 4.0 International Public License ("Public License"). To the
+extent this Public License may be interpreted as a contract, You are
+granted the Licensed Rights in consideration of Your acceptance of
+these terms and conditions, and the Licensor grants You such rights in
+consideration of benefits the Licensor receives from making the
+Licensed Material available under these terms and conditions.
+
+
+Section 1 -- Definitions.
+
+  a. Adapted Material means material subject to Copyright and Similar
+     Rights that is derived from or based upon the Licensed Material
+     and in which the Licensed Material is translated, altered,
+     arranged, transformed, or otherwise modified in a manner requiring
+     permission under the Copyright and Similar Rights held by the
+     Licensor. For purposes of this Public License, where the Licensed
+     Material is a musical work, performance, or sound recording,
+     Adapted Material is always produced where the Licensed Material is
+     synched in timed relation with a moving image.
+
+  b. Adapter's License means the license You apply to Your Copyright
+     and Similar Rights in Your contributions to Adapted Material in
+     accordance with the terms and conditions of this Public License.
+
+  c. Copyright and Similar Rights means copyright and/or similar rights
+     closely related to copyright including, without limitation,
+     performance, broadcast, sound recording, and Sui Generis Database
+     Rights, without regard to how the rights are labeled or
+     categorized. For purposes of this Public License, the rights
+     specified in Section 2(b)(1)-(2) are not Copyright and Similar
+     Rights.
+
+  d. Effective Technological Measures means those measures that, in the
+     absence of proper authority, may not be circumvented under laws
+     fulfilling obligations under Article 11 of the WIPO Copyright
+     Treaty adopted on December 20, 1996, and/or similar international
+     agreements.
+
+  e. Exceptions and Limitations means fair use, fair dealing, and/or
+     any other exception or limitation to Copyright and Similar Rights
+     that applies to Your use of the Licensed Material.
+
+  f. Licensed Material means the artistic or literary work, database,
+     or other material to which the Licensor applied this Public
+     License.
+
+  g. Licensed Rights means the rights granted to You subject to the
+     terms and conditions of this Public License, which are limited to
+     all Copyright and Similar Rights that apply to Your use of the
+     Licensed Material and that the Licensor has authority to license.
+
+  h. Licensor means the individual(s) or entity(ies) granting rights
+     under this Public License.
+
+  i. Share means to provide material to the public by any means or
+     process that requires permission under the Licensed Rights, such
+     as reproduction, public display, public performance, distribution,
+     dissemination, communication, or importation, and to make material
+     available to the public including in ways that members of the
+     public may access the material from a place and at a time
+     individually chosen by them.
+
+  j. Sui Generis Database Rights means rights other than copyright
+     resulting from Directive 96/9/EC of the European Parliament and of
+     the Council of 11 March 1996 on the legal protection of databases,
+     as amended and/or succeeded, as well as other essentially
+     equivalent rights anywhere in the world.
+
+  k. You means the individual or entity exercising the Licensed Rights
+     under this Public License. Your has a corresponding meaning.
+
+
+Section 2 -- Scope.
+
+  a. License grant.
+
+       1. Subject to the terms and conditions of this Public License,
+          the Licensor hereby grants You a worldwide, royalty-free,
+          non-sublicensable, non-exclusive, irrevocable license to
+          exercise the Licensed Rights in the Licensed Material to:
+
+            a. reproduce and Share the Licensed Material, in whole or
+               in part; and
+
+            b. produce, reproduce, and Share Adapted Material.
+
+       2. Exceptions and Limitations. For the avoidance of doubt, where
+          Exceptions and Limitations apply to Your use, this Public
+          License does not apply, and You do not need to comply with
+          its terms and conditions.
+
+       3. Term. The term of this Public License is specified in Section
+          6(a).
+
+       4. Media and formats; technical modifications allowed. The
+          Licensor authorizes You to exercise the Licensed Rights in
+          all media and formats whether now known or hereafter created,
+          and to make technical modifications necessary to do so. The
+          Licensor waives and/or agrees not to assert any right or
+          authority to forbid You from making technical modifications
+          necessary to exercise the Licensed Rights, including
+          technical modifications necessary to circumvent Effective
+          Technological Measures. For purposes of this Public License,
+          simply making modifications authorized by this Section 2(a)
+          (4) never produces Adapted Material.
+
+       5. Downstream recipients.
+
+            a. Offer from the Licensor -- Licensed Material. Every
+               recipient of the Licensed Material automatically
+               receives an offer from the Licensor to exercise the
+               Licensed Rights under the terms and conditions of this
+               Public License.
+
+            b. No downstream restrictions. You may not offer or impose
+               any additional or different terms or conditions on, or
+               apply any Effective Technological Measures to, the
+               Licensed Material if doing so restricts exercise of the
+               Licensed Rights by any recipient of the Licensed
+               Material.
+
+       6. No endorsement. Nothing in this Public License constitutes or
+          may be construed as permission to assert or imply that You
+          are, or that Your use of the Licensed Material is, connected
+          with, or sponsored, endorsed, or granted official status by,
+          the Licensor or others designated to receive attribution as
+          provided in Section 3(a)(1)(A)(i).
+
+  b. Other rights.
+
+       1. Moral rights, such as the right of integrity, are not
+          licensed under this Public License, nor are publicity,
+          privacy, and/or other similar personality rights; however, to
+          the extent possible, the Licensor waives and/or agrees not to
+          assert any such rights held by the Licensor to the limited
+          extent necessary to allow You to exercise the Licensed
+          Rights, but not otherwise.
+
+       2. Patent and trademark rights are not licensed under this
+          Public License.
+
+       3. To the extent possible, the Licensor waives any right to
+          collect royalties from You for the exercise of the Licensed
+          Rights, whether directly or through a collecting society
+          under any voluntary or waivable statutory or compulsory
+          licensing scheme. In all other cases the Licensor expressly
+          reserves any right to collect such royalties.
+
+
+Section 3 -- License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the
+following conditions.
+
+  a. Attribution.
+
+       1. If You Share the Licensed Material (including in modified
+          form), You must:
+
+            a. retain the following if it is supplied by the Licensor
+               with the Licensed Material:
+
+                 i. identification of the creator(s) of the Licensed
+                    Material and any others designated to receive
+                    attribution, in any reasonable manner requested by
+                    the Licensor (including by pseudonym if
+                    designated);
+
+                ii. a copyright notice;
+
+               iii. a notice that refers to this Public License;
+
+                iv. a notice that refers to the disclaimer of
+                    warranties;
+
+                 v. a URI or hyperlink to the Licensed Material to the
+                    extent reasonably practicable;
+
+            b. indicate if You modified the Licensed Material and
+               retain an indication of any previous modifications; and
+
+            c. indicate the Licensed Material is licensed under this
+               Public License, and include the text of, or the URI or
+               hyperlink to, this Public License.
+
+       2. You may satisfy the conditions in Section 3(a)(1) in any
+          reasonable manner based on the medium, means, and context in
+          which You Share the Licensed Material. For example, it may be
+          reasonable to satisfy the conditions by providing a URI or
+          hyperlink to a resource that includes the required
+          information.
+
+       3. If requested by the Licensor, You must remove any of the
+          information required by Section 3(a)(1)(A) to the extent
+          reasonably practicable.
+
+       4. If You Share Adapted Material You produce, the Adapter's
+          License You apply must not prevent recipients of the Adapted
+          Material from complying with this Public License.
+
+
+Section 4 -- Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that
+apply to Your use of the Licensed Material:
+
+  a. for the avoidance of doubt, Section 2(a)(1) grants You the right
+     to extract, reuse, reproduce, and Share all or a substantial
+     portion of the contents of the database;
+
+  b. if You include all or a substantial portion of the database
+     contents in a database in which You have Sui Generis Database
+     Rights, then the database in which You have Sui Generis Database
+     Rights (but not its individual contents) is Adapted Material; and
+
+  c. You must comply with the conditions in Section 3(a) if You Share
+     all or a substantial portion of the contents of the database.
+
+For the avoidance of doubt, this Section 4 supplements and does not
+replace Your obligations under this Public License where the Licensed
+Rights include other Copyright and Similar Rights.
+
+
+Section 5 -- Disclaimer of Warranties and Limitation of Liability.
+
+  a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
+     EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
+     AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
+     ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
+     IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
+     WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
+     PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
+     ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
+     KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
+     ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
+
+  b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
+     TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
+     NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
+     INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
+     COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
+     USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
+     ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
+     DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
+     IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
+
+  c. The disclaimer of warranties and limitation of liability provided
+     above shall be interpreted in a manner that, to the extent
+     possible, most closely approximates an absolute disclaimer and
+     waiver of all liability.
+
+
+Section 6 -- Term and Termination.
+
+  a. This Public License applies for the term of the Copyright and
+     Similar Rights licensed here. However, if You fail to comply with
+     this Public License, then Your rights under this Public License
+     terminate automatically.
+
+  b. Where Your right to use the Licensed Material has terminated under
+     Section 6(a), it reinstates:
+
+       1. automatically as of the date the violation is cured, provided
+          it is cured within 30 days of Your discovery of the
+          violation; or
+
+       2. upon express reinstatement by the Licensor.
+
+     For the avoidance of doubt, this Section 6(b) does not affect any
+     right the Licensor may have to seek remedies for Your violations
+     of this Public License.
+
+  c. For the avoidance of doubt, the Licensor may also offer the
+     Licensed Material under separate terms or conditions or stop
+     distributing the Licensed Material at any time; however, doing so
+     will not terminate this Public License.
+
+  d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
+     License.
+
+
+Section 7 -- Other Terms and Conditions.
+
+  a. The Licensor shall not be bound by any additional or different
+     terms or conditions communicated by You unless expressly agreed.
+
+  b. Any arrangements, understandings, or agreements regarding the
+     Licensed Material not stated herein are separate from and
+     independent of the terms and conditions of this Public License.
+
+
+Section 8 -- Interpretation.
+
+  a. For the avoidance of doubt, this Public License does not, and
+     shall not be interpreted to, reduce, limit, restrict, or impose
+     conditions on any use of the Licensed Material that could lawfully
+     be made without permission under this Public License.
+
+  b. To the extent possible, if any provision of this Public License is
+     deemed unenforceable, it shall be automatically reformed to the
+     minimum extent necessary to make it enforceable. If the provision
+     cannot be reformed, it shall be severed from this Public License
+     without affecting the enforceability of the remaining terms and
+     conditions.
+
+  c. No term or condition of this Public License will be waived and no
+     failure to comply consented to unless expressly agreed to by the
+     Licensor.
+
+  d. Nothing in this Public License constitutes or may be interpreted
+     as a limitation upon, or waiver of, any privileges and immunities
+     that apply to the Licensor or You, including from the legal
+     processes of any jurisdiction or authority.
+
+
+=======================================================================
+
+Creative Commons is not a party to its public
+licenses. Notwithstanding, Creative Commons may elect to apply one of
+its public licenses to material it publishes and in those instances
+will be considered the “Licensor.” The text of the Creative Commons
+public licenses is dedicated to the public domain under the CC0 Public
+Domain Dedication. Except for the limited purpose of indicating that
+material is shared under a Creative Commons public license or as
+otherwise permitted by the Creative Commons policies published at
+creativecommons.org/policies, Creative Commons does not authorize the
+use of the trademark "Creative Commons" or any other trademark or logo
+of Creative Commons without its prior written consent including,
+without limitation, in connection with any unauthorized modifications
+to any of its public licenses or any other arrangements,
+understandings, or agreements concerning use of licensed material. For
+the avoidance of doubt, this paragraph does not form part of the
+public licenses.
+
+Creative Commons may be contacted at creativecommons.org.
\ No newline at end of file
diff --git a/.claude/skills/microsoft-writing-style-guide/NOTICE.md b/.claude/skills/microsoft-writing-style-guide/NOTICE.md
new file mode 100644
index 000000000..4377a3264
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/NOTICE.md
@@ -0,0 +1,20 @@
+# Notices and attribution
+
+This repository contains an unofficial community implementation of the
+Microsoft Writing Style Guide. It isn't endorsed by Microsoft or Anthropic.
+
+Microsoft is the source of the adapted Microsoft Writing Style Guide content:
+
+* Source: [MicrosoftDocs/microsoft-style-guide-pr](https://github.com/MicrosoftDocs/microsoft-style-guide-pr)
+* Pinned commit: [`c78a330b932812a342be2ebca0ec8bc3d01fbac2`](https://github.com/MicrosoftDocs/microsoft-style-guide-pr/commit/c78a330b932812a342be2ebca0ec8bc3d01fbac2)
+* Content license: [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/)
+
+The adapted content has been modified by consolidating pages, resolving
+include payloads, removing build frontmatter, and adding a term index,
+routing, a source manifest, evaluations, and validation.
+
+The full upstream content license is included in
+[`LICENSE-CONTENT`](LICENSE-CONTENT). The repository's MIT license applies
+only to original code, metadata, scripts, and other original contributions;
+Microsoft-derived reference content and adapted guide text remain under
+CC BY 4.0.
diff --git a/.claude/skills/microsoft-writing-style-guide/SKILL.md b/.claude/skills/microsoft-writing-style-guide/SKILL.md
new file mode 100755
index 000000000..fff91bb74
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/SKILL.md
@@ -0,0 +1,197 @@
+---
+description: Use when writing, rewriting, or reviewing Microsoft-branded or customer-facing content, or resolving Microsoft terminology. Covers voice, grammar, punctuation, capitalization, UI text, procedures, accessibility, bias-free and global-ready language, developer content, and the complete Microsoft A-Z word list.
+license: MIT AND CC-BY-4.0; see LICENSE, LICENSE-CONTENT, and NOTICE.md
+metadata:
+    github-path: plugins/microsoft-writing-style/skills/microsoft-writing-style-guide
+    github-pinned: d9227efa6c984c13260e3bf869f4b6132cfb3c19
+    github-ref: d9227efa6c984c13260e3bf869f4b6132cfb3c19
+    github-repo: https://github.com/msbrettorg/microsoft-writing-style
+    github-tree-sha: 73d4edd9337016a22a9918497b1ba377449894fb
+name: microsoft-writing-style-guide
+---
+# Microsoft Writing Style Guide
+
+## Purpose
+
+Apply the Microsoft Writing Style Guide to documentation, UI text, error
+messages, notifications, marketing copy, emails, slides, procedures, developer
+content, and conversational experiences.
+
+Microsoft voice is **warm and relaxed, crisp and clear, and ready to lend a
+hand**. Use bigger ideas and fewer words. Write with less head and more heart.
+
+This skill is a pinned, offline reference snapshot. See
+`references/source-manifest.md` for its authoritative source commit, coverage,
+and synchronization date.
+
+## When to use
+
+Use this skill to:
+
+* Draft content in Microsoft voice.
+* Rewrite content for clarity, brevity, accessibility, or global readiness.
+* Review content for Microsoft style violations.
+* Resolve a specific term, spelling, capitalization, or UI-language question.
+* Check procedures, developer documentation, bot content, or error messages.
+
+Don't use it to:
+
+* Rewrite legal or contractual text without legal review.
+* Change code identifiers, API syntax, commands, URLs, or literal UI text.
+* Replace a product's documented naming conventions.
+* Impose Microsoft voice on content for another brand.
+
+## Choose a mode
+
+| Mode | Use when | Result |
+|---|---|---|
+| **Term lookup** | The user asks which word, spelling, capitalization, or interaction verb to use | Preferred form, concise guidance, example, and source heading |
+| **Write** | The user needs new Microsoft-style content | Publication-ready content that follows the relevant rules |
+| **Rewrite** | The user provides content to improve | Revised content plus a brief list of material changes |
+| **Review** | The user asks for an audit, critique, or compliance check | Severity-ranked findings with exact fixes; no invented issues |
+
+If the user requests more than one mode, do them in this order: **review,
+rewrite, write**. Use term lookup whenever another mode encounters a
+questionable term.
+
+## Source precedence
+
+Use the most specific applicable guidance:
+
+1. Exact A-Z term entry.
+2. Relevant term collection.
+3. Topic guidance and content-type rules.
+4. Checklist.
+5. Quick-reference guidance in this file.
+
+Match literal UI, code, and product names when the task requires it. If two
+rules appear to conflict, prefer the more specific rule and explain the
+exception only when it affects the result.
+
+For a rule that may have changed after the synchronization date, verify the
+live [Microsoft Writing Style Guide](https://learn.microsoft.com/style-guide/)
+when live access is available. Otherwise, disclose the snapshot date if
+freshness is material to the answer.
+
+## Load only what you need
+
+Never load the full corpus by default.
+
+### Term lookup
+
+1. Search `references/term-index.tsv` for the canonical term.
+2. Load the routed A-Z file and read the complete matching `###` section.
+3. If the term isn't indexed, search the applicable term collection.
+4. Return the preferred form, rule, example, and reference heading.
+
+Example search:
+
+```bash
+rg -i '^plugin\t|^plug-in\t' references/term-index.tsv
+```
+
+### Topic routing
+
+| Content or question | Load |
+|---|---|
+| Fast pre-publication scan | `references/checklists.md` |
+| Grammar, voice, person, or sentence structure | `references/grammar-and-parts-of-speech.md`, `references/word-choice.md` |
+| Punctuation | `references/punctuation.md` |
+| Capitalization, acronyms, or numbers | `references/numbers-acronyms-capitalization.md` |
+| Typography or text treatment | `references/text-formatting.md` |
+| Accessibility or inclusive language | `references/accessibility-and-bias-free-communication.md` |
+| Localization or worldwide audiences | `references/global-communications.md` |
+| Content strategy, search, responsive content, or URLs | `references/content-planning-and-process.md` |
+| Headings, lists, tables, procedures, or UI interactions | `references/scannable-content-and-procedures.md` |
+| APIs, code examples, reference docs, bots, or virtual agents | `references/developer-and-bot-content.md` |
+| Category terminology or symbols | `references/term-collections-numbers-symbols.md` |
+| Keys and shortcuts | `references/keys-and-keyboard-shortcuts.md` |
+| Exact word choice | `references/term-index.tsv`, then the routed `references/a-z-term-list-*.md` file |
+
+## Apply the selected mode
+
+### Term lookup
+
+Return:
+
+* **Use:** the preferred form.
+* **Guidance:** the rule and important exceptions.
+* **Example:** one correct example when useful.
+* **Source:** the reference file and heading.
+
+Don't infer a rule from spelling alone. Read the complete term entry.
+
+### Write
+
+1. Identify the audience, content type, intended action, and space constraints
+   from the request.
+2. Load the smallest relevant reference set.
+3. Draft the content with the important information first.
+4. Check terminology, accessibility, global readiness, and the applicable
+   checklist.
+5. Return the finished content. Mention assumptions only when they materially
+   affect the result.
+
+### Rewrite
+
+1. Preserve facts, intent, required terminology, placeholders, code, and
+   literal UI strings.
+2. Fix explicit Microsoft-style violations.
+3. Improve structure, clarity, brevity, and scanability without flattening the
+   meaning.
+4. Return the revised content first.
+5. Follow with a short **Material changes** list. Omit it when the user asks
+   for only the revised text.
+
+### Review
+
+Review the content type and audience before applying rules. Run the applicable
+checklist, look up questionable terms, and deepen the review only in areas
+that the quick scan flags.
+
+Use these severities:
+
+| Severity | Use for |
+|---|---|
+| **Blocker** | Accessibility or inclusive-language failures that exclude readers, or wording that changes required meaning |
+| **High** | Explicit terminology, UI, procedure, voice, or capitalization violations that materially affect usability |
+| **Medium** | Grammar, punctuation, formatting, consistency, or global-readiness issues |
+| **Low** | Optional concision or polish that doesn't correct a clear violation |
+
+For each finding, provide:
+
+```markdown
+### [Severity] Short finding
+
+**Text:** "Exact problematic text"
+**Fix:** "Exact replacement text"
+**Rule:** Category and reference heading
+**Why:** One concise explanation
+```
+
+Group repeated instances of the same issue. Omit empty severity sections. If
+the content has no material issues, say so—don't invent findings.
+
+## Quick reference
+
+| Rule | Guidance |
+|---|---|
+| Bigger ideas, fewer words | Cut every word that doesn't earn its place |
+| Write conversationally | Use familiar words, contractions, and natural phrasing |
+| Get to the point | Lead with the information or action customers need |
+| Use sentence-style capitalization | Capitalize only the first word and proper nouns unless an exact name requires otherwise |
+| Limit end punctuation | Omit periods and colons from most titles, headings, and short UI text |
+| Use the serial comma | Write *Android, iOS, and Windows* |
+| Use one space | Use one space after periods and colons; don't add spaces around em dashes |
+| Prefer active, direct writing | Start with a verb; remove weak *you can* and *there is/are* constructions |
+| Write for everyone | Use accessible, bias-free, people-first or preference-aware language |
+| Write for the world | Avoid idioms, cultural assumptions, and ambiguous dates or measurements |
+
+## Guardrails
+
+* Don't alter technical meaning to satisfy a style preference.
+* Don't replace exact UI text with the preferred generic term.
+* Don't flag an exception as a violation.
+* Don't claim factual, legal, security, or product accuracy from a style review.
+* Don't load or quote large reference sections when a concise answer is enough.
+* Cite the reference file and heading when explaining a disputed rule.
diff --git a/.claude/skills/microsoft-writing-style-guide/evals/evals.json b/.claude/skills/microsoft-writing-style-guide/evals/evals.json
new file mode 100755
index 000000000..d0cc6a26d
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/evals/evals.json
@@ -0,0 +1,77 @@
+{
+  "skill_name": "microsoft-writing-style-guide",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "For Microsoft documentation, should I write plug-in, plugin, or add-in when describing an AI component that gives an agent access to external APIs?",
+      "expected_output": "Uses term lookup mode, routes through the term index to the plugin entry, recommends plugin as one word, preserves the distinction from add-in and add-on, and cites the reference file and heading.",
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Review this security sentence for Microsoft terminology: Add the user to the whitelist and place unknown devices on the blacklist.",
+      "expected_output": "Flags whitelist and blacklist as explicit terminology violations, recommends allow list and block list as two words, provides exact replacement text, and cites the matching A-Z entries.",
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Write a concise Microsoft-style error message for an invalid work email address. The required example format is someone@example.com.",
+      "expected_output": "Produces warm, direct, actionable UI text that explains the expected email format, avoids blame and jargon, and does not add unnecessary rationale.",
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Rewrite this for Microsoft product documentation: There are a number of configuration options which you can utilize in order to optimize performance.",
+      "expected_output": "Returns the concise rewrite first, removes there are, you can, utilize, and in order to, preserves the meaning, and briefly identifies only the material changes.",
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Review this heading and sentence: ## Configure Your New Account:  You can click the Save button in order to continue.",
+      "expected_output": "Uses review mode, flags title-style capitalization, the trailing colon, two spaces, weak you can phrasing, click, unnecessary button naming, and in order to; groups related issues and gives exact fixes with severity and rule sources.",
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Review this text and report only real Microsoft style violations: Select Save. The settings take effect immediately.",
+      "expected_output": "States that no material Microsoft style issues were found and does not invent low-value findings or rewrite already clear content.",
+      "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "Rewrite this alt text guidance inclusively: The image shows a disabled person confined to a wheelchair. Click here to see it.",
+      "expected_output": "Applies accessibility and bias-free guidance, avoids pity or confinement language, uses preference-aware person or identity wording as context supports, replaces click here with descriptive language, and preserves only visually meaningful information.",
+      "files": []
+    },
+    {
+      "id": 8,
+      "prompt": "Make this globally ready: Our fall sale starts 10/11/26. Prices begin at $25 and setup is a piece of cake.",
+      "expected_output": "Removes the seasonal reference and idiom, replaces the ambiguous numeric date with an unambiguous month-name date, clarifies currency when audience context requires it, and cites global communications guidance.",
+      "files": []
+    },
+    {
+      "id": 9,
+      "prompt": "Rewrite this procedure step: Click on the Settings button, then click the Privacy tab, and check the Allow diagnostics checkbox.",
+      "expected_output": "Uses location-before-action structure and input-neutral verbs, avoids unnecessary UI element types, preserves literal labels in bold, and uses select or clear consistently with procedure guidance.",
+      "files": []
+    },
+    {
+      "id": 10,
+      "prompt": "Review an API reference that italicizes method names, rewrites parameter identifiers into friendly words, and changes the literal --force option to Force.",
+      "expected_output": "Protects code identifiers, syntax, and literal options from style rewriting, applies developer-content formatting guidance, and distinguishes prose improvements from technical tokens.",
+      "files": []
+    },
+    {
+      "id": 11,
+      "prompt": "Write a virtual-agent response for a failed payment that sounds helpful without saying Oops or blaming the customer.",
+      "expected_output": "Uses conversational bot guidance, gives the outcome and next action clearly, avoids Oops, excessive apology, blame, and unsupported explanations, and keeps the response concise.",
+      "files": []
+    },
+    {
+      "id": 12,
+      "prompt": "Audit and then rewrite this announcement: We are pleased to inform users that they can visit the admin page to execute setup. The page is required for all administrators.",
+      "expected_output": "Reviews before rewriting, distinguishes visit from required go to navigation, replaces execute with a clearer verb where appropriate, removes formal filler and weak can phrasing, preserves the requirement, and returns a concise rewrite plus material changes.",
+      "files": []
+    }
+  ]
+}
diff --git a/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-a-c.md b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-a-c.md
new file mode 100755
index 000000000..c16116a5f
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-a-c.md
@@ -0,0 +1,1155 @@
+# A-Z word list: a-c
+
+Alphabetical Microsoft style guidance for individual words and terms. Each entry gives preferred usage, prohibited usage, and notes.
+
+## A
+
+### Abort, Abortion
+
+Never use *abortion.*
+
+Don't use *abort* in content or user experiences for a general audience. If *abort* appears in a UI that you can't edit, use an alternative term to describe the customer action.
+
+Use *abort* for a technical audience only if it's part of the application programming interface (API). Use an alternative term in comments and descriptions.
+
+### Alternative Terms
+
+  - *End:* use for communications and network connections.
+  - *Close:* use for apps and programs.
+  - *Stop:* use for hardware operations.
+  - *Cancel:* use for requests and processes.
+
+### Above
+
+Don't use to mean *earlier*.
+
+Don't use as an adjective preceding a noun (*the above section*) or following a noun (*the code above*). Use a link, or use *previous, preceding,* or *earlier.*
+
+**Examples** Use the preceding code to display information about the database. See Installation instructions. See Installation instructions, earlier in this article.
+
+**See also** below, earlier
+
+### Access Key
+
+See Keys and keyboard shortcuts term collection
+
+### Access
+
+It's OK to use as a verb to mean *obtain access to*.
+
+Don’t use *access* to mean *start, create,* or *open.* Use a more specific verb or phrase instead.
+
+### Accessible
+
+Reserve *accessible* and *accessibility* to refer to things that are easy to use for everyone, including people with disabilities.
+
+Don't use *accessible* as a synonym for *simple*. Use *easy to learn, easy to use,* or *intuitive.* But don't assume that what's easy for you is easy for customers. A better choice is to refer to the specific characteristics that make something easy to use, such as a familiar UI or simplified navigation.
+
+**Examples** Support high-contrast themes to make the app more accessible for customers who have low vision. Reading view sweeps distracting content out of your way, so it's easier to read what you want.
+
+**See also**  assistive, Accessibility guidelines and requirements
+
+### Achievement
+
+Refers to an accomplishment that's formally recognized by a game, site, or app. Achievements are sometimes represented by a virtual badge, star, medal, or other reward.
+
+Use title-style capitalization for the achievement name. Lowercase the word *achievement* when it follows the achievement name.
+
+For Microsoft games, use *achievement* only if the achievement is awarded in a player’s Xbox Live profile. Don't use *achievement* for any other accomplishments that are tracked by a game.
+
+**Examples**<br />You just earned the Superstar achievement\! <br />Take a bow—you’ve earned your Superstar.
+
+**See also** badge
+
+### Actionable
+
+Don't use unless you have no other choice.
+
+**Examples** information that you can act on Once identified, the problem is easy to solve. Aggregate customer data to make it easier to act on. Aggregate customer data to make it more conducive to action.
+
+### Active Player, Active User
+
+Use *active player,* not *active user,* to refer to a person who's currently being tracked or recognized by a motion sensor or camera.
+
+**Example** When the game ends, the active player’s score will be displayed.
+
+### Adapter
+
+**See** Computer and device term collection
+
+### Add-In, Add-On
+
+Use *add-in* to refer to software that adds functionality to a larger program, such as the Skype Meeting Add-in for Microsoft Outlook. *Add-in* can also refer to a driver or to a customer-written program that adds functionality to a larger program, such as a wizard.
+
+Use *add-on* to refer to a hardware device, such as an external drive, that's attached to the device.
+
+In content for a general audience, use *add-in* and *add-on* primarily as modifiers. For example, *add-in program* or *add-on drive*.
+
+### Add
+
+Use as a verb to describe installing add-ins and add-ons. Use *remove* to describe removing them.
+
+Don't use *add* to refer to installing apps and programs. Use *install* instead.
+
+**See also** install
+
+### Adjacent Selection
+
+Don't use if you can use *multiple selection* instead. It's OK to use *adjacent selection* if you must emphasize that the selected items are adjacent to one another.
+
+Don't use *contiguous selection*.
+
+**See also** multiple selection
+
+### Administer
+
+Use instead of *administrate*.
+
+### administrator, admin
+
+Use *administrator, admin,* or *system administrator* unless you need to specify a particular kind of administrator, such as a network administrator or a database administrator.
+
+Don't capitalize *administrator* or *admin* except when referring to the *Administrator* account type. Capitalize *Administrators* only when referring to the Administrators group in Windows security.
+
+**Examples** To log on as an administrator, you need to have a user account on the computer with an **Administrator**  account type. Limit the number of users in the Administrators group.
+
+### afterward
+
+Use instead of *afterwards*.
+
+### against
+
+Don't use to refer to running or building a program on a particular platform or operating system. Use *on* instead.
+
+It's OK to use *against* in content for a technical audience to discuss evaluating a value *against* an expression or running a query *against* a database.
+
+**Examples** Run queries on HDInsight using Hadoop, HBase, or Apache Storm clusters to extract meaning from structured and unstructured data in Azure Storage. Use Elastic Database jobs to run T-SQL scripts against all of the databases in an elastic database pool.
+
+### alarm
+
+Don't use as a general reference to a sound intended to get the customer's attention. Use *beep* or a more specific description of the sound instead.
+
+It's OK to use *alarm* in a specific description, such as *the low-battery alarm*.
+
+### alert
+
+For technical audiences, it's OK to use *alert* to refer to automated messages from apps, products, services, and websites.
+
+For general users, don't use *alert* to refer to a system message. Use *notification* instead.
+
+Don't use *alert* as a synonym for *reminder.*
+
+**Examples** When hosting a service in the cloud, you may need to monitor and send alerts in response to specific conditions, such as service interruptions. To receive an alert whenever an event occurs .... Select **Add alert**.
+
+### alias
+
+Don't use to mean an email address, account name, or distribution group name.
+
+### allow, allows
+
+Don't use *allows* (or *enables* or *lets*) to describe things that Microsoft or Microsoft apps make possible for the customer.
+
+It's OK to use *allows* to refer to features, such as security, that permit or deny some action or access.
+
+In content for technical audiences, write around the use of *allow/allows* by referring to customers in the third person, such as *the customer can*.
+
+**Examples** Windows allows a user without an account to sign in as a guest. Microsoft Word supports saving files in HTML format.
+
+### allow list
+
+An *allow list* is a list of users, accounts, or other entities allowed to access resources and other things. It's the opposite of a *block list*.
+
+Guidelines:
+
+- Two words.
+- Lowercase.
+- Don't use as a verb, such as *allow-list the address*. Use phrasing like *add to an allow list* or *use an allow list*.
+- Don't use one word (*allowlist*).
+
+**See also** block list whitelist blacklist
+
+### alphabetical
+
+Use instead of *alphabetic*.
+
+### alphanumeric
+
+Use to refer to character sets that include only letters and numerals or to individual characters that can be only letters or numerals.
+
+Don't use *alphanumerical*.
+
+### AM, PM
+
+**See** Date and time term collection
+
+### ampersand (&)
+
+Don't use *&* in place of *and* in text or headings unless you're referring to the use of the symbol in UI.
+
+It's OK to use *&* in content for technical audiences that covers its use in HTML or programming languages.
+
+**Example**<br />To display a reserved character in HTML, use a character reference, which consists of an ampersand, the code name or number of the character, and a semicolon. For example, use *\&lt;* or *&\#60;* to display the less than sign (\<), and use *\&gt;* or *&\#62;* to display the greater than sign (\>).
+
+**See also** plus sign (+)
+
+### and/or
+
+Don't use unless it helps you avoid lengthy, complex wording. Most of the time, *or* can stand on its own.
+
+**Example** Save the document, using its current name or a new name.
+
+### and so on
+
+Don't use. Instead, be specific. When space is limited, use *such as* or *like* followed by an example or two.
+
+**Example** Body text is most readable in Times New Roman, Palatino, and other serif fonts. (Not *Body text is most readable in Times New Roman, Palatino, and so on.*) Body text is most readable in serif fonts like Palatino.
+
+Don't use *and so on* to end a phrase that begins with *for example, such as,* or *like.* It's redundant.
+
+**Example** Body text is most readable in serif fonts, such as Times New Roman and Palatino. (Not *Body text is most readable in serif fonts, such as Times New Roman, Palatino, and so on.*)
+
+### anti-malware
+
+Hyphenate. Use only as an adjective. 
+
+*Antivirus* is often used interchangeably with *anti-malware* to describe any program that removes malware. Use *antivirus* when you want to differentiate between antispyware and other anti-malware programs.
+
+**Examples**  
+Microsoft Defender contains powerful anti-malware tools to help protect your device. 
+
+Windows Defender has both antivirus and antispyware capabilities. 
+
+Anti-malware settings
+### antialiasing
+
+Don't hyphenate. Don't capitalize *antialiasing* unless it begins a sentence or phrase. Don't capitalize *aliasing* in *antialiasing*.
+
+**Example** Microsoft ClearType antialiasing is a smoothing method that improves font display resolution, compared to traditional antialiasing.
+
+### antispyware
+
+Use only as an adjective. Don't hyphenate.
+
+**Example** antispyware tools
+
+### antivirus
+
+Use only as an adjective. Don't hyphenate.
+
+*Antivirus* is often used interchangeably with *anti-malware* to describe any program that removes malware. Use *antivirus* when you want to differentiate between antispyware and other anti-malware programs.
+
+**Examples** antivirus program Windows Defender has both antivirus and antispyware capabilities.
+
+### app, application
+
+If possible, refer to a product by its descriptor, such as *database management system* or *spreadsheet.*
+
+Most of the time use *app,* not *application,* to describe desktop apps and cloud apps for tablets and mobile devices. 
+
+**Global tip** The abbreviated form, *app,* isn't available in all languages, so allow enough space for the full translated term in localized content.
+
+For full-featured products, such as Office and Visual Studio, it's OK to use *program* instead of *application.*
+
+It's OK to use *application* in
+content for a technical audience, especially to refer to a set of
+software files that includes executable files and other components.
+
+Don't use *application program.*
+
+**See also**  
+[add-in, add-on](/style-guide/a-z-word-list-term-collections/a/add-in-add-on)  
+[applet](/style-guide/a-z-word-list-term-collections/a/applet)  
+[tool](/style-guide/a-z-word-list-term-collections/t/tool)   
+[Control Panel](/style-guide/a-z-word-list-term-collections/c/control-panel)
+### appendix, appendices
+
+Use *appendices* as the plural form of *appendix,* not *appendixes*.
+
+### applet
+
+Use to refer to an HTML-based program that a browser downloads temporarily to a customer's hard drive. *Applet* is most often associated with Java.
+
+In general, when referring to a small program, use the name of the program or the most appropriate term, such as *item, app, program, add-in,* or *applet.*
+
+**Example** A Java applet in an HTML document supports animation, music, and page updates.
+
+**See also** <br />add-in, add-on,<br />app, application, <br />tool
+
+### application developer, app developer
+
+Don't use *application developer,* *applications developer,* or *app developer*. Use *software developer, web developer, developer,* or *programmer* instead.
+
+### application file, app file
+
+Don't use. Use the specific name of the file if you can. Otherwise, use *program file*.
+
+### application icon, app icon
+
+Don't use to refer to a program icon. Use the specific product name, such as *the* *Word* *icon,* instead. If you must use a general term, use *app icon.*
+
+It's OK to use *application icon* in content for developers when discussing programming elements such as the **ApplicationIcon** property.
+
+### application window, app window
+
+Don't use to refer to a specific product window. Use the product name, such as *the Word window,* instead.
+
+It's OK to use *application window* in content for developers when discussing programming elements, such as the **WindowSize** event.
+
+### argument vs. parameter
+
+These terms are often used interchangeably.
+
+Use *argument* in content for a general audience. Differentiate with *parameter* only if necessary.
+
+In content for a technical audience, use the same term consistently to refer to the same kind of element. When you need to differentiate between them:
+
+ - Use *argument* for a value or expression that contains data or code that's used with an operator or passed to a function. 
+ - Use *parameter* for a value that's given to a variable and treated as a constant until the operation is completed. For example, a date could be a parameter that's passed to a scheduling function.
+
+**See also** Reference documentation, Formatting developer text elements
+
+### arrow keys
+
+**See** Keys and keyboard shortcuts term collection
+
+### arrow
+
+In content teaching basic skills, it's OK to use *arrow* to identify the arrow next to a list box label. Don't use *up arrow* or *down arrow,* which refer to the arrow keys on the keyboard.
+
+**Example** Select the **Font** arrow to display the list.
+
+### AI (artificial intelligence)
+
+**See** AI and bot term collection
+
+### as well as
+
+Don't use as a synonym for *and.*
+
+### ask
+
+Don't use as a noun. Use *request, task,* or another suitable word.
+
+**Examples** Your assigned tasks After you submit your request, you’ll receive a confirmation email.
+
+### assembly language
+
+Use instead of *assembler* or *machine language*.
+
+Hyphenate as an adjective.
+
+### assistive
+
+Use to describe devices, technologies, and organizations that help people with disabilities. Eye trackers and motion sensors are examples. Keep in mind that some devices and organizations are useful to everyone. Refer to them as *assistive* only in discussions about supporting people with disabilities.
+
+**Examples** (General discussion) Calibrate your motion sensor to track your body movements correctly. (Specific discussion) Learn about assistive technology built into Windows 10.
+
+**See also**  Accessibility guidelines and requirements
+
+### assure, ensure, insure
+
+*Ensure, insure,* and *assure* are interchangeable in many situations. To improve worldwide readability, Microsoft style makes these distinctions:
+
+  - Use *ensure* to mean *to make sure* or *to guarantee*. 
+  - Use *insure* to mean *to provide insurance*. 
+  - Use *assure* to mean *to state positively* or *to make confident*.
+
+### asterisk (\*)
+
+See Keys and keyboard shortcuts term collection
+
+### at sign (@)
+
+See Keys and keyboard shortcuts term collection
+
+### attribute
+
+Don't use as a synonym for *property*.
+
+**See** property
+
+### audiobook
+
+One word.
+
+### author
+
+Don't use as a verb to mean *to make something.* Instead, use a clearer verb that accurately describes the action, such as *write, create, design, produce,* or *build.*
+
+**Examples** Design mobile-optimized reports that people can access anywhere. You don't need a runtime class if you're implementing a Windows Runtime interface for local consumption—for example, if you're writing an app based around CoreApplication. This article describes how to create a Transact-SQL stored procedure.
+
+In content for a technical audience, it's OK to use authoring in reference to programming languages and tools. For example, it's OK to use *authoring tools, authoring environments,* and *authoring in XML.*
+
+It's OK to use *coauthor* and *coauthoring* to refer to people working on an Office document simultaneously.
+
+**Example** In Word, multiple people can coauthor a document at the same time.
+
+### auto-
+
+In general, don’t hyphenate words beginning with *auto-,* such as *autoscale* and *autodial,* unless it's necessary to avoid confusion. When in doubt, check *Merriam-Webster Dictionary.*
+
+Don’t create new words beginning with *auto-.*
+
+To learn more about hyphenation, see Hyphens.
+
+For more information about prefixes, see *The Chicago Manual of Style*.
+
+### avg
+
+OK to use the abbreviation, without a period, in UI when space is tight. Otherwise, spell out *average.*
+
+## B
+
+### back end, back-end
+
+In content for a general audience, don't use as a synonym for *server*, *operating system*, *database*, or *network*.
+
+In content for a technical audience, it's OK to use *back end* (noun) and *back-end* (adjective that precedes a noun) if it's necessary for accuracy.
+
+**Examples** Verify that the database is sending information to the dashboard. Create two virtual machines to use as back-end servers.
+
+### Back Up, Backup
+
+Two words as a verb, one word as an adjective or a noun.
+
+**Examples** Back up your files regularly. Schedule automatic backups.
+
+### Backbone
+
+Don't use in content for a general audience. You don't need to define *backbone* in content for a technical audience.
+
+### Backlight
+
+One word.
+
+### Backspace
+
+One word. OK to use as a verb.
+
+### Backtab
+
+Don't use. Instead, instruct the customer to use Shift+Tab.
+
+### Badge
+
+A star, medal, or other virtual recognition that indicates an achievement in a game or other program. Use title-style capitalization for a badge name. Lowercase the word *badge*.
+
+**See also** achievement
+
+### Baseline
+
+Use *baseline* (one word) to refer to an established standard, as in *baseline data*.
+
+### Baud
+
+**See** Units of measure term collection
+
+### Beep
+
+Use instead of *alarm* or *tone* to refer to a beeping sound.
+
+**Example** Recording begins when you hear the beep.
+
+### Below
+
+Don't use to mean *later*.
+
+Don't use as an adjective preceding a noun (*the below section*) or following a noun (*the code below*). Use a link, or use *later* or *the* *following*.
+
+**Examples** Use the following code to display information about the database. See Installation instructions. See Installation instructions, later in this article.
+
+**See also** above, later
+
+### beta
+
+See preview
+
+### Bi-
+
+In general, don't hyphenate words beginning with *bi-,* such as *bidirectional,* *bimodal,* and *bimonthly,* unless it's necessary to avoid confusion. When in doubt, check *Merriam-Webster Dictionary.*
+
+To learn more about hyphenation, see Hyphens.
+
+### big data
+
+Don't capitalize.
+
+### Big-Endian, Little-Endian
+
+It’s OK to use *big-endian* and *little-endian* in content for a technical audience. *Big-endian* refers to the method of physically storing numbers so that the most significant byte is placed first. *Little-endian* is the opposite.
+
+### Billion, B
+
+**See** Numbers
+
+### Bio
+
+OK to use as an abbreviation for *biography*.
+
+**Global tip** In many languages, the full term is translated because an abbreviation isn't available. So you'll still need to allow ample space for expansion in localized text.
+
+### Bitmap
+
+One word.
+
+Don't use generically to refer to any graphic. Use *illustration, figure, picture,* or a similar term instead.
+
+### bits per second
+
+See Bits and bytes term collection
+
+### Black Box
+
+Don't use.
+
+### Black Hat Hacker
+
+See Security term collection
+
+### blacklist
+
+Never use *blacklist*. Use *block list* instead. For more specific usage, *blocked senders list* can be used.
+
+**Examples** *Block lists* can help prevent unwanted spam. It could be useful to have a *blocked senders list*.
+
+### blade
+
+Don't use. See pane.
+
+### blank
+
+Don't use as a verb to mean removing the contents of a cell in a table or sheet. Use *clear* instead.
+
+### block list
+
+A *block list* is a list of users, accounts, or other entities restricted from accessing resources and other things. It's the opposite of an *allow list*.
+
+Guidelines:
+
+- Two words.
+- Lowercase.
+- Don't use as a verb, such as *block-list the address*. Use phrasing like *add to a block list* or *use a block list*.
+- Don't use one word (*blocklist*).
+
+**See also** allow list blacklist whitelist
+
+### blog, blogger, blogroll, weblog
+
+Use *blog* as a noun or verb. Don't use *weblog.*
+
+Use *blogger* to refer to a person who writes or publishes entries for a blog.
+
+Use *blogroll* to refer to a list of links to other online content, particularly blogs, that's provided on a blog page.
+
+### Blu-ray Disc
+
+Use this spelling and capitalization when talking about the disc. After the first mention, it's OK to abbreviate to *BD* (no hyphen).
+
+When referring to the technology (not a specific disc), it's OK to use *Blue-ray [X]*.
+
+### blue screen, bluescreen
+
+Don't use *blue screen* or *bluescreen,* either as a noun or as a verb, to refer to an operating system that's not responding. As a verb, use *stop.* As a noun, use *stop error.*
+
+It's OK to use *blue screen* (two words) to refer to the screen display itself.
+
+**Example** The operating system stopped unexpectedly, and an error message appeared on a blue screen.
+
+### Bluetooth
+
+Bluetooth is a proper noun and a registered trademark. Always capitalize. Use the registered trademark symbol (®) upon first mention.
+
+### board
+
+Don't use to describe hardware that provides a connection between a peripheral device and a computer. Use *card* instead.
+
+**Examples** video card motherboard
+
+### bold
+
+Use only as an adjective, not as a noun or verb. Don't use *bolded, boldface,* or *boldfaced*.
+
+**Examples** To apply bold formatting to the selected text, select **Ctrl+B**. The newly added parameters are displayed in bold type. The selected text is bold.
+
+In writing for customers, use regular type to describe type that's neither bold nor italic.
+
+### bookmark
+
+One word. Use *favorite,* not *bookmark,* to refer to a saved site or webpage.
+
+**See** favorite
+
+### Boolean
+
+Always capitalize.
+
+### boot
+
+Don't use as a verb. Use *turn on* to refer to turning on power to a device.
+
+In content for a technical audience, it's OK to use *boot* as an adjective, as in *boot sector* and *boot sequence*—but use *startup* instead if possible.
+
+If the UI or API uses *boot* in a label or element name, use *boot* to refer to the label or element name, but use *start* or *startup* to refer to the action or event described.
+
+**Examples** The Boot.ini file stores startup options. Diagnosing and correcting problems that affect the startup process is an important troubleshooting skill.
+
+**See also** turn on, turn off
+
+### bot
+
+**See** AI and bot term collection
+
+### bottom left, bottom right
+
+Don't use except in discussions of the **BottomLeft** and **BottomRight** properties. Use *lower left* and *lower right* instead.
+
+Hyphenate *lower left* and *lower right* as adjectives.
+
+**See also** lower left, lower-left, lower right, lower-right
+
+### bounding outline
+
+Use to describe the visible element, usually a dotted rectangle, that surrounds a set of selected elements. If necessary, use *dotted rectangle* or *dotted box* to describe the bounding outline in content for a general audience, and then use *bounding outline* in subsequent references.
+
+Don't use *marquee* as a synonym.
+
+### box
+
+Most of the time, avoid talking about UI elements.
+
+When you need to refer to dialog box elements by name, use *box* instead of *field* to refer to any box except a checkbox or a list box. For a checkbox, use the complete term, *checkbox*. For an element that displays a list, such as a dropdown list box, use *list* instead of *box* for clarity.
+
+**Examples** the **Read-Only** box the **File Name** box the **Hidden Text** checkbox the **Wallpaper** list
+
+Don't use *box* as a synonym for client and server hardware.
+
+**See also** Describing interactions with UI Formatting text in instructions Computer and device term collection
+
+### bps
+
+**See** Bits and bytes term collection
+
+### breakpoint
+
+One word.
+
+### broadcast
+
+OK to use as an adjective, a noun, or a verb. Use *broadcast,* not *broadcasted,* as the past-tense form of the verb.
+
+Use *webcast* to refer to a broadcast delivered on the web.
+
+### browse
+
+Use to refer to manually scanning internet sites or other files. To describe using the search feature of an app, product, or service, or using an internet search engine, use *find* or *search.*
+
+It's OK to use *browse the web,* but use *browse through* a list, database, document, or similar item.
+
+### bug fix
+
+Don't use. To describe the general category of fixes for an issue, use *software update*.
+
+### build
+
+Don't use in content for a general audience to mean creating things like documents, charts, graphics, and worksheets. Use *create* instead.
+
+In content for a technical audience, it's OK to use *build* as a verb to mean to compile and link code and as a noun to refer to a prerelease version.
+
+### bulk
+
+In content for a general audience, don’t use *bulk* as an adverb, such as *bulk add* or *bulk edit,* unless the term is in the UI.
+
+In content for a technical audience, avoid using *bulk* as an adverb to describe an action performed on multiple objects. Try *in bulk* as an alternative.
+
+Don’t use *bulk* in compound nouns.
+
+Don't hyphenate.
+
+**Examples** Add multiple users at the same time. Replace a value across a large number of fields. Update multiple product attributes in a single operation.
+
+### button
+
+Most of the time, avoid talking about UI elements.
+
+When you need to discuss UI elements, use *button* instead of *command button,* *option button,* or *action button*. If possible, refer to a button by its label only without using the word *button*. If you need to use the word *button* for clarity, *button* is lowercase. For example, references to an unnamed button such as **Maximize** may be clearer if you describe it as *the* ***Maximize*** *button*.
+
+**Examples** Select a file, and then select **OK**. To enlarge a window to fill the entire screen, select the **Maximize** button.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### by (publisher or company name)
+
+In an online store (either in a product experience or the web), avoid including *by* in the publisher line. For example, use *Microsoft* not *by Microsoft.*
+
+If you must include *by,* lowercase it.
+
+## C
+
+### C, C++, C\#
+
+It's OK to use *C, C++,* and *C\#* as adjectives. Don't form hyphenated modifiers with them, such as *C-based* or *C-callable*.
+
+**Examples** a C program a program based on C++ built with exported functions that are callable by C
+
+### cable
+
+Don't use as a verb.
+
+### cabling
+
+Don't use as a synonym for *cable* or *cables*.
+
+In a discussion of network connections, it's OK to use *cabling* to refer to a combination of cables, connectors, and terminators.
+
+### cache vs. disk cache
+
+Differentiate between *cache* and *disk cache*.
+
+  - Use *cache* to refer to a special memory subsystem where data values are duplicated for quick access. 
+  - Use *disk cache* to refer to a portion of RAM that temporarily stores information read from a disk. 
+
+Don't use *cache* or *file cache* to refer to the location of internet files that are downloaded as you browse the web. Use *Temporary Internet Files folder*.
+
+### calendar
+
+Don't use as a verb. Use *schedule, list,* or another appropriate verb instead.
+
+### call back, callback
+
+Two words as a verb, one word as an adjective or a noun.
+
+In content for developers, don't use *callback* to mean *callback function*.
+
+### call out, callout
+
+Two words as a verb, one word as an adjective or a noun.
+
+### can, may
+
+When you see *can* in your writing, consider deleting it. *Can* implies ability but not action. Rewrite to describe the action if possible.
+
+**Example** Use the **/b** option to force a black-and-white screen.
+
+When ability is what you need to express, it's OK to use *can* to describe actions or tasks that the reader or program is able to do. Use *might* to express possibility. Don't use *may,* which might be interpreted as providing permission.
+
+Don't substitute *could* for *can* unless you're referring to the past.
+
+### cancel, canceled, canceling, cancellation
+
+Use *cancel the selection* instead of *deselect* or *unmark*. Use *clear* to refer to checkboxes.
+
+Use *cancel* to describe ending code requests and processes before they're complete.
+
+Spell *canceled* and *canceling* with one *l,* but spell *cancellation* with two <em>l'</em>s.
+
+### carry out vs. run
+
+Use *run,* not *carry out,* to describe actions related to commands, macros, and programs.
+
+**See also** run vs. execute
+
+### Cascading Style Sheets (CSS)
+
+Capitalize references to the technique for adding fonts, colors, and so on to web content. Spell out unless the abbreviation *CSS* is familiar to your audience.
+
+Lowercase references to style sheets created using the technique. Don't use *CSS* to refer to a specific cascading style sheet. Instead, use *the CSS file, the cascading style sheet,* or *the style sheet.*
+
+**Examples** If this is your first time working with Cascading Style Sheets (CSS), don’t worry. Use a custom style sheet to create a unique look for your SharePoint site. It looks like there's a problem with the CSS file.
+
+### catalog
+
+Use instead of *catalogue.*
+
+### category axis
+
+Lowercase. Don't hyphenate.
+
+Refer to the *category (x) axis* on the first mention. On subsequent mentions, use *x-axis*. It's OK to use *horizontal (x) axis* in content for a general audience.
+
+In 3D charts, both the x-axis and y-axis are usually category axes<em>.</em>
+
+Don't use italic formatting for the *x* in *x-axis* or the *y* in *y-axis* unless the entire word is italic.
+
+**See also**
+ 
+value axis x-axis y-axis
+
+### cell phone, cellular phone
+
+Don't use.
+
+**See** Computer and device term collection
+
+### cellular
+
+Don’t use *cellular phone* or *cell phone*.
+
+It's OK to use *cellular* in the context of *cellular data network* or *cellular data connection*.
+
+**See** Computer and device term collection
+
+### center on
+
+Use instead of *center around.*
+
+### character set
+
+Don't use as a synonym for *code page*. A character set appears on a code page.
+
+### chart
+
+Don't use as a verb when referring to entering data for a chart. Use *plot* instead.
+
+Use the noun *chart* instead of *graph* to refer to graphic representations of data. For example, use *bar chart, pie chart,* and *scatter chart.*
+
+### chat
+
+Use as an adjective, a noun, or a verb in the context of internet or intranet chat. Use *voice chat* and *video chat* if necessary to avoid ambiguity.
+
+### chatbot
+
+**See** AI and bot term collection
+
+### check, checkbox, check mark
+
+Use *check mark* to refer to a mark placed next to an item to show it’s selected.
+
+Use *checkbox*, not *box* or *check box*, to refer to a checkbox in UI. Avoid talking about UI elements. Instead, discuss what the customer needs to do or what they're looking at.
+
+Use *select* and *clear* with checkboxes, not *turn on* and *turn off,* *mark* and *unmark,* *check* and *uncheck,* or *select* and *deselect.*
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### check in
+
+OK to use as a verb phrase, as in *check in code* or *check in changes*. Don't use as a noun.
+
+### child folder
+
+Don't use. Use *subfolder,* *subdirectory,* *folder,* or the name of the folder.
+
+### choose
+
+**See** Describing interactions with UI
+
+### clear
+
+**See** Describing interactions with UI
+
+### click
+
+Avoid this verb, which is specific to using a mouse. Instead, use verbs that work with multiple devices, such as *select*.
+
+It's OK to use *click* when you need to describe mouse actions specifically.
+
+**See** Describing interactions with UI
+
+### clickstream
+
+One word. Don't use in content for a general audience.
+
+### clickthrough
+
+One word. Don't use in content for a general audience.
+
+### client/server
+
+Always use the slash. Capitalize both words if the context requires *client* to be capitalized.
+
+### client side, client-side
+
+Don't use for a general audience. Use *client* instead.
+
+It's OK to use *client side* in writing for a technical audience when it refers specifically to the client part (side) of a program or protocol that acts on both a server computer and a client computer.
+
+Avoid using *client-side* as an adjective. If you must use it as an adjective, hyphenate it.
+
+### client
+
+Don't use *client* to refer to a person. Use *customer* instead.
+
+**See**  Computer and device term collection
+
+### clipboard
+
+Don't precede *clipboard* with *Windows*.
+
+Material is moved or copied *to* the clipboard, not *onto* it.
+
+### Close button
+
+Spell out and capitalize the word *Close*. It's OK to use *the* ***Close*** *button* to eliminate ambiguity in content that teaches beginning skills, but for general audiences, just use ***Close***. Use bold for ***Close*** when you're talking about the **Close** button. If you can, use an inline graphic of the button.
+
+**Examples** Select the **Close** button :::image type="icon" source="media/close-button/1581618122.png":::. Select **Close** :::image type="icon" source="media/close-button/1581618122.png":::.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### close
+
+**See** Describing interactions with UI
+
+### cloud native, cloud-native
+
+Cloud-native architecture and technologies are an approach to designing, constructing, and operating workloads that are built in the cloud and take full advantage of the cloud computing mode.
+
+Guidelines:
+
+- Lowercase.
+- Hyphenate as an adjective that precedes a noun, as in *cloud-native app*. Don't hyphenate in other instances.
+- In general, avoid *cloud native* and *cloud-native*. They might be unclear to some audiences or come across as jargon. Use friendlier language like *cloud-first*, *cloud-based*, *cloud-optimized*, *built for the cloud*, or *built in the cloud*.
+- OK to use with developers and other technical audiences.
+
+### cloud platform
+
+**See** Cloud-computing term collection
+
+### cloud services
+
+**See** Cloud-computing term collection
+
+### cloud
+
+**See** Cloud-computing term collection
+
+### co-
+
+In general, don’t hyphenate words beginning with *co-,* such as *coauthor* and *coordinate,* unless it’s necessary to avoid confusion. When in doubt, check *Merriam-Webster Dictionary.*
+
+To learn more about hyphenation, see Hyphens.
+
+### code page
+
+Don't use as a synonym for *character set*. A character set appears on a code page.
+
+### code point
+
+Two words.
+
+### codec
+
+Don't spell out as *compressor/decompressor* or *coder/decoder*. Use only in content for a technical audience or when *codec* appears in the UI.
+
+### color map
+
+Two words when referring to the color lookup table in a video card.
+
+### column format
+
+Use instead of *columnar* or *columnlike*.
+
+### combo box
+
+Two words. Use only in content for a technical audience to describe a box in which the user can enter or select a value. Don't use in content for a general audience. Instead, refer to it as a *box,* using the label provided in the UI.
+
+Use *enter* to indicate that the user can either type an item in the box or select an item in the list. Or just say *For \[Control name\],* *enter \[value\].*
+
+**Examples** In the **Size** box, enter the font size you want. For **Size**, enter a font size.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### command button
+
+Don't use in content for a general audience. Most of the time, just refer to the button by its UI label. In content that teaches beginning skills, use the label followed by the word *button*.
+
+**Examples** For information about the dialog box, select the **Help** button. For information about the dialog box, select **Help**.
+
+It's OK to use *command button* in content for developers about creating command buttons.
+
+Don't refer to a command button as an *action button* or *push button*.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### command line, command-line
+
+Two words as a noun. Hyphenate as an adjective.
+
+**Examples** command-line parameter command-line tool
+
+Customers enter commands *at* a *command prompt,* not *on* a *command line.*
+
+It's OK to use *on the command line* in the context of building apps using command-line tools in Visual Studio.
+
+Use *command-line program* in content for a general audience. Use *console application* only in content for a technical audience.
+
+**See also** Formatting developer text elements command prompt console
+
+### command prompt
+
+Use instead of *C prompt, command-line prompt,* or *system prompt.*
+
+*Command prompt* refers only to a prompt itself. For example, *C:>* is a command prompt. The window in which a command prompt appears is the *Command Prompt window.* Note the capitalization.
+
+Don't refer to the Command Prompt window as a *console window* except in content for a technical audience.
+
+Describe entering commands *at a command prompt,* not *on a command line*.
+
+**Example** At the command prompt, enter **certutil -setreg ca**.
+
+**See also**  command line, console
+
+### command
+
+In general, avoid talking about the UI. Instead, talk about what the customer needs to do. If you must refer to commands on menus in content for a general audience, use *command* instead of *menu item, choice,* or *option.*
+
+In content for developers about creating UI elements, it's OK to use *menu item* when appropriate.
+
+**See also** Describing interactions with UI Formatting text in instructions option, option button
+
+### community cloud
+
+**See** Cloud-computing term collection
+
+### company vs. organization
+
+Use the term that makes the most sense for your audience.
+
+*Company* is appropriate for businesses, which don't think of themselves as organizations.
+
+*Organization* includes schools, nonprofits, and government customers in addition to companies.
+
+**See also** enterprise, org, organization
+
+### compile
+
+It's OK to use *compile* as an adjective, as in *compile time,* or as a verb. Don't use as a noun.
+
+**Example** After you save the file, compile your program.
+
+### compute
+
+It’s OK to use *compute* as a verb in content for all audiences.
+
+In content for a technical audience, it’s OK to use *compute* to refer to computation, such as in *compute hours* and *compute-intensive*. For a general audience, use terms such as *computing time* or *processor-intensive*.
+
+**Examples** Learn how to compute the periodic annual interest rate in Microsoft Excel. Each Microsoft Azure compute instance represents a virtual machine.
+
+### computer
+
+**See** Computer and device term collection
+
+### connect
+
+Use *connect, make a connection,* and similar phrases to describe attaching a computer to a network, whether intranet or internet.
+
+Don't use *connect* as a synonym for *sign in* or *map,* as in mapping a drive letter to a shared network folder. But use *disconnect* to describe removing a mapped network drive.
+
+**See also**  sign in, sign out
+
+### console
+
+Use *console window* and *console application* only in content for a technical audience. Use *Command Prompt window* and *command-line program* in content for a general audience.
+
+Don't use *console* as a synonym for *snap-in*.
+
+**See also** command line, command-line command prompt snap-in
+
+### context menu
+
+Use *context menu* only in content for developers. Make it clear that it refers to the shortcut menu.
+
+**Examples**<br />The **Control.ContextMenu** property gets or sets the shortcut menu associated with the control.<br />**Undo**, **Cut**, **Copy**, **Paste**, **Delete**, and **Select All** menu commands are included as a standard part of the context menu for the **TextBox** control and appear on the resulting shortcut menu.
+
+**See also** shortcut, shortcut menu, pop-up
+
+### context-sensitive
+
+Always hyphenate.
+
+### contiguous selection
+
+Don't use. Use *multiple selection* instead. If it's important to emphasize that all the selected items are adjacent to one another, use *adjacent selection*.
+
+**See also** multiple selection
+
+### control-menu box
+
+Avoid referring by name to this icon and the menu that it opens. If you must, refer to the *\<App Name\> icon* or the *\<title bar\> shortcut menu*.
+
+**Figure** A shortcut menu includes selectable icons such as **Undo** and **Redo**.
+
+### Control Panel
+
+Use *Control Panel,* not *the Control Panel,* to refer to the entire Windows Control Panel feature.
+
+Most of the time, refer to specific, named control panels. When you must discuss control panels generically, refer to an individual control panel as a *control panel item* (lowercase). When you must refer to the icons that represent control panels, use *control panel icon* (lowercase). Don't use *applet, program, tool,* or *control panel* to refer to either the icons or the items.
+
+Use bold formatting for the names of control panel items and icons and to refer to the **Control Panel** command on the Start menu. Otherwise, don't use bold formatting.
+
+In documentation for a technical audience, refer to *control panel home page* and *control panel category page* (lowercase).
+
+When referring to a control panel item’s hub page, use *main \<control panel item name\> page*.
+
+**Examples** In Control Panel, select **Network and Internet**, and then select **Internet Options**. To open **Internet Options**, select **Start**, select **Control Panel**, and then select **Network and Internet**.
+
+**See also** add-in, add-on app, application applet tool
+
+### control
+
+In content for a general audience, don't use *control* to refer to a UI element such as a text box, checkbox, or list box. It's OK to use *control* to refer to adding a user-defined control in a program.
+
+In other contexts, it's OK to use *control*.
+
+**Examples** In the **Font** list, select the font that you want to use. On the **Developer** tab, in the **Controls** group, click the **Rich Text** control or the **Text** control. What can I control with Parental Controls?
+
+### controller
+
+**See** Computer and device term collection
+
+### conversation as a platform (CaaP)
+
+**See** AI and bot term collection
+
+### conversational user interface (CUI)
+
+**See** AI and bot term collection
+
+### corrupted
+
+Avoid. Try to use a more empathetic statement to describe a file or data that has been damaged. Better yet, offer help in fixing it if possible. Don't use *corrupt*.
+
+**Example** Looks like something's wrong with that file. Do you want to try to repair it?
+
+### country or region
+
+Use instead of *country*
+for list headings, descriptions, and other contexts that might include
+named dependencies or disputed territories. In general discussions, use
+just *country.* Don't use *geography* or *geo* as a synonym for *country* or *country or region.*
+
+**Examples**  
+This product isn't available in some countries.  
+Enter your country or region.
+
+It's OK to use *country/region* where space is limited. Capitalize both words if the context requires *country* to be capitalized. For example, if *country/region* is used as a label in a form, capitalize as *Country/Region.*
+### crash
+
+Don't use.
+
+Use *fail* for disks or other hardware, or *stop responding* for programs or the operating system.
+
+### cut, cut-and-paste
+
+Don't use *cut:*
+
+  - As a verb, even to refer to an action involving the **Cut** command. Use *delete* instead.
+  - As a verb to describe temporarily moving text to the clipboard. Use *move* or *copy* instead.
+  - As an imperative verb in procedures involving the **Cut** or the **Delete** command. Use *delete* instead.
+  - As a noun to refer to the action of the **Delete** command. Use *deletion* instead. 
+
+It's OK to use *cut-and-paste* as an adjective.
+
+Don't use *cut-and-paste* or *cut-and-replace* as a noun or verb. Use *delete* instead. It's OK to use *paste* by itself.
+
+**Examples** Select **Cut** to delete the selected text. Select the text you want to delete, and then select **Cut**. Select **Cut** to move the selected text to the clipboard. Delete the text and paste it somewhere else. Cut-and-paste capabilities are available across most Windows devices.
+
+### cyber-
+
+Don’t hyphenate words that begin with *cyber,* such as *cybersecurity,* *cyberspace,* and *cyberattack*.
+
+To learn more about hyphenation, see Hyphens.
+
+### \-core
+
+Hyphenate adjectives formed by adding *-core* in reference to types of processors.
+
+**Example** single-core, dual-core, and multi-core processors
diff --git a/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-d-g.md b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-d-g.md
new file mode 100755
index 000000000..0042f2eb1
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-d-g.md
@@ -0,0 +1,1100 @@
+# A-Z word list: d-g
+
+Alphabetical Microsoft style guidance for individual words and terms. Each entry gives preferred usage, prohibited usage, and notes.
+
+## D
+
+### dark mode
+
+Lowercase, two words.
+
+*Dark mode* is a display setting that changes the interface from a bright background color to a darker color. This setting can be easier on the eyes in lower-light environments and for people who prefer interfaces that aren’t as bright.
+
+**Examples** Use *dark mode* to reduce eye strain.
+
+Turn on *dark mode* automatically at sunset.
+
+### data binding
+
+Two words.
+
+### data, datum
+
+Use *data* as both a singular and plural noun. Don't use *datum.*
+
+Always use *data* with a singular verb, even if you're talking about more than one data set. Don't use *the data are.*
+
+Lowercase *data* unless it's at the beginning of a sentence or phrase.
+
+**Examples** The data shows that 95 percent of users prefer a graphical interface. The data gathered so far is incomplete. These facts contradict earlier data.
+
+**See also** big data
+
+### data record
+
+Don't use. Use *record* instead<em>.</em>
+
+### database
+
+One word.
+
+### datacenter
+
+One word.
+
+### datagram
+
+One word.
+
+### datasheet
+
+One word.
+
+### deaf or hard-of-hearing
+
+**See** Accessibility term collection
+
+### debug
+
+Use only in the context of software development. Don't use as a synonym for *troubleshoot*.
+
+### deceptive software
+
+**See** Security term collection
+
+### decrement
+
+Use only in content for a technical audience.
+
+As a verb, use only to refer to decreasing an integer count by one. Don't use as a synonym for *decrease*.
+
+It's OK to use *decrement* as an adjective when discussing decrement operators and values.
+
+### default
+
+Don't use as a verb.
+
+**Examples** If you don't choose a template, Normal.dot is applied by default. This value specifies the number of sheets to add. The default is one sheet.
+
+### defragment
+
+Don't abbreviate to *defrag*.
+
+### deinstall
+
+Don't use except to reference the term when it appears in the UI or an API. Don't use *deinstall* to refer to the related action. Use *remove* instead.
+
+**Example** The **DeInstall** method removes the specified network component from the operating system.
+
+**See also** uninstall
+
+### delete
+
+Use as a verb to describe the results of using the **Delete** or **Cut** command, such as moving files to the **Recycle Bin** in Windows, moving items to the Deleted folder in Outlook, and moving items to the clipboard. Use *delete* to describe these actions even if the customer uses a different method, such as by dragging a file to the **Recycle Bin** or using the **Cut** command.
+
+Use *delete* to refer to actions that result from pressing the Delete or Backspace key on the computer, such as deleting selected text.
+
+Don't use *delete* as a synonym for *remove*. Don't use *cut* or *erase* as a synonym for *delete*.
+
+**Examples** Delete the second paragraph. Delete MyFile.txt from the Windows folder. Remove the **Size** column from the Inbox.
+
+**See also** cut, cut-and-paste, remove
+
+### demilitarized zone (DMZ)
+
+Don't use. Use *perimeter network* instead. On the first mention, it's OK to say:
+
+>perimeter network (also known as *DMZ, demilitarized zone,* and *screened subnet*)
+
+### deprecated
+
+Avoid in content for a technical audience.
+
+Don't use in content for a general audience. Use *obsolete* or another appropriate word.
+
+### depress, depressed
+
+**See** Keys and keyboard shortcuts term collection
+
+### deselect
+
+Don't use. Use *clear* for checkboxes and *cancel the selection* for other UI elements.
+
+**See also** Describing interactions with UI
+
+### desktop
+
+Use to refer to the work area on the Windows screen. Refer to the desktop as *client area* only in content for a technical audience and only if necessary.
+
+It's OK to use *desktop* when it's necessary to distinguish the core version of an app from its variations. **Example** The feature is available on the Outlook desktop, Outlook on the web, and Outlook.com.
+
+**See also** Computer and device term collection
+
+### destination drive, destination file
+
+Avoid. If you can, use more specific language, such as *copy the file to OneDrive.* Don't use *target drive* or *target file*.
+
+### destination
+
+Use a more precise term, such as *website* or *folder,* to describe an end point, such as the location reached when a customer clicks a link, the folder to which a file is copied or moved, or the document in which a linked or embedded object is stored. Use *destination* as a modifier only if necessary for clarity.
+
+Don't use *target* as a synonym.
+
+### device driver, driver
+
+Use *device driver* only in the context of a driver development kit (DDK) or in a general discussion about installing peripheral devices. If you're referring to a driver for a specific device, refer to the driver for that device, such as *mouse driver* or *printer driver*.
+
+In content for a general audience, define *driver* on the first mention.
+
+**See also** Computer and device term collection
+
+### device
+
+**See** Computer and device term collection
+
+### DevOps
+
+Note spelling and capitalization.
+
+### dial-up
+
+Use only as an adjective (as in *dial-up connection*), not as a noun or verb. Always hyphenate.
+
+Use *dial* as the verb to refer to placing a call or using a dial-up device.
+
+### dialog box, dialog, dialogue
+
+In general, avoid talking about UI. Instead, talk about what the customer needs to do.
+
+When you need to refer to a dialog box, use *dialog*. Don't use *pop-up window*, *dialog box*, or *dialogue box*.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### different
+
+Don't use *different* to mean *many* or *various*.
+
+In comparisons, use *different from* most of the time. Use *different than* only when *than* is followed by a clause. Don't use *different to*.
+
+**Examples** The result of the first calculation is different from the result of the second. If the result is different from the result that you expected, verify that you entered your data correctly.
+
+Make sure comparative statements that use *different* are parallel. Read them carefully to make sure they mean what you intended.
+
+**Example** The result of the first calculation is different from the result of the second.
+
+Sentences that use *different than* are often difficult to read, even if they're grammatically correct. They work best when the clauses on both sides of the comparison are balanced and parallel. If it's difficult to make them parallel, consider rewriting.
+
+**Example** The regional setting doesn't match the language of the localized version of the operating system.
+
+### dimmed
+
+Most of the time, talk about the actions that customers should take rather than describing UI.
+
+Don’t use to describe commands or options that are in an unusable state—use *not available* or *isn’t available* instead. It’s OK to use *appears dimmed* if you must describe their appearance. Use *shaded* to describe the appearance of checkboxes that represent a mixture of settings.
+
+**Examples** The command isn't available until you select text. If the option appears dimmed, it's not available. Selected effects appear shaded.
+
+**See also** disable, disabled, unavailable
+
+### direction keys
+
+**See** Keys and keyboard shortcuts term collection
+
+### directory
+
+Most of the time, use *folder* instead. Use *directory* only in content for developers when you need to refer to the structure of the file system or to match the API.
+
+Don't use *directory icon.*
+
+**See also**  folder
+
+### disable, disables, disabled (functionality)
+
+In descriptions of product functionality, avoid *disable*, *disables*, and *disabled* to prevent an association with accessibility terms.
+
+Don't use *disable* to describe making a feature, setting, command, or function available, unless you need to match the UI. Use *turn off*.
+
+Don't use *disabled* to describe the state of a feature, setting, command, or function, unless you need to match the UI. Use *off*, *turned off*, or *not available*.
+
+In UI, avoid using **Enable**/**Disable** as labels for a toggle that controls availability. Use **On**/**Off**, if those words are accurate for the feature or capability. Or use more specific words, such as **Show**/**Hide**, **Add**/**Remove**, or **Allow**/**Block**.
+
+**Example** If the command prompt isn't available, your network administrator might have turned off this feature.
+
+**See also** Accessibility term collection turn on, turn off disabled (person).md) unavailable enable, enables
+
+### disabled (person)
+
+Don’t use *disabled* to refer to people with disabilities, unless you know that a specific audience prefers otherwise. Use *person with a disability* or a more specific, people-first term like *person with low vision*. 
+ 
+For more details on exceptions to this guideline, see [Accessibility term collection](/style-guide/a-z-word-list-term-collections/term-collections/accessibility-terms)  
+
+**See also** [Accessibility guidelines and requirements](/style-guide/accessibility/accessibility-guidelines-requirements)
+### disc
+
+**See** Computer and device term collection
+
+### disjoint selection
+
+Don't use except in content for a technical audience, and only if the term appears in the UI or API.
+
+If you need to describe nonadjacent selected items, use *multiple selection* or list the specific items.
+
+**See also** multiple selection
+
+### drive resource
+
+Use to refer to a drive or part of a drive shared on a server.
+
+### disk space
+
+In general, avoid. Use *storage* or *storage space* to refer to available capacity on a drive.
+
+When referring to storage in a partition of space, mention it specifically and use *drive* instead of *disk*.
+
+**Example**
+
+Storage in local drive (C:)
+
+**See also** storage, storage space
+
+### disk
+
+**See** Computer and device term collection
+
+### display adapter, display driver
+
+Don't use. Use *video card* and *video driver* instead.
+
+### display
+
+**See** Computer and device term collection
+
+### DNS
+
+Spell out as *Domain Name System,* not *Domain Name Server.* When discussing the DNS networking protocol, spell out *Domain Name System* on the first mention. When discussing the Windows DNS feature, don't spell out *DNS.*
+
+The Windows feature is *DNS,* not *DNS Server* or *Microsoft DNS Server.* If you must emphasize that you're referring to the Windows feature and not to the networking protocol, mention Windows.
+
+Don't use *dynamic DNS* or *DDNS.*
+
+A DNS server (lowercase *s*) is a computer that's running DNS server software. DNS Server (capital *S*)
+is the Windows service that appears in the Computer Management console.
+In general, refer to the service only in a discussion about
+stopping and starting it.
+
+A DNS client (lowercase *c*) is a client of a DNS server. DNS Client (capital *C*)
+is the Windows service that appears in the Computer Management console.
+In general, refer to the service only in a discussion about stopping
+and starting it.
+### document
+
+Use for text files, such as files created in Word.
+
+To refer to any editable file located in a folder, use a more specific word, such as *workbook, presentation,* or *database,* if you can. Precede the descriptive word with a product name, such as *PowerPoint presentation,* when you need to distinguish a file created in a certain product from files created in other products.
+
+Use *file* for more general uses, such as *file management* or *file structure,* or references to files of mixed types.
+
+### domain
+
+*Domain* has different meanings in database design, Windows, and internet addresses. Define the term on the first use, if necessary, to make sure the meaning is clear.
+
+### dot-com
+
+Don't use.
+
+### dotted rectangle
+
+Use only if you need to describe the appearance of the element that a customer drags to select a region on the screen. Otherwise, use *bounding outline* (not *marquee*) instead.
+
+**See** bounding outline
+
+### double buffering
+
+Two words as a noun.
+
+Hyphenate as an adjective.
+
+Don't use as a verb. Instead, use a phrase such as *uses double buffering*<em>.</em>
+
+### double-click, double-clicking
+
+See Mouse and mouse interaction term collection
+
+### downgrade
+
+Use only if necessary to express the concepts of downgrade rights, downgrading licenses, downgrading products, downgrading files, and similar subjects. Use only in content for an audience that will understand your use of the word in those contexts.
+
+### download
+
+Use *download* to describe the intentional transfer of data and files to a system or device. Use *install* to describe adding apps, hardware, and drivers to a device.
+
+When you use *download* as a verb, describe what the customer is transferring *and* where the customer is transferring it *to.*
+
+Don't use *download* to describe the process of opening, viewing, or switching to a webpage.
+
+It's OK to use *download* as a noun to describe data or a file that's available for downloading or that has been downloaded.
+
+In your writing, make sure it's clear whether *download* is used as a noun or verb.
+
+**Examples**<br />Install the app.<br />To learn more about integrating data security across your enterprise, download the poster to your device.
+
+**See also** <br />install<br />load<br />upload
+
+### drag, drag and drop
+
+Don't use *drag and drop* except as an adjective to describe behavior that a programmer puts in a program, such as *drag-and-drop editing* or *drag-and-drop feature*. Use *move* or *drag* instead.
+
+Don't use *click and drag.* It's OK to use *press and drag* to teach mouse techniques in content that teaches beginning skills.
+
+**See also** Describing interactions with UI
+
+### drill down, drill up, drill through
+
+It's OK to use *drill down, drill up,* and *drill through* in content about data and the reports generated from them.
+
+Two words as a verb. Hyphenate *drill-down* and *drill-up* as adjectives. Note that *drillthrough* as a noun or an adjective is one word, no hyphen.
+
+**Examples** If you have grouped items in your PivotTable, you can drill down on a group name. Then, you can drill back up to analyze summary data. Using drill-down and drill-up actions, you can expand and collapse sections within a report to find the data that interests you the most. If you add the ability to drill through on an existing mining model, the model must be reprocessed before you can drill through to the data. Use a drillthrough query to retrieve details from the underlying cases or structure data. Drillthrough is useful if you want to see additional details from the case data.
+
+Don't use to mean following a path (such as folders) or giving something further examination.
+
+**Example** Microsoft MVPs joined an in-depth discussion about Azure security management solutions.
+
+### drive name
+
+Use instead of *drive specification, designator,* or *designation*.
+
+### drive
+
+**See** Computer and device term collection
+
+### dropdown
+
+Most of the time, avoid talking about UI elements. Instead, describe what the customer needs to do. If you must refer to a *dropdown* menu or list, it’s OK to use *dropdown* as an adjective. Avoid using *dropdown* as a noun. (Like as a UI label: *Dropdowns*.)
+
+**Examples** Pick from the options in the dropdown list.
+
+Use the dropdown menu to find the category you want.
+
+**See also** Describing interactions with UI, Formatting text in instructions, Computer and device term collection
+
+### DVD
+
+Don't spell out *DVD*. If you refer to a DVD as a *disc,* use the correct spelling.
+
+Most of the time, use *DVD* by itself. If you need to be specific, it's OK to use *video DVD, audio DVD, DVD-ROM, DVD-R, DVD-RAM,* or *DVD-RW.*
+
+Refer to the drive for a DVD as the *DVD drive,* not the *DVD player*.
+
+Don't use *DVD disc,* *DVD-ROM disc,* or other redundant phrases.
+
+### dynamic-link library (DLL)
+
+Spell out on the first mention unless you're positive that your audience knows the term. On subsequent mentions, use the abbreviation *DLL*. Use *.dll* (lowercase with a period) to refer to the file name extension.
+
+Don’t use *dynalink*.
+
+### dynamic service capacity
+
+**See** Cloud-computing term collection
+
+## E
+
+### e-book
+
+Always hyphenate. Don't use *ebook* or *eBook.*
+
+Use *E-book* at the beginning of a sentence or heading. In uncommon situations where title-style capitalization is required, use *E-Book*.
+
+**See also** Capitalization
+
+### e-commerce
+
+Always hyphenate. Don't use *ecommerce* or *eCommerce*.
+
+Use *E-commerce* at the beginning of a sentence or heading. In uncommon situations where title-style capitalization is required, use *E-Commerce*.
+
+**See also** Capitalization
+
+### e-discovery
+
+Always hyphenate. Don't use *ediscovery* or *eDiscovery.*
+
+Use *E-discovery* at the beginning of a sentence or heading. In uncommon situations where title-style capitalization is required, use *E-Discovery*.
+
+**See also** Capitalization
+
+### e-form, form
+
+Don't use *e-form.* Use *form* instead.
+
+### e-learning
+
+Always hyphenate. Don't use *elearning* or *eLearning.*
+
+Use *E-learning* at the beginning of a sentence or heading. In uncommon situations where title-style capitalization is required, use *E-Learning*.
+
+**See also** Capitalization
+
+### e-sports
+
+Always hyphenate. Don't use *esports* or *eSports.*
+
+Use *E-sports* at the beginning of a sentence or heading. In uncommon situations where title-style capitalization is required, use *E-Sports.*
+
+**See also** Capitalization
+
+### e-words
+
+Don't create new words with *e-* (for *electronic*).
+
+It's OK to use e-words, such as *e-book* and *e-commerce,* that are included in this guide and in *Merriam-Webster Dictionary.*
+
+Almost all e-words are hyphenated. *Email* is an exception.
+
+Lowercase the *e* in body text, and capitalize the *E* at the beginning of a sentence or a heading. The letter following the hyphen is capitalized only when title-style capitalization is required, which is rare in Microsoft content.
+
+**Examples** (Sentence-style capitalization) E-commerce and security (Title-style capitalization) Strategic E-Commerce Systems and Tools for Competing in the Digital Marketplace
+
+**See also** Capitalization
+
+### earlier
+
+If possible, use a hyperlink to help users find information elsewhere in the content. If you can't use a link, use *earlier, preceding,* or *previous* instead of *above* to mean earlier in a piece of content.
+
+Use *or earlier* or *previous* instead of *or lower* to refer to all versions of a product that precede a particular release if the statement is accurate for all preceding releases. For example, don't use *Windows 10 or earlier* unless the statement is accurate for Windows 1.0.
+
+**Example** You can open files created in previous versions of Microsoft Visio. (If you can open files in every version of Visio including and previous to the version being discussed.)
+
+**See also**  later
+
+### edutainment
+
+Don't use.
+
+### e.g.
+
+Don't use. Use *for example, such as,* or *like,* as appropriate.
+
+**Examples** There are some legitimate business reasons for spoofing—for example, an assistant might need to send email for another person within your organization. The template can work for different environments, such as testing, staging, and production. Learn how to use infrastructure automation tools, like Packer and Azure Automation, to manage Azure virtual machines.
+
+### either/or
+
+Don't use. Use a complete phrase, such as *either close the document or close the program*.
+
+### elastic service capacity
+
+**See** Cloud-computing term collection
+
+### ellipsis button
+
+The name of the ellipsis button varies, based on the result of using it. 
+
+![Screenshot of the square blue ellipsis icon.](/style-guide/a-z-word-list-term-collections/e/media/ellipsis-button/447573893.png)
+
+On the first mention, provide a graphic of the button or include (…) after the button name. On subsequent mentions, use the graphic rather than the words. 
+
+Don't capitalize *ellipsis* when used as a button name.
+### email
+
+Use to refer generically to an electronic mail program, to refer collectively to email messages, or to refer to individual email messages. If necessary to distinguish these meanings, use *email message* or *message* to refer to an individual piece of email. Make sure it's clear that you're not referring to instant messaging. After you have established the context of electronic mail, it's OK to use *mail* instead of *email*.
+
+It's OK to use *email* as a verb.
+
+**Global tip** In some languages, the translation of *email* is different for noun and verb forms. If you use *email* as a noun, provide enough context that localizers can identify its role in the sentence. For example, write *send an email,* which positions *email* after a verb and an article, where a noun is expected. In contrast, *Email* used by itself as a heading could be a noun or a verb.
+
+Use *Email* at the beginning of a sentence or heading. Never hyphenate *email* or capitalize the *m.*
+
+**Examples** You have two new emails. Scroll through email to find the message you want to read. You have new mail. Email us your comments.
+
+**See also** message
+
+### embed
+
+Use instead of *imbed*.
+
+### emoji, emoticons
+
+An *emoji* (plural *emoji*) is a small image that represents an emotion, concept, or object. Examples include :grinning: and :frowning_face:.
+
+An *emoticon* is a combination of keyboard characters that expresses an emotion or attitude. Examples include <span role="img" aria-label="colon, closing parenthesis">:)</span> for a smiling face and <span role="img" aria-label="colon, opening parenthesis">:(</span> for a frowning face.
+
+In social media posts and informal communications, emoji and emoticons add personality and can help communicate meaning and tone.
+
+Use emoji instead of emoticons. Emoji are better for accessibility because:
+
+- Every emoji has a type of alt text that screen readers can read out to users.
+- Screen readers don't interpret the combination of characters in an emoticon. Instead, they try to process the characters literally, ignore them, or indicate their presence only through a pause.
+
+However, not all screen readers support emoji. Always ensure that your intended meaning and tone get across without them.
+
+### General guidelines for emoji use
+
+Follow these guidelines to use emoji in a way that's effective, positive, and accessible:
+
+- Don't use emoji in content that's related to a serious topic. They might make the topic seem unserious or trivial.
+- Don't use emoji in place of words.
+- Don't use emoji in the middle of a sentence. Put them at the end of the sentence. Even better, put them at the end of the paragraph, message, or post.
+- To keep emoji from losing their impact, don't overuse them.
+
+A general rule is to use a maximum of three emoji per message or post. Use a maximum of three emoji in a row, and always put a space between them.
+- Don't use emoji at the beginning of consecutive lines to simulate bullets in a list.
+- Don't embed emoji (or emoticons) in images.
+- Don't use emoji in profile names.
+
+### Guidelines for choosing emoji
+
+- **Limit yourself to popular emoji that are widely recognized and understood**. Avoid ambiguous and obscure emoji.
+
+- **Ensure that the literal and figurative meanings of an emoji reflect your intended meaning**. The literal meaning of every emoji is provided by a string that's called the *Common Locale Data Repository (CLDR) short name* or *Unicode name*. Screen readers use this name as alt text.
+
+In addition to its literal meaning, an emoji might have one or more figurative meanings. Make sure that both types of meaning are consistent with what you're trying to convey.
+
+**Tip** You can find the CLDR short name for every emoji on sites such as Unicode.org and Emojipedia.org.
+
+- **Consider potential cultural and diversity implications, and avoid any emoji that might be inappropriate**. The connotations of an emoji can vary across cultures and communities. What one group considers innocent, friendly, or humorous might be offensive to another group. To learn more, see Bias-free communication and Global communications.
+
+**Note** Emoji (and emoticons) might be removed from localized versions of your content.
+
+- **When you feel you can, use the standard version of emoji**. Custom emoji that represent different skin tones are great for inclusiveness, but they can have longer alt text and take longer for screen readers to read.
+
+- **Use emoji that work across devices**. The appearance of an emoji can vary across platforms and devices. Websites such as Emojipedia.org show the variations of each emoji. Avoid emoji that might appear to users in a form that changes or undermines your intended meaning.
+
+### enable, enables, enabled
+
+Avoid using *enables* (or *allows* or *lets*) to refer to things that technology makes possible for the customer. Rewrite to focus on what's important or possible from the customer's point of view. For example, use "Write, draw, and take notes on webpages by using Microsoft Edge" instead of "Microsoft Edge enables you to write, draw, and take notes on webpages."
+
+Don't use *enable* to describe making a feature, setting, command, or function available, unless you need to match the UI. Use *turn on*.
+
+Don't use *enabled* to describe the state of a feature, setting, command, or function, unless you need to match the UI. Use *on*, *turned on*, or *available*.
+
+In UI, avoid using **Enable**/**Disable** as labels for a toggle that controls availability. Use **On**/**Off**, if those words are accurate for the feature or capability. Or use more specific words, such as **Show**/**Hide**, **Add**/**Remove**, or **Allow**/**Block**.
+
+**Example** After your administrator turns on the feature, verify that the button is available.
+
+**See also** disable, disables, disabled (functionality) turn on, turn off
+
+### End-User License Agreement (EULA)
+
+Don't use. Use *Microsoft Software License Terms*.
+
+**See also**  Microsoft Software License Terms
+
+### end
+
+Use as a verb to describe stopping communications and network connections. Use *close* for apps and programs.
+
+**Example** To end your server connection, go to **Tools** and select **Disconnect Network Drive**.
+
+**See also** Describing interactions with UI
+
+### endline
+
+One word.
+
+### endpoint
+
+One word.
+
+### ensure, insure, assure
+
+*Ensure, insure,* and *assure* are interchangeable in many situations. To improve worldwide readability, Microsoft style makes these distinctions:
+
+  - Use *ensure* to mean *to make sure* or *to guarantee*. 
+  - Use *insure* to mean *to provide insurance*. 
+  - Use *assure* to mean *to state positively* or *to make confident*.
+
+### enter
+
+**See** Describing interactions with UI
+
+### enterprise
+
+It's OK to use *enterprise* for an IT pro or developer audience to mean a *large company* or *corporation*. Use as an adjective if possible, as in *enterprise computing* or *enterprise deployment,* rather than as a noun to mean *corporation*.
+
+Don't use in content for a general audience.
+
+**See also** company vs. organization
+
+### entry field
+
+Don't use to refer to a text-entry field. Refer to the box by its label. If you must use a descriptor, use *box*.
+
+It's OK to use *entry field* in a database context.
+
+### environment variable
+
+An *environment variable* contains configuration information that can be referenced by anything in the environment.
+
+### erase
+
+Don't use as a synonym for *delete* unless the app requires it, as in Paint.
+
+**See also** delete
+
+### et al.
+
+Don't use except in a citation that includes three or more authors. Use *and others* instead.
+
+### etc.
+
+Don't use. Instead be specific. When space is limited, use *such as* or *like* followed by an example or two.
+
+**Examples** Body text is most readable in Times New Roman, Palatino, and other serif fonts. (Not *Body text is most readable in Times New Roman, Palatino, etc.*) Body text is most readable in serif fonts like Palatino.
+
+### euro
+
+Lowercase.
+
+Plural: *euros*
+
+Symbol: €
+
+In US content, place the euro symbol in front of the amount. Different locales might place the euro symbol elsewhere, as appropriate. A euro is divided into 100 *cents.* When expressing an amount in euros and cents in US content, use a decimal point. Different locales might use a decimal point or a comma, as appropriate.
+
+**Example** €3.50
+
+Use *supports the euro currency standard* to refer to a country's use of the euro.
+
+Use the following phrases to refer to countries that have adopted the euro as their currency:
+
+  - European Union (EU) members trading in euros 
+  - European Union (EU) members that have adopted the euro 
+  - euro nations 
+  - members of the Economic and Monetary Union (EMU) 
+
+Use references to the EMU cautiously. Some people aren't familiar with the organization.
+
+**Note** On subsequent mentions, it's OK to use the abbreviations *EU* and *EMU.* It's also OK to refer to EU members as *EU member states* and to EMU members as *EMU member states.*
+
+Use *non-euro nations* to refer to EU member states that haven't adopted the euro as their currency.
+
+The terms *euroland* and *eurozone* are OK to use on websites with an informal tone. Don't use these terms in product documentation or other formal contexts, especially if the content will be localized.
+
+**See also** Currency
+
+### executable, .exe
+
+Use *executable* and *.exe* as adjectives, not nouns. Use *an,* not *a,* as the article preceding .exe: *an .exe file.*
+
+**Examples** an executable program the .exe file
+
+Use *executable file* only in content for a technical audience. For a general audience, use *program file* instead.
+
+### execute
+
+Don't use except to follow the UI. Use *run* instead. Even if the UI includes *execute,* the action is *run*. Always use *run* in the context of macros and queries.
+
+**Examples** To run the program, select **Execute**. Commands are run in the order in which they're listed in the file. A thread is the basic unit of program execution.
+
+### exit
+
+Don't use to describe closing an app or program.
+
+**See** Describing interactions with UI
+
+### expand, collapse
+
+Use to describe a customer action that displays more or fewer subentries in a folder or outline.
+
+**Example** To expand the folder, select the plus sign (+).
+
+### expose
+
+Don't use in content about UI. Use *make available,* *display,* or a similar term.
+
+It's OK to use *expose* in content about object-oriented programming technologies, such as the Component Object Model (COM), to describe making an object's services available to clients.
+
+### extend
+
+Use *extend* instead of *grow* to refer to extending a selection.
+
+### extension, file name extension
+
+Use instead of *file extension*.
+
+**Examples** the .bak extension the .bak file name extension
+
+## F
+
+### FALSE
+
+In content for developers, use all uppercase to refer to a return value, or follow the capitalization used in the specific programming language.
+
+### fail over, fail back, failover, failback
+
+Two words as a verb, one word as an adjective or a noun. Don't use in content for a general audience.
+
+**Examples** failover cluster a planned failover Follow these instructions to fail back your servers after they've failed over to Azure.
+
+### fail
+
+In content for a general audience, use only to refer to disks and other hardware. Use *stop responding* to refer to programs or the operating system.
+
+It's OK to use *fail* in content for a technical audience to describe an error condition. For example, E_FAIL is a common return value in COM programs. A function that returns E_FAIL has failed to do something.
+
+**Example** Back up your files to safeguard them against loss if your hard drive fails.
+
+**See also** stop, stop responding
+
+### family
+
+Use instead of *line* to refer to a set of related Microsoft products or services.
+
+### Far East
+
+Don't use to refer to the geographic region of East Asia. Use *East Asia* or *Asia* instead.
+
+### far-left, far-right
+
+Don't use. Use *leftmost* or *rightmost* instead.
+
+**Accessibility tip** Don't use directional terms (*left, right, up, down*) as the only clue to location. Individuals with cognitive disabilities might have difficulty interpreting them, as might people who are blind and use screen-reading software. It's OK to use a directional term if another indication of location, such as *in the* ***Save As*** *dialog box, on the* ***Standard*** *toolbar,* or *in the title bar,* is also included. Directional terms are also OK to use when a sighted user with dyslexia can clearly see a change in the interface as the result of an action, such as a change in the right pane when an option in the left pane is selected.
+
+### favorite
+
+Use to refer to a webpage or site the customer may want to return to later in Microsoft Edge or Internet Explorer. Customers save favorites to the Favorites menu. Use lowercase when referring to a favorite website, and capitalize the menu name. Avoid using as a verb.
+
+**Examples** Select **Add to favorites** to add a website to the **Favorites** menu. Go to the **Favorites** menu to see your list of favorite websites.
+
+### fax
+
+Lowercase. Abbreviation for *facsimile*. It's OK to use *fax* as an adjective (*fax machine*, *fax transmission*), as a noun (*your fax arrived*), or as a verb (*fax a copy of the order*).
+
+### field
+
+Don't use to refer to a text-entry box. Refer to the box by its label. If you must use a descriptor, use *box* instead of *field*.
+
+It's OK to use *field* to refer to Word field codes, in a database context, and in other technical contexts.
+
+### file attributes
+
+Use lowercase for file attributes such as *hidden,* *system,* *read-only,* and *archive*.
+
+### File Explorer
+
+Use instead of *Windows Explorer.* Don't use an article, such as *the,* to precede *File Explorer.* Don't shorten to *Explorer.*
+
+### file name extension, extension
+
+Use instead of *file extension*.
+
+**Examples** the .bak extension the .bak file name extension
+
+### file name
+
+Two words as an adjective or a noun when referring to the name of a file. Don't hyphenate.
+
+Usually one word when referring to a programming term, such as the **FileName** property.
+
+**Example** Set the **FileName** property before you set an initial file name.
+
+### file
+
+Try to use a more specific term, such as *document* (Word), *workbook* (Excel), or *presentation* (PowerPoint).
+
+It's OK to use *file* to discuss units of storage or file management or to refer to files of mixed types.
+
+### finalize
+
+Don't use. Use *finish* or *complete* instead.
+
+### find and replace
+
+Use *find* and *replace* as separate verbs, not as a single verb phrase. Don't use *find and replace* or *find-and-replace* as a noun or an adjective.
+
+**Examples** Find the word *gem,* and replace it with *diamond*. Search through your document, and replace *cat* with *dog*.
+
+Don't use *global* to describe finding and replacing. Use *all instances* or *all occurrences* instead.
+
+**Examples** Find all occurrences of the word *gem,* and replace it with *diamond*. Search through your document, and replace all instances of *cat* with *dog*.
+
+Use *find characters* and *replacement characters* to describe what the customer enters into a find or replace box.
+
+### first line, first-line
+
+Two words as a noun. Hyphenate as an adjective.
+
+**Examples** The XML declaration typically appears as the first line in an XML document. Help your first-line workers to perform more efficiently.
+
+### fitness band
+
+**See** Computer and device term collection
+
+### fixed disk
+
+**See** Computer and device term collection
+
+### flick
+
+**See** Touch and pen interaction term collection
+
+### flush, flush to
+
+In content for a general audience, don't use *flush, flush to, flush left,* or *flush right* to describe text alignment. Instead, use *even, left-aligned,* or *right-aligned,* as appropriate.
+
+In content for a technical audience, it's OK to use *flush* as a verb, for example, *flush the buffer*.
+
+### flyout
+
+Don’t use in content for a general audience. Instead, describe what the customer needs to do.
+
+It’s OK to use *flyout* as an adjective in content for a technical audience if you need to describe a transient UI element that displays settings or information related to what the customer is doing.
+
+**Examples** flyout menu flyout message flyout control
+
+Avoid using *flyout* as a noun (for example, “the flyout appears”). Don’t use as a verb (for example, “the menu will fly out”).
+
+### folder, folder icon
+
+In general, try not to talk about UI. Instead, talk about what the customer should do.
+
+In content about Windows, use *folder* to refer to a container for files and other folders. Use *directory* only in content for developers when you need to refer to the structure of the file system or to match the API. For MS-DOS, use *directory*.
+
+Use *folder icon* to describe the visual representation of a folder. Don't use *directory icon.*
+
+**Note** Not all folders contain files or other folders. For example, the Printers and Control Panel apps are also folders. Describe the nature of the folder, if necessary.
+
+In instructions, use bold formatting for the folder name if you're directing the customer to select, type, or otherwise interact with the name.
+
+**Examples**<br />You can find the file on your hard drive in C:\\Windows\\System\\Color. <br />You can find the file on X:\\Windows\\System\\Color. <br />You can find the file in the Color folder. <br />The system files are in the System subdirectory in the Windows directory. <br />Select the **Windows** folder.<br />Select **Documents**, and then select the file you want.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### following
+
+In text that introduces art, a code block, a list, or a table, you can use *the following*, *this* (for one item) or *these* (for multiple items), followed by a noun. Don't use *below*.
+
+**Examples** The following table compares the rates. The administrator has these permissions:
+
+**See also** earlier later Lists
+
+### font, font style
+
+Use *font,* not *typeface,* for the name of a typeface design such as Times New Roman or Segoe UI.
+
+Use *font style,* not *type style,* to refer to the formatting, such as bold, italic, or small caps, and *font size,* not *type size,* for the point size, such as 12 points or 14 points.
+
+When referring to bold formatting, use *bold,* not *bolded, boldface,* or *boldfaced.* When referring to italic formatting, use *italic,* not *italics* or *italicized*.
+
+**Example** Select the bold characters, and then select **Bold** to remove bold formatting.
+
+In writing for customers, use *regular type* to describe type that's neither bold nor italic.
+
+For information about when to use various font styles, see Text formatting.
+
+### foo, foobar, fubar
+
+Don't use *fubar*.
+
+Don't use *foo,* *foobar,* or related words in content for a general audience. It's OK to use these words as placeholders or variable names in content for a technical audience, but if you can, use another placeholder instead, such as *Example.exe*.
+
+### footer
+
+In content related to word-processing and publishing apps, use instead of *bottom running head* or *running foot* when discussing page layout. It's OK to use *running foot* as a synonym in keyword lists.
+
+**See also** header
+
+### foreground program
+
+In content for a technical audience, use instead of *foreground process*.
+
+### format, formatted, formatting
+
+Use *format* to refer to the overall layout or pattern of a document.
+
+Use *formatting* or *formatted* to refer to specific character formatting, paragraph formatting, and other types of formatting.
+
+**See also** font, font style
+
+### fourth-generation language
+
+Spell out on the first mention. On subsequent mentions, it's OK to abbreviate as *4GL*.
+
+### frameset
+
+Use only in content for developers.
+
+Use *frames* to refer to the independently scrollable regions on a webpage.
+
+Use *frameset document* to describe the HTML document that describes the frame layout in a frames page.
+
+Use *frames page* to describe the page itself, but don't use this term in content for a general audience. In general discussions, use *frames*.
+
+### freeze, frozen
+
+Don't use *freeze* as a synonym for *stop responding*. Don't use *frozen* to describe the resulting state.
+
+**See also** stop, stop responding
+
+### friendly name
+
+Don't use. Use *display name* instead to refer to a person's name as it appears in an address or email list.
+
+### from vs. on
+
+Use *from* to indicate a specific place or time as a starting point.
+
+**Examples** Paste the text from the clipboard. From the time you set the clock, the alarm is active.
+
+Use *on* to indicate the starting place for selecting a command or option.
+
+**Example** On the **File** menu, select **Open**.
+
+### front end, front-end
+
+In content for a general audience, don't use as a synonym for the desktop interface to a database or server. Instead, refer to the program by name, or use a term like *interface*, *program*, or *app*.
+
+In content for a technical audience, it's OK to use *front end* (noun) and *front-end* (adjective that precedes a noun) if it's necessary for accuracy.
+
+**Examples** The server sends information to the web interface. Front-end applications call back-end APIs.
+
+### full screen, full-screen
+
+Two words as a noun. Hyphenate as an adjective before a noun. **Examples** full-screen display To make the display full screen …. Full screen (in the UI)
+
+### function
+
+Don't use to mean *application programming interface (API)*.
+
+Don't use *API* to mean *function*.
+
+**Examples** A RESTful API uses HTTP requests to get, put, post, and delete data. Every C++ program has at least one function, which is **main()**.
+
+## G
+
+### gallery
+
+Don't use to mean a marketplace or store.
+
+It's OK to use *gallery* to refer to a collection of pictures, charts, graphics, templates, components, or other items that the customer can select from. Use the verb *select* for items in a gallery.
+
+**Example** Select a picture from the gallery.
+
+**See also** store, marketplace, gallery
+
+### game pad
+
+Two words.
+
+### garbage collection, garbage collector
+
+OK to use in content for a technical audience to refer to the automatic recovery of heap memory or to the automatic deletion of objects that the runtime environment determines are no longer being used.
+
+Use *garbage collector* to describe the component of a runtime environment that performs garbage collection.
+
+### General Data Protection Regulation (GDPR)
+
+Capitalize and spell out on the first mention. 
+
+Include *the* when used as a noun. When *General Data Protection Regulation* or *GDPR* is used as an adjective, include *the* if the syntax of the sentence requires it.
+### general protection fault, GP fault
+
+Spell out on the first mention. On subsequent mentions, it's OK to abbreviate as *GP fault*.
+
+### gigabit, Gbit
+
+**See** Bits and bytes term collection
+
+### gigabyte, GB, G, G byte, Gbyte
+
+**See** [Bits and bytes term collection](/style-guide/a-z-word-list-term-collections/term-collections/bits-bytes-terms)
+
+*GB* is also the abbreviation for *Great Britain* (England, Scotland, and Wales). Don't use *United Kingdom (UK),* *Great Britain (GB),* and *England* interchangeably.
+### gigahertz, GHz
+
+**See** Units of measure term collection
+
+### given
+
+Don't use to mean *specified, particular,* or *fixed*.
+
+**Examples** Look in the specified folder. Use the **Find**  command to search for all occurrences of a specific word. The meeting is always at a particular time.
+
+### global
+
+It's OK to use *global* to mean *worldwide*.
+
+In content for a technical audience, use *global* to refer to:
+
+  - Memory that's accessible to more than one process.
+  - A variable whose value can be accessed and modified by any statement in a program. This is called a *global variable.* 
+  - Similar elements that pertain to an entire program.
+
+Don't use *global* to describe the process of finding and replacing. Instead, describe the action or use *all instances* or *all occurrences.*
+
+**Examples** Use the **Find** and **Replace** commands to find all occurrences of specific text and replace it with different text. The manufacturer is using Office 365 to expand its global supply chain.
+
+**See also** worldwide vs. international
+
+### glyph
+
+Don't use to refer generically to a graphic or pictorial image 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.
+
+### go to
+
+**See** Describing interactions with UI
+
+### graphic, graphics, graphical
+
+As a noun, use *graphic* to refer to a picture, display, chart, or other visual representation.
+
+Use *graphics* to refer in general to pictures, displays, charts, and other visual representations using computers. For example, *graphics software.*
+
+Most of the time, use *graphical* as an adjective. Use *graphic* as an adjective only to mean vivid or realistic or in the phrase *graphic arts.*
+
+**Examples**<br />To import a graphic from another file, select **Picture**.<br />Select the graphics file you want to open. <br />The image is graphic and accurate.<br />This course provides graphic design basics.<br />The graphical UI simulates a coliseum.
+
+### graphics adapter
+
+Don't use. Use *video card* instead.
+
+### gray, grayed out
+
+Most of the time, talk about the actions that customers should take.
+
+Don’t use *gray* or *grayed out* to describe commands or options that are in an unusable state—use *not available* or *isn’t available* instead. Use *appears dimmed* if you must describe their appearance. Use *shaded* to describe the appearance of checkboxes that represent a mixture of settings.
+
+**Examples** The command isn’t available until you select text. If the option appears dimmed, it's not available. Selected effects appear shaded.
+
+**See also** disable, disabled, unavailable
+
+### greater, better
+
+Don't use *greater* or *better* to mean *or later* when identifying multiple versions of programs or apps.
+
+**See** later
+
+### greylist
+
+Note spelling.
+
+Use only to discuss the spam-reduction technique in which mail from an unknown sender is rejected by the server, and an SMTP response tells the client to try again later.
+
+### gridline
+
+One word.
+
+### group box
+
+Two words.
+
+Most of the time, avoid talking about specific UI elements. Instead, talk about what the customer needs to do.
+
+When you need to refer to a group box for a general audience, don't include the words *group box*. Just refer to the name of the group box.
+
+**Example** Under **Effects**, select **Hidden**.
+
+It's OK to use *group box* in content for a technical audience.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### group, newsgroup
+
+Use *newsgroup,* not *group,* to refer to an internet discussion group that focuses on a particular topic.
+
+### grow
+
+Don't use as a verb meaning to increase the size of something. Use a more specific verb.
+
+**Examples** If you want to increase your business .... To extend the selection ....
diff --git a/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-h-m.md b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-h-m.md
new file mode 100755
index 000000000..2ff4fff13
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-h-m.md
@@ -0,0 +1,1247 @@
+# A-Z word list: h-m
+
+Alphabetical Microsoft style guidance for individual words and terms. Each entry gives preferred usage, prohibited usage, and notes.
+
+## H
+
+### hack, hacker
+
+**See** Security term collection
+
+### half inch
+
+Hyphenate as an adjective. Use instead of *half an inch* or *one-half inch*. When space is limited or the measurement needs to be specific, use *0.5 in*.
+
+**Global tip** Be careful when using abbreviations or acronyms that form English words. Machine translation might incorrectly translate the abbreviation *in.* as the word *in*.
+
+**See also** Units of measure term collection
+
+### handheld, handheld device
+
+**See** Computer and device term collection
+
+### handle
+
+When you use *handle* to describe a token that's temporarily assigned to a device or object to identify and provide access to the device, insert a space between the word *handle* and the sequential number.
+
+**Examples** handle 0 handle 1 handle 2
+
+To describe a handle in UI that the customer uses to move or size an object, use *move handle* or *sizing handle*. Don't use *size handle, grab handle, little box,* or similar phrases.
+
+### handshake
+
+One word. In content for a general audience, briefly define the term on the first mention.
+
+**Example** Systems must use the same flow-control (or *handshake*) method. To determine whether the systems use the same handshake method ....
+
+### hang
+
+Don't use.
+
+Use *stop responding* to describe a situation in which a program encounters a problem and can’t close itself. (It's OK to mention *hang* to support search engine optimization.)
+
+**Example** If the application stops responding, or *hangs,* you might have to restart your computer.
+
+Use *close* to describe the action a program takes to close itself when it has encountered a problem and can’t continue.
+
+**Note** Sometimes the computer itself stops responding, and sometimes a program does. In messages, refer to the problem with precision and specificity.
+
+**See also** stop, stop responding
+
+### hard-code, hard-coded, hard-coding
+
+Always hyphenate.
+
+OK to use in content for a technical audience when writing about a routine or program that uses embedded constants (in place of more general input). Don't use in content for a general audience.
+
+### hard copy
+
+Two words. Use only as a noun.
+
+**Example** Scan a hard copy of a document and save it as a file.
+
+Don't use *soft copy.*
+
+### hard drive
+
+**See** Computer and device term collection
+
+### hard-of-hearing
+
+**See** Accessibility term collection
+
+### hardwired
+
+One word. Don't use in content for a general audience.
+
+### HDMI (High-Definition Multimedia Interface)
+
+Use only as an adjective.
+
+Use the abbreviation *HDMI* most of the time. It’s OK to spell out in parentheses on the first mention.
+
+Use *an* as an article with *HDMI.*
+
+**Examples** This monitor requires an HDMI cable. Connect the HDMI cable to the HDMI port on your TV.
+
+### he/she
+
+Don't use.
+
+**See** Bias-free communication
+
+### header
+
+In content related to word-processing and publishing apps, use instead of *running head* when discussing page layout. It's OK to use *running head* for clarification or as a keyword.
+
+Don't use *header* as a synonym for *heading*.
+
+In technical content, it's OK to use *header* as a short form of *file header,* as in *HTML header.*
+
+Don't use *header* as a synonym for *header file,* which refers to the file at the beginning of a program that contains definitions of data types and variables used by the program's functions.
+
+**See also** footer
+
+### heading
+
+Use instead of *head* or *header* to refer to the heading of an article or a section.
+
+**See also** Headings
+
+### hearing-impaired
+
+**See** Accessibility term collection
+
+### Help
+
+Most of the time, use just *Help.* Don't use *online Help* unless you need to describe the Help system. Capitalize when referring to a Help system within a product.
+
+It's OK to use *definition Help, context-sensitive Help,* and *online Help files* to describe the Help system itself or to explain how to develop a Help system.
+
+**Example** Word Help
+
+### hexadecimal
+
+Don't abbreviate as *hex*. Use *h* or *0x* when abbreviating a number. Don't insert a space between the number and *h,* and use all uppercase for alphabetical characters displayed in hexadecimal numbers.
+
+**Examples** Interrupt 21h
+
+addresses greater than 0xFFFE
+
+For the hexadecimal color value, enter **#FF0000**.
+
+### hierarchical menu
+
+Don't use. Use *submenu* if you need to emphasize how the menu works as a feature. Better yet, avoid talking about UI. Instead, talk about what the customer wants to do.
+
+It's OK to use *hierarchical menu* when you need to explain types of menus to a technical audience.
+
+**Examples** On the **Edit** menu, point to **Clear**, and then select the item you want to clear. Select **Edit**, point to **Clear**, and then select the item you want to clear.
+
+### high-level-language compiler
+
+Hyphenate as shown.
+
+### high-quality
+
+Don’t use *quality* by itself as an adjective. Always use *high-quality*.
+
+### high-resolution
+
+Always hyphenate. Don’t abbreviate as *hi-res*.
+
+### higher
+
+Don't use *or higher* to mean *or later* to refer to multiple versions of software.
+
+It's OK to use *higher* to refer to display resolution.
+
+Don't use *higher* to refer to processor speed. Use *faster* instead.
+
+**Examples** 1920 × 1200 pixels or higher resolution a processer speed of 2.5 gigahertz (GHz) or faster
+
+**See** later
+
+### hint
+
+Don't use *hint* as a heading for a type of note. Use *tip* instead.
+
+### hit
+
+Don't use to refer to pressing a key. Use *select* instead.
+
+Use *page view* or *page request,* not *hit,* to refer to the number of times a complete webpage, with all its associated files, has been downloaded. It's OK to use *hits* to refer to the number of times a file that's part of a webpage has been retrieved. A single page view can result in many hits.
+
+**See** Describing interactions with UI
+
+### home directory
+
+Don't use.
+
+In content for developers, use *root directory* to refer to the starting point in a hierarchical file structure. In Windows, the root directory is indicated by a backslash (\\).
+
+In all other content, use *top-level folder*.
+
+**See also** root directory
+
+### home, home page
+
+Use *home* to refer to the main page of a website or the page a browser displays upon opening. Capitalize *Home* only when it’s used as a UI label or in references to a UI label.
+
+Use *home page,* two words, in generic references if needed for clarity.
+
+**Examples** Select **Home** to return to the main portal page. Use **Settings** to choose the home page you want to see when the browser opens.
+
+Don't use *start page.*
+
+### honeypot
+
+Don't use.
+
+In content that's specifically about network decoy technology, try to write around the reference. If you can't, define the term on the first mention.
+
+### host name
+
+Two words unless you're referring to a programming element, such as the **HostName** property.
+
+### hosted service
+
+**See** Cloud-computing term collection
+
+### hosting provider
+
+**See** Cloud-computing term collection
+
+### hot key
+
+**See** Keys and keyboard shortcuts term collection
+
+### hot link
+
+Don't use to describe a connection that enables information in related databases or files to be updated when information in another database or file is changed.
+
+Don't use to refer to a link.
+
+**See also** hyperlink
+
+### hot spot, hotspot
+
+Don't use to refer to a link.
+
+In content for a technical audience, use two words to refer to the specific pixel on the pointer that defines the exact location to which a user is pointing.
+
+Use one word when referring to a site that offers internet access over a wireless LAN.
+
+Use one word when referring to programming elements, such as the elements of the **HotSpot** class, or to match UI.
+
+**See also**  hyperlink
+
+### hover over, hovering
+
+**See** Mouse and mouse interaction term collection
+
+### how to, how-to
+
+Don’t use *how-to* as a noun. Always hyphenate as an adjective. Never capitalize the *t* in *to*.
+
+**Examples** how-to book how-to article How to add an article to the library (Title-style capitalization) Writing a How-to Article
+
+### HTML
+
+Don't spell out. If you have a reason to spell out, use *Hypertext Markup Language.*
+
+### HTTP, HTTPS
+
+Don’t spell out unless you're discussing protocols or URLs, and your audience might be unfamiliar with the abbreviation. When you have a reason to spell out, use *Hypertext Transfer Protocol* for HTTP and *Hypertext Transfer Protocol Secure* for HTTPS.
+
+Use all uppercase when referring to the HTTP or HTTPS protocol itself. In general, omit *https://* and *https://* from URLs. If for some reason you need to include *https://* or *https://* as part of a URL, use all lowercase.
+
+**See also** URLs and web addresses
+
+### hybrid cloud
+
+**See** Cloud-computing term collection
+
+### hyperlink
+
+Use *hyperlink* or *link* to describe text or a graphic that readers can select to go to another document, to another place within the same document, or to a webpage. Use *hyperlink* to refer to a UI element labeled *hyperlink*.
+
+Don't use *hot spot, hot link,* or *shortcut* to refer to a link.
+
+Use *go to* to describe the process of going to another document, place, or webpage. Don't use *click* or *click on.*
+
+Use *create* to describe writing the HTML code that forms the link.
+
+In content for web designers, it's OK to use *followed link* to refer to a destination that the reader has already visited. Don't use in content for other audiences.
+
+**Examples** Select the link to go to another webpage. On the **Insert** tab, select **Hyperlink** in the **Links** group.
+
+**See also** URLs and web addresses, Describing interactions with UI
+
+## I
+
+### icon
+
+Use only to describe a graphic representation of an object that a customer can select and open, such as a drive, folder, document, or app.
+
+Don't use *icon* to describe graphical dialog box options or options that appear on ribbons, toolbars, toolboxes, or other areas of a window. For options that have graphics rather than text labels, use the most descriptive term available, such as *button, box,* or *checkbox*. To refer to the graphic itself, if there's no other identifying label, use *symbol,* as in *warning symbol.*
+
+When referring to an icon, use bold formatting for the icon name. In instructions, use the name of the icon and its image, but don't use the word *icon*.<br /><br />**Example**<br />Select **Xbox** (shown as a circle divided into four sections by an X).
+
+It's OK to use the word *icon:*
+
+  - In content that teaches beginning Windows skills. 
+  - When you don't have an image of the icon. 
+  - In discussions about the icon itself. 
+  - When you need to differentiate between the Start icon and the Start button (a rare occurrence)​. 
+
+**Example**<br />Most apps have their own settings. Look for the settings symbol (a gray gear) in the app.
+
+### iconize
+
+Don't use. Use *shrink to an icon* or *minimize* instead.
+
+### i.e.
+
+Don't use. Use *that is* instead.
+
+### if vs. whether vs. when
+
+Use *if* to express a condition, use *whether* to express uncertainty, and use *when* for situations that require preparation or to denote the passage of time.
+
+In informal writing for the web, it's OK to use *if* to express uncertainty. Don't use *whether or not* to express uncertainty.
+
+**Examples** If you don't know whether a network key is needed, contact your network administrator. Use your BitLocker recovery key to sign in if you're locked out of your computer after too many failed password attempts. When Setup is complete, restart your computer. To find out whether TrueType fonts are available …. (Informal) To find out if TrueType fonts are available …. Save a webpage to view it later, even if you're not connected to the internet.
+
+### illegal
+
+Don't use to mean *invalid* or *not valid.* 
+
+**Examples**  
+The queue path name is not valid.
+
+**See also**  [invalid, not valid](/style-guide/a-z-word-list-term-collections/i/invalid-not-valid)
+### image map
+
+Two words unless you're referring to a programming map such as the elements of the **ImageMap** class.
+
+### imbed
+
+Don't use. Use *embed* instead.
+
+### impact
+
+Use only as a noun. As a verb, use *affect* or another synonym.
+
+### inactive, inactive state
+
+Don't use in content for a general audience. Describe what the customer needs to do in simpler terms.
+
+In content for a technical audience, use instead of *not current* to refer to windows, apps, documents, files, devices, or portions of the screen that are available but not currently in use.
+
+### inbound
+
+Don't use to describe email being delivered. Use *incoming* instead.
+
+It's OK to use *inbound* and *outbound* to describe marketing tactics.
+
+### incoming, outgoing
+
+Use to refer to email messages that are being downloaded or sent. Don't use *inbound* and *outbound*.
+
+### increment
+
+In content for developers and IT pros, use *increment* as a verb only to mean *increase by one or by a specified interval*. As a noun, use *increment* to refer to the specified interval.
+
+In other content, it's OK to use *increment* as long as the meaning is clear.
+
+### indent, outdent
+
+Use *indent* to refer to a single instance of indentation. For example, use *hanging indent, nested indent, negative indent,* or *positive indent*.
+
+Use *indentation* to refer to the general concept.
+
+Don't use *outdent.*
+
+Don't use *indenting* or *outdenting into the margin*. Use *extending text into the margin* or *indenting to the previous tab stop* instead.
+
+### index, indexes, indices
+
+Use *indexes* as the plural form of *index.* Use *indices* only in the context of mathematical expressions.
+
+### info
+
+It's OK to use *info* as an abbreviation for *information* in content with an informal tone.
+
+**Global tip** The abbreviated form isn't available in all languages, so allow enough space for the full translated term in localized content.
+
+### infrastructure as a service (IaaS)
+
+**See** Cloud-computing term collection
+
+### initialize
+
+Don't use to mean *start a program or app* or *turn on a device.*
+
+It's OK to use *initialize* to refer to preparing a disk or device for use or setting a variable to an initial value.
+
+**See also** start, restart, turn on, turn off
+
+### initiate
+
+Don't use to mean *start a program or app.*
+
+**See** Describing interactions with UI
+
+### inline
+
+One word. Don't hyphenate.
+
+Use *inline styles* to describe styles embedded in tags using the *STYLE* parameter, which override styles in cascading style sheets.
+
+### input/output, I/O, input/output control
+
+Avoid *input/output* in content for a general audience. If you must use it, spell out on the first mention, and then abbreviate as *I/O*.
+
+In content for a technical audience, you don't need to spell out on the first mention.
+
+Use *input/output control* only in content for a technical audience. Always spell out on the first mention. On subsequent mentions, it's OK to abbreviate as *I/O control* or *IOCTL*.
+
+### input
+
+Don't use as a verb. Use *enter* or another appropriate verb instead.
+
+In content for a general audience, don't use as a noun to mean data or values entered into an app.
+
+**Examples** Existing characters move to the right as you enter new text. To verify the text that you entered …. (Technical audience) Windows Presentation Foundation provides an API for obtaining input from a variety of devices.
+
+**See also** Describing interactions with UI
+
+### insecure
+
+Don't use to mean *not secure*.
+
+### inside
+
+Use instead of *inside of.*
+
+**Example** To change the margins inside the text box ....
+
+### install
+
+Use *install* to describe adding apps, hardware, and drivers to a device. Don't use *download.* Use *uninstall* to describe removing them.
+
+Don't use *install* as a noun. Use *installation* instead.
+
+**See also** add
+
+### instant message, IM
+
+Spell out *instant message* or *instant messaging* on the first mention if your audience might not be familiar with the abbreviation. After that, it's OK to use *IM* as a noun or modifier<em>.</em>
+
+Don't use *instant message* or *IM* as a verb. Use *send an instant message* or *send an IM* instead.
+
+**Exception** In mobile UI content or to form a parallel construction with another one-word phrase, it's OK to use *IM* as a verb. For example, *tap a name to call or IM someone*.
+
+**Examples** To send an instant message, select **Send IM**  on the toolbar. Customize instant messaging features based on your friends, family, and work contacts.
+
+**Global tip** The abbreviated form isn't available in all languages, so allow enough space for the full translated term in localized content.
+
+**See also** message
+
+### instantiate
+
+Don't use. Use *create an instance of* (a class) instead. If you have a reason to use *instantiate,* its direct object must be the name of a class or a general reference to classes. You instantiate a class, not an object.
+
+### insure, assure, ensure
+
+*Ensure*<em>,</em> *insure,* and *assure* are interchangeable in many situations. To improve worldwide readability, Microsoft style makes these distinctions:
+
+  - Use *ensure* to mean *to make sure* or *to guarantee*. 
+  - Use *insure* to mean *to provide insurance*. 
+  - Use *assure* to mean *to state positively* or *to make confident*.
+
+### intelligence, intelligent technology
+
+**See** AI and bot term collection
+
+### interface
+
+Use only as a noun, as in *user interface* and *application programming interface*. Use *interface* by itself only if the context is clear.
+
+For a general audience, it's OK to use *UI* or *API* after spelling out on the first mention. For a technical audience, it's not necessary to spell out those terms on the first mention.
+
+Don't use *interface* as a verb. Use *interact* or *communicate* instead.
+
+**Examples** The familiar interface helps to minimize training requirements. With Skype for Business, you can communicate with your team from wherever you are.
+
+### Internet Connection Sharing
+
+Capitalize. Always spell out; don't abbreviate to *ICS*.
+
+### Internet Explorer
+
+Capitalize. Always spell out; don't abbreviate.
+
+### internet, intranet, extranet
+
+Use *internet* to refer to the worldwide collection of networks that use open protocols such as TCP/IP to communicate with one another. Don't capitalize.
+
+Use *intranet* to refer to a communications network based on web technology but that's available only to certain people, such as the employees of a company. Don't capitalize.
+
+Use *extranet* to refer to an extension of an intranet that uses internet protocols to give authorized outside users limited access to the intranet. Don't capitalize.
+
+### Internet of Things (IoT)
+
+Note the capitalization. Spell out on the first mention unless you're sure that your audience knows the term 
+or *IoT* appears as part of a Microsoft product name. On subsequent mentions, use the abbreviation *IoT.*  
+
+Include *the* with the spelled-out term but not the acronym.  
+
+**Examples**   
+The Internet of Things (IoT) is reshaping every industry from manufacturing to medicine. And although IoT 
+is a complicated endeavor, new innovations are making projects easier to deploy.  
+Learn how to use Microsoft Azure IoT Hub to connect, monitor, and control billions of Internet of Things assets.
+### internet service provider (ISP)
+
+Spell out on the first mention. Lowercase the spelled-out term.
+
+Use to refer to an organization that provides customers with internet access for activities such as web browsing, email, and newsgroups.
+
+### invalid, not valid
+
+Both terms are OK to use, but try to use more specific terms instead.
+
+**Global tip** Use *not valid* instead of *invalid* if possible because machine translation might not translate *i*<em>nvalid</em> correctly.
+
+**Examples** There are several reasons why a product key might not be valid. The FileType you specified is too long. The FileType must begin with a period and can be 1 to 64 characters long.
+
+### invite
+
+*Invite* can be used as a noun or a verb.
+
+An *invite* is used to request an individual’s virtual participation in a meeting, organization, or an event.
+
+**Examples** The working group will *invite* other stakeholders to weigh in on the proposal.
+
+Send an *invite* that includes dial-in conferencing.
+
+### invoke
+
+Don't use in content for a general audience.
+
+In content for a technical audience, it's OK to use *invoke* to refer to a function, process, or similar element.
+
+### IP address
+
+Don't spell out.
+
+### issue
+
+Don't use as a verb. Describe what's happening, or use a more specific verb instead.
+
+**Example** Windows displays an error message.
+
+Don't use as a synonym for *problem.*
+
+**Example** Outlook has run into a problem and needs to restart.
+
+### IT pro, IT professional
+
+Use *IT pro,* not *IT professional*. Note capitalization. Don't spell out *information technology*—always use *IT.*
+
+### italic
+
+Use only as an adjective, not as a noun. Don't use *italics* or *italicized*.
+
+**Examples** To make the selected characters italic, select **Ctrl+I**. The characters are displayed in italic type.
+
+In writing for customers, use *regular type* to describe type that's neither bold nor italic.
+
+### its vs. it's
+
+Proofread your work to be sure you've used the correct word.
+
+  - *Its* is a possessive form meaning *belonging to it.*
+  - *It's* is the contraction meaning *it is* or *it has.*
+
+**Examples** It's OK to switch to another webpage anytime—your changes are saved automatically. After you remove your device from its box ....
+
+## J
+
+### Java, JScript, JavaScript
+
+Use *Java* to refer to the object-oriented programming language developed by the Sun Corporation.
+
+Use *JScript* to refer to the Microsoft implementation of the ECMAScript scripting language specification, an open standard.
+
+Use *JavaScript* to refer to the widely used web-based programming language, under the Oracle trademark.
+
+### join
+
+Don't use to mean *embed*.
+
+In discussions about databases and related products, use *j*<em>oin</em> only to refer to a relationship or association between fields in different tables.
+
+**Examples** If you join numeric fields that don't have matching **FieldSize**  property settings, Microsoft Access might not find all the matching records when you run the query. When you add fields from both tables to the query design grid, the default, or inner, join tells the query to check for matching values in the join fields. To embed one object into another, select **Paste** on the **Edit** menu.
+
+### joystick
+
+**See** Computer and device term collection
+
+### jump
+
+Don't use as a noun to refer to cross-references to other pages or to links.
+
+Don't use as a verb to refer to going from one link to another. Use *go to* instead.
+
+### justify, justified
+
+Don't use as a synonym for *aligned*. Justified text is text that is both left-aligned and right-aligned. To describe alignment on one margin only, use *left-aligned* or *right-aligned,* not *left-justified* or *right-justified*.
+
+If your content has an index or a glossary that includes articles about alignment, include *justify* in the index or glossary with cross-references to *align, left align,* and *right align,* as appropriate.
+
+**See also** left align, left-aligned, right align, right-aligned
+
+## K
+
+### Kerberos protocol
+
+Always use *Kerberos* as an adjective (*Kerberos protocol*), not as a noun (*Kerberos*).
+
+On the first mention, indicate what version or versions of the Kerberos protocol you're referring to.
+
+**Example** Windows Server 2012 implements the Kerberos version 5 authentication protocol.
+
+### key combination
+
+See Keys and keyboard shortcuts term collection
+
+### key performance indicator (KPI)
+
+Spell out on the first mention and include the abbreviation in parentheses immediately following the expanded form. Lowercase the spelled out term.
+
+On subsequent mentions on the same screen or pane, or in the same topic, article or flow, it’s OK to use the abbreviation *KPI*.
+
+In UI, if the full term cannot be spelled out due to space constraints, it’s OK to abbreviate on the first mention. If possible, use the spelled out term somewhere else within the same flow for context.
+
+**See also** key result (KR).md), objectives and key results (OKR).md)
+
+### key sequence
+
+See Keys and keyboard shortcuts term collection
+
+### keyboard shortcut
+
+See Keys and keyboard shortcuts term collection
+
+### keypad
+
+**See** Keys and keyboard shortcuts term collection
+
+### keypress, keystroke
+
+**See** Keys and keyboard shortcuts term collection
+
+### kilobit, Kbit
+
+**See** Bits and bytes term collection
+
+### kilobits per second, Kbps
+
+**See** Bits and bytes term collection
+
+### kilobyte, KB, K, K byte, Kbyte
+
+**See** Bits and bytes term collection
+
+For information about using *K* as an abbreviation for *thousand,* see Numbers.
+
+### kilobytes per second, KBps
+
+**See** Bits and bytes term collection
+
+### kilohertz, kHz
+
+**See** Units of measure term collection
+
+### knowledge base, Knowledge Base
+
+Use title-style capitalization to refer to the Microsoft Knowledge Base. (You don't need to precede *Knowledge Base* with the company name.)
+
+Otherwise, use lowercase for generic references to a *knowledge base,* or *expert system*.
+
+## L
+
+### labeled, labeling
+
+Use one *l,* not two.
+
+### laptop
+
+**See** Computer and device term collection
+
+### later
+
+If possible, use a link to help readers find information elsewhere in the content. If you can't use a link, use *later* instead of *below* in cross-references such as *later in this article.*
+
+It's OK to use *or later* or *and later* to refer to multiple versions of software. Keep in mind that the phrases and later and or later might imply that the functionality or feature discussed will be included or supported in all future releases. If you're not sure, list each applicable version instead.
+
+**Examples** Internet Explorer 7 or later, Firefox 3.6 or later
+
+Windows 7, Windows 8, Windows 8.1, Windows 10, and later.
+
+Download and install the Power BI publisher for Excel to use with Microsoft Excel 2010 or later versions.
+
+**See also** earlier
+
+### launch
+
+Don't use to mean opening an app or form. Use *open* instead.
+
+**Examples** Select a tile to open an app. Select **Register** to open the registration form.
+
+**See also** Describing interactions with UI
+
+### lay out, laid out, layout
+
+In formatting discussions:
+
+  - Use *lay out* as a verb to describe positioning elements on a page. 
+  - Use *laid out* as a verb in the past tense.
+  - Use *layout* to describe the result of laying out elements on a page. 
+
+**Examples** Lay out complex information in a table to make it easier to read. Add formatting to your table after it's laid out. A table layout clarifies complex information.
+
+### leading
+
+Use instead of *preceding* or *beginning* in phrases such as *leading slashes* or *leading* *spaces,* which might occur at the beginning of strings, parameters, or other values. *Leading* in this context is the opposite of *trailing.*
+
+### leave
+
+Don't use to refer to closing an app or program. Use *close* instead.
+
+**See** Describing interactions with UI
+
+### left align, left-aligned
+
+Use to refer to text that's aligned at the left margin. Always hyphenate *left-aligned*. Don’t use *left-justified*.
+
+**See also** justify, justified, right align, right-aligned
+
+### left justify, left-justified
+
+Don’t use. Use *left-aligned* instead.
+
+**See** left align, left-aligned
+
+### left, leftmost, left-hand
+
+Don't use *left* as a directional term by itself. Instead, use a term such as *upper left,* *lower left,* *leftmost,* or *on the left side of*. Include a hyphen when you use *left* to modify a noun, as in *upper-left corner*. Don't use *left-hand* as a modifier.
+
+**Accessibility tip** Don't use directional terms (*left, right, up, down*) as the only clue to location. Individuals with cognitive disabilities might have difficulty interpreting them, as might people who are blind and use screen-reading software. It's OK to use a directional term if another indication of location, such as *in the* ***Save As*** *dialog box,* *on the* ***Standard*** *toolbar,* or *in the title bar,* is also included. Directional terms are also OK to use when a sighted user with dyslexia can clearly see a change in the interface as the result of an action, such as a change in the right pane when an option in the left pane is selected.
+
+### left mouse button
+
+**See** Mouse and mouse interaction term collection
+
+### legacy
+
+Don't use to describe a previous version of a product. Use *previous,* *former,* *earlier,* or a similar term instead. Be specific if necessary, especially when discussing compatibility issues.
+
+### legal
+
+Use only to refer to matters of law. Don't use to mean *valid,* as in a *valid action*.
+
+**Example** Enter a valid path name.
+
+### less vs. fewer vs. under
+
+When comparing quantities:
+
+  - Use *less* to refer to a mass amount, value, or degree. 
+  - Use *fewer* to refer to a countable number of items. 
+  - Don't use *under* to refer to a quantity or number.
+
+**Examples** The new building has less floor space and contains fewer offices. The new building has fewer square feet of floor space and contains fewer offices. Fewer than 75 members were present. Less than a quorum attended.
+
+### let, lets
+
+Don't use *lets* (or *allows* or *enables*) to refer to things that Microsoft or Microsoft apps make possible for the customer. Instead, focus on what the customer wants to do.
+
+**Example** Present schedule information in a variety of ways using Microsoft Project.
+
+### leverage
+
+Don't use as a verb to mean *take advantage of.* Use *take advantage of,* *use,* or another more appropriate word or phrase.
+### license terms
+
+**See** Microsoft Software License Terms
+
+### lifecycle
+
+One word. This style choice is an intentional deviation from the Merriam-Webster Dictionary.
+
+**Examples** For products under existing lifecycle policies, we'll continue to provide support. New capabilities for the products are available across the entire customer lifecycle. With purpose-built agents, AI spans the full lifecycle of the contact center.
+
+### \-like
+
+In general, don't hyphenate words ending with *-like* unless the root word ends in double <em>l'</em>s or the root word has three or more syllables.
+
+**Examples** maillike bell-like computer-like
+
+To learn more about hyphenation, see Hyphens.
+
+### line of business, line-of-business
+
+Lowercase. Don’t hyphenate as a noun. Always hyphenate as an adjective. Don’t abbreviate as *LOB.*
+
+**Examples** line-of-business app In any line of business, …
+
+### line
+
+Don't use to refer to a series of related Microsoft products or services. Use *family* instead.
+
+### link
+
+**See** hyperlink
+
+### list box
+
+Two words.
+
+In general, avoid talking about UI. Instead, talk about what the customer needs to do.
+
+When you need to help a customer interact with UI, refer to a list box by its label and the word *list,* not *list box*. For the Mac, use *pop-up list* to refer to unnamed list boxes.
+
+**Examples** In the **Background** list, select **Coffee Bean**. In the pop-up list, select **Microsoft Excel**. (Mac only)
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### load
+
+Don't use as a synonym for *start, install, run, set up,* or *download.*
+
+In content for a technical audience, use *load* only to describe dynamically calling graphics, documents, or installed programs or data, such as drivers, DLLs, scripts, registry entries, and profiles, into RAM or a program's virtual memory. Use *unload* or *remove* to refer to removing these items from memory.
+
+For games, use *load* to refer to continuing gameplay at the last place that a game was saved. *Load game* and *Load saved game* are typical button labels for game UI.
+
+**Examples**<br />Load the device driver into the upper memory area.<br />Loading your personal settings ... (system status message)<br />When you sign in, the app loads your profile.<br />Run the program in character mode.<br />Setting up Office 365 (heading)<br />Download the e-book (link text)<br />When you're ready to play again, load your saved game.
+
+**See also** download
+
+### lock up
+
+Don't use to describe a hardware failure or a program or an operating system that has stopped responding. Use *fail* instead for hardware, and *stop responding* for programs or the operating system.
+
+**See also** fail, stop, stop responding
+
+### lock
+
+**See** Security term collection
+
+### log on, log off
+
+Don't use *log in, login, log into, log on, logon, log onto, log off, log out, logout,* or a similar term unless it appears in the UI (and you're writing instructions).
+
+Use *sign in* or *sign out* instead.
+
+**See** sign in, sign out, connect
+
+### low-resolution
+
+Always hyphenate. Don’t abbreviate as *lo-res*.
+
+### lower left, lower-left, lower right, lower-right
+
+Hyphenate as adjectives. Use instead of *bottom left* and *bottom right*.
+
+**Accessibility note** Don't use directional terms (*left, right, up, down*) as the only clue to location. Individuals with cognitive impairments might have difficulty interpreting them, as might people who are blind and use screen-reading software. It's OK to use a directional term if another indication of location, such as *in the* ***Save As*** *dialog box,* *on the* ***Standard*** *toolbar,* or *in the title bar,* is also included. Directional terms are also OK to use when a sighted user with dyslexia can clearly see a change in the interface as the result of an action, such as a change in the right pane when an option in the left pane is selected.
+
+### lower
+
+Don't use to indicate product version numbers. Use *earlier* instead.
+
+**See** earlier
+
+### lowercase
+
+One word. Don't use *lowercased*. Don't use as a verb.
+
+When using *lowercase* and *uppercase* together, don't use a suspended hyphen (as in *upper- and lowercase*). Spell out both words instead.
+
+**Examples** Change all the uppercase letters to lowercase. Change the case of both lowercase and uppercase letters. Microsoft uses sentence-style capitalization, meaning most words are lowercase.
+
+## M
+
+### machine learning
+
+In general discussions, use lowercase. Use title-style capitalization to refer to named services, such as Machine Learning API and Machine Learning Studio.
+
+### machine
+
+**See** Computer and device term collection
+
+### main document
+
+Use to describe the document that contains the unchanging material in a merged document, such as a form letter. Don't use *core document*.
+
+### makefile
+
+One word. Use only in content for a technical audience.
+
+### malicious code
+
+**See** Security term collection
+
+### malicious user
+
+**See** Security term collection
+
+### malware, malicious software
+
+**See** Security term collection
+
+### management information systems
+
+Abbreviate as *MIS*. Most of the time, use *IS* for *information systems* instead, unless the reference is specifically to management information systems.
+
+### manipulate
+
+Use *work with, handle,* or *use* instead.
+
+### marquee
+
+It's OK to use *marquee* to refer to the scrolling text feature on webpages. Don't use to refer to the feature that draws a dotted line around a selection on the screen. Use *bounding outline* instead.
+
+**See also** bounding outline, dotted rectangle
+
+### master/slave
+
+Don't use *master/slave*. Use *primary/replica* or alternatives such as *primary/secondary*, *principal/agent*, *controller/worker*, or other appropriate terms depending on the context.
+
+Use *primary/subordinate* as an adjective. Refer to arrangements in which one device controls another as a *primary/subordinate arrangement*, or refer to the controlling device as the *primary server* and the controlled device as the subordinate server.
+
+Don't use *primary/subordinate* as a synonym for *parent/child*.
+
+**Examples** Each subordinate device has a unique 7-bit or 10-bit address. The architecture uses a standard primary/subordinate design to replicate data from one server to many.
+
+**See also** parent/child
+
+### mathematical
+
+Use instead of *mathematic*.
+
+### matrix, matrices
+
+Use *matrices,* not *matrixes,* as the plural form of *matrix*.
+
+### Maximize button, maximize
+
+Use the ***Maximize*** *button* to refer to the button, not just ***Maximize***. *Maximize* as part of the ***Maximize*** *button* is always bold. Don't use *Maximize box* or *Maximize icon*.
+
+It's OK to use *maximize* as a verb.
+
+**Examples** Select the **Maximize** button. To fill the screen, maximize the window. Select the **Maximize** button (a square within a square).
+
+### medium, media
+
+Use *medium,* not *media,* as a singular subject. Ensure that the verb agrees with the subject (that is, *the medium is* and *the media are*).
+
+Use *media* to describe:
+
+  - Materials or substances, such as fiber optic cable or wire, through which data is transmitted. 
+  - Materials on which data is recorded or stored, such as magnetic disks, CDs, or tapes. 
+  - The mass-communications industry and its practitioners, such as publishing and broadcasting. 
+  - Journalists as a group, whether they're published in print or on the web, or broadcast. 
+
+Don't use *media* as a shortened form of *multimedia*.
+
+**Examples** The media include online broadcasts as well as newspapers, magazines, radio, and television. The media covers computer industry news. The medium used for many large computer programs is the DVD-ROM.
+
+### megabit, Mb, Mbit
+
+**See** Bits and bytes term collection
+
+### megabits per second, Mbps
+
+**See** Bits and bytes term collection
+
+### megabyte, MB, meg, M, M byte, Mbyte
+
+**See** Bits and bytes term collection
+
+### megahertz, MHz
+
+**See** Units of measure term collection
+
+### member function
+
+Don't use if you can correctly use *method* instead.
+
+### memory-resident
+
+Always hyphenate. Use *memory-resident program,* not *TSR,* in content for a general audience.
+
+In content for a technical audience, it's OK to use *TSR* as an abbreviation for *terminate-and-stay-resident*.
+
+### memory
+
+Always refer to a specific kind of memory, such as *random-access memory (*<em>RAM)</em>*, read-only memory (ROM),* or *hard drive space*.
+
+Spell out RAM and ROM on the first mention unless you're positive that your audience is familiar with the term.
+
+In the noun forms that refer to memory measurements, use *of* in a prepositional phrase, as in *512 MB of RAM*.
+
+**Example** Here's what it takes to upgrade to Windows 10 on your PC or tablet:
+
+  - **Latest OS**: Make sure you're running the latest version—either Windows 7 SP1 or Windows 8.1 Update.
+    
+      - Find out which version you're running 
+    
+      - Need the latest version? Download Windows 7 SP1 or Windows 8.1 Update.
+
+  - **Processor**: 1 gigahertz (GHz) or faster processor or SoC
+
+  - **RAM**: 1 gigabyte (GB) for 32-bit or 2 GB for 64-bit
+
+  - **Hard drive space**: 16 GB for 32-bit OS or 20 GB for 64-bit OS
+
+  - **Graphics card**: DirectX 9 or later with WDDM 1.0 driver
+
+  - **Display**: 800 × 600
+
+**See also** Bits and bytes term collection, Units of measure term collection
+
+### menu item
+
+In general, avoid talking about the UI. Instead, talk about what the customer needs to do. If you must refer to commands on menus in content for a general audience, call them *commands,* not *menu items.*
+
+In content for developers, it's OK to use *menu items* in the context of UI development.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### message
+
+Don't use *message* as a verb. Use *send, receive, email, text,* or *send an* *IM* instead.
+
+Use *email,* *message,* or *email message* to refer to an item sent or received using email.
+
+Use *text* or *text message* to refer to an item sent or received using SMS.
+
+To refer to an item sent or received using instant messaging, spell out *instant message* on the first mention if your audience might not be familiar with the abbreviation. After that, it's OK to use *IM.*
+
+**See also** email instant message, IM text, text message
+
+### metafile
+
+One word.
+
+### micro-
+
+In general, don't hyphenate words beginning with *micro-,* such as *microprocessor* and *microsecond,* unless it's necessary to avoid confusion. When in doubt, check *Merriam-Webster Dictionary.*
+
+To learn more about hyphenation, see Hyphens.
+
+### microprocessor
+
+Use instead of *processor* to refer to the chip used in personal computers.
+
+### Microsoft account
+
+Don't capitalize *account*.
+
+Use *Microsoft account* to refer to the sign-in credentials (email address and password) that give someone access to Microsoft services, such as Skype, Xbox Live, and Outlook.com, and to products, such as Xbox consoles.
+
+Don't use *Microsoft account* to refer to corporate domain accounts, which are used to connect to corporate resources and services.
+
+*Microsoft account* was formerly known as *Windows Live ID*.
+
+**Example** This contact info is from your Microsoft account. Friends who have it will be able to find you on Skype. Would you like to add it?
+
+### Microsoft AI
+
+**See** AI and bot term collection
+
+### Microsoft Store
+
+Use the full name *Microsoft Store.* Note the capitalization.
+
+In general, don’t include *the* (*the Microsoft Store*) unless it's necessary to fix awkward wording. Avoid it in marketing content.<br />
+**Exceptions** In the UI, it’s OK to omit *Microsoft* when space is limited, and it’s OK to include *the* (*the Microsoft Store, the Store*) when it reads better.
+
+Don’t use *Windows Store* or *Xbox Store.* Always use the singular *Microsoft Store.* Don’t use *Microsoft Stores.*
+
+Refer to a brick-and-mortar store as a *location.*   
+**Example** <br />Get it at a Microsoft Store location near you.
+
+If your message applies only to a specific part or parts of Microsoft Store, add descriptors if needed for clarity. The approved descriptors are:
+- Microsoft Store on Windows 10
+- Microsoft Store on Xbox One
+- Microsoft Store online
+- Microsoft Store location 
+
+When you use two descriptors, don’t repeat *Microsoft Store.*  
+**Example** <br />Microsoft Store on Windows 10 and Xbox One
+
+If one of the references is to Microsoft Store online, put it first.  
+**Example** <br />Microsoft Store online and on Windows 10
+### Microsoft
+
+Never abbreviate *Microsoft.* Don't use *Microsoft's.*  
+**Examples**  
+Microsoft software and services  
+Microsoft Surface  
+the Microsoft approach to diversity and inclusion  
+
+**Exception** To avoid awkward wording, it's OK to use *Microsoft's* occasionally when you're referring 
+to the company itself rather than the trademark or brand name.  
+**Example**  
+Microsoft's privacy policies  
+
+Include *Microsoft* the first time you mention a product or service name in body text. When you list several 
+product names, it's OK to include *Microsoft* before the first name only.
+
+**Exceptions** Never include *Microsoft* before *Bing, Skype, Xbox,* or *Windows.*  
+
+In general, focus on the customer, and avoid making Microsoft the subject of the sentence. For example, say, 
+"Learn about the options available for upgrading," not "Microsoft offers a variety of options for upgrading." It's 
+OK to use phrasing like *we recommend* if it helps you avoid awkward wording like *it's recommended.*
+
+When it's necessary for Microsoft to be the subject, choose the pronouns that best fit your message.
+
+- When the tone is friendly, informative, or inspiring, use *we* and *our.*  
+  **Examples**  
+  We believe in what people make possible.   
+  We recommend that you upgrade to the latest version of the service when it becomes available. 
+
+- In formal legal or business content, use *it* and *its.*  
+  **Example**  
+  Microsoft and its subsidiaries  
+  
+- Don't mix pronouns. Don't use *we* to refer to Microsoft and *its* as the possessive pronoun.
+### midnight
+
+**See** Date and time term collection
+
+### million, M
+
+**See** Numbers
+
+### Minimize button, minimize
+
+Use the ***Minimize*** *button* to refer to the button, not just ***Minimize***. *Minimize* as part of the ***Minimize*** *button* is always bold. Don't use *Minimize box* or *Minimize icon*.
+
+It's OK to use *minimize* as a verb.
+
+**Examples** Select the **Minimize** button. Select the **Minimize** button (a horizontal line in a square).
+
+### MIP mapping
+
+Two words. Note capitalization.
+
+### mission critical, mission-critical
+
+Two words. Hyphenate as an adjective.
+
+Use *business-critical* or simply *critical* instead if you can. When necessary, it's OK to use this term in a technical context to describe an application or business process.
+
+### mixed reality, mixed-reality
+
+Two words as a noun. Hyphenate as an adjective.
+
+**Examples** In mixed reality, digital information is represented by holograms that appear in the space around you. Use mixed-reality video calling to help you make better business decisions and reduce costs.
+
+### mobile device, mobile phone
+
+**See** Computer and device term collection
+
+### monitor
+
+**See** Computer and device term collection
+
+### monospace
+
+One word.
+
+### more than vs. over
+
+Use *more than* to refer to quantifiable figures and amounts—things you can count.
+
+Use *over:*
+
+  - To refer to a position or location that's above something.
+  -  In a comparison in which *more* is already used.
+
+**Examples** The Design Gallery contains more than 16 million colors. After you compress your drive, it will have over 50 percent more free space.
+
+### mouse over
+
+**See** Mouse and mouse interaction term collection
+
+### mouse
+
+**See** Computer and device term collection, Mouse and mouse interaction term collection
+
+### movable
+
+Note spelling. Don't use *moveable.*
+
+### move
+
+Use as a verb to describe transferring files or folders from one local location to another.
+
+Use *move* or *drag* as a verb to describe moving any window.
+
+**See also** Describing interactions with UI, upload
+
+### MPEG
+
+Don’t spell out. The extension for MPEG files is .mpg.
+
+### multi-
+
+In general, don't hyphenate words beginning with *multi-* unless it's necessary to avoid confusion or *multi-* is followed by a proper noun.
+
+Don't invent new words by combining words with multi-. Check *Merriam-Webster Dictionary.* If you don't find the word there or in the following list of examples, use *multiple* before the word instead.
+
+**Examples**<br />multicast <br />multichannel <br />multicloud <br />multicolumn <br />multiline <br />multiprocessor
+
+To learn more about hyphenation, **see also** Hyphens.
+
+### multifactor authentication
+
+When describing an authentication that uses more than one factor, use the term *multifactor authentication*. 
+
+Don’t use *multi-factor*. Instead always use *multifactor*, without the hyphen. 
+
+Don’t use the abbreviated or acronym form of this term.
+### multiple selection
+
+Use to refer to a selection that includes multiple items. It's OK to use *adjacent selection* if you must emphasize that the selected items are adjacent to one another.
+
+Don't use *disjoint selection,* *nonadjacent selection,* or *noncontiguous selection,* except in content for a technical audience, and only if the term appears in the UI or API. If you need to refer to nonadjacent selected items, use *multiple selection* or list the specific items.
+
+### multiplication sign (×)
+
+Use the multiplication sign (×), not the letter *x,* to indicate the mathematical operation. Use an asterisk (\*) if you need to match the UI.
+
+Use × to mean *by* when you refer to screen resolution or dimensions.
+
+**Examples** 48 × 48 pixels The application icon should be 62 × 62 pixels and PNG format.
+
+### multitask, multitasking
+
+Don't use *multitask* as a verb. *Multitasking* is OK to use as a noun or an adjective.
+
+**Examples** A multitasking operating system divides the available microprocessor time among the processes that need it. Multitasking on Microsoft Surface is a snap.
+
+### multithreaded
+
+Use instead of *multithread*.
+
+### Microsoft Software License Terms
+
+When referring to the license agreement, use *Microsoft Software License Terms,* not *End-User License Agreement* or *EULA*. On the first mention, use the full name. On subsequent mentions, it's OK to shorten to *license terms*.
+
+Don't use *licensing terms*.
diff --git a/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-n-r.md b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-n-r.md
new file mode 100755
index 000000000..f5bfb62b1
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-n-r.md
@@ -0,0 +1,1182 @@
+# A-Z word list: n-r
+
+Alphabetical Microsoft style guidance for individual words and terms. Each entry gives preferred usage, prohibited usage, and notes.
+
+## N
+
+### n
+
+Use a lowercase *n* in italic type to refer to a generic use of a number—when the value of a number is arbitrary or immaterial.
+
+**Example** Move the cursor *n* spaces to the right.
+
+Reserve a lowercase *x* in italic type for representing an unknown in mathematical equations (a variable).
+
+**Global note** Because *n* doesn't refer to the generic use of a number in all languages, using *n* for this purpose might lead to mistranslation in machine-translated content.
+
+**See also** x
+
+### namespace
+
+One word.
+
+### nanosecond
+
+See Date and time term collection
+
+### native language
+
+Don't use to refer to a computer system's machine language. Use *machine language* or *host language* instead.
+
+### natural user interface, NUI
+
+Don't use *natural user interface* in content for a general audience. Don't abbreviate as *NUI.*
+
+### navigate, navigation
+
+In most situations, avoid using *navigate* (verb) and *navigation* (noun or adjective) because they're formal words that might not localize well. Use simpler words instead.
+
+**See also** browse Describing interactions with the UI
+
+### Alternatives to *navigate*
+
+| To describe | Use | Example |
+| ----------- | --- | ------- |
+| Going from place to place on the internet or an intranet | *browse* | To browse the web, select any link on your home page. |
+| Going directly to a webpage or website, whether by entering a URL or by selecting a link | *go to* | To go to a webpage, enter the address of the page on the address bar, and then select **Go**. |
+| Going to a folder or file | *browse* if the user has to find it<br><br>*go to* if the action is direct | Go to your **Downloads** folder and open the file. |
+| Moving through a page, file, or app | *move through* | Use the **Next** buttons to move through the pages. |
+
+### Alternatives to *navigation*
+
+Avoid referring to UI controls and buttons as *navigation buttons* and to webpages that orient the customer as *navigation topics* or *navigation pages*. Most of the time, the *navigation* part is unnecessary and you can simply use *buttons*, *topics,* and *pages*.
+
+Don't use *navigation pane* or *navigation menu* unless the term appears in the UI. Use *left pane* or *left menu* instead if the use of a direction is appropriate.
+
+If you need to use *navigation*, never abbreviate it to *nav* (as in *nav pane* or *left nav*) because it's slang.
+
+**Examples** Use the buttons to make your selection. On the service menu, select your service. Then, on the left pane, select your resource.
+
+You don't need to find an alternative to *navigation* when it's the most precise word in the context.
+
+**Example** This change improves code organization and navigation.
+
+### near real time, near-real-time
+
+The term *near real time* describes something that's diplayed or reported a short time after an event happens.
+
+The noun form is three words and typically follows the preposition *in*. When the term is an adjective that precedes a noun, the entire string is hyphenated.
+
+**Examples**  
+The service provides analytics in near real time.  
+The service provides near-real-time analytics.
+
+**See also**  
+[real time, real-time](~/a-z-word-list-term-collections/r/real-time.md)
+### need
+
+Use *need* to discuss a requirement or obligation; use *want* when the customer has a choice of actions.
+
+**Example** If you want to use a laser printer, you need a laser printer driver.
+
+### .NET
+
+Note capitalization. Always begin with a period (.). Don't spell out as *dot NET*.
+
+Use *Microsoft .NET* on the first mention. After that, it's OK to use *.NET.*
+
+It's OK to begin a sentence with *.NET* to avoid awkwardness or ambiguity, but be aware that the consecutive periods *(. .NET)* might briefly confuse some readers.
+
+### network adapter
+
+**See** Computer and device term collection
+
+### network administrator
+
+Use only to specifically refer to the administrator of networks. In general, use *administrator* or *system administrator* unless you must specify a particular kind.
+
+**See also** administrator, admin
+
+### network connection
+
+Use instead of *local area network connection*.
+
+### network drive
+
+Use instead of *remote drive*.
+
+### network
+
+Don't shorten to *net*.
+
+Don't use *network* as a verb to describe the action of connecting a computer to a network.
+
+A computer is *on,* not *in,* a network, and computers on a network are *linked* or *connected,* not *networked*.
+
+Use *network* as a verb and the noun *networking* only to describe making personal and business connections.
+
+### newsreader
+
+One word.
+
+### non-
+
+Don't hyphenate words beginning with *non-,* such as *nonnumeric* and *nonzero,* unless a hyphen is necessary to avoid confusion, as in *non-native,* or *non-* is followed by a proper noun, as in *non-English.* When in doubt, check *Merriam-Webster Dictionary.* Don't use *non-* to negate an entire phrase.
+
+**Example** unrelated to security (instead of *non-security related*)
+
+To learn more about hyphenation, see  Hyphens.
+
+### nonadjacent selection
+
+Don't use in content for a general audience to describe multiple selected items that don't touch. Use *multiple selection* or list the specific items instead.
+
+Use in content for a technical audience only if the term appears in the UI or API.
+
+### noncontiguous selection
+
+Don't use in content for a general audience to refer to selecting multiple items that don't touch. Use *multiple selection* instead, or describe the specific noncontiguous items.
+
+Use in content for a technical audience only if the term appears in the UI or API.
+
+**Example** To select multiple cells, select **Ctrl** as you select the cells.
+
+### nonprintable, nonprinting
+
+Use *nonprintable* to refer to an area of a page that can't be printed on. Use *nonprinting* to refer to characters and other data that can't or won't be printed.
+
+Don't use *unprintable*.
+
+**Examples** Some text extends into the nonprintable area of the page. Select **Show/Hide** to display  all nonprinting characters, including paragraph marks and space marks.
+
+### normal, normally
+
+Don't use *normal* to mean *customary, usual, typical,* or a similar term. Don't use *normally* to mean *often, usually, ordinarily, typically, generally,* or a similar term.
+
+### notification area
+
+In Windows 8 and Windows 10, use to refer to the area on the taskbar where the clock and system notifications appear.
+
+In Windows 11, this UI element is referred to as the *system tray*.
+
+**See also** system tray
+
+### notification
+
+Use instead of *notice* to describe information displayed to a customer about communications, contacts, a service problem, or other item. Don't use *pop-up, toast,* or *banner* for this purpose.
+
+**Examples** When you receive a message, a notification briefly appears at the top of Start ... If you get a notification, tap it before you unlock the phone and you'll be automatically taken to the notification.
+
+### null-terminated, null-terminating
+
+Use *null-terminated* as an adjective, as in *null-terminated string*. Don’t use *null-terminating,* as in *null-terminating character*. Use *terminating null character* instead.
+
+### null, NULL, Null
+
+Use lowercase *null* to refer to a null value. Better yet, use *null value* to avoid confusion with the constant.
+
+Use **NULL** or **Null** (depending on the language) only to refer to the constant.
+
+### number sign (\#)
+
+Always spell out *number* in *number sign.* Don't use *pound sign.*
+
+Don't use the \# symbol preceding a numeral. Spell out *number* instead. For example, use *number 7,* not *\#7*. When space is limited, as in tables, it's OK to abbreviate *number* as *No*.
+
+**Global tip** The abbreviation *No.* isn't used to abbreviate *number* in other languages, so using *No.* for this purpose might lead to mistranslation in machine-translated content.
+
+In social media, it's OK to use the \# symbol to indicate a hashtag. Don't use *number sign* to refer to the hashtag.
+
+**Example** (on X, formerly known as Twitter) A quick look at top conversations and \#Office365 product announcements of the week.
+
+It's OK to use the \# symbol in references to the \# key on the keyboard.
+
+**See also** Keys and keyboard shortcuts term collection
+
+### numeric
+
+Use instead of *numerical*.
+
+For the keypad, use *numeric keypad* instead of *numerical keypad* or *numeric keyboard*.
+
+## O
+
+### object
+
+Don't use *object* as a synonym for *item* or *thing*. Instead, refer to a specific object.
+
+For example, in object-oriented programming, an object is an instance of a class that contains both methods and data and is treated as one entity. Similarly, in COM-based technologies, an object is a combination of code and data that implements one or more interfaces. In assembly language, *object* refers to the object module, which contains data that has been translated into machine code.
+
+### objectives and key results (OKR)
+
+Spell out on the first mention and include the abbreviation in parentheses immediately following the expanded form. Lowercase the spelled out term.
+
+On subsequent mentions on the same screen or pane, or in the same topic, article or flow, it’s OK to use the abbreviation *OKR*.
+
+In UI, if the full term cannot be spelled out due to space constraints, it’s OK to abbreviate on the first mention. If possible, use the spelled out term somewhere else within the same flow for context.
+
+**See also** key result (KR).md), key performance indicator (KPI).md)
+
+### obsolete
+
+Don't use as a verb. Use a phrase such as *make obsolete* instead.
+
+### of
+
+Don't use *of* after another preposition in phrases such as *off of* or *outside of*.
+
+**Example** The taskbar is outside the main window area.
+
+### off-premises, on-premises
+
+**See** Cloud-computing term collection
+
+### offline
+
+One word. Use only in the sense of not being connected to or part of a system or network.
+
+### OK, okay
+
+Use *OK* instead of *okay* or *all right.* Never use *alright.*
+
+### on demand, on-demand
+
+The term *on demand* describes something that's available or provided whenever it's requested or needed.
+
+Don't hyphenate *on demand* when you're using it as an adverbial phrase after a verb.
+
+**Examples** Watch on demand. Provision your resources on demand. You can access reports on demand from the dashboard.
+
+Hyphenate *on-demand* when you're using it as a adjective that comes before a noun.
+
+**Examples** Watch the on-demand webinar. Use on-demand compute resources to scale quickly. The service provides on-demand reporting.
+
+### on-screen keyboard
+
+**See** Keys and keyboard shortcuts term collection
+
+### on-screen
+
+Always hyphenate as an adjective or adverb. Instead of using as an adverb, try to rewrite by using a phrase such as *on the screen*.
+
+### on the fly
+
+OK to use in content for a technical audience to refer to something that's not created until it's needed.
+
+### on
+
+Use *on* as a preposition with:
+
+  - Menus
+  - Tabs
+  - Taskbar, toolbar, ruler, and desktop
+  - Disks, in the sense of a program being on a disk
+  - Networks
+  - Hardware platforms
+  - The web
+
+In COM programming, an interface is implemented *on* an object.
+
+**See also** Describing interactions with UI
+
+### onboarding
+
+Don't use to mean the process of introducing employees to a new role or organization. Use *orientation* instead.
+
+### once
+
+Don't use as a synonym for *after*.
+
+**Example** After you save the document, you can close the app.
+
+### online services
+
+Avoid. If you need to refer generally to apps and services that you access online, mention the services by name or use *services.*
+
+Don’t use *online services* to refer to protocols and data formats, such as XML, SOAP, and WSDL, that provide the means for integrating web-based apps. Use *web services* instead.
+
+**See** web services
+
+### online
+
+One word, both as an adjective and adverb.
+
+**Examples** Search Help for more information. Check online for more up-to-date information.
+
+### onto
+
+Use one word (*onto*) to indicate moving something to a position on top of something else, as in *drag the icon onto the desktop*.
+
+**See also**  sign in, sign out
+
+### opcode
+
+It's OK to use *opcode* to refer to a programming term, such as the *opcode* parameter.
+
+Don't use *opcode* as a shortened form of *operation code*. Use *operation code* instead.
+
+### open source, open-source
+
+Lowercase unless you're talking about the Open Source Initiative.
+
+Hyphenate *open-source* as an adjective preceding a noun, as in *open-source software.* Don't use *open-sourced* as an adjective<em>.</em>
+
+Don't hyphenate in other instances, such as *Open source is a development model in which ....*
+
+Don't use *OSS* as an abbreviation for *open-source software.*
+
+### open
+
+Use *open,* not *opened,* to describe the open state: *an open folder*.
+
+Use *open,* not *start* or *launch,* to describe opening a program or app. Don't use *open* to describe selecting a command, a menu, an option, or other similar element.
+
+**See** Describing interactions with UI
+
+### operating environment, operating system
+
+OK to use in content for a technical audience, but avoid in content for a general audience.
+
+Use *operating environment* or *environment* to describe both hardware and the operating system software.
+
+Use *operating system* to describe only the software.
+
+Use *graphical environment* to describe the graphical user interface (GUI) of an operating system.
+
+Use *on,* *under,* or *with* as prepositions with *operating system*. Don't use *against*.
+
+**Examples**<br />Word 2016 runs with the Windows operating system. <br />Microsoft Exchange Server runs on the Windows Server operating system.
+
+**See also** platform
+
+### opt in, opt out
+
+*Opt in* is a general term for an action that a user takes to subscribe to, sign up for, or start to receive information about a service, app, or site, or to give consent for data collection, processing, and storage.
+
+*Opt out* is a general term for an action that a user takes to avoid subscribing, signing up, or giving consent, or to unsubscribe, cancel a sign-up, or withdraw consent.
+
+Unless space is limited or you're referring to the opt-in or opt-out process in a general way, use a more precise term that gives a clearer idea of what users must do.
+
+**Examples** Sign up to receive our newsletter. Select the checkbox to agree to legal terms and conditions. To give consent for data collection or use, turn on the toggle. To unsubscribe, select the link.
+
+If you must use the terms:
+
+- Use *opt in* and *opt out* as verb phrases. Write *opt in to*, not *opt into*.
+- Use the hyphenated forms *opt-in* and *opt-out* as adjectives. Don't use them as nouns.
+
+**Examples** If you want to opt in to our offer program, follow the link. Complete the opt-out form. Opting out isn't an option.
+
+### option, option button
+
+In general, avoid talking about the UI. Instead, talk about what the customer needs to do. Refer to an option by its UI label only. If you must provide a descriptor, use *option*. Use the exact label text, including its capitalization, but don't capitalize the word *option.*
+
+Avoid referring to the option button itself. Just discuss the option that it controls. When you must mention the button for clarity, use *option button*.
+
+**Examples** Select **No header row.** When you select the **Keep source formatting** option, .... For **Paste options**, select **Keep text only**.
+
+In content for a technical audience, it's OK to use *option* instead of *switch* to refer to a command argument or compiler option, such as **/b** or **/Za**.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### org, organization
+
+Use the term that makes the most sense for your audience.
+
+In content for a business or technical audience, it's OK to use *org* as an abbreviation for *organization.* Don't use a period after the abbreviation.
+
+**Examples** Get an online org chart application that works with Azure Active Directory and Office 365. How to prepare for your cross-org Exchange migration
+
+**See also** company vs. organization
+
+### output
+
+Don't use as a verb. Instead, use a verb that describes the kind of output, such as *write to,* *display on,* or *print to*.
+
+Avoid using as a noun or an adjective in content for a general audience. Use a more specific term instead.
+
+**Examples** Print a document to a file or to a specific printer. The **HttpResponse.Output** property delivers text output to the outgoing HTTP response stream.
+
+### outside
+
+Use instead of *outside of*.
+
+**Example** The taskbar is outside the main window area.
+
+### over
+
+Use *over* to refer to a position or location above something. For quantities, use *more than*.
+
+**Examples** A transparent viewing layer with a red border appears over the diagram. The installed base is more than 2 million.
+
+Don't use to refer to version numbers. Use *later* instead.
+
+**See also** later
+
+### overwrite
+
+Use only to describe replacing existing data with new data. Use *replace* to describe replacing an existing file with a new one that has the same name.
+
+Don't use *overwrite* as a synonym for *type over*.
+
+## P
+
+### p-code
+
+Abbreviation for *pseudocode*. Spell out on the first mention.
+
+Capitalize as *P-code* when it's the first word in a sentence.
+
+Use only in content for a technical audience.
+
+### page
+
+Use *page* or *webpage* to describe one of a collection of web documents that make up a website. Use *page* to refer to the page the reader is on or to a specific page, such as the home page or start page.
+
+In a wizard, use *page* instead of *screen* to refer to an individual screen.
+
+### palette
+
+Use to describe a collection of colors or patterns that the customer can apply to objects.
+
+Most of the time, avoid talking about UI elements. Instead, talk about what the customer needs to do. When you must refer to a palette by name, use bold formatting for the name of the palette. Use sentence-style capitalization unless you need to match the UI.
+
+**Examples** In **Colors**, let Windows pull an accent color from your background, or choose your own color. In the **Color** palette, choose a color for the object outline.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### pan
+
+**See** Touch and pen interaction term collection
+
+### pane
+
+Use *pane* to refer to the separate areas of a split window. For example, a list of resources might appear on one pane and the contents of a selected resource on another pane.
+
+If a pane isn't labeled in the UI, use lowercase for the name that describes it. If a pane is labeled in the UI, use bold on the name.
+
+Use the preposition *in* when you refer to a pane.
+
+Use *open* and *close* as verbs with panes.
+
+**Examples** Open the annotation pane. In the **Score** pane, select an asset to view details.
+
+If you're creating UI text, use sentence-style capitalization for pane names.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### parameter
+
+Use for a value given to a variable until an operation is completed. Don't use to mean *characteristic,* *element,* *limit,* or *boundary*.
+
+**See also** argument vs. parameter
+
+### parent/child
+
+It's OK to use *parent/child* in content for a technical audience to refer to the relationships among processes in a multitasking environment or in content about databases to describe the relationships among nodes in a tree structure.
+
+Don't use as a synonym for a primary/subordinate relationship.
+
+**See also** master/slave
+
+### parenthesis, parentheses
+
+Use *opening parenthesis* or *closing parenthesis* for an individual parenthesis, not *open parenthesis,* *close parenthesis,* *beginning parenthesis,* *ending parenthesis,* *left parenthesis,* or *right parenthesis*. It's OK to use *parenthesis* by itself if it doesn't matter or it's clear which parenthesis is being discussed.
+
+**See also** Formatting punctuation
+
+### passwordless
+
+Avoid. Instead, use wording that's friendlier and more clearly describes the benefit.
+
+When you must use *passwordless,* don't include a hyphen, and use it only as an adjective, not as a noun. For example, use "the steps to a passwordless environment" not "the steps to passwordless."
+
+**Examples** Learn why getting rid of passwords is important. Before you can do away with passwords, you need something to replace them. See how a password-free environment works. Sign in without a password. An authentication solution that doesn't require passwords
+
+### path
+
+Use *path* instead of *pathname,* both in general references and in syntax.
+
+Use *path* to refer to a drive and any folders below the root directory. When a path also specifies a file, use *full path*.
+
+In command syntax, use *path* to represent only the folder portion of the full path:
+
+> **copy** \[*drive:*\]\[*path*\]*filename*
+
+To indicate a path, first type the drive name, followed by a colon and a backslash. Then type the name of each folder in the order that you would open it, separated by a backslash, as follows:
+
+> C:\Documents and Settings\user1
+
+Use *address* or *URL,* not *path,* to refer to a location on the internet.
+
+In general, use *path of,* not *path to,* to refer to the location of a file.
+
+**Example** The full path of my current tax form is: C:\\Documents and Settings\\user1\\My Documents\\Taxes\\This year's taxes
+
+When documenting products for the Mac, use colons with no spaces to separate zones, file servers, shared disks, folders, and file names. File names don't require extensions.
+
+**Example** (Mac) Macintosh HD:My Documentation:Sales CORP-16:TOMCAT:EX130D Mac Temp:Workbook1
+
+**See also**  Formatting common text elements, URLs and web addresses
+
+### PC
+
+**See** Computer and device term collection
+
+### pen
+
+**See** Computer and device term collection
+
+### per
+
+It's OK to use *per* to mean *for each* in statistical or technical contexts. In other contexts, use *a* or the phrase *for each* instead of *per*.
+
+**Examples** Customers who sign in only once a day are rare. You can have only one drive letter per network resource.
+
+Don't use *per* to mean *by* or *in accordance with*.
+
+**Examples** Find all the articles that contain a specific word by following the instructions on your screen. Identify your computer by using the procedure in the next section.
+
+### percent, percentage
+
+Use the percent sign (“%”) with numerals, rather than spelling out “percent.” You don’t need a space between the percent sign and the numeral.
+
+**Exceptions**
+  - Don't use "%" to refer to the symbol itself—refer to the “percent sign.”
+  - Don't use the percent sign at the beginning of a sentence.
+  - Don't use the percent sign to mean "percentage."
+
+### perimeter network
+
+On the first mention, use:
+
+> perimeter network (also known as *DMZ, demilitarized zone,* and *screened subnet*)
+
+After that, just use *perimeter network.*
+
+### peripheral
+
+Don't use as a noun. Use *peripheral device* or a more specific term instead.
+
+**See also** Computer and device term collection
+
+### permissions
+
+Use only to refer to operations associated with a specific shared resource, such as a file, directory, or printer, that are authorized by the system administrator for individual user accounts or administrative groups. Permissions are *granted* or *assigned,* not *allowed*.
+
+If you refer to a named permission, use title-style capitalization and regular type.
+
+Don't use *privileges* or *permission records* as a synonym for *permissions*.
+
+**Examples** Setting the Traverse Folder permission on a folder doesn't automatically set the Execute File permission on all files within that folder. Grant Read, Read and Execute, and List Folder Content permissions to the Users group. Whenever possible, assign permissions to groups instead of users.
+
+**See also** rights, user rights
+
+### personal digital assistant
+
+**See** AI and bot term collection
+
+### phone, phone number
+
+Don’t use *telephone number*. Use *phone number* instead. 
+
+As a UI label, use *Phone*, not *Phone number*. 
+
+For information about referring to mobile phones, see [Computer and device term collection](/style-guide/a-z-word-list-term-collections/term-collections/computer-device-terms).
+
+For information about how to format phone numbers, see [Numbers](/style-guide/numbers).
+### photo
+
+OK to use as an abbreviation for *photograph.* Don't use as a verb. Use *photograph* or *take pictures* instead.
+
+### pin, unpin
+
+Use *pin* to refer to placing an item, such as a tile, an app, or a command, in a given area of the UI, so it's always accessible in that area. Use *unpin* to describe removing a pinned item.
+
+**Examples** When you pin an app, it's added to the Start menu as a new tile. Pin important messages to the top of the message list, and unpin them when you're done with them.
+
+**Pin apps to Start**
+
+1.  Select the **Start** button (shown with the Windows logo), and then select **All apps**.
+
+2.  Press and hold (or right-click) the app you want to pin.
+
+3.  Select **Pin to Start**.
+
+### pinch
+
+**See** Touch and pen interaction term collection
+
+### ping, PING
+
+Don't use *ping* to refer generally to searching for a program.
+
+It's OK to use *p*<em>ing</em> to refer to using the PING protocol, which is used to determine the presence of a host on the internet. Don't spell out PING. If necessary, describe it as Packet Internet Groper.
+
+### pipe
+
+Don't use as a verb in content for a general audience. Use a more specific term, such as *send, move, copy, direct, redirect,* or *write*.
+
+It's OK to use *pipe* as a verb in content for a technical audience to refer to routing data from the standard output of one process to the standard input of another.
+
+The symbol for a pipe in programming content is a vertical bar ( | ).
+
+**See also** Special characters term collection
+
+### placeholder
+
+Don't use as a verb.
+
+For information about formatting placeholders, see Formatting text in instructions and Formatting developer text elements.
+
+### plaintext, plain text
+
+Use *plaintext* only to refer to nonencrypted or decrypted text in content about encryption. Use *plain text* to refer to ASCII files.
+
+### platform as a service (PaaS)
+
+**See** Cloud-computing term collection
+
+### platform
+
+Don't use in content for a general audience.
+
+It's OK to use *platform* in content for a technical audience when you need to distinguish differing behaviors of a function or other API element in various operating systems.
+
+In content for a technical audience, use *cross-platform* to refer to an app or device that can run on more than one operating system.
+
+Use *on* as a preposition with *platform* in discussions about hardware platforms: *on the Intel Atom platform,* for example, but *in Windows 10.*
+
+**See also**  operating environment, operating system
+
+### playlist
+
+One word. A customer *adds* media *to* a playlist and *deletes* media *from* a playlist.
+
+### please
+
+Avoid *please* except in situations where the customer is asked to do something inconvenient or the application or site is to blame for the situation.
+
+**Example** The network connection was lost. Please reenter your password.
+
+### Plug and Play, plug and play
+
+Use *Plug and Play* as a noun or an adjective to refer to a set of specifications developed by Intel for the automatic configuration of a computer so that it works with various peripheral devices. Note capitalization. Don't hyphenate.
+
+It's OK to use all lowercase (*plug and play*) for all audiences to refer to the ability of a computer to automatically configure a device that's added to it.
+
+Don't use as a synonym for *Universal Plug and Play* (UPnP).
+
+**Examples** Plug and Play functionality Plug and Play printer Plug and Play records the information in an event log.
+
+**See also** UPnP
+
+### plugin
+
+A plugin is a component that adds specific abilities to an application. In generative AI experiences, a plugin is a component that extends what a language model or an agent can do by giving it access to capabilities in Microsoft and non-Microsoft services and sites through APIs.
+
+In either case, use one word (no hyphen).
+
+Don't use as a synonym for *add-in* or *add-on*.
+
+**See also** add-in, add-on
+
+### plus sign (+)
+
+Don’t use the plus sign (+) to replace words like *and, over,* and *plus.*
+
+**Exception** Where space is limited, like in UI or a headline, it’s OK to use the plus sign to indicate a count that exceeds a certain number.
+
+**Examples** Microsoft Dynamics 365 and Office 365 are better together. Choose from more than 750,000 apps in Microsoft Store. 999+ connections (in the UI)
+
+**See also** ampersand (&)
+
+### point to
+
+**See** Mouse and mouse interaction term collection
+
+### pointer
+
+In a programming context, a pointer is a variable that contains a memory location. In the rare case where both types of pointers are discussed, use *mouse pointer* and *pointer variable* as necessary to avoid ambiguity.
+
+**See** Mouse and mouse interaction term collection
+
+### pop-up
+
+Don’t use as a noun. For example, don't use *a pop-up;* use *a pop-up window* instead.
+
+Don't use *pop up* or *pops up* as a verb to describe the appearance of a window. Use *open* or a similar verb instead.
+
+It’s OK to use *pop-up window* to refer to windows that pop up in Help. Don’t use *pop-up window* as a synonym for *dialog*.
+
+It’s OK to use *pop-up menu* for a programming audience to describe the menu that appears when a customer right-clicks an item. If you must use a term to describe this type of menu in content for a general audience, use *shortcut menu*.
+
+**Examples** Answer the questions in the wizard as they appear. Some commands carry out an action immediately. Others open a dialog so that you can select options. A pop-up window gives additional information about an option. If you want to print the information in a pop-up window, right-click the window, and then select **Print Topic**. In the pop-up list, select **Microsoft Excel**.
+
+**See also** context menu, shortcut, shortcut menu
+
+### port
+
+Use the verb forms *port to* and *port* only in content for a technical audience in reference to portability.
+
+Don't use in content for a general audience.
+
+### postal code
+
+Unless you're writing content that's specifically for the United States, use *postal code* instead of *ZIP Code*.
+
+**See also** ZIP Code
+
+### pound key, pound sign (\#)
+
+**See** Keys and keyboard shortcuts term collection and Special characters term collection
+
+### power cord
+
+Use instead of *power cable*.
+
+### power down, power up, power off, power on
+
+Don't use. Use *turn off* and *turn on* instead. Don't use *shut down* to refer to turning off a device.
+
+**See also** start, restart shut down, shutdown turn on, turn off
+
+### power user
+
+Don't use to mean that someone must be an expert to use certain programs or features. Instead, identify the specific knowledge or skill that's required.
+
+### pre-
+
+In general, don’t hyphenate words beginning with *pre-,* such as *preallocate* and *preempt,* unless it’s necessary to avoid confusion, as in *pre-engineered,* or if *pre-* is followed by a proper noun, as in *pre-C++.* When in doubt, refer to *Merriam-Webster Dictionary.*
+
+To learn more about hyphenation, see Hyphens.
+
+### preceding
+
+It's OK to use *preceding,* *previous,* or *earlier* to mean earlier in a piece of content, but use a hyperlink instead if you can. Don't use *above.*
+
+### press, press and hold
+
+Use only to describe pushing a physical button on hardware.
+
+**See** Describing interactions with UI Touch and pen interaction term collection Keys and keyboard shortcuts term collection
+
+### preview
+
+Prerelease versions of software and services are typically identified as *Product Name Preview* (preferred) or *Code Name Preview.*
+
+In generic references, lowercase *preview.*
+
+Avoid using *beta* to refer to a prerelease product that's ready for unstructured testing by customers. Use *preview* instead.
+
+**Examples** Office 2016 Preview Windows 10 Insider Preview Microsoft Power BI Preview A preview of Azure Container Service is available.
+
+**See also** sample vs. preview
+
+### print, printout
+
+As a verb, use *print* instead of *print out*. It's OK to use *printout* as the result of a print job, if necessary, but try to be more specific.
+
+### print queue, printer queue
+
+Don’t use. Use *list of documents* instead.
+
+**Examples** Your document will be sent to the printer. Your file will be added to the list of documents waiting to be printed.
+
+### private cloud, hosted private cloud
+
+**See** Cloud-computing term collection
+
+### privileges
+
+Don't use as a synonym for *permissions* or *rights*.
+
+**See** permissions, rights
+
+### profile
+
+Lowercase unless you need to match the UI.
+
+### program file
+
+It's OK to use *program file* as an alternative to *executable file* in content for a general audience. If possible, use the specific name of the file instead.
+
+Don't use *app file* or *application file.*
+
+### program
+
+**See** app, application
+
+### prompt, prompting
+
+The process of instructing an AI to do a task is called *prompting*. We tell the AI a set of instructions (the prompt) and it performs the task. Prompts can be as simple as a question, or as complex as context, instructions, and multiple examples. Prompts can contain prompts, sometimes referred to as prompt chaining.
+
+**Guidelines**
+
+Focus on outcomes: Tell the user how to describe what they want to achieve their desired results, and include clear, relevant examples.
+
+Avoid using *prompt* as a noun within product UI, as in "Write your prompt." Instead, use request as in "Try a different request."
+
+Avoid using *prompt* as a noun phrase, as in "prompt field."
+
+Do not use *prompt* as a verb, as in "Then prompt Copilot to write your reply."
+
+**Learn prompting** If you want quality outputs, you need fine-tuned prompts. To start becoming a prompting pro, check out this prompt crafting guide (for marketing content) from Writer.com. Additional guidance we like:
+
+Prompts for communicators using the new AI-powered Bing - The Official Microsoft Blog
+
+LearnPrompting.org
+
+Resources to learn prompting
+
+**See also**  command prompt
+
+### prop
+
+Don't use as an abbreviation for *propagate*<em>.</em>
+
+### property sheet, property page
+
+Don't use in content for a general audience. Use *dialog box* or *tab* instead.
+
+### property
+
+Use only to reference something named in the UI as a property.
+
+### protected mode
+
+Use instead of *protect mode*.
+
+### public cloud
+
+**See** Cloud-computing term collection
+
+### pull down, pull-down
+
+In general, avoid talking about UI. Instead, describe what the customer needs to do.
+
+Don't use *pull down* as a verb to describe how to use a menu or list. Don't use *pull-down* as an adjective to describe the appearance of a menu or list.
+
+**Examples** In the **Background** list, select **Solid color**. Go to **Tools**, and select **Change language**.
+
+**See also** dropdown Describing interactions with UI Formatting text in instructions
+
+### purge
+
+Use only in the context of a programming term, such as the Purge method. Otherwise, use *delete,* *clear,* or *remove* instead.
+
+### push button, push-button
+
+Two words. Hyphenate as an adjective.
+
+Don't use as a synonym for *button* or *command button*. In content for developers, it's OK to use *push button* parenthetically or to describe programming elements such as the **PushButton** class.
+
+**See also** command button
+
+## Q
+
+### quality, high-quality
+
+Don’t use *quality* by itself as an adjective. Always use *high-quality*.
+
+### quit
+
+Don't use *quit* to refer to any of the following:
+
+  - Closing an app or a program. Use *close* instead. 
+  - Closing a document or window. Use *close* instead. 
+  - The action a program takes to close itself when it has encountered a problem and can't continue. Use *close* instead. 
+  - Ending a session on a computer or network. Use *sign out* instead. 
+  - Ending a network connection. Use *end* instead. 
+
+Use *stop responding,* not *quit,* when an app encounters a problem and can't close itself.
+
+## R
+
+### radio button
+
+Use *radio button* only in content for developers in which the API includes the term. In that case, use wording such as *\<name\> option button* (also known as a *radio button*).
+
+In other content, refer to a radio button by its label. If you must provide a descriptor, use *option*. Capitalize the label text as it appears in the UI, but don't capitalize the word *option*.
+
+**See also** option, option button Describing interactions with UI Formatting text in instructions
+
+### ragged right
+
+Don't use. Use *left-aligned* to describe text with an uneven right edge.
+
+**See** left align, left-aligned
+
+### RAM
+
+**See** memory
+
+### range selection
+
+Don't use. In content for a general audience, use a phrase such as *a range of cells* or a *range of dates* to refer to a selection of adjoining cells, dates, or other items.
+
+Use the same type of phrasing in content for a technical audience, but if you're describing the feature, use *adjacent selection*.
+
+Use *multiple selection* to describe selecting more than one nonadjacent item.
+
+### re-
+
+In general, don’t hyphenate words beginning with *re-* unless it’s necessary to avoid confusion or *re-* is followed by a proper noun. When in doubt, refer to *Merriam-Webster Dictionary.*
+
+**Examples** reenter recover (to get back or regain) re-cover (to cover again) recreate (to take part in a recreational activity) re-create (to create anew)
+
+To learn more about hyphenation, see Hyphens.
+
+### read-only
+
+Always hyphenate.
+
+**Examples** read-only memory This file is read-only.
+
+**See also** read/write, read/write permissions
+
+### read/write, read/write permission
+
+Use instead of *read-write.* Capitalize both *read* and *write* if the context requires *read* to be capitalized.
+
+Use *read/write permission,* not *read/write access*.
+
+### real time, real-time
+
+The term *real time* describes something that's diplayed or reported as an event is happening.
+
+The noun form is two words and typically follows the preposition *in*. Hyphenate as an adjective that precedes a noun.
+
+**Examples**  
+Respond quickly to security events by monitoring them in real time.  
+Respond quickly to security events by using real-time monitoring.
+
+**See also**  
+[near real time, near-real-time](~/a-z-word-list-term-collections/n/near-real-time.md)
+### reboot
+
+Don't use. Use *restart* instead, and be clear that *restart* in this context refers to the device, not to a program or an app.
+
+**Example** After Setup is complete, restart your computer.
+
+If the UI or API uses *reboot* in a label or an element name, it's OK to refer to the label or element name, but use *restart* to describe the action or event that occurs.
+
+**Example** The **Reboot** method shuts down the device and then restarts it.
+
+### recommend
+
+It's OK to use *we recommend* to introduce a Microsoft recommendation. Don't use *Microsoft recommends* or *it is recommended*.
+
+Don't use *recommend* when something is required.
+
+**Examples** Windows 10 requires 16 GB of hard drive space for 32-bit OS and 20 GB for 64-bit OS.<br /> Small storage devices, like devices with 32-GB hard drives or older devices with full hard drives, might require additional storage to complete the upgrade. If you have limited hard drive space available, we recommend that you have a USB flash drive handy when you install Windows 10.
+
+**See also** should vs. must
+
+### Recycle Bin, recycle bin
+
+Capitalize both words when referring to the *Recycle Bin* on the Windows desktop.
+
+Lowercase when referring to the *recycle bin* in OneDrive.
+
+In UI, it's OK to use *Recycle bin* for labels and headings.
+
+Always use the definite article *the,* as in *the* *recycle bin*.
+
+### refresh
+
+Use to describe updating a webpage.
+
+Don't use *refresh* to describe an image being restored on the screen or data being updated. Use *redraw* or *update* instead.
+
+### registry, registry settings
+
+Use lowercase for the word *registry* except when referring to a named system component, such as the Registry Editor.
+
+Use all uppercase letters for the first-level subtrees, separating words with underscore characters. Registry subtrees are usually bold.
+
+**Examples** **HKEY\_CLASSES\_ROOT** **HKEY\_LOCAL\_MACHINE**
+
+Keys are developer defined and are usually all uppercase or a mix of uppercase and lowercase characters, with no underscores. Subkeys are usually a mix of uppercase and lowercase characters.
+
+**Examples** **SOFTWARE** **ApplicationIdentifier** **CurrentVersion**
+
+Refer to an entire subkey path as a *subkey,* not a *path*.
+
+**Example** (typical subkey ) **\\HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\AuthRoot**
+
+In a subkey, use *entries* to describe the items in the **Name** column. Use *values* to describe the items in the **Data** column.
+
+**See also** Formatting developer text elements
+
+### reinitialize
+
+Don't use to mean *restart*.
+
+**See also** initialize, start, restart
+
+### relationship chatbot
+
+**See** AI and bot term collection
+
+### REM statement
+
+OK to use as an abbreviation for *remark statement* in Visual Basic and some other programs.
+
+Don't use generically to refer to a comment. Use *comment* instead.
+
+### remote
+
+It's OK to use *remote* as an adjective to describe a person or computer at another site.
+
+Don't use *remote drive* to describe a drive on a remote computer. Use *network drive* instead.
+
+Don't use *remote* as a verb.
+
+Don't use *remote* as a noun except to refer to a remote-control device.
+
+### remove
+
+Don't use *remove* to mean *delete*.
+
+Use *remove:*
+
+  - To describe taking an item off a list in a dialog box that has **Add** and **Remove** buttons. 
+  - To
+describe taking a toolbar button off a toolbar or hiding displayed data, such as columns in a spreadsheet, without deleting the data.
+  - As a synonym for *unload*. 
+  - As a verb to describe removing add-ins and add-ons. 
+
+**See also**  uninstall, delete, load
+
+### replace
+
+Don't use *replace* as a noun.
+
+**Examples** To replace all instances of a word or phrase at one time .... The **Replace** method replaces text found in a regular expression search.
+
+Use *replace* instead of *overwrite*.
+
+**Examples** Replace the selected text with the new text. Replace the file with the changed file.
+
+**See also** find and replace
+
+### restart
+
+Use to describe closing and reopening a program or app or turning a device off and then immediately back on. Make it clear which of these you're talking about.
+
+### restore
+
+Use as a verb instead of *undelete* to describe restoring an item that was deleted.
+
+Use as a verb to describe restoring an item or condition to its previous state, such as a window that was previously maximized or minimized.
+
+Don't use as an adjective or as a noun in content for a general audience unless you need to match the UI.
+
+**Examples** Restore the file. Restore the window to its minimized state. For more information about System Restore ....
+
+For content about SQL Server:
+
+  - Use *restore* to describe restoring a series of one or more database backups. 
+  - Use *restore* as an adjective only when necessary.
+
+**Examples** Under the full recovery model, first restore one or more data backups, and then restore the subsequent log backups to roll the database forward in time. Restore the database. Use the RESTORE statement to specify the restore operation.
+
+### reverse video
+
+Use instead of *inverse video,* *invert video,* or *reverse screen* to describe the displaying of inverted background and text colors. Use *highlighted* to refer to the appearance.
+
+### right align, right-aligned
+
+Use to refer to text that's aligned at the right margin. Always hyphenate *right-aligned*. Don’t use *right-justified*.
+
+**See also** justify, justified, left align, left-aligned
+
+### right-click
+
+Use only when you need to talk specifically about mouse actions. Define in content that teaches beginning skills if you think it's necessary.
+
+Use *select and hold (or right-click)* when the instruction isn't specific to the mouse.
+
+Hyphenate.
+
+**Examples** Right-click to select the file. Using the right mouse button (right-click) …. Select and hold (or right-click) the Windows taskbar, and then select **Cascade windows**.
+
+**See** Describing interactions with UI, Mouse and mouse interaction term collection
+
+### right justify, right-justified
+
+Don’t use. Use *right-aligned* instead.
+
+See right align, right aligned
+
+### right mouse button
+
+**See** Mouse and mouse interaction term collection
+
+### right, rightmost, right-hand
+
+Don't use *right* as a directional term by itself. Instead, use a term such as *upper right,* *lower right,* *rightmost,* or *the right side of.* Include a hyphen when you use *right* to modify a noun, as in *upper-right corner*. Don't use *right-hand* as a modifier.
+
+**Accessibility tip** Don't use directional terms (*left, right, up, down*) as the only clue to location. Individuals with cognitive disabilities might have difficulty interpreting them, as might people who are blind and use screen-reading software. It's OK to use a directional term if another indication of location, such as *in the* ***Save As*** *dialog box,* *on the* ***Standard*** *toolbar,* or *in the title bar,* is also included. Directional terms are also OK to use when a sighted user with dyslexia can clearly see a change in the interface as the result of an action, such as a change in the right pane when an option in the left pane is selected.
+
+### rights
+
+Use *rights* only in a nonspecific way to refer to system actions that are authorized by the system administrator. For specific references, use *user rights*.
+
+Don't confuse *rights,* which apply to system operations, with *permissions,* which apply to specific system resources, such as files or printers.
+
+Don't use *privileges* as a synonym for *rights*.
+
+**Example** Domain administrators should use a primary user account, which has basic user rights in the domain.
+
+**See also** permissions, user rights
+
+### ROM
+
+**See** memory
+
+### Roman
+
+Don't use to describe type that's neither bold nor italic. Use *regular type* instead.
+
+### root directory
+
+In content for developers, use *root directory,* not *home directory,* to refer to the directory or folder from which all other directories or folders branch. In Windows, the root directory is indicated by a backslash (\\). Don’t shorten to *root* when you mean the directory.
+
+In other content, use *top-level folder*.
+
+**Example** Change to the root directory, and enter the following command: **edit autoexec.bat**
+
+**See also**  top-level folder
+
+### rotate
+
+**See** Touch and pen interaction term collection
+
+### run vs. execute
+
+Avoid *execute* except to follow the UI. Use *run* instead. If the UI includes *execute,* the resulting action is still *run*.
+
+Always use *run* in the context of operating systems, macros, and queries.
+
+**Examples** To run the program, select **Execute**. Commands are run in the order in which they're listed in the file.
+
+### running foot, running head
+
+Don't use. Use *footer* and *header* instead. If you think your audience might search for these terms, use *also known as r*<em>unning foot</em> *and* *running head* on the first mention.
+
+### runs vs. runs on
+
+Avoid *run* for a general audience. For a technical audience, use *run* to refer to an operating system and *run on* to refer to a program.
+
+**Examples** To install Exchange 2016, your computer must be running the full installation of Windows Server. Office 2016 runs on the following versions of Windows: Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 10, Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows 10.
+
+### runtime
+
+Use *runtime:*
+
+  - To indicate an environment required to run apps that aren't compiled to machine language. 
+  - To indicate the time during which an application is running.
+  - As an adjective to describe a thing that's occurring or relevant at runtime.
+
+Don't use *runtime* as a synonym for reader programs, such as Microsoft Office file viewers.
diff --git a/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-s-u.md b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-s-u.md
new file mode 100755
index 000000000..006cd5367
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-s-u.md
@@ -0,0 +1,1052 @@
+# A-Z word list: s-u
+
+Alphabetical Microsoft style guidance for individual words and terms. Each entry gives preferred usage, prohibited usage, and notes.
+
+## S
+
+### (s), (es)
+
+Don't add *(s)* or *(es)* to a singular noun to indicate that it can be singular or plural. Most of the time, use plural instead. If it's important to indicate both, use *one or more*.
+
+**Examples** To add rows or columns to a table, .... To add one or more rows or columns to a table, ....
+
+**See also**  Nouns
+
+### sample vs. preview
+
+Use *sample* to describe a graphic representation of something that might show up on the screen. Use *preview* to describe a graphic representation of exactly what the customer will see on the screen.
+
+**Examples** This displays a sample of what the control will look like with the scheme applied. To preview what the control will look like with the scheme applied, select **Preview**.
+
+**See also** preview
+
+### save
+
+Use as a verb to describe saving app installation files to a device and saving files to a local drive or share.
+
+### scan line
+
+Two words when referring to either the row of pixels read by a scanning device or one of the horizontal lines on a display.
+
+### screen reader
+
+A screen reader is assistive software that renders text and image content as speech or braille output.
+
+When the term is a noun, it's two words. When you're using it as an adjective before a noun, hyphenate it for clarity. Never use a one-word form.
+
+**Examples** The screen reader reads the contents of the screen aloud for users who are blind or have low vision. The app is designed for screen-reader compatibility.
+
+**See also** Writing for all abilities Colors and patterns in text, graphics, and design Alternative text (alt text)
+
+### screen resolution
+
+For screen resolutions, use *number* × *number* instead of *number by number.* For example, use *640 × 480* instead of *640 by 480.*
+
+Use the multiplication sign (×) instead of the letter *x.*
+
+### screen
+
+Use instead of *screenful* or *full screen*.
+
+**Exception** It's OK to say that a program or app is running in *full-screen mode*.
+
+It's OK to use *screen* in instructions to describe what customers see on the screen or how they interact with it.
+
+**See also** Computer and device term collection
+
+### screened subnet
+
+Don't use. Use *perimeter network* instead. On the first mention, it's OK to say:
+
+>perimeter network (also known as *DMZ, demilitarized zone,* and *screened subnet*)
+
+### screenshot
+
+One word.
+
+### script, scriptlet
+
+Avoid *scriptlet*. Most of the time, use *script* or a more specific term.
+
+It's OK to use *scriptlet* when necessary to refer to a specific component in COM, a section of embedded code, or a small script.
+
+### scroll bar, scroll arrow, scroll box
+
+Most of the time, avoid talking about elements in UI. Instead, describe what the customer needs to do.
+
+Don't use *arrow* to refer to a *scroll arrow*.
+
+Don't use *slider* or *slider box* as a synonym for *scroll box*.
+
+Don't use *gray* or *shaded area* to refer to the *scroll bar*.
+
+### scroll
+
+Avoid. Use a verb phrase such as *move through* instead, if the context is clear.
+
+It's OK to use *scroll* in content that teaches beginning skills to describe interacting with a document by using a mouse, keyboard, or other peripheral device.
+
+**Examples** Move through the folder until you see the file you want. Move the wheel button on the Microsoft Arc Touch Mouse to scroll up and down in a document.
+
+### search, search and replace
+
+Don't use *search and replace* to describe finding and replacing things in a document or other location. Use *find* and *replace* instead.
+
+Use *search* and *replace* as verbs, not as nouns or adjectives.
+
+**Example** Search your document.
+
+**See also** find and replace
+
+### search box
+
+Don't capitalize unless you need to match the UI.
+
+### secondary menu
+
+Don't use in content for a general audience. If it's important to describe how the menu works, use *submenu*.
+
+In content for developers, use only in content about creating menus and only if you can't use *submenu*.
+
+### see, see also, and similar phrases
+
+Phrases like *see*, *see also*, *view*, *view all*, and *watch it later* are fine to use from an inclusive design perspective, as long as they're being used in contexts that otherwise support accessibility. The problem is when we use that language and then fail to provide a way for the person to consume the content.
+
+See Accessibility guidelines and requirements for more information about creating products and content that are accessible to people of all abilities.
+
+### select
+
+Use *select* to refer to marking text, objects, cells, and other items that a customer will take action on, such as copying or moving. Describe the marked items as *the selection* or *the* *selected* text, objects, cells, and so on.
+
+Don't use *highlight* or *pick* as a synonym for *select*.
+
+For information about using *select* as a verb in instructions and procedures, see Describing interactions with UI.
+
+### server
+
+**See** Computer and device term collection
+
+### service-level agreement (SLA)
+
+Spell out on the first mention. Use lowercase for the spelled-out term, and note the hyphen. Use *an* not *a* with the acronym.
+
+**Examples** A service-level agreement (SLA) is an agreement between a service company and a service customer. An SLA defines for both the company and the customer when a service job should be completed.
+
+### service-oriented architecture (SOA)
+
+**See** Cloud-computing term collection
+
+### set, specify
+
+Avoid generic terms such as *set* and *specify* to describe customer actions. Try to use more specific verbs.
+
+**Examples** Select a color for an appointment or a meeting. Enter a location for **Tab stop position**.
+
+Don't use *set* to indicate entering or selecting a value in a dialog box or other UI element.
+
+It's OK to use *set* in content for developers to describe entering or selecting the value of a property.
+
+**See also** Describing interactions with UI
+
+### set-top box
+
+Note hyphen. Don't abbreviate.
+
+### set up, setup, Setup
+
+Use as a verb to describe the process of preparing hardware and installed apps for initial use. Two words as a verb, one word as an adjective and a noun. Don't hyphenate.
+
+Capitalize *Setup* when it refers to the Setup program.
+
+**Examples** Unpack everything before you set up your computer. The setup time is about 15 minutes. Your office setup should be ergonomically designed. Run Setup before you open other apps.
+
+### setting, value
+
+Avoid generic nouns, such as *setting* or *value,* in content for a general audience. Use a specific noun, such as *width, color,* or *font,* instead.
+
+**Examples** Select a color for an appointment or a meeting. Enter a location for **Tab stop position**.
+
+It's OK to use *settings* or *values* occasionally when you need to talk generally about more than one. Don't use *attributes* or *properties* as a synonym.
+
+### shaded
+
+Most of the time, talk about the actions that customers should take.
+
+Don’t use to describe commands or options that are in an unusable state—use *not available* or *isn’t available* instead. If you must describe their appearance, use *appears dimmed.*
+
+It’s OK to use *shaded* to describe the appearance of checkboxes that represent a mixture of settings.
+
+**Examples** The command isn’t available until you select text. If the option appears dimmed, it's not available. Selected effects appear shaded.
+
+**See also** unavailable
+
+### shell
+
+OK to use as a noun in content for a technical audience. Don't use in content for a general audience.
+
+Don't use as a verb, such as *shell* or *shell out*. Use more precise terminology, such as *create a new shell* or *return to the operating system*.
+
+### ship
+
+Don't use to refer to making products or services available to customers. Use *release* instead.
+
+**Example** Windows 10 was released in July 2015.
+
+### shortcut, shortcut menu
+
+*Shortcut* is one word as an adjective or a noun. Don't use as a verb. Don't use as a synonym for *link.*
+
+Use *shortcut menu* only if it helps the customer locate the item in the UI. Most of the time, just describe what the customer needs to do.
+
+**Examples** Use **Alt+Spacebar** to display the shortcut menu for the active window. Right-click the selected text, and then select **Copy**. Select the text, open the shortcut menu, and then select **Copy**.
+
+**See also** Describing interactions with UI Keys and keyboard shortcuts term collection pop-up
+
+### should vs. must
+
+Before using *should* or *must,* consider other ways to discuss recommendations or requirements, such as the imperative mood for required actions and a phrase such as *we recommend* for optional ones. Don't use *Microsoft recommends* or *it is recommended*. Be careful to make your tone helpful, not bossy. (For information about the imperative mood, see Verbs.)
+
+**Examples** You'll need an internet connection to install the upgrade. We recommend that you wait for us to notify you when we've confirmed that your PC is ready. Free technical support is available when you register with Microsoft.
+
+Use *should* only to describe an action that's recommended but optional. Don't use *should* to indicate probability. If you can't make a definitive statement, use *might* or rephrase.
+
+**Examples** You should back up your data periodically. If you don't use automatic updating, you should check for updates yourself at least once every week. If the anti-malware app is compatible and current, it will be preserved during the upgrade.
+
+Use *must* only to describe a required action.
+
+**Example** To save copies of a document in the same location, you must save each copy with a different file name.
+
+### shut down, shutdown
+
+Two words as a verb, one word as a noun.
+
+Use *shut down* to describe exiting the operating system and turning off the device in a single action.
+
+Don't use *shut down* to describe turning off a device or as a synonym for *close*.
+
+**Examples** To turn off your computer, select **Settings**, and then select **Shut down**. Use the **Shut down** command to safely close open apps, shut down Windows, and turn off the device. Many computers turn the power off automatically. The accidental shutdown might have damaged some files.
+
+**See also** Describing interactions with UI turn on, turn off sleep
+
+### sign in, sign out
+
+Use *sign in* to describe starting a session on a computer, a device, a network, an app, or anywhere a username and password are required. Use *sign out* to refer to ending a session.
+
+Don't use *log in, login, log into, log on, logon, log onto, log off, log out, logout, sign into, signin, signoff, sign off,* or *sign on* unless these terms appear in the UI (and you're writing instructions).
+
+The verb form is two words, *sign in* or *sign out.* Avoid using as a noun or adjective (*sign-in, sign-out*). Instead, use a more descriptive or precise term.
+
+**Examples** Enter your password to sign in. Learn how to sign in to Power BI service on the web and how to sign out of it. After an extended period without activity, the network will sign you out automatically.
+
+**See also** connect, single sign-on (SSO)
+
+### simply
+
+Don't use to mean that something is easy to do.
+
+**Examples** To publish your files to the web, select **Publish to the web**. When you see a clip that you like, drag it into your document.
+
+### single sign-on (SSO)
+
+Spell out on the first mention, and lowercase the spelled-out term. Note hyphen.
+
+**See also** sign in, sign out
+
+### site map
+
+Two words.
+
+### site
+
+Use to describe a collection of webpages that's part of a larger whole, such as the Microsoft website or the MSDN website. Use *website* instead of *site* if necessary for clarity.
+
+Information is *on* a site, but the address of a site is *at* www.example.com.
+
+**See also** page, URLs and web addresses
+
+### size, resize
+
+It's OK to use *size* as a verb, as in *size the window*.
+
+Use *resize* to mean *change the size of*.
+
+### SKU
+
+Avoid using the abbreviation *SKU* (pronounced "skew") to describe an offering type for a product, because it's jargon. Instead, use a term that's precise and well understood, like *subscription*, *edition*, *version*, or *tier*.
+
+If you need to use *SKU* because customers expect it, you don't need to spell it out. If you choose to spell it out, use *stock-keeping unit (SKU)* at first mention.
+
+**Examples** Pricing depends on the subscription level. Choose a storage tier. For **SKU**, select an option. Remember that **Standard** has more features than **Basic**.
+
+### sleep
+
+Use to describe putting a device into a power-saving state without shutting it down.
+
+**See also** shut down, shutdown
+
+### slider
+
+In general, avoid talking about UI elements. Most of the time, just describe what the customer needs to do.
+
+In content for a general audience, it's OK to use *slider* when you need to describe the UI element used to set a value on a continuous range of possible values, such as screen brightness, mouse-click speed, or volume.
+
+**Figure** A cursor-thickness slider previews the selected thickness.
+
+In content for developers, it's OK to refer to a slider as a *trackbar control*.
+
+Don't refer to the scroll box or a progress indicator as a slider.
+
+**Example** Move the slider downward to decrease the volume.
+
+### slideshow
+
+One word unless you need to match the UI. Don’t use *carousel* as a synonym.
+
+### small caps
+
+Don't use small caps for key names or for *AM* and *PM*.
+
+It's OK to use the term *small caps*. If necessary for clarity, refer to them as *small capitals* on the first mention, followed by a phrase such as, "often referred to as *small caps.*"
+
+### smart card, Smart Card
+
+Two words. Use lowercase for generic references to smart cards or smart card technology.
+
+Capitalize as part of proper nouns, such as *Lenovo* *Integrated* *Smart Card Reader,* but not in general references to smart card implementations.
+
+### smartphone
+
+**See** Computer and device term collection
+
+### SMB
+
+Avoid using the acronym *SMB*. Use *small or medium-sized business* instead.
+
+### snap-in
+
+Always hyphenate. Use only to describe a program that runs in Microsoft Management Console.
+
+### social chatbot
+
+**See** AI and bot term collection
+
+### soft copy
+
+Don't use. Use a more specific term, such as *electronic document* or *file,* instead.
+
+### software as a service (SaaS)
+
+**See** Cloud-computing term collection
+
+### software-plus-services
+
+Don't use.
+
+**See** Cloud-computing term collection
+
+### sorry
+
+Use *sorry* (and similar wording) only in error messages that notify the customer about a serious problem or one that they might find very frustrating, such as:
+  - Data is lost.
+  - The customer can't continue to use the device, service, or application.
+  - The customer must get help from a support representative.
+  - A product or service fails. 
+
+Error messages should apologize only for things that went wrong with the Microsoft product. Don't apologize for problems that are outside the product, such as a broken link or waiting for a network connection to be found. In those cases, be direct about what went wrong.
+
+**Examples** We're sorry, but we detected a problem, and your PC was shut down to protect your files and other data. Sorry, the service isn't available right now. This task couldn't be completed. Please try again. You're not connected. Let's get you back online. The page can't be reached. This page didn't load properly.
+
+**See also** please
+
+### spam
+
+Lowercase.
+
+Use *spam* only to refer to unsolicited commercial email.
+
+Don't use to refer generally to commercial email, such as bulk email sent to a customer list. Don't use to refer to an inappropriate posting to a large distribution list.
+
+Don't use *spam* as a verb.
+
+### specification
+
+Always spell out. Don't use *spec*.
+
+### spell checker
+
+Use *spell checker* as a general term for a tool that checks spelling. To refer to a specific tool, use the name that appears in the UI.
+
+Use *check spelling* as a verb.
+
+Don't use *spell check* as a noun.
+
+**Examples** Use the Spelling and Grammar tool to check spelling in the document. Check the spelling in the document. Use a spell checker to find spelling errors in your document.
+
+### spin box
+
+It's OK to use *spin box* in content for a technical audience to describe a control that users can use to move, or spin, through a fixed set of values, such as dates.
+
+**Figure** The **Duration** field has a clock symbol and arrows for setting the value.
+
+For a general audience, just discuss what the customer needs to do. If you need to refer to the control, refer to a spin box by its label. **Example** the **Start time** box
+
+### split bar, split box
+
+**Figure** The split-bar and split-box symbol appears when the pointer is over an area that can be split.
+
+It's OK to use *split bar* and *split box* in content for all audiences.
+
+### spoofing
+
+It's OK to use *spoofing* in content for all audiences if you're sure that your audience will understand the meaning. To avoid ambiguity, be specific about the kind of spoofing you're referring to, such as *email spoofing* or *IP spoofing*.
+
+### spreadsheet vs. workbook
+
+Use *spreadsheet* to refer to an accounting app, such as Microsoft Excel. Use *workbook* to refer to the file produced using a spreadsheet app.
+
+### spyware
+
+**See** Security term collection
+
+### SQL, SQL Server
+
+When you're referring to a computer that's running Microsoft SQL Server, use *a computer running SQL Server* or *a computer that's running SQL Server*. (Note the capital *S* in *Server*.)
+
+When you're referring to Structured Query Language as *SQL,* treat *SQL* as an acronym pronounced “sequel” and use the indefinite article *a:* *a* *SQL database.*
+
+**Examples**
+
+Connect Power BI to an external data source, such as a SQL database.
+
+Review installation requirements, system configuration checks, and security considerations for a SQL Server installation.
+
+### Start button, Start menu
+
+Capitalize references to the Start menu and the Start button on the Windows taskbar. Don't use bold formatting for *Start* unless you're referring to the menu or button in instructions.
+
+Don't refer to the Start button as the *Windows Start button*.
+
+Don't include the word *button* unless it's necessary for clarity. If you do, *button* is lowercase.
+
+If possible, to help customers locate the button, include the Start graphic :::image type="icon" source="media/start-button-start-menu/967781121.png"::: in references to the Start button.
+
+**Example** You'll find the Start :::image type="icon" source="media/start-button-start-menu/967781121.png"::: button on the taskbar.
+
+### start page
+
+Don't use to refer to the main page of a website or the page a browser displays upon opening. Use *home page* instead.
+
+**See also** home, home page
+
+### start, restart
+
+Don't use *start* to describe selecting a program or app to open it. Use *open* instead.
+
+Use *restart* to describe closing and reopening a program or app or turning a device off and then immediately back on.
+
+**See also** Describing interactions with UI, turn on, turn off
+
+### start up, startup
+
+Don't use *start up* as a verb. Use *start* instead.
+
+**Note** Use *open,* not *start,* to describe selecting a program or app from the Start menu to open it.
+
+Don't use *on startup* or similar noun phrases in content for a general audience. It's OK to use *on startup* in content for a technical audience.
+
+It's OK to use *startup* as an adjective in phrases such as *startup screen*.
+
+**Examples** To open the app, select the icon. When the app opens, a startup screen appears. Open OneNote and start taking notes.
+
+**See also** Start button, Start menu
+
+### status bar
+
+Use instead of *status line* or *message area* to refer to the area at the bottom of a document window that shows the status of a document and other information, such as the meaning of a command. Messages appear *on,* not *in,* the status bar.
+
+**Figure** A progress bar shows a document download and provides a cancel button.
+
+**Figure** A document status bar shows the current page, section, line, and column.
+
+**Example** The page number is displayed on the status bar.
+
+### stop, stop responding
+
+Don't use *stop* to mean *exit a program*. It's OK to use *stop* for hardware operations.
+
+Use *stop responding* only when a program encounters a problem and can't close itself. Use *close* to describe the action a program takes to close itself when it has encountered a problem and can't continue.
+
+**See also** Describing interactions with UI
+
+### storage, storage space
+
+Use *storage* or *storage space* to refer to local capacity on a device.
+
+It's OK to use *storage device* to refer generally to external drives, USB drives, and other types of storage hardware.
+
+When referring to cloud, use *cloud storage* or refer to the specific cloud provider storage in OneDrive instead.
+
+### store, marketplace, gallery
+
+Use *store,* not *marketplace, gallery,* or another word, to refer to any Microsoft online shopping site―whether all products, services, and items are from Microsoft only or from partners as well. Examples: Microsoft Store, Microsoft Store for Business.
+
+In an online store (either in a product experience or the web), avoid including *by* in the publisher line. For example, use *Microsoft,* not *by Microsoft.* If you must include *by,* lowercase it.
+
+**See also** Microsoft Store
+
+### stream, streaming
+
+OK to use as a noun or verb to refer to audio, video, or graphics coming to a browser or media player over the internet. *Stream* is also OK to use as an I/O management term in C programming.
+
+### stretch
+
+**See** Touch and pen interaction term collection
+
+### struct, structure
+
+Don't use *struct* in text to refer to a data structure identified by the **struct** language keyword. Use *structure* instead.
+
+### style sheet
+
+Two words. Use to refer to a file of instructions for formatting a document or to a list of words and phrases and how they're used or spelled in a particular document.
+
+In XML context, use *style sheet* to refer to an .xsl file. Use *Extensible Stylesheet Language* (or its abbreviation, *XSL,* if the term is familiar to your audience) to refer to the related technology.
+
+**See also** Cascading Style Sheets (CSS)
+
+### sub-
+
+In general, don’t hyphenate words beginning with *sub-,* such as *subheading* and *subsection,* unless it’s necessary to avoid confusion or if *sub-* is followed by a proper noun, as in *sub-Saharan*. When in doubt, check *Merriam-Webster Dictionary.*
+
+To learn more about hyphenation, see Hyphens.
+
+### subaddress
+
+Don't use to refer to parts of an address that go to a specific place in a file, such as a bookmark. Use a more specific term.
+
+### subclass
+
+Don't use as a verb. Use a common verb, such as *create a subclass,* instead.
+
+### subnet, subnetwork
+
+In general terms, a subnet (short for *subnetwork*) is a segment of a network. For technical audiences, you can use *subnet* without explaining that it's an abbreviation.
+
+### surf
+
+OK to use in informal contexts to describe a more random browsing than the less informal *browse* implies.
+
+### swipe
+
+**See** Touch and pen interaction term collection
+
+### switch
+
+As a verb, use instead of *activate* or *toggle.*
+
+**Example** Use **Alt+Tab** to switch between open windows.
+
+In content for a technical audience, it's OK to use *switch* as a noun to refer to command-line and compiler options, such as **/Za**.
+
+**See also** turn on, turn off
+
+### symbol
+
+Use to refer to a graphic or special character that represents something else, but differentiate a symbol from an icon. (An icon represents an object the customer can select and open. A symbol can appear on an icon.)
+
+Follow these guidelines when discussing symbols:
+
+  - Write
+out the name of the symbol in text and, if the symbol itself is important, enclose the symbol in parentheses. Use a symbol by itself only in tables and lists where space is limited or in mathematical expressions. <br />**Examples**<br />Enter a backslash (\\) to return to the previous directory. <br />Only 75 percent of the students attended.
+
+  - For
+UI elements, such as buttons, you can use a graphic of the button by itself after it has been named once or if selecting it displays a definition. <br />**Examples**<br />Select the **Minimize** button (shown as a minus sign in a square).<br />Select the **Close** button (shown as an X in a square).
+
+  - Write out the plurals of symbols, showing the use in parentheses. Don't add *s* or *'s* to a symbol. <br />**Example** <br />Enter two backslashes (\\\\) to show a network connection. 
+
+  - Don't insert a space between a number and the symbol it modifies. <br />**Examples**<br />75%<br />\<100 
+
+**See also** Special character term collection, Keys and keyboard shortcuts term collection
+
+### sync
+
+You can abbreviate *synchronize* or *synchronization* to *sync* for a friendlier tone, if it works well in the context. For example, a user can sync a file, folder, or library with a local drive, a SharePoint drive, a server, or the cloud. A user can also sync settings, messages, and other data across devices, apps, and accounts.
+
+Abbreviations of *synchronize* and *synchronization* don't save space when they're localized. In languages other than English, localization uses the unabbreviated forms.
+
+**Guidelines**
+
+- Don't include *h* in the abbreviation. Use *sync*, *syncs*, *synced*, and *syncing*, not *synch*, *synchs*, *synched*, or *synching*.
+
+- In general, use the phrase *sync with* instead of *sync from* or *sync to*. If information is being synced to and from two sources, describe it as syncing between or syncing across.
+
+- Don't use *sync* to abbreviate *synchronous*.
+
+### system administrator
+
+**See** administrator, admin
+
+### system prompt
+
+**See** command prompt
+
+### system software
+
+Use *system software* (singular) instead of *systems software* (plural).
+
+### system tray
+
+In Windows 11, use to refer to the area on the taskbar where the clock and system notifications appear.
+
+In earlier versions of Windows, this UI element was referred to as the *notification area*.
+
+**See also** notification area
+
+## T
+
+### tab
+
+Don't use as a verb.
+
+As a noun, use only to refer to tabs on a ribbon, a webpage, in a dialog box, and so on.
+
+For other uses, clarify the meaning with a descriptor, such as *the Tab key, a tab stop,* or *a tab mark on the ruler*.
+
+**Examples** Use the **Tab** key to move through a dialog box. Set a tab stop on the ruler. On the **View** tab ....
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### table of contents
+
+Don't use *Table of contents* as the heading for the list of contents at the beginning of a document or file. Use just *Contents* instead.
+
+It's OK to refer generically to a *table of contents*.
+
+Don't use to describe on-screen navigation.
+
+### tablet
+
+**See** Computer and device term collection
+
+### tap, double-tap, tap and hold
+
+**See** Touch and pen interaction term collection
+
+### target drive, target file
+
+Don't use. Refer to the specific drive, folder, or file instead. If the concept of *target* is important to the discussion, use *destination drive* or *destination file* instead.
+
+**Examples** Set your phone to automatically save photos and videos to Microsoft OneDrive. By default, the file is saved to the Scanned documents folder. Copy the file to the USB drive.
+
+### taskbar
+
+One word.
+
+### terabyte, TB
+
+**See** Bits and bytes term collection
+
+### terminate
+
+Don't use as a synonym for *close* or *exit*.
+
+In content for a technical audience, it's OK to use *terminate* in phrases such as *null-terminated string* or *terminate a process.*
+
+**See also** Describing interactions with UI
+
+### text box
+
+Refer to a box in which the user enters text only by its label. If you must use a descriptor, use *box*. Don't use *field* or *entry field,* except in content about database programs.
+
+**Examples** **File name** box Enter or update an email address for **Work email**.
+
+In content for developers, it's OK to use *text box* in content about designing and developing the UI.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### text, text message
+
+Use as an adjective, a noun, or a verb in the context of SMS messages. Use *text message* and *send* or *receive* *a text message,* if necessary, to avoid ambiguity.
+
+Use *text* or *text message* rather than *SMS* (short message service) or *MMS* (multimedia messaging service) for the US audience. For markets where SMS may be the more common usage, localization teams will use the appropriate term.
+
+**Global tip**  In some languages, *text* is translated differently as a noun and a verb. Provide enough context for localization to determine how to translate *text.* For example, instead of *text a friend,* say *send a text to a friend* or *text a quick message to a friend.*
+
+**See also** message
+
+### thanks, thank you
+
+In general, use *thanks* not *thank you.* It's OK to use *thank you* in content that has a formal tone or is about a serious subject, such as cybersecurity or privacy.
+
+Don't use *thanks* unnecessarily. Use *thanks* as the closing in email, a letter, or a similar message. Otherwise, thank the customer only when they've been inconvenienced or they went out of their way to do something.
+
+**Examples** Thanks for your feedback. Microsoft offers a 10 percent military discount as a way to say thank you for your service.
+
+### that vs. which
+
+Use *that* at the beginning of a clause that’s necessary for the sentence to make sense. Don’t put a comma before *that.*
+
+**Global tip** Include *that* even if the sentence is clear without it. It helps to clarify the sentence structure.
+
+Use *which* at the beginning of a clause that adds supporting or parenthetical information. If you can omit the clause and the sentence still makes sense, use *which,* and put a comma before it.
+
+**Examples** To learn more about features that aren’t supported in the trial version, see the feature comparison chart. Catch the latest episode of “This Week on Windows,” which looks at the new Surface Book and more. The comparison chart shows which features aren't supported in the trial version.
+
+Don’t use *that* or *which* in clauses that refer to a person. Use *who* instead.
+
+**See also** who vs. that
+
+### thousand, K
+
+**See** Numbers
+
+### tile, Live Tile
+
+Lowercase *tile* in general references to the shortcuts on the Start menu that customers can move around. These can be static, live, or content tiles.
+
+Capitalize *Live Tile* to describe the feature and in marketing materials.
+
+### timeout, time out
+
+One word, unhyphenated, as a noun or an adjective in computing contexts. Two words as a verb phrase.
+
+In computing, a *timeout* is an event that interrupts a running process if some expected action or event doesn't occur within a predefined time.
+
+**Examples**
+
+Noun: After 30 seconds, a timeout occurs, and you must resubmit your query.
+
+Adjective: If you receive a timeout error, try to sign in again.
+
+Verb phrase: If there is no response within 30 seconds, the connection times out.
+
+### time stamp
+
+Two words.
+
+### to-do
+
+Don’t use *to-do* as a noun. Always hyphenate as an adjective. Don't capitalize.
+
+**Examples** items on your to-do list Here's what you need to do.
+
+### toast
+
+Don't use to refer to a notification triggered by an app or the operating system that's displayed in a pop-up notification. Use *notification* instead.
+
+### toggle
+
+Don't use as a verb. Instead, use *switch, turn on,* or *turn off* with the name of the toggle or command to describe what the customer must do.
+
+OK to use as a noun or an adjective, as in *toggle key* or *toggle switch.* A toggle turns a particular mode on or off.
+
+When you must refer to a toggle by name, use bold formatting for the name of the toggle. Use sentence-style capitalization unless you need to match the UI. Include the word *toggle* if it adds needed clarity.
+
+**Examples** Use the **Caps lock** key to switch from typing capital letters to typing lowercase letters. To switch between Normal, Outline, and Slide Sorter views, use the buttons on the **View** tab. To make text and apps easier to see, turn on the toggle under **Turn on high contrast**. To keep all applied filters, turn on the **Pass all filters** toggle.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### tone
+
+Don't use to refer to a beeping sound. Use *beep* instead.
+
+It's OK to use *tone* in other contexts dealing with sound, such as a *dial tone* or a *tone* coming from a speaker.
+
+### tool
+
+Use *tool,* not *utility,* to describe a feature that helps customers accomplish tasks.
+
+**See also** add-in, add-on app, application applet Control Panel
+
+### toolkit
+
+One word.
+
+### tooltip
+
+A tooltip is a small pop-up note that provides information about a UI element (such as a control, icon, or link) when a user hovers over it or selects it.
+
+The term *tooltip* is one word and lowercase. Don't spell it as *ToolTip*.
+
+The guidelines for creating tooltips vary by product. Here are general principles:
+
+- Use them sparingly because they can be distracting.
+- Be brief.
+- Make sure that the information is helpful as a tip and doesn't just repeat what a label shows.
+- Use sentence-style capitalization. (Capitalize only the first word and proper nouns.)
+- If the tooltip is a fragment, don't end it with a period. If it needs to read like a full sentence, end it with a period.
+
+### top left, top right
+
+Don't use.
+
+**See** upper left, upper right
+
+### top-level folder
+
+In content for a general audience, use instead of *root directory* to refer to the directory or folder from which all other directories or folders branch.
+
+In content for developers, use *root directory*.
+
+**Example** The top-level folder for most customers is the Documents folder.
+
+**See also** root directory
+
+### touch-sensitive
+
+Always hyphenate.
+
+### touchpad
+
+**See** Computer and device term collection
+
+### touchscreen
+
+**See** Computer and device term collection
+
+### toward
+
+Use instead of *towards*.
+
+### trackball
+
+**See** Computer and device term collection
+
+### trailing
+
+Use instead of *following* in phrases such as *trailing periods,* *trailing slashes,* and *trailing spaces,* which might occur at the end of strings, parameters, or other values. *Trailing* in this context is the opposite of *leading.*
+
+### trojan horse, trojan
+
+**See** Security term collection
+
+### turn on, turn off
+
+Use instead of *power on/power off, start/stop,* or *switch on/switch off* to mean turning the device on and off.
+
+Use instead of *enable* and *disable* to refer to commands and features that can be activated or deactivated. Or use more specific pairs of words such as *make available* and *make unavailable*; *show* and *hide*; *add* and *remove*; or *allow* and *block*.
+
+Don't use to refer to selecting or clearing checkboxes in instructions. Use *select* and *clear* instead. It's OK to use *turn on/turn off* to refer to webpage options and toggles.
+
+**Examples** To turn on pop-up blocking …. To keep all applied filters, turn on the **pass all filters** toggle. If the command prompt isn’t available, your network administrator might have turned off this feature.
+
+**See also** Describing interactions with UI disable, disables (functionality) enable, enables shut down, shutdown unavailable
+
+### turnkey
+
+One word.
+
+### type
+
+**See** Describing interactions with UI
+
+## U
+
+### UK
+
+Avoid using as an abbreviation for *United Kingdom* unless space is limited. 
+
+Don't use as a synonym for *Great Britain (GB)* or *England.*
+### Ultrabook
+
+Use only to differentiate the Intel device from other types of thin and light laptops.
+
+**See also** Computer and device term collection
+
+### un-
+
+In general, don’t hyphenate words beginning with *un-,* such as *undo* and *unread,* unless it’s necessary to avoid confusion, as in *un-ionized,* or unless *un-* is followed by a proper noun, as in *un-American.* When in doubt, check *Merriam-Webster Dictionary.*
+
+To learn more about hyphenation, see Hyphens.
+
+### unavailable
+
+Most of the time, talk about the actions that customers should take rather than describing UI.
+
+When you must discuss UI, use *not available* or *isn’t available* instead of *unavailable, disabled,* or *grayed* to describe commands and options that are in an unusable state. Use *appears dimmed* if you must describe their appearance. It’s OK to use *unavailable* to describe an outage or a service that isn’t offered to certain customers.
+
+**Examples** The command isn’t available until you select text. If the option appears dimmed, it's not available. If the command prompt isn’t available, your network administrator might have turned off this feature. Some My Site features are temporarily unavailable. Please try again later.
+
+**See also** disable, disabled, turn on, turn off
+
+### uncheck, unmark, unselect
+
+Don't use to refer to clearing a checkbox. Use *clear* instead.
+
+### undelete
+
+Don't use.
+
+**See** restore
+
+### underline vs. underscore
+
+Use *underline* to describe text formatting that puts a line under the characters. Use *underscore* to refer to the underscore character ( \_ ).
+
+### undo
+
+OK to use as a verb to describe the action associated with the **Undo** command. Don't use as a noun. For example, don't say, *After an undo, you can redo ....*
+
+**Examples** To undo multiple actions .... After undoing an action, ....
+
+### uninstall
+
+Use *uninstall* as a verb to describe removing apps, programs, and hardware drivers from a device.
+
+Don't use *uninstall* as a noun.
+
+**See also** remove
+
+### unregister
+
+Don't use in content for a general audience. It's OK to use *unregister* in content for developers.
+
+### unwanted software
+
+**See** Security term collection
+
+### upgrade
+
+Use as a verb to describe replacing an installed version of a product with a newer version of the same product. Use as a noun to describe the process of upgrading software.
+
+Don't use *upgrade* as a synonym for *update,* *service pack,* or any other release that occurs between product versions.
+
+**Examples** Upgrade qualified Windows 7 or Windows 8.1 devices for free. The upgrade was successful.
+
+### upload
+
+Use as a verb to describe transferring files from a local device to a website, server, or share.
+
+When you use *upload* as a verb, describe what the customer is transferring *and* where the customer is transferring it *to.* In grammatical terms, use both a subject (the thing to be uploaded) and an object (the thing the subject is uploaded to) with the verb *upload.*
+
+**Example** Upload a document from your computer to this library.
+
+**See also** download, load
+
+### UPnP
+
+Don't spell out as *Universal Plug and Play*. Don't use as a synonym for *Plug and Play* or *PnP*.
+
+Use *UPnP* as an adjective followed by *certified,* if appropriate, and a specific term, such as *device, architecture,* or *standards.*  
+**Example**  
+This UPnP certified device features .... 
+
+Don't use *UPnP* to refer to an uncertified device.
+
+Don't use as a noun by itself. For example, don't say, *UPnP is an architecture for pervasive peer-to-peer network connectivity.* Rephrase the sentence as, *The UPnP architecture enables pervasive peer-to-peer network connectivity.*
+
+For other guidelines, see the [Open Connectivity Foundation website](https://openconnectivity.org/). 
+
+**See also** [Plug and Play, plug and play](/style-guide/a-z-word-list-term-collections/p/plug-and-play)
+### upper left, upper right
+
+Hyphenate as adjectives. Use instead of *top left* and *top right*.
+
+**Example** The upper-right corner
+
+**Accessibility note** Don't use directional terms (*left, right, up, down*) as the only clue to location. Individuals with cognitive impairments might have difficulty interpreting them, as might people who are blind and use screen-reading software. It's OK to use a directional term if another indication of location, such as *in the* ***Save As*** *dialog box, on the* ***Standard*** *toolbar,* or *in the title bar,* is also included. Directional terms are also OK to use when a sighted user with dyslexia can clearly see a change in the interface as the result of an action, such as a change in the right pane when an option in the left pane is selected.
+
+### uppercase
+
+Most of the time, use *capital letters* instead of *uppercase.* It's OK to use *uppercase* when comparing with *lowercase* or to follow the UI.
+
+One word. Don't use *uppercase* as a verb. Don't use *uppercased*.
+
+When using *uppercase* and *lowercase* together, don't use a suspended hyphen (as in *upper- and lowercase*). Spell out both words instead.
+
+**Examples** Change all the lowercase letters to uppercase. Change the case of both lowercase and uppercase letters.
+
+### upsize
+
+Don't use<em>.</em> Use *scale up* instead.
+
+### upward
+
+Use instead of *upwards.*
+
+### URI
+
+A uniform resource identifier (URI) is a series of characters that identify a resource. A URL is a type of URI.
+
+**Guidelines**
+
+- In content for a general audience, use *resource ID* rather than *URI* unless you need to match the interface.
+
+- In content for a technical audience, you don't need to spell out *URI* on the first mention.
+
+- If you need to spell out the term, use lowercase.
+
+- Use *a,* not *an,* as an article before *URI*.
+
+- Use *of* (not *for*) to describe the relationship of the word *URI* to a resource. 
+
+**Example** Copy the URI of the resource that you created.
+
+### URL
+
+In content for a general audience, use *address* rather than *URL*. In content for a technical audience, don't spell out *URL* on the first mention. If you have a reason to spell out URL, use *uniform* *resource locator*. Use *a,* not *an,* as an article preceding *URL*.
+
+Use *of* (not *for*) to describe the relationship of the word *URL* to a resource.
+
+**Example** Search results include the URL of the page.
+
+**See also** URLs and web addresses
+
+### US
+
+It's OK to use *US* as an abbreviation for *United States* as an adjective and when space is limited. Spell out *United States* as a noun except when third-party, legally required content specifies otherwise. 
+
+Don't use *USA,* *U.S.,* or *U.S.A.*
+
+If you use the abbreviation, you don't have to spell out *United States* on the first mention.
+### usable
+
+Use instead of *useable.*
+
+### USB
+
+**See** Computer and device term collection
+
+### use terms
+
+Don't use to mean *license terms.*
+
+**See** Microsoft Software License Terms
+
+### user, end user
+
+Don't use *end user*.
+
+Avoid *user* when you can. Use *audience,* *customer*<em>, person, people, employee, coworker,</em> or *you* instead.
+
+It's OK to use *user* in content for developers to distinguish the technology developer from the technology user. It's also OK to use *user* in content for technology professionals to distinguish the system administrator from the system users.
+
+### user rights
+
+Use *user rights* only to refer to Windows security policies that apply to individual user accounts or administrative groups. The system administrator manages user rights through the User Rights Assignment snap-in. User rights are *assigned,* not *granted* or *allowed*.
+
+When you refer to a named user right, use sentence-style capitalization and bold formatting for the name itself.
+
+If an operation requires that the user be signed in to an account that's a member of a specific administrative group, refer to the group instead of to the associated user rights.
+
+Don't use *privilege* as a synonym for *user right*.
+
+**Examples** You must have the **Perform volume maintenance tasks** user right to perform this task. You must be signed in as a member of the Administrators group to perform this task.
+
+**See also** permissions, rights
+
+### using, by using, with
+
+In instructions or technical content, use *by using* or *that use* to eliminate ambiguity.
+
+**Examples** Refine your pictures by using the photo editor. Azure DNS is a hosting service that uses Azure infrastructure to provide DNS name resolution.
+
+Don't use *with* as a synonym for *using* or *by using.* It's OK to use *with* in marketing contexts and with product and service names.
+
+**Example** With OneDrive, you can share your favorite things across your favorite devices, including PCs, Macs, tablets, and phones.
+
+### utility
+
+Don't use.
+
+**See** add-in, add-on app, application applet tool Control Panel
diff --git a/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-v-z.md b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-v-z.md
new file mode 100755
index 000000000..2a2c6269f
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/a-z-term-list-v-z.md
@@ -0,0 +1,446 @@
+# A-Z word list: v-z
+
+Alphabetical Microsoft style guidance for individual words and terms. Each entry gives preferred usage, prohibited usage, and notes.
+
+## V
+
+### value axis
+
+Lowercase. Don't hyphenate.
+
+Usually refers to the vertical axis in 2D charts and graphs, which shows the values being measured or compared. Refer to it as the *value (y) axis* on the first mention. On subsequent mentions, use *y-axis*. It's OK to use *vertical (y) axis* in content for a general audience.
+
+Don't use italic formatting for the *y* in *y-axis* unless the entire word is italic.
+
+In 3D charts, the z-axis is usually the value axis.
+
+**See also** category axis, z-axis
+
+### versus, vs.
+
+In headings, use the abbreviation *vs.,* all lowercase. In text, spell out as *versus*.
+
+### video call, videoconference
+
+Use *video call,* not *videoconference,* when you need to be specific. Otherwise, it's OK to use *call* or *meeting*.
+
+In a verb phrase, follow the UI or use *start a video call, join a video call, participate in a video call,* or *end a video call*.
+
+### video card
+
+Use *video card* instead of *video adapter,* *display adapter,* *graphics adapter*, *graphics card*, or *graphics board*<em>.</em>
+
+### video display
+
+Don't use.
+
+**See** Computer and device term collection
+
+### video driver
+
+Use *video driver* instead of *display driver* or *graphics driver.*
+
+### video game, video-game
+
+Two words as a noun. Hyphenate as an adjective.
+
+**Examples** Tips for playing your video game Video-game tips
+
+### virtual agent
+
+**See** AI and bot term collection
+
+### virtual
+
+Use only to refer specifically to a device or service that appears to be something it's not or that doesn't physically exist. For example, a *virtual machine* isn't an actual computer; it's something that emulates one.
+
+Don't use in content for a general audience.
+
+**Examples** Each Azure service is supported by a different type of virtual machine. virtual desktop virtual memory virtual root virtual server
+
+### virtualize
+
+Don't use in content for a general audience.
+
+In content for a technical audience, it's OK to use *virtualize* sparingly to mean creating a virtual implementation. For example, it's OK to use *virtualize storage* to refer to creating virtual storage.
+
+Don't use as a synonym for *simulate*.
+
+### visit
+
+To describe opening or switching to a website or webpage, use *go to* in most cases.
+
+It's OK to use *visit* in the context of a website or webpage if you're using a tone that's meant to imply:
+
+* More of a suggestion than a required action.
+* The intention of staying for a while and browsing around, rather than viewing specific information.
+
+**Examples** For information about billing, go to the pricing page. Visit the product website to learn about offerings, get advice, and more.
+
+**See also** Describing interactions with the UI
+
+### voice-activated device
+
+**See** AI and bot term collection
+
+### voice user interface (VUI)
+
+**See** AI and bot term collection
+
+### voicemail
+
+One word. Don't abbreviate as *v-mail* or *vmail*.
+
+Use to refer generically to a voicemail app, to refer collectively to messages, or to refer to an individual message. If necessary to distinguish these meanings, use *voicemail message* or *message* to refer to an individual voicemail.
+
+Don't use as a verb. Use *leave a voicemail* or *leave a message* instead.
+
+**Examples** You have two new voicemails. To respond to the caller with a message ....
+
+### vulnerability
+
+**See** Security term collection
+
+## W
+
+### W3C
+
+Don't spell out.
+
+### want
+
+Use instead of *wish* or *desire* when the customer has a choice of actions. Don't use when you mean *need,* which indicates a requirement or obligation.
+
+**Example** Select **PC info** if you want to find out what version of Windows you're running.
+
+### we
+
+In general, don't use. Focus on the customer, and avoid making Microsoft the subject.
+
+It's OK to use phrasing like *we recommend* if it helps you avoid awkward phrasing like *it's recommended,* but write around it if you can.
+
+**Examples** The scheduled default setting is the easiest way to keep your computer up to date. (Instead of *We recommend that you use the scheduled default setting ....)* Select the people you want to give permission to. We'll verify their identities before opening the document. In September, we took a major step forward in introducing Windows 10 to our enterprise customers.
+
+**See also** Microsoft
+
+### wearable, wearable device
+
+**See** Computer and device term collection
+
+### web services
+
+Use *web services* to refer to protocols and data formats, like XML, SOAP, and WSDL, that provide the means for integrating web-based apps.
+
+Don’t use *web service* or *web services* to refer generally to apps and services that you access online. Instead, mention the service by name or use *service* or *services* instead.
+
+### web, World Wide Web, WWW
+
+Lowercase *web* as a modifier except to match UI or in feature names that include *web.*
+
+Avoid the phrase *World Wide Web.* Use *the web* instead.
+
+Lowercase *www* in URLs and internet addresses.
+
+Use *on* to refer to material existing on the web. Use *to* or *on* to refer to the action of creating and publishing something *to the web* or *on the web.*
+
+The following terms that include *web* are one word:
+
+  - webpage 
+  - website 
+  - webcam 
+  - webcast 
+  - webmaster 
+  - webzine 
+
+The following terms that include *web* are hyphenated:
+
+  - web-centric 
+  - web-based 
+  - web-enabled 
+
+The following terms that include *web* are two words:
+
+  - web address
+  - web app 
+  - web browser 
+  - web content 
+  - web crawler 
+  - web document 
+  - web folder 
+  - web part
+
+**See also** URLs and web addresses
+
+### wellbeing
+
+Do not use *well-being*, but *wellbeing*. Do not hyphenate.
+
+**Example** MyAnalytics gives you insights into your work patterns around focus, network, *wellbeing*, and collaboration over the past four weeks.
+
+### where
+
+Use to introduce a list, as in code or formulas, to define the meaning of elements such as variables or symbols.
+
+**Example** Use the following formula to calculate the return, where: *r* = rate of interest *n* = number of months *p* = principal.
+
+### while
+
+Use only to refer to something occurring in time. Don't use as a synonym for *although,* *whereas, on the contrary,* or *in spite of*.
+
+**Examples** We're having trouble getting this info right now. Check back in a little while. Although the icon indicates that the print job is finished, you might have to wait until a previous job is finished.
+
+### white hat hacker
+
+See Security term collection
+
+### white paper
+
+A white paper is a research-based report that offers a focused description of a complex topic, usually involving a product or a study of its industry.
+
+Use two words.
+
+### white space
+
+Two words.
+
+### whitelist
+
+Never use *whitelist*. Use *allow list* instead.
+
+For more specific usage, *safe senders list* can be used.
+
+**Examples** You can use *safe senders lists* to help with false positives. The *allow list* is a list of digits that will not be blocked by the app.
+
+### who vs. that
+
+Use *who* instead of *that* to introduce clauses referring to people.
+
+**Example** Custom Setup is the best choice for customers who want to alter the standard Windows configuration.
+
+### Wi-Fi
+
+Try to use a general phrase instead, such as *wireless network,* or refer to the specific technology that you're describing, such as *wireless LAN*.
+
+*Wi-Fi* is a proper noun and a registered trademark. Capitalize and hyphenate when referring specifically to Wi-Fi technologies. Don’t use *WiFi, wifi,* or *Wifi*. Don’t include the registered trademark symbol (&reg;).
+
+### wildcard character
+
+Use *wildcard character,* not just *wildcard,* to describe a character used to represent one or many characters, such as the asterisk (\*) or question mark (?).
+
+*Wildcard* is one word.
+
+### window
+
+Don't use as a verb.
+
+**See also** Describing interactions with UI, Formatting text in instructions
+
+### Windows 10, Windows 11
+
+Always use the entire name. Don't precede the name with *Microsoft.*
+
+### Windows Explorer
+
+Don't use.
+
+**See** File Explorer
+
+### Windows, Windows-based
+
+Use *Windows* as a modifier for aspects or elements of the Windows operating system. Don't use *Windows-based.*
+
+It's OK to use *Windows user* sparingly to avoid awkward constructions, but try to avoid *user* in general.
+
+**Examples** Windows app Windows device the Windows Recycle Bin a device running Windows
+
+**See also** user, end user, runs vs. runs on
+
+### wireframe
+
+One word.
+
+### wireless
+
+Avoid talking about wireless technology to general users except in the context of connecting to a network. Even in that context, whenever you can, discuss connecting to the internet without referring to the technology.
+
+### wizard
+
+In general, don't use the term *wizard* unless it appears in the UI. Instead, talk about what the customer needs to do to accomplish the task.
+
+It's OK to use *wizard* in content for a technical audience that discusses how to develop wizards.
+
+Use lowercase for the generic term *wizard*. Capitalize *wizard* if it's part of a feature name that appears in the UI. (This is uncommon.)
+
+If you need to refer to an individual screen in a wizard, call it a *page*.
+
+### word processing, word-processing
+
+Use *word processor* or *word processing* as a noun.
+
+Hyphenate *word-processing* as an adjective.
+
+Don't use *word process* or *word processing* as a verb. Use *write, format*, or another term instead.
+
+### wordwrap, wordwrapping
+
+Don't use.
+
+### work area, workspace
+
+*Work area* is two words. *Workspace* is one word.
+
+In general, don't discuss UI. Instead, talk about what the customer wants to do.
+
+If it's necessary to describe UI, use *workspace* to refer to the area within a window where the customer interacts with the UI.
+
+Use *work area* only when the term has a specific meaning in a particular product.
+
+### work style
+
+Two words.
+
+### workgroup
+
+One word.
+
+### working memory
+
+Don't use. Use *available memory* instead.
+
+### workstation
+
+One word.
+
+Avoid except in discussions of clients and servers.
+
+### workstream
+
+Use as one word without a hyphen.
+
+**Examples** *Workstreams* are channels within a team that aid the team in organizing their work.
+
+Each channel represents a different topic or *workstream* within the overall team.
+
+Creating channels is a great way to organize conversations and files by *workstream* or subject.
+
+### worldwide vs. international
+
+Use *worldwide* to describe something that encompasses all regions or involves the entire world. It's OK to use *global* to mean *worldwide*.
+
+**Examples** Get one month of free, worldwide calling. OneNote Mobile for Android is now available in more than 20 markets worldwide. Ensuring global acceptability in the usability of our products along with local relevance (world readiness).
+
+Don't use *international* in the context of something that encompasses the entire world as it can imply a US-centric worldview.
+
+Don’t use *international* to mean “outside the United States.” Instead, refer to a specific region or use wording that describes what you mean.
+
+**Examples** In the first half of 2016, Azure achieved new certifications in Japan, Spain, and the United Kingdom and expanded certifications in seven other regions. Microsoft is driving the transformation of business and industry across Europe and around the world.
+
+**See also** global
+
+### write-only
+
+Always hyphenate.
+
+**See also** read/write, read/write permission
+
+### write-protect, write-protected
+
+Always hyphenate.
+
+Use *write-protect* as a verb. Use instead of *lock* to refer to the action of protecting disks from being overwritten.
+
+Use *write-protected* as an adjective.
+
+**Examples** to write-protect a disk a write-protected disk
+
+## X
+
+### x-axis
+
+Lowercase. Hyphenate.
+
+On the first mention, use *category (x) axis* to refer to the horizontal axis in charts and graphs that shows the categories being compared. On subsequent mentions, use *x-axis.* It's OK to use *horizontal (x) axis* in content for a general audience.
+
+Don't use italic formatting for the *x* in *x-axis* unless the entire word is italic.
+
+**See also** value axis, category axis
+
+### x-coordinate
+
+Lowercase. Hyphenate.
+
+Don't use italic formatting for the *x* in *x-coordinate* unless the entire word is italic.
+
+### x
+
+Use a lowercase *x* in italic type as a placeholder number or variable.
+
+Don't use *x* to refer to a generic, unspecified number. Use *n* instead.
+
+Don't use *x* in place of a multiplication sign.
+
+**See also** n, multiplication sign (×)
+
+### XON/XOFF
+
+Note capitalization and slash.
+
+## Y
+
+### y-axis
+
+Lowercase. Hyphenate.
+
+On the first mention, refer to the y-axis as the *value (y) axis*. On subsequent mentions, use *y-axis*. It's OK to use *vertical (y) axis* in content for a general audience.
+
+Don't use italic formatting for the *y* in *y-axis* unless the entire word is italic.
+
+**See also** category axis, value axis
+
+### y-coordinate
+
+Lowercase. Hyphenate.
+
+Don't use italic formatting for the *y* in *y-coordinate* unless the entire word is italic.
+
+## Z
+
+### z-axis
+
+Lowercase. Hyphenate.
+
+In 3D charts, the z-axis shows depth and generally represents values. On the first mention, refer to the z-axis as the *value (z) axis,* where both the x-axis and y-axis are category axes. On subsequent mentions, use *z-axis*.
+
+Don't use italic formatting for the *z* in *z-axis* unless the entire word is italic.
+
+**See also** value axis
+
+### z-
+
+Hyphenate all words referring to entities that begin with *z* used as a separate letter, such as *z-axis, z-coordinate, z-order,* and *z-test.*
+
+Don't use italic formatting for the *z* in these words unless the entire word is italic.
+
+### zero, zeros
+
+Use *zeros,* not *zeroes,* as the plural of *zero*.
+
+When a measurement includes 0, use the plural form of the spelled-out unit of measure.
+
+**Examples** 0 MB 0 megabytes
+
+**See also** Units of measure term collection
+
+### ZIP Code
+
+It’s OK to use *ZIP Code* in content that's intended for a US audience only. Otherwise, use *postal code.*
+
+Capitalize as shown.
+
+### zoom in, zoom out
+
+Use *zoom in* and *zoom out* as generic verbs in instructions for all input methods.
+
+Don't use *dezoom* or *unzoom.*
+
+**See also** Touch and pen interaction term collection
diff --git a/.claude/skills/microsoft-writing-style-guide/references/accessibility-and-bias-free-communication.md b/.claude/skills/microsoft-writing-style-guide/references/accessibility-and-bias-free-communication.md
new file mode 100755
index 000000000..bae2d8532
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/accessibility-and-bias-free-communication.md
@@ -0,0 +1,318 @@
+# Accessibility and bias-free communication
+
+## Accessibility Guidelines and Requirements
+
+Microsoft devices and services empower people of all abilities, around the globe—at home, at work,
+and on the go—to do the activities they value most. 
+
+This section provides an overview of accessibility guidelines:
+
+  - [Writing for all abilities](/style-guide/accessibility/writing-all-abilities)
+  - [Colors and patterns in text, graphics, and design](/style-guide/accessibility/colors-patterns-text-graphics-design) 
+  - [Graphics, design, and media](/style-guide/accessibility/graphics-design-media)
+
+**See also** [Accessibility term collection](/style-guide/a-z-word-list-term-collections/term-collections/accessibility-terms)
+
+**Learn more**  
+[Microsoft Accessibility site](https://www.microsoft.com/accessibility/)
+## Writing for all abilities
+
+Microsoft style—clean, simple design and crisp, clear content—is easier for all readers to use, so nearly every writing recommendation in this guide will improve accessibility. Pay special attention to the following guidelines.
+
+## Put the person first
+
+In general, use people-first language (refer first to the person, followed by the disability). To ensure clarity and consistency, this should be the default unless you know a specific audience prefers identity-first language. When you must describe specific disabilities or people with specific disabilities, consult approved Accessibility terminology.
+
+## Write brief, meaningful, and focused text
+
+**Be especially clear and concise** in instructions for product setup, basic features, input methods, and accessibility features.
+
+**Lead with what matters most,** so readers know immediately where to focus their attention.
+
+**Keep paragraphs short and sentence structure simple.** Aim for one verb per sentence. Read text aloud and imagine it spoken by a screen reader.
+
+**Use parallel writing structures for similar things.** For example, use singular nouns for each top-level heading. Or, use a verb to start each item in a list.
+
+**Spell out words like** ***and, plus,*** **and** ***about.*** Screen readers can misread or skip text that uses special characters like the plus sign (+) and tilde (~).  See special characters for more detailed information.
+
+**Write brief but meaningful link text.** Be descriptive—links should make sense without the surrounding text.
+
+**Distinguish link text visually.** Use redundant visual cues, such as both color and underline.
+
+**Don’t force line breaks** (also known as hard returns) within sentences and paragraphs. They may not work well in resized windows or with enlarged text.
+
+## Use content structure and location to communicate
+
+**Emphasize important points visually and stylistically.** Lists, headings, and tables reinforce relationships between concepts. Provide a brief description of what a table contains immediately preceding it in the text, and use concise and specific column headings.
+
+**Use heading levels** instead of text formatting to communicate the hierarchy of content.
+
+**Don’t use directional terms as the only clue to location.** *Left, right, up, down, above,* and *below* aren’t very useful for people who use screen-reading software. Instead, use specific language that conveys context, such as “the first item in the following list” or “on the toolbar.”
+
+## Document alternate input methods
+
+**In product documentation, document all supported modes of interaction, input commands, and keyboard shortcuts.** Include mice, keyboards, voice recognition devices, game controllers, gestures, and other interaction modes.
+
+In procedures and instructions, use generic verbs that apply to all input methods and devices. Avoid verbs like *click* (mouse) and *swipe* (touch) that don't make sense with some alternative input methods used for accessibility.
+
+**Learn more** Describing alternative input methods
+
+Describing interactions with UI
+
+## Colors and patterns in text, graphics, and design
+
+Choose colors and patterns carefully. High contrast may improve readability for people who have low vision. For people with some types of color blindness, certain color combinations are difficult to distinguish.
+
+**Don’t convey information with color alone.** For example, use both color and underlined text for links, and use pattern and color to differentiate information in charts and graphs. Remember that high-contrast personalization themes in Windows alter text color.
+
+**Don’t hard-code colors.** They can become illegible in high-contrast themes.
+
+**Choose color combinations with a minimum contrast ratio of 4.5:1.** Don’t use low-contrast or hard-to-read color combinations, such as light green and white or red and green.
+
+**Don’t use screens or tints in art.**
+
+**Don’t use screened or shaded backgrounds, watermarks, or other images behind text.** Reduced contrast makes text harder to read and hinders screen readers.
+
+## Alternative text (alt text)
+
+Alternative text (abbreviated as *alt text*) is a textual replacement for images, including graphics, photographs, charts, and screenshots. Alt text is an essential part of accessibility because it benefits users who can't view or process images. The purpose is to provide an equivalent user experience by communicating the same basic information that other users gain from looking at the image.
+
+In your alt text, accurately but concisely convey the image's purpose. Writing good alt text isn't about describing every detail. It requires interpretation and judgment.
+
+## General guidelines
+
+- Add alt text to all images that convey important meaning.
+
+- Images that are purely decorative don't need alt text. An example is the image of an icon that immediately follows the icon name in text.
+
+For decorative images in web content, use null alt text (`alt=""`) instead of omitting the `alt` attribute.
+
+- Begin alt text with a capital letter. End it with a period, even if it's just a fragment, if doing so is practical for the image type.
+
+- Don't start alt text with a general word such as "Image." Screen readers already announce images as images. Instead, start by specifying what the image is; for example, a drawing, photograph, diagram, chart, or screenshot.
+
+- Don't use the file name of an image as alt text.
+
+- If text is embedded in an image, include it in the alt text if surrounding content doesn't include that information. You might need to paraphrase if you suspect that screen readers would have difficulty reading it.
+
+- Limit the length to 150 characters. If an image is complex, consider including a detailed description in the surrounding text or in linked content.
+
+- Avoid simply repeating surrounding text in alt text.
+
+- If an image has a caption, ensure that the caption and alt text aren't redundant.
+
+## Considerations for button and link images
+
+- If a button or link has an image but no text, the image must have alt text.
+
+- Alt text should focus on what the button or link does, not what the image shows.
+
+- Don't start the alt text with "Button" or "Link." Screen readers already announce buttons as buttons and links as links.
+
+- If a button or link has both an image and text, it typically doesn't need alt text because it's just decorative.
+
+## Examples
+
+| Scenario | Appropriate alt text | Inappropriate alt text | Notes |
+| -------- | -------------------- | ---------------------- | ----- |
+| A procedure in technical content includes a screenshot that illustrates preceding steps by showing a tab where users enter information for creating an account. | Screenshot of the tab for creating an account. | Screenshot of the 'Create an account' tab with boxes for username, organization, and product tier and a Create button highlighted. | There's no reason to describe every detail in the interface because the procedural steps provide that information. |
+| The button that opens an app's user settings has no text label and is identified only by a graphic of two gearwheels. | Open user settings. | Image of two interlocking gears, one larger than the other. | If you simply describe what the image looks like, users won't know the purpose of the button. |
+| A social media post has, as its main content, a photo that shows reactions to an announcement at a product launch event. | A group of people smiling, cheering, and taking photos of a speaker. | Photograph from the launch event. | In this case, the image's meaning lies in the details of the photo and what the people are doing. The alt text needs to be descriptive to provide an equivalent user experience. |
+| A search button for a website consists of a graphic of a magnifying glass but no label text. | Search this site. | Magnifying glass button for searching. | What the button does is more important than what the button image shows. |
+| A link for chatting with a support agent consists of a photo of woman wearing a headset but doesn't provide link text. | Open an online chat session with customer support. | Photo of a smiling woman wearing a headset. | The alt text acts as link text, so what the link does is more important than what it looks like. |
+| A link to a product upgrade page consists of the link text **Upgrade now**, followed by a graphic of the product logo. | (Not applicable.) | Graphic of the product logo. | The graphic is decorative, so it doesn't need alt text. Instead, provide a null value (`alt=""`). |
+
+## See also
+
+Graphics, design, and media Everything you need to know to write effective alt text
+
+## Graphics, design, and media
+
+Websites need to be accessible to everyone. Websites that are accessible to people with disabilities also support customers with various browsers, settings, and devices or who use older technologies.
+
+In general, use clean and simple graphic design. Provide alternate ways to get the information that's conveyed by pictures, multimedia, and image maps.
+
+## Design
+
+**Keep text within a rectangular grid** for visibility and ease of scanning.
+
+**Format tables** according to the Web Content Accessibility Guidelines (WCAG) 2.0.
+
+**If you use frames,** provide alternative pages without them.
+
+**Don't use scrolling marquees** unless the customer has control over them.
+
+## Images, image maps, and multimedia
+
+**Provide clear descriptions that don't require pictures,** or provide both. Make sure the reader can get the whole story from either the picture or the written description.
+
+**Provide text alternatives for all elements that aren't text but convey important meaning.** These elements might include images (such as graphics, photographs, charts, or screenshots), audio, video, or animations (including animated GIFs). Here are some examples of text alternatives:
+
+- Alt text for images, unless they're purely decorative. Learn more in Alternative text (alt text).
+- Closed captions, transcripts, or descriptions for audio and video content. Video content requires both closed captions and audio descriptions. If a video has a thumbnail image, add alt text to the thumbnail.
+- Detailed descriptions in the surrounding text, or in a separate document that you link to, for complex elements or images that require long alt text.
+
+**Provide text links** in addition to image maps.
+
+**Plan links and image-map links to support Tab key navigation** with bidirectional text.
+
+## Bias-free communication
+
+Microsoft technology reaches every part of the globe, so it's critical that all our communications are inclusive and diverse.
+
+**Use gender-neutral alternatives for common terms.**
+
+
+|         **Use this**         | **Not this** |
+|------------------------------|--------------|
+|       chair, moderator       |   chairman   |
+| humanity, people, humankind  | man, mankind |
+|       operates, staffs       |     mans     |
+|     sales representative     |   salesman   |
+|   synthetic, manufactured    |   manmade    |
+| workforce, staff, personnel |   manpower   |
+
+**Don't use *he, him, his, she, her,* or *hers* in generic references.** Instead:  
+- Rewrite to use the second person (*you*).  
+- Rewrite the sentence to have a plural noun and pronoun.
+- Use *the* or *a* instead of a pronoun (for example, "the document"). 
+- Refer to a person's role (*reader, employee, customer,* or *client,* for example).
+- Use *person* or *individual.*  
+
+If you can't write around the problem, it's OK to use a plural pronoun (*they, their,* or *them*) in generic references to a single person. Don't use constructions like *he/she* and *s/he.*
+
+
+|         **Use this**         | **Not this** |
+|------------------------------|--------------|
+|    If you have the appropriate rights, you can set other users' passwords.<br />A user with the appropriate rights can set other users' passwords.       |   If the user has the appropriate rights, he can set other users' passwords.   |
+| Developers need access to servers in their development environments, but they don't need access to the servers in Azure.                                       | A developer needs access to servers in his development environment, but he doesn't need access to the servers in Azure. |
+|       When the author opens the document ….       |     When the author opens her document ….     |
+|     To call someone, select the person's name, select **Make a phone call**, and then choose the number you'd like to dial.                                   |   To call someone, select his name, select **Make a phone call**, and then select his number.   |
+|   If you want to call someone who isn't in your Contacts list, you can dial their phone number using the dial pad.                                             |   If you want to call someone who isn't in your Contacts list, you can dial his or her phone number using the dial pad.    |
+
+**When you're writing about a real person, use the pronouns that person prefers,** whether it's *he, she, they,* 
+or another pronoun. It's OK to use gendered pronouns (like *he, she, his,* and *hers*) when you're 
+writing about real people who use those pronouns themselves.
+
+It's also OK to use gendered pronouns in content such as direct quotations and the titles of works and when gender 
+is relevant, such as discussions about the challenges that women face in the workplace.  
+**Examples**  
+The skills that Claire developed in the Marines helped her move into a thriving technology career.  
+Anthony Lambert is executive vice president of gaming. With his team and game development partners, 
+Lambert continues to push the boundaries of creativity and technical innovation.  
+The chief operating officer of Munson's Pickles and Preserves Farm says, "My great uncle Isaac, who employed  
+his brothers, sisters, mom, and dad, knew that they—and his customers—were depending on him."  
+Do you have a daughter? Here are a few things you can do to inspire and support her interest in STEM subjects.  
+
+**In fictitious scenarios, strive for diversity and avoid stereotypes in job roles.** Choose names that reflect 
+a variety of gender identities and cultural backgrounds. 
+
+**In text and images, represent diverse perspectives and circumstances.** Depict a variety of people from all 
+walks of life participating fully in activities. Be inclusive of gender identity, race, culture, ability, age,
+sexual orientation, and socioeconomic class. Show people in a wide variety of professions, educational settings, 
+locales, and economic settings. Avoid using examples that reflect primarily a Western or affluent lifestyle. 
+In drawings or blueprints of buildings, show ramps for wheelchair accessibility. 
+
+**Be inclusive of job roles, family structure, and leisure activities.** If you show various family groupings, 
+consider showing nontraditional and extended families. 
+
+**Be mindful when you refer to various parts of the world.** If
+you name cities, countries, or regions in examples, make sure
+they're not politically disputed. In examples that refer to several
+regions, use equivalent references—for example, don't mix
+countries with states or continents.
+
+**Don't make generalizations about people, countries, regions, and cultures,** not even positive or neutral generalizations. 
+
+**Don't use slang,** especially if it could be considered cultural appropriation, such as *spirit animal.*  
+
+**Don't use profane or derogatory terms,** such as *pimp* or *bitch.*    
+
+**Don't use terms that may carry unconscious racial bias or terms associated with military actions, politics, or historical events and eras.** See [Militaristic language](/style-guide/militaristic-language) for more information.
+
+
+|    **Use this**    |       **Not this**       |
+|--------------------|--------------------------|
+| primary/subordinate |       master/slave       |
+| perimeter network  | demilitarized zone (DMZ) |
+|  stop responding   |           hang           |
+
+**Focus on people, not disabilities.** For example, talk about readers who are blind or have low vision and customers with limited dexterity. Don't use words that imply pity, such as *stricken with* or *suffering from.* Don't mention a disability unless it's relevant. For more information, see the [Accessibility term collection](/style-guide/a-z-word-list-term-collections/term-collections/accessibility-terms). 
+
+**Inclusive language** Use title-style capitalization for Asian, Black and African American, Hispanic and Latinx, Native American, Alaska Native, Native Hawaiian, Pacific Islander, and Indigenous Peoples. Microsoft style is to lowercase multiracial and white. 
+
+**Learn more** For more information about writing that conveys respect to all people and promotes equal opportunities, see the [Guidelines for Inclusive Language](https://www.linguisticsociety.org/content/guidelines-inclusive-language "Linguistic Society of America's guidelines for inclusive language") from the Linguistic Society of America. 
+
+**See also** [Militaristic language](/style-guide/militaristic-language), [Accessibility guidelines and requirements](/style-guide/accessibility/accessibility-guidelines-requirements), [Global communications](/style-guide/global-communications/)
+## Militaristic language
+
+Avoid using terms associated with violence and military actions unless you are referring to physical combat operations.  
+
+In the context of cybersecurity at Microsoft, use the following recommendations in the table of militaristic terms. 
+
+
+|         **Use this**                       |                   **Not this**              |
+|----------------------------------------------|-------------------------------------------|
+|       address; protect against; respond to       |   combat; fight; eliminate               |
+| cyberattack chain   | (cyber) kill chain  |
+|      cyberattacker; bad actor; threat actor        |     attacker; adversary     |
+|     impact    |   blast radius   |
+|   multilayered approach; defense-in-depth cybersecurity    |   defense-in-depth approach     |
+| protect; safeguard; defend  |   guard; ward    |
+| secured  |   locked down   |
+| security; protection; defense  |   fortifications; first line of defense; frontlines    |
+| security teams; security analysts; defenders  |   frontline analysts    |
+| vulnerabilities; points of access; external exposure  |   external attack surface    |
+
+
+**Attack** 
+It’s ok to use *attack* if there’s context in front of it describing what kind of attack it is. For example, say, *Early detection is critical to preventing damage from malware attacks* instead of *Get protection from sophisticated attacks*. 
+
+If there’s no context before attack that describes what kind of attack it is, add *cyber*- in front of threat so it reads *cyberattack*, all one word, no space, no hyphen.  
+
+**Example**  
+Uncover and defend against advanced cyberattacks across your entire digital estate. 
+
+**Defend, defense, and defenses**
+It’s ok to use *defend* and *defenses* if there’s context in the same sentence that makes it clear they’re referring to cybersecurity. 
+
+**Examples**  
+Learn how to defend your cloud and on-premises workloads. 
+Extend your defenses across endpoints and clouds with Microsoft Security. 
+
+**External attack surface**
+It’s ok to use this phrase when discussing external attack surface management, external attack surface management capabilities, or the product Microsoft Defender External Attack Surface Management. 
+
+Don’t use the phrase *external attack surface* when referring to a customer’s points of access that are potentially vulnerable to an attack. Use *vulnerabilities*, *points of access*, or *external exposure* instead. 
+
+**Threat**
+It’s ok to use *threat* if there’s context in front of it describing what kind of threat it is.   
+
+**Example**  
+Explore an integrated identity threat and response solution.  
+
+If there’s no context before *threat* that describes what kind of threat it is, add *cyber*- in front of threat so it reads *cyberthreat*, all one word no space no hyphen. 
+
+**Example**  
+Identify and remediate cyberthreats in the cloud and on-premises. 
+
+**Threat intelligence**
+It’s ok to use *threat intelligence* if the surrounding context makes it clear it’s related to cybersecurity. Don’t shorten to *threat intel*.  
+
+**Example**  
+Get actionable insights into new and emerging cyberthreats with dynamic threat intelligence. 
+
+**Never use**
+These terms are overtly militaristic and should never be used in the context of cybersecurity at Microsoft (though they may be used to refer to physical combat operations): 
+
+air cover  
+bomb, email bomb, mail bomb, time bomb  
+enemy, enemies, enemy lines  
+go on the offensive  
+invade, invasion  
+missile, torpedo  
+nuke, go nuclear  
+strike  
+troops  
+
+See also [Bias-free communication](/style-guide/bias-free-communication)
\ No newline at end of file
diff --git a/.claude/skills/microsoft-writing-style-guide/references/checklists.md b/.claude/skills/microsoft-writing-style-guide/references/checklists.md
new file mode 100755
index 000000000..de056106a
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/checklists.md
@@ -0,0 +1,315 @@
+# Checklists
+
+## Acronyms checklist
+
+Although some acronyms are widely understood and preferred to the spelled-out term, others aren’t well known or are familiar only to a specific group of customers. These tips will help you use acronyms and abbreviations in a way that’s clear and meaningful.
+
+- Always spell out Microsoft product and feature names.
+- Only use acronyms that your audience is familiar with.  
+- For most acronyms, spell out the term first and include the acronym in parentheses. On subsequent mentions, you can use the acronym without spelling it out.  
+- Lowercase all words in the spelled-out form of an acronym except for proper nouns.
+- Don’t spell out the acronym if it’s listed in *Merriam-Webster Dictionary* or if the **A–Z word list** says to use the acronym without spelling it out. If you’re sure your audience is familiar with an acronym, it’s OK to use it without spelling it out.  
+- Don’t introduce an acronym that’s used just once unless it’s needed for SEO.  
+- Avoid using an acronym for the first time in a title or heading, unless it’s a keyword that you need to place in the title or heading for SEO.  
+- Use *a* or *an,* depending on how you pronounce the acronym (for example, *an ISP, a SQL database*).  
+- Form the plural of an acronym like you would any other noun (for example, *three APIs*).  
+- Unless an acronym refers to a person or an organization, avoid using the possessive form.  
+- In content that will be machine translated, be careful with acronyms that form common English words, like *RAM.* They can be translated incorrectly.  
+
+**Learn more** about acronyms. **Learn more** about abbreviations of units of measure.
+
+## Capitalization checklist
+
+In general, Microsoft style is sentence-style capitalization.
+
+- Always capitalize proper nouns.
+- Lowercase everything except the first word in a sentence, UI label, phrase, heading, or title (including the titles of blogs, articles, and press releases).
+- Don’t capitalize the spelled-out form of an acronym unless it's a proper noun.
+- Use title-style capitalization for product and service names, book and song titles, article titles in citations, names of blogs, and titles of people (_Vice President_, for example).
+- It's OK to use title-style capitalization in tweets to set off a quoted article.
+- In programming languages, follow the traditional capitalization of keywords and other special terms.
+- Don't use all uppercase for emphasis.
+- Don't use all lowercase as a design choice.
+
+**Learn more** about capitalization. **Learn more** about proper nouns.
+
+## Grammar and parts of speech checklist
+
+As creative as it is, the art of writing is governed by a set of rules with a lot of built-in flexibility. This checklist covers rules of grammar that are important in Microsoft content and how to apply them. You'll notice a preference for style and word choices that are simple, straightforward, and human. That's what makes us sound like Microsoft—and helps you connect with customers.
+
+These basic guidelines will get you started creating clear and useful content.
+
+- Use present-tense verbs—verbs that indicate the action is happening now, like *is* and *open.* Avoid *will, was,* and verbs ending in *–ed,* which indicate that text isn't in the present tense. Learn more.
+
+- For most content, write simple statements of fact (called the *indicative mood*). Use direct commands (*imperative mood*) for procedures and instructions. Use wishes, hypotheses, and suggestions (*subjunctive mood*) sparingly. Learn more.
+
+- Use active voice (where the subject performs the action) whenever you can. In passive voice, the receiver of the action is the subject. Learn more.
+
+- Match a verb with its subject in person and number. Learn more.
+
+**Examples** The document is in the folder. The documents are in the folder.
+
+- Use second person most of the time. Second person often uses the pronoun *you,* as though you're speaking to the customer. Learn more.
+
+- Don't use gender-specific singular pronouns (*he* or *she*) in generic references. Instead, use *you* or refer to someone's role. Learn more.
+
+- Capitalize proper nouns—things like names of unique people, places, and things (products, books, organizations, and companies, for example). Check Merriam-Webster Dictionary or the **A–Z word list** to find out whether a term is a proper noun. Learn more.
+
+- Be careful with words ending in –*ing*, which can play different roles in a phrase. For example, in the phrase *meeting requirements,* make sure it's clear whether this is a discussion about requirements for a meeting or how to meet requirements. Learn more.
+
+- Prepositional phrases modify something else in a sentence. For example, in *The reading pane displays the content of the selected message,* the phrase *of the selected message* modifies *the content.* Avoid using consecutive prepositional phrases. Long chains of prepositional phrases are hard to read and interpret. Learn more.
+
+- Modifiers are words or phrases that modify other words or phrases. Make sure it's clear what they modify. For example, in the phrase *the selected text only is modified,* the word *only* could modify *text* or *is modified.* Rewrite as *only the selected text is modified* to clarify. Learn more.
+
+## Numbers checklist
+
+When you write about numbers used in examples or UI, duplicate them exactly as they appear in the UI. In all other content, follow these guidelines. For detailed guidelines, see Numbers.
+
+## Spelled out numbers
+
+Use for:
+
+- Zero through nine, unless space is limited.
+- One of the numbers, when two numbers that refer to separate categories must appear together. For example, *two 3-page articles*.
+- At the beginning of a sentence.
+- Ordinal numbers, such as *first.* Don't add *-ly*, as in *firstly*, to ordinal numbers.
+
+## Numerals
+
+Use for:
+
+- Numbers in UI.
+- Numbers 10 or greater.
+- Numbers zero through nine when you have limited space.
+- All numbers in a category if one or more numbers requires a numeral. For example, *a 16-page article, a 7-page article, and a 3-page article.*
+- Measurements of distance, temperature, volume, size, weight, pixels, points, and so on. To learn more, see Units of measure term collection.
+- A round number of 1 million or more.
+- Numbers the customer is directed to type.
+- Dimensions. Use the multiplication sign (×), preceded and followed by a space, for tile sizes, screen resolutions, and paper sizes. For everything else, spell out *by*.
+- Time of day.
+- Percentages. Use the percent sign (“%”) with numerals, rather than spelling out “percent.” 
+- Coordinates of tables or worksheets and numbered sections of documents.
+
+## Commas
+
+- Use in numbers that have four or more digits, regardless of how they appear in the UI.
+Exception: When designating years or baud, use commas only when the number has five or more digits.
+- Don't use in page numbers, street addresses, or decimal fractions.
+
+## Dates
+
+- Don't use ordinal numbers, such as *June first* or *October twenty-eighth*, for dates. Use a numeral instead.
+- Always spell out the name of the month.
+
+Learn more about dates and time.
+
+## Negative numbers
+
+- Form a negative number with a minus sign, not an en dash. Learn more about Em dashes, en dashes, hyphens, and minus signs.
+
+## Compound numbers
+
+- Hyphenate compound numbers when they're spelled out. Learn more about Em dashes, en dashes, hyphens, and minus signs.
+
+## Fractions and decimals
+
+- Don't use numerals separated by a slash to express fractions.
+Exception: When an equation occurs in text, it's OK to use a slash between the numerator and the denominator.
+- Hyphenate spelled-out fractions. Connect the numerator and denominator with a hyphen unless either already contains a hyphen (for example, *one-third* but *three sixty-fourths*). Learn more about Em dashes, en dashes, hyphens, and minus signs.
+- In tables, align decimals on the decimal point.
+- In decimal fractions less than one, include a zero (*0.1255*, for example) unless the customer is asked to type the value.
+- When spelling out units of measure, use the singular form for quantities of one or less, except for zero, which takes the plural form. Learn more about units of measure.
+
+## Ranges of numbers
+
+- In most cases, use *from* and *through* to describe a range of numbers.
+Exception: Use an en dash in a range of pages or where space is an issue, such as in tables and UI.
+- Don't use *from* before a range indicated by an en dash, such as *10–15*.
+
+Learn more about Em dashes, en dashes, hyphens, and minus signs.
+
+## Abbreviations
+
+- In UI, avoid *K, M,* and *B* as abbreviations for *thousand, million,* and *billion* unless space is limited.
+- In other content, spell out *thousand, million,* and *billion,* or use the entire number.
+- Contact your localization team before using these abbreviations in content that will be localized.
+- If you must use the abbreviations, follow these guidelines:
+  - Capitalize *K, M,* and *B.*
+  - Don't put a space between the number and the abbreviation.
+  - Use the decimal form of a number (such as *8.25M*) only if it really will save space.
+
+See also Numbers Date and time term collection Units of measure term collection Em dashes, en dashes, hyphens, and minus signs
+
+## Procedures and instructions checklist
+
+In the best-case scenario, the UI is so clear and task driven that you don't need additional instructions. When the task is more complex or involves more than one UI, look for the simplest way to present it. That might be:
+
+- A picture, an illustration, a poster, or an infographic.
+- A video.
+- A single sentence.
+- A numbered procedure, supplemented if necessary with pictures, videos, and links or buttons that take customers where they need to go.
+
+Follow this checklist when procedures are the best way to help your customers complete a task. Use consistent text formatting—see Formatting text in instructions. And always think accessibility—see Accessibility guidelines and requirements.
+
+Learn more about procedures and instructions.
+
+## Step-by-step instructions
+
+- Use numbered steps.
+- Write a complete sentence for each step. Capitalize the first word and end the sentence with a period.
+- Use imperative verb forms.
+- Consider using a heading that tells customers what the procedure will help them do.
+- Keep it short—ideally, fit the whole procedure on one screen. Omit unnecessary details. Combine simple actions that occur in the same place in the UI into a single step.
+- Include actions that complete a procedure, such as selecting the **OK** or **Apply** button.
+- Make sure customers know where the action in the step takes place. Provide a brief phrase if you need to, such as "on the **Design** tab, …." Or provide an introductory step to avoid any confusion: "On the ribbon, go to the **Design** tab."
+- If there's only one step, use the format that you use for procedures with multiple steps, but replace the number with a bullet. Or use regular paragraph text.
+- If your editorial style guide allows it, abbreviate simple sequences of menu interactions by using greater-than symbols. Don't use bold formatting for the symbols. Include a space before and after each one.  
+**Example** Select **Accounts** > **Other accounts** > **Add an account**.
+
+Learn more about step-by-step instructions.
+
+## Interactions with the UI
+
+Use the following verbs, which describe any input method—touch, mouse, keyboard, voice, and so on.
+
+- *Open* for apps, shortcut menus, files, and folders.
+- *Close* for apps, panes, dialogs, windows, files, and folders.
+- *Leave* for websites and webpages.
+- *Go to* for a menu or a particular place in the UI, like search, a ribbon, or a tab.
+- *Select* for UI options, values, links, and menu items.
+- *Select and hold* for pressing and holding an element in the UI for about a second.
+- *Clear* for removing the selection from a checkbox.
+- *Choose* for a general choice rather than selecting something specific.
+- *Enter* for instructing the reader to type or otherwise enter a value.
+- *Specify* for instructing a reader to type or select a value, such as in a combo box (in content for technical audiences only).
+- *Move* for moving something from one place to another by dragging, pasting, or another method.
+- *Zoom*, *zoom in*, and *zoom out* for changing the magnification of a screen or window.
+
+Avoid *press*, *press and hold*, and *right-click* if you can. Try to use an input-neutral verb instead.
+
+Learn more about describing interactions with the UI.
+
+## Alternative input methods
+
+- Most of the time, use input-neutral verbs to describe interactions with the UI. See Describing interactions with the UI to learn how.
+- For accessibility, always document keyboard procedures, even if they're indicated in the UI by underlined letters.
+- If you need to document mouse procedures, be consistent. For example, list the mouse method before the keyboard method consistently if you document both. Don't combine keyboard and mouse actions by using a plus sign. For example, use *hold down Shift while clicking* instead of *Shift+click*.
+- If you describe joystick interactions, assume that a mouse is a primary input device. Include joystick information in a table along with other alternative input methods.
+- Use these verbs for pen and touch input:  
+  
+  - Use *tap* to describe selecting something on the screen by tapping it once with a finger or pen. Don't use *tap on*. Don't use *click*.  
+  - Use *double-tap* to describe selecting something on the screen by tapping twice in quick succession. Don't use *double-tap on*. Don't use *double-click*.  
+  - Use *tap and hold* only if a program or app requires it. Don't use *touch and hold*.  
+  - Use *pan* to describe moving the screen in multiple directions, as you would pan a camera to see different views of the environment. For contact gestures, use *pan* to refer to moving a finger, hand, or pen on the device surface to move through screens or menus. Don't use *drag* or *scroll* for these actions.  
+  - Use *flick* to describe moving one or more fingers to scroll through items on the screen. Don't use *scroll*.
+  - Use *swipe* to describe a short, quick movement in the direction opposite to how the page scrolls.
+
+Learn more about alternative input methods.
+
+## Multiple input methods
+
+If you need to document multiple ways to perform a task, use one of these methods:
+
+- List the steps in a table. Put the step numbers in the left column, and provide a separate column for each input method.
+- Document the primary input method, and provide alternative instructions in parentheses or separate sentences.
+- If there are alternative ways to perform an entire procedure, such as saving a file and continuing to work or saving a file and closing a program, use a table. List each alternative in the left column and instructions on the right.
+- If a step has more than one option, list the options as bullets under the numbered step.
+
+Learn more about multiple input methods.
+
+## Punctuation checklist
+
+Keep it simple.
+
+- Stick to short, simple sentences. Sentences that contain lots of punctuation tend to be complex and hard to read.  
+
+- End all sentences with a period, even if they're only two words.  
+
+- Use only one space after periods, question marks, exclamation marks, and colons.  
+
+- Include a colon at the end of a phrase that directly introduces a list.
+  - If one or more list elements complete the introductory phrase preceding the colon, use a period after every list element. 
+  - If all list elements are short phrases (three words or fewer), don’t end them with periods, even if they form a complete sentence together with the list introduction.  
+  - If one or more list elements are complete sentences, use a period after every element, even if a list element contains three or fewer words.
+
+- Include commas after every item in a series, including the last one.  
+Example networks, storage, and virtual machines
+
+You might know that extra comma as the Oxford comma. Learn more.
+
+- Use a comma following an introductory phrase, to join independent clauses with a conjunction, and to surround the year when you use a complete date within a sentence. Learn more.
+
+- Use an apostrophe to indicate a missing letter in a contraction (such as _don’t_) and to form the possessive case of a noun (as in _Insider’s Guide_). Don’t use an apostrophe for the possessive of _it_ (its) to avoid confusion with the contraction _it’s_. Learn more.
+
+- When you use a colon in a sentence, lowercase the word that follows it unless it's a proper noun or the first word of a quotation. Learn more.
+
+- A sentence that contains a semicolon might be complex. Try to rewrite the sentence as multiple sentences or break it into a list. Learn more.
+
+- Use exclamation points sparingly. Save them for when they count.  
+
+- Use question marks sparingly. Customers expect _us_ to give _them_ answers. Learn more.
+
+- Place closing quotation marks:
+  - Outside commas and periods.
+  - Inside other punctuation.
+
+Exception If punctuation is part of the quoted material, place it inside the quotation marks.
+
+- In general, don’t use hyphens unless leaving them out could result in confusion. Learn more.
+
+- Don’t use spaces around em dashes (—). Learn more.
+
+- Don’t use a slash (/) to indicate a choice or as a substitute for _or_. Learn more.
+
+- In general, format punctuation in the same font style as the main content of a sentence or phrase unless it's part of an element such as a command, option, keyword, placeholder, link, pop-up text, or user input.
+
+Learn more about punctuation.
+
+## Responsive content checklist
+
+Assume that most content will be viewed on tablets or mobile devices by some customers. Plan for it.
+
+- Consider the order in which columns will display on a small screen.
+- Write short sections and short paragraphs—ideally, the reader should be able to see a full paragraph on the screen.
+- Limit headings to one short line.
+- Organize infographics in compact sections for mobile viewing, and provide a way for readers to open the infographic so they can enlarge areas.
+- Simplify charts and graphs, and write short chart titles and axis labels.
+- Limit the number of columns in a table.
+
+**Learn more** about responsive content.
+
+## Text-formatting checklist
+
+- Use the Segoe font family.
+- Use sentence-style capitalization for everything except proper nouns.
+- Use left alignment. Never center text or align both right and left margins.
+- Avoid widows, orphans, and lines that end with hyphens.
+- Don’t compress line spacing.<br/>
+Learn more about using type.
+- Format text elements consistently.
+
+Learn about Formatting common text elements Formatting titles Formatting developer text elements
+
+## Word choice checklist
+
+Choose simple, precise words that you use in conversations.
+
+- Use common contractions, such as _that's_ and _don’t_. They’re friendly and conversational. Learn more.
+
+- Avoid words with more than one meaning. Learn more.
+
+- Use as few words as possible. Omit unnecessary adverbs (words that describe how, when, or where) and use precise, one-word verbs (such as _try_ instead of _attempt to_) whenever you can. Learn more.
+
+- If you mean the same thing, use the same word. Use the **A–Z word list** and your group's editorial style guide to find preferred terms for Microsoft content.
+
+- Don’t give technical meanings to common words (like using _bucket_ to mean _group_) or use nouns as verbs or verbs as nouns. Learn more.
+
+- Don’t create a new word if one already exists. If you’re working on emerging technology, research terminology already in use before you create a new term. Learn more.
+
+- Use technical terms carefully and define them in context if there’s a chance your audience won’t understand them. Use plain language whenever you can. Learn more.
+
+- Use the words your audience uses. If you're writing for a particular industry, such as healthcare or construction, refer to reputable language sources (industry glossaries or associations, for example) to make sure you’re using industry terms correctly. Learn more.
+
+- Avoid jargon when there’s a familiar word that will do. Learn more.
+
+- Don't use words that attribute human characteristics to devices and products. Devices don't think, feel, or otherwise exhibit human characteristics.
diff --git a/.claude/skills/microsoft-writing-style-guide/references/content-planning-and-process.md b/.claude/skills/microsoft-writing-style-guide/references/content-planning-and-process.md
new file mode 100755
index 000000000..71d3c1d1a
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/content-planning-and-process.md
@@ -0,0 +1,264 @@
+# Content planning and publishing process
+
+## Content planning
+
+Great content starts with a plan that begins with these questions.
+
+**Who is your audience?** This could be broad—developers, for example—but defining your audience more specifically will help you refine your plan. Is your audience writing software? Apps? IT tools? Games? Are they hobbyists, full-time developers, or IT pros who write code? What development software do they use?
+
+**What do they want to accomplish?** Are they deciding whether to buy your product? Setting up a new computer? Learning new software? Preparing for a migration? Struggling with a PivotTable? Planning for network security? Is their need urgent? Few customers come to us to see what’s new. Understanding why they come will help you satisfy their needs.
+
+**What is your business goal for providing the content?** Are you building enthusiasm for an upcoming product launch? Establishing a competitive position in the marketplace? Documenting an out-of-band release? Providing support content to accelerate migration? Although the customer’s goals are paramount, every communication has a business reason, too.
+
+**Do you have time or budget constraints?** If time is of the essence, content you can create quickly might be best. The budget and the availability of an agency or specialized resources, like illustrators, designers, and video producers, will help you determine what content options are realistic.
+
+**What kind of content best meets the customer's needs and business goals?** If the concepts are hard to explain, video or infographics could be just the thing. If the customer is preparing for a major project, maybe they need checklists and sample project plans, or a pricing calculator. For breaking news, tweets or a strategic blog post might be the best approach.
+
+**How will the customer find the content?** What search terms will the customer use? Plan for search keyword optimization; links back to your content; and promotion through home pages, blogs, newsletters, events, third-party sites, communities, and social media if appropriate. To learn more, see Search and writing.
+
+**Where will the customer look for information?** Part of knowing your customers is understanding where they go for information. If they have a problem, they may look to product documentation, Microsoft support, or an expert community. For training, Microsoft Virtual Academy or a video platform like YouTube might be their source. For tips and tricks, maybe it’s social media and blogs.
+
+**What devices will the customer use to experience the content?** Laptops? Tablets? Phones? Wearable devices? Entertainment consoles? All of those? Plan for a great experience across devices the customer is likely to use.
+
+**Will the content be translated or localized?** If so, plan your content to streamline those processes and contain costs. To learn more about developing content for translation and localization, see Global communications.
+
+**How will you measure success?** Do you have numeric targets for views, clicks, or downloads? Goals for mentions or backlinks? Targets for lead generation? Planning for specific objectives up front will help you create content that meets them.
+
+With these questions answered, you can narrow your approach. For example:
+
+  - If the customer need is immediate, maybe you blog today and create a more polished article later. 
+  - If budget and timeline are tight, you might choose a simple text format. 
+  - If the audience is large and the topic complex, a short, professionally produced video might make sense.
+  - If
+content will be localized in multiple languages, graphics supported by text might meet the customer and business need at a lower cost.
+
+## Content ideas for specific user needs
+
+| **Need** | **Content types** | **Examples** |
+|---|---|---|
+| **Complete a simple task or use a simple feature in an app** | UI text<br /> Documentation<br /> Short video<br /> Blog, if it's a common issue or cool, little-known feature | Setting up email<br /> Recall and replace sent messages<br /> 5 easy and powerful Excel features you may not know about |
+| **Complete a complex task or use a complex feature in an app** | UI text  <br /> Video <br /> Webcast <br /> Documentation <br /> Tutorial <br /> End-to-end scenarios or conceptual articles <br /> Technical papers or articles <br /> Wizard | Try the latest touchpad gestures <br /> OneNote for (holiday) planning <br /> Set up Office 365 for business <br /> Getting started with Microsoft Intune <br />  |
+| **Get timely communications, including news, announcements, event updates, tips, and stories** | Blog <br /> Newsletter | OneNote, The Microsoft Office Blog <br /> Virtual PC Guy’s blog <br />  |
+| **Get answers and expertise from a community** | Wiki <br /> Forum | TechNet wiki <br /> Exchange Server Forum <br /> Microsoft Answers |
+| **Learn a complex or comprehensive concept or skill** | Online training <br /> Tutorial <br /> Technical white paper <br /> Interactive graphics <br /> System architecture | Make and receive calls using Skype for Business <br /> SharePoint Automation with DSC <br /> Azure Network Security (PDF) <br /> Technical diagrams for SharePoint 2013 |
+| **Learn or increase knowledge and skills related to a product, service, technology, or business concept** | Concept papers <br /> E-books <br /> Infographics | Azure Security, Privacy, and Compliance (PDF) <br /> SharePoint with SQL Server AlwaysOn <br /> Microsoft Dynamics NAV: Grow Your Business e-book |
+| **Learn product tips and tricks** | UI text <br /> Web documentation <br /> Apps <br /> Microblogs (such as X, formerly known as Twitter) <br /> Blogs <br /> E-books <br /> Newsletters <br /> Communities | Useful Tips and Tricks to Bring with You to the Vermintide 2 Beta on Xbox One <br /> Skype: Keeping you connected on your vacation <br /> Windows 10 Tip: Go back and forth in time with Timeline |
+| **Understand a process** | Interactive graphics <br /> Interactive flow charts <br /> Sample workflows <br /> Sample files | What is governance in SharePoint 2013? <br /> Overview of the upgrade process for SharePoint 2013 <br /> 
+| **Troubleshoot a problem** | Interactive flow chart <br /> UI troubleshooter | How to run the Audio Troubleshooter in Windows 10 |
+
+## Design planning
+
+Design is more than a pretty face. It provides a familiar environment for content. Text
+length, the use of images, headings, tables, lists, and other
+writing choices all play a role in the quality of your readers’
+content experience. Writing with design in mind builds predictability into content, helping readers to navigate it and find what they need. 
+
+The time to think about design is before you start writing.
+
+## Consult with your design partners early
+
+Collaborate with your designer and marketing manager or PM to develop the [content strategy](/style-guide/content-planning). 
+
+If
+you’re working with a designer, meet early and often. Share your
+outline, your preliminary drafts, and this style guide. Provide preliminary content early in the process so you can identify and solve issues in the design or content approach.
+
+## Make layout decisions before you begin
+
+If
+you’re writing for a platform that limits your design choices,
+such as a blog platform or website, research proven layout choices
+and find out where the design is flexible.
+
+If
+you have options for positioning content elements, place them in the
+same area on every page. Tips, procedures, blog rolls, references,
+definitions, and other distinct content types are easier to find when
+they’re located consistently. 
+
+
+## Start with a template
+
+Templates
+provide a well thought out framework for clear and simple
+communication. The brand and visual consistency templates bring to
+content provides predictability to your readers, so they can
+focus on what you have to say. Taking advantage of all your
+template has to offer will both enhance the customer experience and
+streamline modifications you need to make down the road. 
+
+  - **Use manual formatting sparingly.** Templates
+    take care of most formatting for you. You may need a bold or
+    italic phrase now and then, but always use the built-in styles for headings, subheadings, bulleted lists, tables, and whatever else your template provides.
+    
+  - **Use a limited number of styles.** Most
+    content needs just a couple of heading levels, bulleted and
+    numbered lists, tables, and of course body text. Using three or fewer
+    styles leads to more streamlined, polished-looking results.
+    
+  - **Don’t create new styles or modify existing ones.** New
+    styles complicate design. You’ll almost always find enough styles
+    in a template to meet the needs of your communication.
+    
+  - **Use styles consistently** for headings, tables, lists, notes, tips, and other text, throughout your communication.
+  
+  - **Don’t fear white space.**
+    Your template probably includes spacing for various text elements. Use
+    it. Empty space helps the reader focus on what’s important and makes
+    text seem less daunting. Wide margins, space around graphics, and space
+    between lines of text all improve readability and can draw attention to
+    particular text elements—especially if you use white space consistently.
+## Final publishing review
+
+Use these tips to help you edit like
+a pro, so your final content and design shine. 
+
+**Hit the mark.** Review the project brief and customer insights one last time. Did you nail the
+objective? Is the value proposition front and center? Are key messages
+and benefits clear? 
+
+**Get a second opinion.** Find someone completely removed from the work to offer feedback and act as
+the customer. (Or hire an editor.) No matter how well you write, a
+second set of eyes always offers a new perspective. And
+don’t take suggestions personally—keep an open mind and be flexible to
+new ways to get the results you want. If something trips up your
+reviewer, get rid of it, no matter how much you like it.
+
+**Read your work aloud.** Read it forward, and then backward—one sentence at a time. It may sound silly, but potential edits will jump out.
+
+**Read only the headings, and then only the first sentence of every paragraph.** Do they tell a story? Are there gaps? Repeated ideas?
+
+**Check for keywords in titles and headings.** Titles and headings help readers scan and help search engines find
+your content. Make sure you include relevant keywords in the first
+few words. While you’re at it, read your first sentence to see if
+it will make sense as a search engine description. To learn more, see [Search and writing](/style-guide/search-writing).
+
+**Search for and remove unnecessary and redundant elements.** Try removing words, sentences, paragraphs, headings, even entire
+sections. If you don't miss it, leave it out. It’s good for your opening
+paragraph to summarize the piece at a high level. But don’t repeat
+phrases verbatim, or include tips or notes found later in the text.
+
+**Pay attention to the spell checker.** Those squiggly lines will help you eliminate a lot of errors. But
+spell checkers can’t think. It’s up to you to check each
+suggestion. Otherwise you might end up saying *manger* where you meant *manager.* 
+
+**Take a break.** Leave the finished piece alone for a day. Read it again tomorrow—you may see things you missed. 
+
+**Evaluate the voice and personality.** Before you call it done, read it one final time. Can you hear the fresh and modern [Microsoft voice](/style-guide/brand-voice-above-all-simple-human)? Your writing should sound warm and relaxed, crisp and clear, and ready to lend a hand.
+## Search and writing
+
+Customers find content in a variety of ways. One of the most common is search. Search engine optimization (SEO) tactics change rapidly, but good writing that addresses customer needs always helps.
+
+As you write, follow these guidelines to help customers find relevant content.
+
+## Keywords
+
+Keywords are the terms customers use when they search for content. To help customers find your content in search engines, front-load keywords in headings, subheadings, and page descriptions.
+
+The search terms that customers use aren't necessarily the same terms you would use when searching. So before you write, identify the keywords that you think customers will use to find your content. These resources can help:
+
+  - Bing Keyword Research tool
+  - Google Adwords Keyword Planner
+  - Google Analytics
+
+When you’ve identified the keywords that apply to your content, use them as early and as often as possible (without being contrived or repetitious) in these places:
+
+  - Titles 
+  - Headings and subheadings 
+  - Summaries 
+  - Overviews 
+  - Introductions 
+  - Page descriptions 
+  - Paragraph text 
+  - Link text 
+  - Image and table alt text 
+
+If your content is video, audio, or images, include keywords in a nearby text description and in alt text.
+
+## Links and backlinks
+
+Linking to supporting information is a good way to stick to the point and keep content concise. In a large body of content, cross-references can improve navigation and make content easier to scan.
+
+  - Write short link text (four or fewer words) that's descriptive and includes keywords.  
+  
+  - If it works, use the title or description of the target page as link text.  
+  
+  - Link to background and related information rather than summarizing it.
+
+Backlinks are links from other online content to your page. Although search engine algorithms change frequently, backlinks are often part of the criteria that determine search ranking. As you plan, think about promotion and what other sites can appropriately link to your content. The more authoritative the site and the closer it maps to your keywords, the more weight the backlink carries.
+
+Never create backlinks just to improve your site's search ranking. Search practices that don’t make sense for your content rarely work and often backfire.
+
+## Responsive content
+
+If you're writing for the web, assume your content will be used on a variety of devices. Many websites today are *responsive*—that is, they reconfigure automatically based on the device in use. Assume your content will be viewed at small sizes.
+
+## Keep it short
+
+**Short text** is always better, but on mobile devices, it's imperative. Try to write sentences and paragraphs that are short enough to read on a mobile screen without scrolling. It's hard to read a paragraph when you need to scroll to see the second half.
+
+**Try to keep headings to one, short line.** Two-line headings take up twice as much scarce vertical space. Use short words in headings, too, if you can. If a customer uses larger fonts to improve accessibility, long words might break across lines.
+
+**Short sections**—headings and the text that follows—are easier to read on small screens. Short sections also make it easier for customers to stop reading and later pick up where they left off.
+
+## Use simple images, charts, and tables
+
+**Keep in mind that the width of your customer's screen** might be just a couple of inches. Keep content simple so it's easy to read and understand.
+
+**Choose simple images, and crop extraneous detail.**
+
+**Add alt text to all images that convey important meaning,** to make them accessible. Images that are purely decorative don't need alt text. Learn more in Alternative text (alt text).
+
+**Create infographics carefully.** Provide a way for readers to open an infographic in an application where they can enlarge specific areas. Organize infographics in compact sections that readers can magnify and view on a small screen. Or, present individual sections of the infographic within text, and provide a link to the full infographic.
+
+**Simplify charts and graphs** so that readers can easily read the whole thing on a small screen. Craft very short chart titles, metrics labels, and axis labels.
+
+**Limit the number of columns in tables** and keep the text in each cell brief—ideally one line. Tables with more than a few narrow columns might be hard to read. Too much text in a cell might cause a table to exceed the height of a mobile screen.
+
+## Consider flow
+
+As you create content, think about how it will flow on a 360-pixel screen. Typically, content on the right side of the page moves below content on the left side. Will the content still make sense?
+
+Work with the designer or developer to determine where breaks in the content will occur, how much content displays at each potential resolution, and the order in which content will appear on small devices.
+
+## URLs and web addresses
+
+Communications to customers often refer to websites and URLs. Follow these guidelines to make your URL references clear and easy for customers to understand.
+
+## URL vs. address
+
+In content for a general audience, use *address* rather than *URL*. In content for a technical audience, don't spell out *URL* on first mention. If you have a reason to spell out URL, use *uniform resource locator*.
+
+Use *a,* not *an,* as an article preceding *URL*.
+
+## References to specific sites and domains
+
+Don't include *https://* in a URL. Include the protocol only if it's something other than HTTP, such as File Transfer Protocol (FTP).
+
+**Examples** www<span></span>.microsoft.com/business ftp<span></span>://example.com/downloads/myfile.txt
+
+The trailing slash at the end of a URL is optional. In most cases, leave it off. Never use a trailing slash in a URL that ends with a file name.
+
+Most of the time, use lowercase for URLs, email addresses, and newsgroup addresses.
+
+To refer to an entire website or top-level domain, such as Microsoft.com, omit *http<span></span>://www* from the URL and capitalize only the first letter of the URL, even if the site name is capitalized differently.
+
+**Examples** www<span></span>.microsoft.com Microsoft.com Codeplex.com is home to the open-source project site hosted by Microsoft.
+
+## Grammar and formatting
+
+Use *of* (not *for*) to describe the relationship of the word *URL* to a resource. Use the preposition *at* with the location of a specific address.
+
+**Examples** Search results include the URL of the page. Learn more about Microsoft products and services at www.microsoft.com.
+
+If the reader might think the period at the end of a sentence is part of the URL, rewrite the sentence or set the URL off.
+
+**Examples** Go to windows.microsoft.com/upgrade to learn how to get your free Windows upgrade. To get your free Windows upgrade, go to our website: windows.microsoft.com/upgrade
+
+Write brief but specific and meaningful link text. Use the title or a description of a page rather than a generic phrase like *click here*.
+
+**Example** Go to the Windows upgrade page to learn how to get your free upgrade.
+
+If a link has an image but no link text, the image must have alt text. The alt text should focus on what the link does, not what the image shows. (If a link has both an image and link text, the image can typically be treated as decorative.) Learn more in Alternative text (alt text).
+
+**Examples** Alt text for a link that consists only of a photo of a woman talking on a phone: "Open an online chat session with Microsoft Support." Alt text for a link that consists only of a graphic of the Windows logo: "Go to the Windows upgrade page."
diff --git a/.claude/skills/microsoft-writing-style-guide/references/developer-and-bot-content.md b/.claude/skills/microsoft-writing-style-guide/references/developer-and-bot-content.md
new file mode 100755
index 000000000..9eee864db
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/developer-and-bot-content.md
@@ -0,0 +1,311 @@
+# Developer content, and chatbots and virtual agents
+
+## Developer content
+
+Though the content for developers and IT professionals tends to be more technical than that for a general audience, the fundamentals of the Microsoft brand voice still apply. Be warm and relaxed, crisp and clear, and ready to lend a hand as appropriate for the context. After all, when they're not coding or managing solutions, developers and IT pros are some of the very same people who play Xbox and use Office.
+
+Of course, it's OK to assume IT pros and developers bring a fundamental understanding of programming concepts. So skip the basic knowledge and focus on technology-specific or product-specific information that helps them achieve their goals.
+
+Two types of content form the foundation of developer documentation: reference documentation and code examples. Reference documentation provides an encyclopedia of all the programming elements, such as classes, methods, and properties, that are available for writing applications. Code examples show how to use those elements.
+
+This section provides guidelines for creating:
+
+  - Reference documentation
+  - Code examples
+
+It also has guidelines for formatting developer text elements.
+
+## Reference documentation
+
+Reference documentation provides details about the programming elements associated with technologies and languages, including class libraries, object models, and programming language constructs.
+
+Consistency is essential in reference documentation. A standard article design, predictable headings and structure, and consistent wording help developers find what they need quickly. Links to articles with related information are also a common feature.
+
+**Note** Information such as configuration schemas, compiler options, and error messages might not follow the guidelines described in this section.
+
+## Article titles
+
+Use the name of a programming element (such as Clear), followed by an element type (such as Class, Method, Property, or Event). If the name is shared by multiple elements, add a differentiator, such as the parent element name or the product or technology name. Differentiators are particularly important in search results, where they help customers find the article for the correct product or element.
+
+**Examples** Clear method Device.Clear method Clear method (ADO)
+
+## Elements of a reference article
+
+The table lists the information typically provided in reference articles. Not all sections appear in all reference articles. Sections vary depending on the language, product, or technology being documented.
+
+|        **Section**         |                                                                                                                                                                                                                                                                   **Contains**                                                                                                                                                                                                                                                                    |
+|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|      **Title and description**       |                                                                                                                            The name of the element and a concise sentence or two describing the element. If possible, explain what the element does or represents without repeating the element name.<br />**Example**<br />MoveRecord method (ADO)<br />Moves the entity represented by a **Record** to another location.                                                                                                                              |
+|   **Declaration/syntax**   |                                                                                                                                                                          The code signature that defines the element. This section might also provide usage syntax. If the technology can be used with multiple programming languages, provide syntax for each language. <br />**Example**<br />`Record.MoveRecord (Source, Destination, UserName, Password, Options, Async)`                                                                                               |
+|       **Parameters**       | If the element has parameters, provide a description of each parameter and its data type. If appropriate, indicate whether the parameter is required or optional and whether it represents input or output. Provide as much useful detail as possible. Don't just repeat the words in the parameter name or the data type.<br />**Examples**<br />*Source*<br />Optional. A **String** value that contains a URL identifying the **Record** to be moved. If *Source* is omitted or specifies an empty string, the object represented by this **Record** is moved. For example, if the **Record** represents a file, the contents of the file are moved to the location specified by *Destination.*<br /><br />*Destination*<br />Optional. A **String** value that contains a URL specifying the location where *Source* will be moved.<br /><br />*UserName*<br />Optional. A **String** value that contains the user ID that, if needed, authorizes access to *Destination.*<br /><br />*Password*<br />Optional. A **String** that contains the password that, if needed, verifies *UserName.*<br /><br />*Options*<br />Optional. A **MoveRecordOptionsEnum** value whose default value is **adMoveUnspecified**. Specifies the behavior of this method.<br /><br />*Async*<br />Optional. A **Boolean** value that, when **True**, specifies this operation should be asynchronous.                                                             |
+|      **Return value**      |                                                                                                                                                                               If the element returns a value, describe the value and information about its data type. If the value is a Boolean that indicates the presence of a condition, describe the condition. <br />**Example**<br />A **String** value. Typically, the value of *Destination* is returned. However, the exact value returned is provider-dependent.                                                                                                                                                                              |
+|        **Remarks**         |                                                                                                                               Additional information about the element and important details that may not be obvious from its syntax, parameters, or return value. For example, you might explain what the element does in more detail, compare it with similar elements, and identify potential issues in its use. <br />**Example**<br />The values of *Source* and *Destination* must not be identical; otherwise, a runtime error occurs. At least the server, path, and resource names must differ.<br /><br />For files moved using the Internet Publishing Provider, this method updates all hypertext links in files being moved unless otherwise specified by *Options.* This method fails if *Destination* identifies an existing object (for example, a file or directory), unless **adMoveOverWrite** is specified.<br /><br />**Note** Use the **adMoveOverWrite** option judiciously. For example, specifying this option when moving a file to a directory will delete the directory and replace it with the file.<br /><br />Certain attributes of the **Record** object, such as the **ParentURL** property, won't be updated after this operation completes. Refresh the **Record** object's properties by closing the **Record**, then reopening it with the URL of the location where the file or directory was moved.<br /><br />If this **Record** was obtained from a **Recordset**, the new location of the moved file or directory won't be reflected immediately in the **Recordset**. Refresh the **Recordset** by closing and reopening it.<br /><br />**Note** URLs using the http scheme will automatically invoke the Microsoft OLE DB Provider for Internet Publishing. For more information, see Absolute and Relative URLs.                                                                                                                              |
+|        **Example**         |                                                                                                                                                                                       A code example that illustrates how to use the programming element. For more information about writing useful code examples, see Code examples.                                                                                                                                                                                       |
+|      **Requirements or Applies to**      |                                                                                                                                                                                                                                             Language or platform requirements for using the element.<br />**Example**<br />Record Object (ADO)                                                                                          |
+|        **See also**        |                                                                                                                                                     References or links to more information about how to use the element. References or links to related elements.<br />**Examples**<br />Move Method (ADO)<br />MoveFirst, MoveLast, MoveNext, and MovePrevious Methods (ADO) <br />MoveFirst, MoveLast, MoveNext, and MovePrevious Methods (RDS)                                                                                                                                    |
+
+Other information can appear in reference articles as appropriate to the language, product, or technology. For example, instead of a parameter description as shown in the preceding table, there can be descriptions of members, methods, property values, and field values. The following table contains an example of a property value and examples of exceptions and permissions.
+
+|        **Section**         |                                                                                                                                                                                                                                                                   **Contains**                                                                                                                                                                                                                                                                    |
+|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|  **Property value**  |                                                                                                                                                                           A description of the value for a property or field. If the property or field has a default value, describe that, too. Include the data type of the property value if applicable.<br />**Example<br />Property Value**<br />String<br />Returns or sets a String value representing the current date according to your system.                                                                         |
+| **Exceptions/error codes** |                                                                                                                                                                                                          If the element can throw exceptions or raise errors when called, list them and describe the conditions under which they occur.<br />**Example**<br />IOException—An I/O error occurred.<br />ArgumentNullException—*format* is null.<br />FormatException—The format specification in *format* is invalid.                                                |
+|      **Permissions**       |                                                                                                                                                                                                                                           Security permissions that apply to the element, if required.<br />**Example**<br />Requires CREATE FUNCTION permission in the database and ALTER permission on the schema in which the function is being created. If the function specifies a user-defined type, requires EXECUTE permission on the type.                                                                                                                                                     |
+
+If you automatically generate reference documentation and comments from the source code, review the quality and appropriateness of the comments. Developers might leave out details that are important to customers. Remove any implementation or internal details that aren't suitable for documentation.
+
+**Learn more** For other examples of technical reference articles, see the .NET API Browser.
+
+## Code examples
+
+Code examples illustrate how to use a programming element to implement specific functionality. They might include:
+
+  - Simple, one-line examples interspersed with text.
+  - Short, self-contained examples that illustrate specific points.
+  - Long samples that illustrate multiple features, complex scenarios, or best practices. 
+
+Developers use code examples to:
+
+  - Assess a technology through its API during planning.
+  - Learn or explore a language or technology.
+  - Write and debug code.
+
+Many developers copy example code from documentation into their own code or adapt code examples to their own needs.
+
+To create useful code examples, identify tasks and scenarios that are meaningful for your audience, and then create examples that illustrate those scenarios. Code examples that demonstrate product features are useful only when they address the problems that developers are trying to solve.
+
+**Guidelines for planning code examples**
+
+- Create concise examples that exemplify key development tasks. Start with simple examples and build up complexity after you cover common scenarios. 
+
+- Prioritize frequently used elements and elements that may be difficult to understand or tricky to use. 
+
+- Don't use code examples to illustrate obvious points or contrived scenarios. 
+
+- Create code examples that are easy to scan and understand. Reserve complicated examples for tutorials and walkthroughs, where you can provide a step-by-step explanation of how the example works.
+
+- Add an introduction to describe the scenario and explain anything that might not be clear from the code. List the requirements and dependencies for using or running the example.
+
+- Provide an easy way for developers to copy and run the code. If the code example demonstrates interactive and animated features, consider providing a way for the developer to run the example directly from your content page.
+
+- Use appropriate keywords, linking strategies, and other search engine optimization (SEO) techniques to improve the visibility and usability of the code examples. For example, add links to relevant code example pages and content pages to improve SEO across your content. See Search and writing. 
+
+**Guidelines for writing code examples**
+
+- Design code for reuse. Help developers determine what to modify. Add comments to explain details, but don't overdo it. Don't state the obvious.
+
+- Show expected output, either in a separate section after the code example or by using code comments within the code example. 
+
+- Consider accessibility requirements for code that creates UI. For example, include alternate text for images. 
+
+- Write secure code. For example, always validate user input, never hard-code passwords in code, and use code-analysis tools to detect security issues. 
+
+- Show exception handling only when it's intrinsic to the example. Don't catch exceptions thrown when invalid arguments are passed to parameters. 
+
+- Always compile and test your code.
+
+## Formatting developer text elements
+
+Consistent text formatting helps readers locate and interpret information. Follow these formatting conventions for text elements that are commonly used in content for developers.
+
+In general, use code style for programmatic or code-related elements. The following table lists examples of common programming elements, and some exceptions to the code style convention. Consider localization needs for the text elements that you're formatting.
+
+The capitalization of developer text elements varies depending on the programming language or operating environment. When you're documenting code, capitalization should follow what the code uses.
+
+**See also** Capitalization Formatting common text elements Formatting text in instructions Procedures and instructions
+
+|                                                               **Element**                                                                |                                                                                                                    **Convention**                                                                                                                    |                                                                                                                          **Example**                                                                                                                           |
+|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **AI prompts** | Quotation marks, if you're referencing prompts in text. <br /><br />If prompts appear in a list and the introductory text makes clear what those items are, special formatting isn't necessary. | "List all of my subscriptions."
+|                                                              **Attributes**                                                              |                                                                                                             Code style.                                                                                                             |                                                                                                                     `IfOutputPrecision`                                                                                                                      |
+|                                                         **Classes (predefined or user-defined)**                                                         |                                                                                                             Code style.                                                                                                             |                                                                                                           `ios`<br />`filebuf`<br />`BitArray`<br /> `BlueTimerControl`                                                                                                           |
+| **Code samples, including keywords and variables within text and as separate paragraphs, and user-defined program elements within text** |                                                                                                                      Code style.                                                                                                                      |                                                                                                              `#include <iostream.h>` <br /> `void main ()`                                                                                                               |
+|                                                        **Command-line commands**                                                         |                                                                                                                 Code style.                                                                                                                |                                                                                                                            `copy`                                                                                                                            |
+|                                        **Command-line options (also known as switches or flags)**                                        |                                                                                                  Code style. Capitalize the way the option must be typed.                                                                                                  |                                                                                                                      `/a`<br />`/Aw`                                                                                                                       |
+|                                                              **Constants**                                                               |                                                                                                         Code style.                                                                                                         |                                                                                                          `INT_MAX`<br />`bDenyWrite`<br />`CS_DBLCLKS`                                                                                                           |
+|                                                           **Control classes**                                                            |                                                                                                                   Code style. All uppercase.                                                                                                                    |                                                                                                                       `EDIT` control class                                                                                                                       |
+|                                                             **Data formats**                                                             |                                                                                                                    Code style. All uppercase.                                                                                                                    |                                                                                                                             `CF_DIB` format                                                                                                                             |
+|                                            **Data structures and their members (predefined)**                                            |                                                                                                             Code style.                                                                                                             |                                                                                              `BITMAP`<br />`bmBits`<br />`CREATESTRUCT`<br />`hInstance`                                                                                               |
+|                                                              **Data types**                                                              |                                                                                                    Code style. Capitalization follows the API.                                                                                                     |                                                                                                            `DWORD`<br />`float`<br />`HANDLE`                                                                                                            |
+|                                                            **Database names**                                                            |                                                                                                  Bold. Code style if using in code syntax.                                                                                                  |                                                                                                                      **Contoso** database<br />`USE ContosoSalesDatabase;`                                                                                                                      |
+|                                                              **Directives**                                                              |                                                                                                                        Code style.                                                                                                                         |                                                                                                                `\#include`<br />`\#define`                                                                                                                 |
+|                                                        **Environment variables**                                                         |                                                                                                                    Code style.                                                                                                                    |                                                                                                                  `INCLUDE`<br />`SESSIONNAME`                                                                                                                   |
+|                                                            **Error messages**                                                            |                                                                          Sentence-style capitalization. Enclose in quotation marks when you're referencing error messages in text.  <br /><br />If error messages appear in a list and the introductory text makes clear what those items are, special formatting isn't necessary.                                                                        | An error occurred during report processing.   <br />If you see the error message "Placeholder text in a content control contains items that aren't valid," remove floating objects, revision marks, or content controls from placeholder text, and try again. |
+|                                                             **Event names**                                                              |                                                                                                        Code style.                                                                                                        |                                                                                                            In the `OnClick` event procedure ....                                                                                                             |
+|                                               **Fields (members of a class or structure)**                                               |                                                                                                        Code style.                                                                                                        |                                                                                                                 `IfHeight`<br />`biPlanes`                                                                                                                 |
+|                                                           **File attributes**                                                            |                                                                                                                    All lowercase.                                                                                                                    |                                                           The `attrib` command displays, sets, or removes the read-only, archive, system, and hidden attributes assigned to files or directories.                                                            |
+|                                                         **File name extensions**                                                         |                                                                                                                    All lowercase.                                                                                                                    |                                                                                                                         .mdb<br />.doc                                                                                                                         |
+|                                                  **File names (user-defined examples)**                                                  |                                                                          Apply code style if used in code. Use bold or plain text if referencing UI.                                                                           |                                                                                                             `MyTaxesFor2025`<br /> My Taxes for 2025                                                                                                             |
+|                                          **Folder and directory names (user-defined examples)**                                          |                                                                Apply code style if used in code. Use bold or plain text if referencing UI.                                                                  |                                                                                                  `MyFiles\Accounting\Payroll\VacPay`<br />Vacation and sick pay                                                                                                  |
+|                                                        **Functions (predefined)**                                                        |                                                                                                         Code style.                                                                                                         |                                                                                                  `CompactDatabase`<br />`CWnd::CreateEx`<br />`FadePic`                                                                                                  |
+|                                                               **Handles**                                                                |                                                                                                                    Code style. All uppercase.                                                                                                                    |                                                                                                                              `HWND`                                                                                                                              |
+|                                               **Keywords (language and operating system)**                                               |                                                                                         Code style. Capitalization follows the API.                                                                                          |                                                                                                             `main`<br />`True`<br />`void`                                                                                                             |
+|                                                          **Logical operators**                                                           |                                                                                                                 Code style.                                                                                                                 |                                                                                                                      `AND`<br />`XOR`                                                                                                                      |
+|                                                                **Macros**                                                                |                                                                                    Code style.                                                                                    |                                                                                                                   `LOWORD`<br />`MASKROP`                                                                                                                    |
+|                                                   **Markup language elements (tags)**                                                    |                                                                                                             Code style.                                                                                                             |                                                                                                `<img>`<br />`<input type="text">`<br />`<!DOCTYPE html>`                                                                                                |
+|                                                 **Mathematical constants and variables**                                                 |                                                                                                                       Italic.                                                                                                                        |                                                                                                                         *a2 + b2 = c2*                                                                                                                         |
+|                                                               **Members**                                                                |                                                                                                             Code style.                                                                                                             |                                                                                                                     `ulNumCharsAllowed`                                                                                                                      |
+|                                                               **Methods**                                                                |                                                                                                             Code style.                                                                                                             |                                                                                                               `OpenForm()`<br />`GetPrevious()`                                                                                                                |
+|                                                              **New terms**                                                               |                                                                             Italicize the first mention of a new term if you're going to define it immediately in text.                                                                              |                                                                                             Microsoft Exchange consists of both *server* and *client* components.                                                                                              |
+|                                                              **Operators**                                                               |                                                                                                                        Bold. Use code style for code-related operators.                                                                                                                         |                                                                                                                      **+, -**<br />`sizeof`                                                                                                                      |
+|                                                              **Parameters**                                                              |                                                                                                            Code style.                                                                                                            |                                                                                                           `Hdc`<br />`grfFlagClientBinding`                                                                                                            |
+|                                              **Placeholders (in syntax and in user input)**                                              |                                                                                                                       Italic when placeholder element is UI text. Use angle brackets for code placeholders when angle brackets aren't part of the language syntax.                                                                                                                         |                                                                                                           Enter *password*.<br /> `/v: <version>`                                                                                                       |
+|                                                                **Ports**                                                                 |                                                                                                                    All uppercase.                                                                                                                    |                                                                                                                              LPT1                                                                                                                              |
+|                                               **Products, services, apps, and trademarks**                                               |                         Usually title-style capitalization. Check the Microsoft trademark list for capitalization of trademarked names.                          |                                                               Microsoft Arc Touch Mouse<br />Microsoft Word<br />Surface Pro<br />Notepad<br />Network Connections<br />Makefile<br />RC program                                                               |
+|                                                              **Properties**                                                              |                                                                                                         Code style.                                                                                                         |                                                                                                  `M_bClipped`<br />`AbsolutePosition`<br />`Message ID`                                                                                                  |
+|                                                              **Registers**                                                               |                                                                                                  Code style.                                                                                                           |                                                                                                                               `DS`                                                                                                                               |
+|                                                          **Registry settings**                                                           | Subtrees (first-level items) all uppercase. Separated by underscores. Usually code style.<br />Registry keys (second-level items) follow the capitalization of the UI.<br />Registry subkeys (below the second level) follow the capitalization of the Regedit UI. |                                                                     `HKEY_CLASSES_ROOT`<br />`HKEY_LOCAL_MACHINE`<br />`SOFTWARE`<br />`ApplicationIdentifier`                                                                      |
+|                                                              **Statements**                                                              |                                                                                                             Code style.                                                                                                              |                                                                                                                  `IMPORTS`<br />`LIBRARY`                                                                                                                  |
+|                                                              **Structures**                                                              |                                                                                                         Code style.                                                                                                         |                                                                                                                         `ACCESSTIMEOUT`                                                                                                                          |
+|                                                               **Switches**                                                               |                                                                                                               Code style. Usually lowercase.                                                                                                               |                                                                                                                      `build: commands`                                                                                                                       |
+|                                                          **UI text or strings**                                                          |                                                                       Treatment varies; see Formatting text in instructions. Sentence-style capitalization.                                                                      |     Import from file<br />Create a new resource<br />See all your resources<br />Manually trigger a flow<br />Report a bug     |
+|                                                                 **URLs**                                                                 |                                      All lowercase for complete URLs. If necessary, line-break long URLs before a slash. Don't hyphenate. Use code style if referring to URLs in code. <br />**See also** URLs and web addresses.                                       |                                                                                                    www<span></span>.microsoft.com<br />www.microsoft.com/download<br />`const url = "https://www.microsoft.com"`                                                                                                         |
+|                                                              **User input**                                                              |                                          Usually lowercase, unless case sensitive. Bold. Use italic only for placeholders.                                           |                                                                                                       Enter **hello world**<br />Enter *password*                                                                                                       |
+|                                                                **Values**                                                                |                                                                                                                    Code style. All uppercase.                                                                                                                    |                                                                                                                         `DIB_PAL_COLORS`                                                                                                                         |
+|                                                              **Variables**                                                               |                                                                                                                  Usually code style.                                                                                                                   |                                                                                                           `bEmpty`<br />`m_nParams`<br />`file_name`                                                                                                           |
+|                                                         **XML schema elements**                                                          |                                                                                                             Code style. Usually surrounded with angle brackets.                                                                                                          |                                                                                                      `<configuration>`<br /> `ElementType` element                                                                                                     |
+
+## Chatbots and virtual agents
+
+A virtual agent is a type of bot that can be used to:
+
+- Provide information and answers. 
+- Complete tasks like booking meetings or buying tickets.
+
+Before you create a virtual agent, make sure it will add value to the customer experience.
+
+This type of bot is good for tasks where it's easier to ask for what you want rather than navigate through a menu or search for keywords. But a bot isn't a human, and there are some things that it isn't suited for.
+
+Technically speaking, there are two kinds:
+
+- One kind is scripted. It can respond only to questions that it was programmed to understand. 
+- Another uses AI, so it can understand what the customer is telling it, and its knowledge grows the more it interacts with people. 
+
+This section includes guidelines and tips to help you create this type of bot:
+
+- Structural and technical considerations
+- Writing for bots
+- Care and feeding of the bot
+
+**Learn more** Microsoft's AI vision, rooted in research, conversations Bot Framework documentation Responsible bots: 10 guidelines for developers of conversational AI
+
+## Structural and technical considerations
+
+<h2>Clarify intent before acting</h2>
+
+Until you're sure your bot can reliably interpret conversational cues, it should:
+
+- Confirm the customer's intent: "You need to reset your password. Is that right?" 
+
+- Clarify and disambiguate the customer's input when necessary: "OK, we'll reset your password. But first, I'd like to know more. 
+Did you forget your password, or are you concerned that someone else has your password? You can say, "I forgot," or "My account is compromised."
+
+Be careful not to overdo it, though. It's better not to annoy the customer with a needless prompt unless misunderstanding the request could cause damage.
+
+<h2>Use buttons and other UI structure to keep users on track</h2>
+
+- Prompt users with actionable statements and buttons to guide the conversation. 
+
+- Offer suggestions when the bot is "confused" about what the user's request is. 
+
+<h2>Pace the conversation carefully</h2>
+
+- Break up messages into separate, readable blocks to make the pace of the conversation feel more natural. 
+
+- Make sure the bot doesn't respond so quickly that it rushes the customer. Add a minimum delay if necessary.  
+
+<h2>Accommodate alternative word order and incomplete requests</h2>
+
+The bot should be able to recognize the customer's request, regardless of how it's phrased.
+
+<h2>Conclude the conversation when the request is resolved</h2>
+
+Mimic the sense of closure typical in human-to-human interaction by wrapping up the conversation. For example: "Is there anything else I can help you with? [No.] OK, then. Have a great day!" Having a sense of completion helps the customer feel like there's a shared goal, reinforces the positive experience, and builds confidence in using the bot.
+
+## Writing for bots
+
+
+
+Tailor the tone of the bot's responses to the context. If it's something serious—like billing or 
+cybersecurity—be empathetic but brief and straightforward. If it's a more mundane situation (like creating a new account), 
+the tone can be more relaxed. And a bot for Xbox can be lighthearted and casual. 
+
+**See** [Microsoft's brand voice](/style-guide/brand-voice-above-all-simple-human)  
+
+## Be honest and build trust 
+
+- Make sure users know that they're not chatting with a person. For example, have the bot introduce itself as a 
+virtual support agent. The message can be brief—research shows that customers are usually aware that they're chatting with a bot. 
+
+- Explain what the bot's purpose is and what it can and can't do. Good ways of framing the functionality are suggesting
+a first task or place to begin, or providing buttons or shortcuts for the most frequent tasks. 
+
+- Admit when things get messed up. And have a plan for dealing with the situation. 
+
+- Plan for common misspellings and errors. These don't derail human-to-human conversations, and being able to 
+accommodate them will build the user's confidence in the bot. 
+
+## Accept—and plan for—the bot's limitations 
+
+There are some questions a bot just won’t have an answer for.  
+
+- Make it clear to the user that the bot has a very specific role. Don't imply an open-ended, "Ask me anything" role. 
+
+- Be prepared for when the bot doesn't know the answer, and have it point the customer in the right direction. 
+
+- Decide what conversational cues will prompt the bot to escalate to a human. At key points in the conversation, 
+let the customer know how they can get help from a human, if they want to. 
+
+## Keep it simple, and keep it short 
+
+Customers abandon a chat when the prompts are lengthy. To keep your writing simple and straightforward, use the 
+Flesch-Kincaid Grade Level feature in Microsoft Word or an app like Hemingwayapp.com to figure out the grade level 
+of your scripts. In general, the lower the grade level, the better. 
+
+## Anticipate mischief 
+
+Plan how the bot should respond when users start to play games with it—for example, asking the same question 
+over and over to test it, using offensive language, or asking nonsense questions. An appropriate response shows 
+that the bot can be relevant and helpful, if given a chance. Humor can be effective, but be careful: a humorous 
+response to an offensive question can backfire.  
+
+## Be a good listener 
+
+- Invite the user into the conversation on a regular basis by asking questions or making suggestions.  
+
+- Respond to the customer in a timely manner. If the bot is taking a while to process the customer's request, 
+use, "I'm thinking" or the typing indicator to let the customer know the bot is working on a response.  
+
+- Boost the relevance of the bot's responses by making them specific to the context. For example, say, 
+"Here's how you change your privacy settings," not "Here's how you do that." 
+
+## Remember whose side you're on 
+
+The bot is working on behalf of the customer and is there to serve the customer. It's not there for Microsoft's benefit. 
+
+## Watch your pronouns: I, me, my 
+
+The bot uses *I, me,* and *my* to refer to itself. 
+
+When the customer communicates to the bot, they also use *I, me,* or *my.* Make sure those pronouns appear on 
+buttons, links, or other elements of the bot that the user selects.  
+
+## Recognize common words 
+
+People are familiar with words like *help, settings, start over,* and *stop.* Make sure your bot recognizes and responds to them.
+## Care and feeding of the bot
+
+<h2>Maintain the bot and evaluate its effectiveness over time</h2>
+
+Have a plan for maintaining and evolving the bot. What's working and what isn't? What's your plan for phasing in new and improved features? What can be done better? How will you know when it's time to retire your bot?
+
+<h2>Learn from customers</h2>
+
+- Make it possible for people to give you feedback directly through the bot. Ask if they got what they were looking for. 
+Give them a way to tell you what they wanted if the results weren't what they expected.
+
+- Label your content blocks in the flow. That way, you can identify the content blocks that users leave from the most, 
+figure out why, and improve them.
+
+- Extend or improve the experience when appropriate. For example, if the customer gives positive feedback, suggest 
+they rate the app. If the experience didn't meet their expectations, provide a link to support.
diff --git a/.claude/skills/microsoft-writing-style-guide/references/global-communications.md b/.claude/skills/microsoft-writing-style-guide/references/global-communications.md
new file mode 100755
index 000000000..93be1c8fc
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/global-communications.md
@@ -0,0 +1,331 @@
+# Global communications
+
+## Global communications
+
+Microsoft
+customers live and work all over the world and speak a variety of
+languages. This section will help you write content for worldwide
+communication.
+
+It's
+usually safe to assume your content will be read in many countries and
+by readers whose primary language isn't English. Some content
+will probably be translated into other languages or localized. 
+
+**Translation** is simply changing the language of content. Translation is often automated using machine translation.
+
+**Localization** is
+the process of adapting a product or content (including text
+and other elements) to meet the language, cultural, and political
+expectations and requirements of a specific local market (locale). Localization is done by people who are familiar with the local language and culture.
+
+This
+section provides guidelines for supporting worldwide customers who use
+English content and for streamlining localization and machine
+translation. You'll find a few exceptions to general Microsoft voice and
+style guidance. 
+
+## Learn more about worldwide audiences
+
+**Be curious.**
+If you write for audiences in particular countries or regions,
+subscribe to local email newsletters, visit local websites, and
+follow local news. 
+
+**Use these resources:**
+
+  - [Microsoft International Style Guides](/globalization/reference/microsoft-style-guides)
+  - [Plain Language Action and Information Network (United States)](https://www.plainlanguage.gov/)
+  - [World Time Zones](https://www.worldtimeserver.com/)
+  - [W3C Internationalization Activity](https://www.w3.org/international/)
+
+**Read more:**
+
+  - John R. Kohl, *The Global English Style Guide: Writing Clear, Translatable Documentation for a Global Market* (Cary, NC: SAS Institute, Inc., 2008).
+  - Edmond H. Weiss, *The
+    Elements of International English Style: A Guide to Writing
+    Correspondence, Reports, Technical Documents, and Internet Pages for a
+    Global Audience* (Armonk, NY: M.E. Sharpe, 2005).
+## Art
+
+Use these guidelines to create or choose images that are helpful, legal, and inoffensive throughout the world.
+
+## Color
+
+**Choose carefully.** Colors may have religious, cultural, or political significance, particularly colors used on flags or for country- or region-specific holidays.
+Neutral and brand colors are usually OK. Your international program manager can provide guidance.
+
+## Images
+
+**Choose simple or generic images that are appropriate worldwide.** Soccer players and equipment, generic landscapes and settings, pens and pencils, international highway signs, and historic artifacts are appropriate images worldwide.
+
+- Avoid holiday or seasonal images.  
+  
+- Avoid major landmarks and well-known buildings, which may have legal protections or be associated with politics or religion.
+  
+- Social or work situations involving men and women are risky in a few locales.
+  
+- Don't use hand signs.
+  
+- Don't use art based on English idioms.
+
+**Limit graphics and animations online.** In some countries or regions, long page-loading times can be expensive.
+
+**If you use text in graphics, make sure it's easy to edit.** Automatic translation software won't translate it. If possible, use captions or describe the graphic in text, instead.
+
+**Add alt text to all images that convey important meaning,** to make them accessible. Images that are purely decorative don't need alt text. This guideline also applies to buttons. If a button has an image but no label text, the image must have alt text. The alt text should focus on what the button does, not what the image shows. (If a button has both an image and a label, the image can typically be treated as decorative.) Learn more in [Alternative text (alt text)](/style-guide/accessibility/alternative-text).
+
+**Store art in a separate file and link to it from within a document** if possible. Localizers can modify art that isn't embedded in the document.
+
+**Check restrictions on imported content**
+in countries or regions where the content will be used. Be especially careful with maps, which may be subject to government review. Improper treatment of a disputed area may be illegal in some countries/regions.
+## Currency
+
+## Currency names
+
+In general, lowercase the names of currencies, but capitalize the reference to the country or region.<br /> 
+**Examples**<br />US dollar<br />Canadian dollar<br />Hong Kong SAR dollar<br />Brazilian real<br />South African rand<br />Pricing through the Microsoft Online Subscription Program is shown in US dollars.
+
+In a structured list, for example a table that compares available pricing
+options, it's OK to capitalize the name of the currency.<br />
+**Example**
+
+![Screenshot of a structured list showing countries and their respective currencies.](/style-guide/global-communications/media/currency/1453401234.png)
+
+## Specific monetary amounts
+
+When you're referencing specific amounts of money, use the currency code, followed by the amount, with no space.<br >
+**Example**<br />The company generated BRL2.89 billion (USD1.42 billion) in net revenue in 2015. 
+
+If it's clear which currency you mean, it's OK to use just the symbol. When referring to a specific amount in euros, use the euro symbol (€), not the word *euros.*<br />
+**Examples**<br />One of the largest companies in the United States, Adatum Corporation generated $1.42 billion in net revenue in 2015.<br />Adatum Corporation generated €1.42 billion in net revenue in 2015.
+## Examples and scenarios
+
+Fictitious
+examples that include the names of people, places, or organizations are
+potentially sensitive.
+Use-case scenarios—detailed descriptions of specific customer
+interactions with a product, service, or technology—present similar
+problems. To globalize examples and use-case scenarios, use these
+guidelines.
+
+**Be sensitive to how use-case scenarios may be perceived** in
+other cultures. Social situations, politics, religion, events,
+holidays, sports, traditions, and legal and business practices vary
+worldwide. For example, greeting cards are uncommon in many parts
+of the world, and in some cultures men and women don’t touch in public,
+even to shake hands.
+
+**Avoid mentioning real places altogether,** or use the names of recognizable cities from different parts of the world. Vary the locales from one example to the next. 
+
+**Avoid discussing technologies and standards** that
+aren't used worldwide. Standards vary, from phone, mobile, wireless,
+and video to measurement, paper size, character sets, and text
+direction. And don’t assume US standards are familiar or
+relevant to everyone.
+## Names and contact information
+
+## Forms that collect information
+
+If you're creating a real or sample form that collects personal information, use these guidelines.
+
+**Names**
+
+  - Use *First name* and *Last name* in forms, or simply *Full name.* 
+  
+  - If you include a *Middle name* field, make it optional. 
+  
+  - Use *Title,* not *Honorific,* to describe words such as *Mr.* and *Mrs.* Not all cultures have equivalents to some titles used in the United States, such as *Ms.*
+
+**Addresses**
+
+  - Provide fields long enough for customers to include whatever information is appropriate for their locale. 
+  
+  - Use *State or province* instead of *State.* Fields that might not be relevant everywhere, such as *State or province,* should be optional. 
+  
+  - Use *Country or region* instead of just *Country* to accommodate disputed territories. It's OK to use *Country/Region* if space is limited.
+  
+  - Include a field for *Country or region code* if you need information for mailing between European countries or regions. It's OK to use *Country/Region code* if space is limited.
+  
+  - Use *Postal code* instead of *ZIP Code.* Allow for at least 10 characters and a combination of letters and numbers. 
+  
+  - Provide enough space for long phone numbers. 
+  
+  ## Communications that use the customer's name
+  
+It's not appropriate in some markets and cultures to address the customer by name—for example, in an email 
+or product home page. 
+
+If you're working on content that addresses the customer by name, confirm that the app can reliably determine what 
+region the customer is in and can use the form of address that's appropriate for that market.
+## Time and place
+
+Use the following guidelines when talking about time and place.
+
+## Dates
+
+  - Begin calendars on Mondays, which is the custom in much of the world. 
+  - Use the date format *month dd, yyyy.* Don’t use numerals to represent months. For example, use January 5, 2018.
+
+## Time
+
+  - Include
+    the time zone when it matters to customers, such as in an event
+    listing. In time stamps that automatically display the customer's local
+    time, you don't need to include the time zone.
+
+## Seasons
+
+  - Don’t
+    refer to seasons if you can avoid it. Talk about months or
+    calendar quarters instead. If you must mention a specific season,
+    establish the hemisphere, too. (Summer in the northern hemisphere
+    is winter in the southern hemisphere.)
+
+## Places
+
+  - In event locations, include the country or region name. 
+
+**See also** [Date and time term collection](/style-guide/a-z-word-list-term-collections/term-collections/date-time-terms)
+## Web, software, and HTML considerations
+
+Web content attracts a worldwide audience. When you develop websites, keep in mind that customers may not have the latest browsers, broadband
+internet access isn't available everywhere, and internet service
+providers don't always charge a flat monthly rate for access. Follow these guidelines to support customers around the world.
+
+## Support a variety of browsers and experiences
+
+**Support browsers likely to be used by worldwide audiences. To support earlier versions of browsers, you might need to:**
+
+  - Provide a no-frames version. 
+  
+  - Avoid certain elements in scripts. 
+  
+  - Include some design information (such as background color) in the document files instead of the style sheet. 
+  
+  - Avoid nested tables.
+  
+  - Test using a variety of browsers and versions. 
+
+**Design content so fonts will be substituted if the specified font isn't
+available.** Avoid hand-drawn fonts and fonts that are hard-coded in text or code.
+
+**Use standard HTML tags, not proprietary tags.** If you’re developing HTML text with scripted code, globalize text that’s generated by the scripts, too.
+
+**Use the simplest possible design solutions.**
+
+## Minimize download time
+
+**Keep pages as small as possible,**
+and include text-only versions for larger content. Internet service
+charges still vary greatly by locale and access method.
+
+**Design pages so text loads first,** followed by graphics, so pages are usable before they're finished loading. 
+
+## Support multiple languages
+
+**Support reading from right to left or from top to bottom.**
+For example, provide key information, such as home
+page links, at both the upper-right and upper-left sides of the
+page. 
+
+**Allow space for text expansion due to localization.**
+
+## Comply with US and local laws as well as software availability
+
+**Follow laws pertaining to software restrictions.** Pay particular attention to downloads and multiproduct DVDs. 
+
+  - US
+    law restricts the international delivery of certain
+    information and technology. Verify that the download complies with
+    US law.
+    
+  - Be
+    aware of local download restrictions. The distribution of
+    marketing statements; political statements; and the names of people,
+    places, and landmarks is restricted by law in some countries and
+    regions. Verify that the download is legal in the country or
+    region.
+
+**Verify availability.**
+Some products and formats aren't available worldwide.
+Localized versions of new and updated products and formats may lag
+behind US availability. 
+
+## Globalize links
+
+**Link only to sites that are available and useful worldwide.**
+
+**Link to a site where the reader can specify the appropriate country or region,** if possible.
+
+**Identify links and cross-references that aren’t globally relevant.** If you must link to a site or refer to a publication that’s not globalized, inform your readers.
+
+## Know where your email is going
+
+**Monitor subscriptions to your newsletter to determine the reader's location.**
+Newsletters emailed to people outside the United States must
+be globalized, localized, or customized to meet local
+requirements.
+## Writing tips
+
+Content that’s easy to read tends to be easy to localize and translate. If you follow the writing recommendations in this style guide, you’re off to a great start. Pay particular attention to:
+
+  - Word choice
+  - Grammar and parts of speech
+  - Punctuation
+
+## Tips for all global content
+
+These practices will help localizers and customers.
+
+**Write short, simple sentences.** Punctuating a sentence with more than a few commas and end punctuation usually indicates a complex sentence. Consider rewriting it or breaking it into multiple sentences.
+
+**Replace complex sentences and paragraphs** with lists and tables.
+
+**Include *that* and *who*.** They help to clarify the sentence structure.<br /> **Examples** Inspect the database to verify that all tables, data, and relationships were correctly migrated. Select the checkbox of each folder that you want to sync with your desktop.
+
+**Include articles,** such as *the.* Articles help readers and translation software identify the nouns and modifiers in a sentence.<br /> **Examples** Empty the container. The empty container
+
+**If necessary for clarity, include verbs** in short headings and UI labels. For example, say *Access is denied* instead of *Access denied.*
+
+**Use sentence-style capitalization.** Capitalize proper nouns only, including trademarks and the names of products.
+
+**Avoid idioms, colloquial expressions, and culture-specific references.** They can be confusing for non-native English speakers and hard to localize. Consider the worldwide implications of what you write. Customers in other locales may not know much about the history and culture of your country.
+
+**Avoid modifier stacks.** Long chains of modifying words are confusing even to native English speakers. For example, say "Your migration will proceed more smoothly if you have a project plan that's well thought out," not "With an extremely well thought-out Windows migration project plan, your migration will go more smoothly."
+
+**Use active voice and indicative mood** most of the time. Use imperative mood in procedures.
+
+**Keep adjectives and adverbs close to the words they modify.** Pay particular attention to the placement of *only.*
+
+**Avoid linking more than three phrases or clauses** by using coordinate conjunctions such as *and,* *or,* or *but.* Better yet, avoid linking more than two.
+
+## Additional tips for machine translation
+
+Writing style affects the quality of machine translation. These tips will help you write text that's more likely to be translated accurately by machine translation. Follow these guidelines for technical content, instructions, white papers, and other content that has high business value but won't be localized.
+
+**Use conventional English grammar and punctuation.** Try to balance a friendly voice with clear, accurate English.
+
+**Use simple sentence structures.** Write sentences that use standard word order (that is, subject + verb + object) whenever possible.
+
+**Use one word for a concept, and use it consistently.** Avoid using synonyms to refer to the same concept or feature. And don’t use the same word to refer to multiple concepts or features.
+
+**Limit your use of sentence fragments.** Sentence fragments can be hard to translate.
+
+**Use words ending in *–ing* carefully.** A word ending in *–ing* can be a verb, an adjective, or a noun. Use the sentence structure and optional words to clarify the role of the *–ing* word.
+
+**Use words ending in *–ed* carefully.** A word ending in *-ed* can be a modifier or part of a verb phrase. Use the sentence structure and optional words to clarify the role of the *–ed* word.
+
+  - Add a determiner (*a, an, the, this*) before or after the *–ed* word.  
+**Example** They have **an** added functionality.
+
+  - Add a form of the verb *be*.  
+**Example** Configure limits for the backup **that are based** on the amount of storage space available.
+
+  - Split the sentence in two.  
+**Example** Configure limits for the backup. These limits should be based on the amount of storage space available.
+
+  - Rewrite the sentence to avoid the *–ed* word.  
+**Example** Configure limits for the backup. **Base the limits** on the amount of storage space available.
+
+**Use only common abbreviations,** such as *USB*, and abbreviations that are defined in glossaries. Check with a localization expert to find out if an acronym is defined.
diff --git a/.claude/skills/microsoft-writing-style-guide/references/grammar-and-parts-of-speech.md b/.claude/skills/microsoft-writing-style-guide/references/grammar-and-parts-of-speech.md
new file mode 100755
index 000000000..5003c1583
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/grammar-and-parts-of-speech.md
@@ -0,0 +1,246 @@
+# Grammar and parts of speech
+
+## Grammar and parts of speech
+
+Simple grammar tends to be easy to read and understand, like a conversation. That basic grammar you learned before you were 12 is probably just right for most Microsoft content.
+
+This section covers common grammatical issues:
+
+  - Verbs 
+  - Person 
+  - Nouns and pronouns 
+  - Words ending in *–ing* 
+  - Prepositions 
+  - Dangling and misplaced modifiers 
+
+**Learn more** For more information about grammar and parts of speech, see *The Chicago Manual of Style*.
+
+## Verbs
+
+Using precise verbs in the right way helps you write clear and simple sentences.
+
+## Verb tense
+
+In the present tense, the action is happening now. The present tense is often easier to read and understand than the past or future tense. It’s the best choice for most content.
+
+**Examples** The Windows Start screen is uniquely yours, personalized with your favorite apps, people, photos, and colors. Windows Update installs important updates automatically.
+
+## Mood of verbs
+
+The mood of a verb expresses the writer’s intent. Most of the time, use the indicative mood. It’s crisp and straightforward without being bossy. Don’t switch moods within a sentence.
+
+|    **Mood**     |                                                **Use for**                                                |                                                       **Examples**                                                        |
+|-----------------|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|
+| **Indicative**  |            Statements of fact, questions, assertions, and explanations—most Microsoft content.            |                             Style sheets are powerful tools for formatting complex documents.                             |
+| **Imperative**  | Instructions, procedures, direct commands, requests, and headings for columns that list customer actions. | Enter a file name, and then save the file.<br />**To do this&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Select this** |
+| **Subjunctive** |                                Wishes, hypotheses, and suggestions—avoid.                                 |                             We recommend that you be careful about opening email attachments.                             |
+
+## Active and passive voice
+
+Voice is either active or passive. Keep it active whenever you can.
+
+  - In active voice, the subject of the sentence performs the action. 
+  - In passive voice, the subject is the receiver of the action.
+
+|  **Voice**  |                                                                                                             **Uses**                                                                                                              |                                                                              **Examples**                                                                               |
+|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Active**  |                                                                                                      Most Microsoft content                                                                                                       |                         Divide your document into as many sections as you want. <br />Office 365 includes the Office 2016 apps for PC and Mac.                          |
+| **Passive** | <ul><li>Avoiding condescending text or blaming the customer, especially in errors, warnings, or notifications</ul></li> <ul><li>Avoiding awkward constructions</ul></li> <ul><li>Emphasizing the receiver of the action</ul></li> | That site can’t be found. Double-check the site address in the Address bar.<br />When the user clicks **OK**, the transaction is committed. (in content for developers) |
+
+## Verb agreement
+
+Verbs have singular and plural forms. Use the verb form that agrees with the subject of the sentence in number.
+
+|                **When the subject is**                |                 **The verb is**                  |                                                           **Examples**                                                            |
+|-------------------------------------------------------|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+|                   A group of things                   |                     Singular                     |                                       A variety of games is available from Microsoft Store.                                       |
+|    Two or more singular things connected by *and*     |                      Plural                      |                                     Facebook and Instagram are available from Microsoft Store.                                      |
+|     Two or more singular things connected by *or*     |                     Singular                     |                            Your tablet or phone is all you need to play your favorite games on the go.                            |
+| A singular thing and a plural thing connected by *or* | Singular or plural, to match the closest subject | Skype or social media apps are available from Microsoft Store.<br />Social media apps or Skype is available from Microsoft Store. |
+
+## Person
+
+In grammar, *person* refers to the point of view represented by a statement and determines which pronoun to use.
+
+## In general, use second-person pronouns (you, your)
+
+In second person, you write as though you're speaking to the reader. The second person often uses the personal pronoun *you* or *your*, but sometimes the word *you* is implied. It supports a friendly, human tone and helps avoid passive voice by focusing the discussion on the reader. Omit *you can* whenever the sentence works without it.
+
+In product UI, avoid using you and your in ways that sound like we're commanding people to do something rather than providing options for them to make their own choices.
+
+However, when AI-generated content is used, we should use past tense (to express action done behind the scenes) by explicitly saying “for you” or by using words that convey uncertainty or subjectivity (to express that a judgment was applied that may or may not be correct).<br />
+
+**Examples** Check if you have local admin rights.
+
+Depending on your choice, some features may be turned off by default.
+
+Change your settings
+
+Suggested for you
+
+## Use singular first-person pronouns sparingly (I, me, my)
+
+In first person, you write as though you’re speaking from the reader’s point of view. Marketing and support documentation should never use first person singular. However, it may be used inside our product experiences. First-person singular pronouns can be used in product UI to show someone’s control over an action in checkbox, button, or toggle labels.<br />
+
+**Examples** Notify me when a new Bluetooth device tries to connect to my computer
+
+Remember my password
+
+I agree to the terms of service
+
+**Exception** In rare cases, it’s OK to use “my” in navigation or filter labels if you need to distinguish a person’s content from other content that may be presented in the same visual space.
+
+**Exception** Cortana is a persona, so the use of *I* is appropriate.
+
+## Avoid plural first person (we, us)
+
+First-person plural, which often uses the pronoun *we,* can feel like a daunting corporate presence—the opposite of Microsoft's modern voice. It's OK to use phrasing like *we recommend* if it helps you avoid awkward phrasing like *it's recommended,* but write around it if you can. Try to keep the focus on the customer, not Microsoft. It’s OK to use we in privacy and security settings where you need to make clear Microsoft is the speaker.  <br />
+
+**Examples** Notify scheduled default setting is the easiest way to keep your computer up to date. (Instead of *We recommend that you use the scheduled default setting ....*)
+
+Change your password (Instead of *We recommend that you change your password.*)
+
+We protect your privacy at every step.
+
+That didn’t work. Try again. (Instead of *We weren’t able to run the Solution Checker. Try running it again.*)
+
+Allow Microsoft to contact you about this feedback
+
+## Nouns and pronouns
+
+## Capitalization and proper nouns
+
+Proper nouns are one of a kind—unique people, places, and things. Capitalize proper nouns wherever they occur.
+
+Proper nouns include:
+
+  - Names and titles of individuals.  
+  
+  - Unique, named places, organizations, events, shows, corporate and philanthropic programs, and other things.  
+  
+  - Product, service, app, and tool names.  
+  
+  - Trademarks.  
+  
+  - Titles of books, songs, and other published works.  
+  
+  - Managed standards, such as Bluetooth.
+
+If there's more than one of a thing, it's a common noun. For example, there are lots of chief operating officers, so *chief operating officer* is a common noun. There's only one *Chief Operating Officer Latasha Sharp,* so that's a proper noun.
+
+Don't capitalize common nouns unless they begin a sentence or the situation calls for title-style capitalization. Most technology concepts, product categories, devices, and features are common nouns, not proper nouns. Examples of common nouns include *cloud computing, smartphone, e-commerce,* and *open source.*
+
+Capitalize technology terms as proper nouns only when:
+
+  - You
+need to distinguish a component or product, such as SQL Server, from a general technology with a similar name, such as an SQL database server.
+    
+  - The terms are typically capitalized in the industry. Search *Merriam-Webster Dictionary,* reputable internet sites, and industry-specific dictionaries. Don't rely on unedited websites. 
+
+If you're not sure whether a term is a proper noun (and thus capitalized) or a common noun (lowercase), check *Merriam-Webster Dictionary,* and the A–Z word list. Default to lowercase unless there's a compelling reason to capitalize the term.
+
+**Learn more** For guidelines for sentence-style and title-style capitalization, see Capitalization.
+
+## Plural nouns
+
+Some nouns can be challenging to use in the plural. The simple rules that follow will help.
+
+To check the spelling of plural forms of words derived from Latin and Greek that retain their Latin or Greek endings (typically *-a, -us, -um, -on, -ix,* or -*ex*), see specific entries in the A–Z word list and *Merriam-Webster Dictionary.*
+
+|               **Noun**                |                                                                **Plural form**                                                                 |               **Examples**                |
+|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|
+| Common and proper nouns ending in *s* |                                                       If the noun ends in *s,* add *es.*                                                       | the Johnsons<br />the Joneses<br />biases |
+|         Singular abbreviation         |                                               Add an *s,* even if the abbreviation ends in *s.*                                                |              ISVs<br />DBMSs              |
+|          Plural abbreviation          |                                       If an abbreviation already represents a plural, don't add an *s.*                                        |   *MFC* (Microsoft Foundation Classes)    |
+|             Single letter             |                   Add an apostrophe and an *s.*<br />The letter itself (but not the apostrophe or the ending *s*) is italic.                   |                   *x*'s                   |
+|                Number                 |                                                                  Add an *s.*                                                                   |                 the 1950s                 |
+|               Variable                | Don't add *(s)* to a word to indicate that it could be either singular or plural unless you have no other choice. Use the plural form instead. |           Wait for *x* minutes.           |
+
+## Pronouns and gender
+
+Don't use gendered pronouns in generic references. Instead, rewrite—for example, use the second person (*you*).
+
+Or refer to a person's role (*customer, employee,* or *client*). It's OK to use *he*, *she*, or *they* when you're writing about real people who use those pronouns themselves.
+
+*They* can be used as a non-binary pronoun for a singular person instead of a binary pronoun (*she* or *he*).
+
+For more guidelines about how to write using gender-neutral pronouns, see Bias-free communication.
+
+## Pronouns and collective nouns
+
+Collective nouns like *company* take a singular pronoun. Don't use a plural pronoun (like *they*) for a collective noun.<br /> **Examples**<br />Meet with up to 250 people. All they need is a phone or internet connection.<br />The company upgraded its cloud storage solution to Microsoft Azure.
+
+**Exception** If the emphasis is on the individuals in a group, it's OK to use a plural pronoun with a singular noun.
+
+## Using pronouns in product UI
+
+See also Person.
+
+## Words ending in -ing
+
+A word ending in *–ing* can be a verb, a noun, or an adjective. Use *–ing* words with care. The sentence should make it clear which role the word plays.
+
+For example, we don’t know whether the heading, *Meeting requirements,* will be a discussion of how to meet requirements or the requirements for a meeting. These examples are clearer:
+
+  - The meeting requirements
+  - Meeting the requirements
+  - The requirements for the meeting
+  - How to meet the requirements
+
+## Prepositions
+
+## Prepositional phrases
+
+A prepositional phrase is a combination of a preposition and a noun that modifies or describes some part of a sentence. In the following sentence:
+
+> The reading pane displays the content of the selected message.
+
+The prepositional phrase, *of the selected message,* describes the noun, *content.*
+
+Avoid joining more than two prepositional phrases. Long chains of prepositional phrases are hard to read and easy to misinterpret.
+
+**Learn more** For information about using prepositional phrases in procedures, see Writing step-by-step instructions.
+
+## Placement in the sentence
+
+It's OK to end a sentence with a preposition when it improves readability.
+  
+**Examples** Use a different instrumentation key for each environment that your application runs in. Specify which event hub you want to send the data to.
+
+## Prepositions with UI elements
+
+Whether you use *in* or *on* as the preposition for a UI element depends on what the element is.
+
+| Element | Preposition |
+| ------- | ----------- |
+| bar (command bar, search bar, taskbar, toolbar) | on |
+| box (list box, search box, text box) | in |
+| command line | on |
+| dialog | in |
+| list | in |
+| menu | on |
+| page | on |
+| pane | in |
+| ribbon | on |
+| search results | in |
+| system tray | in |
+| tab | on |
+| window | in |
+
+**Examples** In the **Server name** box, enter the name that you copied earlier. In the **Create a deployment** pane, enter resource details. On the ribbon, select **Options**. On the toolbar, select **File** > **Save**.
+
+## Dangling and misplaced modifiers
+
+Modifiers are single words or phrases that modify other words or phrases. Position a modifier to make it clear what it modifies.
+
+If you keep sentences short and simple and use active voice, you probably won’t run into dangling or misplaced modifiers.
+
+  - A *dangling modifier* doesn’t modify anything in the sentence. 
+  - A *misplaced modifier* is too far from the thing it modifies or too near to something else that it could modify. 
+
+| **Example** | **Meaning** |
+|---|---|
+| _Only_ the selected text is deleted. | Nothing other than the selected text is deleted. |
+| The selected text _only_ is deleted. | _Only_ could modify _is deleted_ or _text._ This sentence could mean one of two things:<ul><li>The selected graphics aren't deleted.</li><li>The text is deleted but not archived.</li></ul> |
+| There are files _that can’t be removed_ on the disk. | The phrase _that can’t be removed_ modifies _the files._ This sentence clearly explains that the files can’t be removed, and they are on the disk.  |
+| There are files on the disk _that can’t be removed_. | The phrase _that can’t be removed_ probably modifies _the disk,_ but the writer may have intended to modify _files_. This sentence could mean one of two things:<ul><li>The files can’t be removed.</li><li>The disk can’t be removed. </li></ul> |
diff --git a/.claude/skills/microsoft-writing-style-guide/references/keys-and-keyboard-shortcuts.md b/.claude/skills/microsoft-writing-style-guide/references/keys-and-keyboard-shortcuts.md
new file mode 100755
index 000000000..0098fbd3b
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/keys-and-keyboard-shortcuts.md
@@ -0,0 +1,95 @@
+# Keys and keyboard shortcuts
+
+This term collection covers how to refer to keyboard shortcuts and the names of specific keys.
+
+For information about describing customers' interactions with UI, see Procedures and instructions.
+
+## Keyboard actions and access
+
+|                                    Term                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **keyboard shortcut, accelerator key, fast key, hot key, quick key, speed key** |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          In general, use *keyboard shortcut* to describe a combination of keystrokes used to perform a task. <br />**Example**<br />Alt+Ctrl+S <br /><br />Don't use *accelerator key, fast key, hot key, quick key,* or *speed key.*                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|                                 **access key**                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         Don't use in content for a general audience. Use *keyboard shortcut* instead. <br /><br />In content for developers or content about customizing the UI, it's OK to distinguish between an *access key* and a *shortcut key*. An access key is a letter or number that users select to access UI controls that have text labels. For example, the *F* in Alt+F. A shortcut key is a key or key combination that users select to perform a common action. For example, Ctrl+V. If you use these terms, explain the difference.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|                                   **Key Tip**                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         In general, don't use in content for a general audience. Use *keyboard shortcut* instead. <br /><br />In content teaching basic skills or content for a technical audience, it's OK to use *Key Tip* to refer to the letter or number that appears in the ribbon when the Alt key is pressed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|                               **key combination**                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   Don't use in content for a general audience. Use *keyboard shortcut* instead.<br /><br />In content for a technical audience, it's OK to distinguish between a *key combination* (two or more keys selected simultaneously) and a *key sequence* (two or more keys selected sequentially). If you use these terms, explain the difference.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|                                **key sequence**                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   Don't use in content for a general audience. Use *keyboard shortcut* instead.<br /><br />In content for a technical audience, it's OK to distinguish between a *key sequence* (two or more keys selected sequentially) and a *key combination* (two or more keys selected simultaneously). If you use these terms, explain the difference.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|                                   **keypad**                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              Use *numeric keypad* on the first mention. Don't use *keypad* by itself unless the context has been established and there's no possibility the customer will confuse the keypad with the keyboard. When in doubt, continue to use *numeric keypad*. <br /><br />In general, don't distinguish between the keyboard and the numeric keypad. When the customer can select two keys that look the same, direct the customer to the correct key. <br />**Example**<br />Select the Minus sign on the numeric keypad, not the Hyphen key on the keyboard.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|                             **keystroke, keypress**                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 Don't use *keypress*. Use *keystroke* instead.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|                  **select, press, depress, hit, strike, use**                   | Use *select* to describe pressing a key on a physical or on-screen keyboard. Don't use *press, depress, hit,* or *strike*.<br /><br />Don't use *depressed* to describe an indented toolbar button unless you have no other choice.<br /><br />Use *use* when *select* might be confusing, such as when referring to the arrow keys or function keys and *select* might make customers think that they need to select all the arrow keys simultaneously.<br />**Example**<br />Use the arrow keys to move around the text.<br /><br />Use *use* when multiple platform or peripheral choices initiate the same action or actions within a program. <br />**Example**<br />Use the controls on your keyboard or controller to run through the obstacle course. <br /><br />Be specific when teaching beginning skills. <br />**Example**<br />To run through the obstacle course, select the Spacebar on the keyboard or pull the right trigger on the Xbox controller. <br /><br />Consider using a table to present instructions that have more than two alternatives.<br /><br />Use *select and hold* only if a delay is built into the software or hardware interaction. Don't use *select and hold* when referring to a mouse button unless you're teaching beginning skills. <br /><br />**See also** Describing interactions with UI, Mouse and mouse interaction term collection |
+|                                **shortcut key**                                 |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          Don't use in content for a general audience. Use *keyboard shortcut* instead.<br /><br />In content for developers or content about customizing the UI, it's OK to distinguish between an *access key* and a *shortcut key*. An access key is a letter or number that users select to access UI controls that have text labels. For example, the *F* in Alt+F. A shortcut key is a key or key combination that users select to perform a common action. For example, Ctrl+V. If you use these terms, explain the difference.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+## Key names
+
+  - In general, use sentence capitalization for key names.<br />    **Examples**<br />    the Shift key<br />    the Page up key  
+
+  - Capitalize letter keys in general references.<br />    **Example**<br />    the K key  
+
+  - Lowercase and bold a letter key when instructing customers to enter the letter (unless you're instructing them to enter a capital letter).<br />    **Example**<br />    enter **k**    
+
+  - On the first mention, you can use the definite article *the* and the word *key* with the key name if necessary for clarity. <br /> **Example**<br />    Select the **F1** key.  
+
+  - On subsequent mentions, refer to the key by its name only. <br />    **Example**<br />    Select **F1**.
+
+If you need guidance for a key name that isn't on this list, use sentence capitalization and spell it as it appears on the keyboard.
+
+|                                          **Term**                                          |                                                                                                                                                                                                                                                                                                                                     **Usage**                                                                                                                                                                                                                                                                                                                                     |
+|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                          **Alt**                                           |                                                                                                                                                                                                                                                                                                                    Capitalize. Use to refer to the *Alt key*.                                                                                                                                                                                                                                                                                                                     |
+|                                    **Application key**                                     |                                                                                                                                                                                                                                                                         Capitalize. Use *the Application key* to refer to the key that opens a shortcut menu containing commands related to a selection.                                                                                                                                                                                                                                                                          |
+|              **arrow keys, direction keys, directional keys, movement keys**               | Arrow keys are labeled only with an arrow. Refer to similar keys on the numeric keypad as *the arrow keys on the numeric keypad*.<br /><br />Use sentence capitalization to refer to a specific arrow key: *the Left arrow key, the Right arrow key, the Up arrow key,* or *the Down arrow key*. It’s OK to use *arrow key* as a general term for any single arrow key. Include *the* and *key* in references to a specific arrow key except in key combinations or key sequences.<br /><br />Don’t use *direction keys, directional keys,* or *movement keys*.<br /><br />Use specific names to refer to other navigational keys, such as *Page up, Page down, Home,* and *End*. |
+|                                  **asterisk (\*), star**                                   |                                                                                                                                                                                                       Use *asterisk* to refer to the \* symbol.<br /><br />An asterisk is used to indicate multiplication in a programming language or as a wildcard character representing one or more characters.<br /><br />It’s OK to use *star* to refer to the key on a phone keypad.                                                                                                                                                                                                       |
+|                                      **at sign (@)**                                       |                                                                                                                                                                                                                                                                                                                 Pronounced *at*. In most cases, don’t spell out.                                                                                                                                                                                                                                                                                                                  |
+|                                          **Back**                                          |                                                                                                                                                                                                                                                                                    Capitalize. Use to refer to the *Back key,* which performs the same action as the Back button in a browser.                                                                                                                                                                                                                                                                                    |
+|                                       **Backspace**                                        |                                                                                                                                                                                                                                                                                                                 Capitalize. Use to refer to the *Backspace key*.                                                                                                                                                                                                                                                                                                                  |
+|                                        **backtab**                                         |                                                                                                                                                                                                                                                                                                              Don’t use to refer to the Shift+Tab keyboard shortcut.                                                                                                                                                                                                                                                                                                               |
+|                                       **Break caps**                                       |                                                                                                                                                                                                                                                                                                        Use sentence capitalization. Use to refer to the *Break caps key*.                                                                                                                                                                                                                                                                                                         |
+|                                       **Caps lock**                                        |                                                                                                                                                                                                                                                                                                         Use sentence capitalization. Use to refer to the *Caps lock key*.                                                                                                                                                                                                                                                                                                         |
+|                                       **comma (,)**                                        |                                                                                                                                                                                                                                     Spell out *comma* when referring to a key or the punctuation mark. <br /><br />Capitalize *Comma* when instructing a reader to select the key. Include the symbol in parentheses when needed for clarity.                                                                                                                                                                                                                                     |
+|                                        **Command**                                         |                                                                                                                                                                                                                                                                  Capitalize. Use to refer to the *Command key* on the Mac keyboard. Use the bitmap to show this key if possible. It isn't named on the keyboard.                                                                                                                                                                                                                                                                  |
+|                                        **Control**                                         |                                                                                                                                                                                                                                                                                                        Capitalize. Use to refer to the *Control key* on the Mac keyboard.                                                                                                                                                                                                                                                                                                         |
+|                                          **Ctrl**                                          |                                                                                                                                                                                                                                                                                                    Capitalize. Use to refer to the *Ctrl key*. Don’t use for the Mac keyboard.                                                                                                                                                                                                                                                                                                    |
+|                                          **Del**                                           |                                                                                                                                                                                                                                                                                  Capitalize. Use to refer to the *Del key*. On the Mac keyboard only, use to refer to the *forward delete key*.                                                                                                                                                                                                                                                                                   |
+|                                         **Delete**                                         |                                                                                                                                                                                                                                                                                                      Capitalize. Use to refer to the *delete key*.                                                                                                                                                                                                                                                                                                       |
+|                                          **End**                                           |                                                                                                                                                                                                                                                                                                                    Capitalize. Use to refer to the *End key*.                                                                                                                                                                                                                                                                                                                     |
+|                                         **Enter**                                          |                                                                                                                                                                                                                                                                                         Capitalize. Use to refer to the *Enter key*. On the Mac, use only when functionality requires it.                                                                                                                                                                                                                                                                                         |
+|                                          **Esc**                                           |                                                                                                                                                                                                                                                                                                                          Always use *Esc,* not *Escape*.                                                                                                                                                                                                                                                                                                                          |
+|                                         **F1–F12**                                         |                                                                                                                                                                                                                                                                                                       Capitalize the *F*. Don't add a space between the *F* and the number.                                                                                                                                                                                                                                                                                                       |
+|                                        **Forward**                                         |                                                                                                                                                                                                                                                                                 Capitalize. Use to refer to the *Forward key,* which performs the same action as the Forward button in a browser.                                                                                                                                                                                                                                                                                 |
+|                                          **Help**                                          |                                                                                                                                                                                                                                                                                                         Use *the Help key* only to refer to the key on the Mac keyboard.                                                                                                                                                                                                                                                                                                          |
+|                                        **HELP key**                                        |                                                                                                                                                                                                                                                                                            Use *the HELP key* to avoid confusion with the Help button. Always include *the* and *key*.                                                                                                                                                                                                                                                                                            |
+|                                          **Home**                                          |                                                                                                                                                                                                                                                                                                                    Capitalize. Use to refer to the *Home key*.                                                                                                                                                                                                                                                                                                                    |
+|                                       **hyphen (-)**                                       |                                                                                                                                                                                                                                                      Spell out *hyphen* when referring to a key. Capitalize *Hyphen* when instructing a reader to select the key. Include the symbol in parentheses when needed for clarity.                                                                                                                                                                                                                                                      |
+|                                         **Insert**                                         |                                                                                                                                                                                                                                                                                                                   Capitalize. Use to refer to the *Insert key*.                                                                                                                                                                                                                                                                                                                   |
+|                                       **Lock clear**                                       |                                                                                                                                                                                                                                                                                                                 Capitalize. Use to refer to the *Lock clear key*.                                                                                                                                                                                                                                                                                                                 |
+|                                     **minus sign (–)**                                     |                                                                                                                                                                                                                                        Spell out *minus sign* when referring to a key. Use sentence capitalization (*Minus sign*) when instructing a reader to select the key. Include the symbol in parentheses when needed for clarity.                                                                                                                                                                                                                                         |
+|                                    **Num lock option**                                     |                                                                                                                                                                                                                                                                                            Use sentence capitalization. Use to refer to the *Num lock option key* on the Mac keyboard.                                                                                                                                                                                                                                                                                            |
+|                          **number sign (#), pound key, hashtag**                           |                                                                                                                                                                                                        Use *# key* to describe the key.<br /><br />It's OK to use *pound key (#),* including the symbol in parentheses, to refer to the keypad on a telephone. It's OK to use *hashtag (#)* to describe the use of the # key to identify a metadata term in social media.                                                                                                                                                                                                         |
+|               **numeric keypad, keypad, numerical keypad, numeric keyboard**               |                                                                                                                          Use *numeric keypad* on first mention. Don't use *keypad* by itself unless there's no possibility of confusion with the keyboard. Don't use *numerical keypad* or *numeric keyboard*.<br /><br />In general, don't distinguish between the keyboard and the numeric keypad. If a customer can select two keys that look the same, specify the correct key. <br />**Example**<br />Select the Minus sign on the numeric keypad.                                                                                                                           |
+| **on-screen keyboard, keyboard display, soft keyboard, virtual keyboard, visual keyboard** |                                                                                                                                                                                                                     Use to describe the keyboard representation on the screen that the customer touches to enter characters. <br /><br />Hyphenate *on-screen keyboard*. Don't use *virtual keyboard, soft keyboard, visual keyboard,* or *keyboard display*.                                                                                                                                                                                                                     |
+|                                   **Page down, Page up**                                   |                                                                                                                                                                                                                                                                                              Use sentence capitalization. Use to refer to the *Page up key* and the *Page down key*.                                                                                                                                                                                                                                                                                              |
+|                                         **Pause**                                          |                                                                                                                                                                                                                                                                                                                   Capitalize. Use to refer to the *Pause key*.                                                                                                                                                                                                                                                                                                                    |
+|                                       **period (.)**                                       |                                                                                                                                                                                                                                                      Spell out *period* when referring to a key. Capitalize *Period* when instructing a reader to select the key. Include the symbol in parentheses when needed for clarity.                                                                                                                                                                                                                                                      |
+|                                     **plus sign (+)**                                      |                                                                                                                                                                                                                                         Spell out *plus sign* when referring to a key. Use sentence capitalization (*Plus sign*) when instructing a reader to select the key. Include the symbol in parentheses when needed for clarity.                                                                                                                                                                                                                                          |
+|                                      **Print screen**                                      |                                                                                                                                                                                                                                                                                                       Use sentence capitalization. Use to refer to the *Print screen key*.                                                                                                                                                                                                                                                                                                        |
+|                                         **Reset**                                          |                                                                                                                                                                                                                                                                                                                   Capitalize. Use to refer to the *Reset key*.                                                                                                                                                                                                                                                                                                                    |
+|                                         **Return**                                         |                                                                                                                                                                                                                                                                                                         Capitalize. Use to refer to the *Return key* on the Mac keyboard.                                                                                                                                                                                                                                                                                                         |
+|                                      **Scroll lock**                                       |                                                                                                                                                                                                                                                                                                        Use sentence capitalization. Use to refer to the *Scroll lock key*.                                                                                                                                                                                                                                                                                                        |
+|                                         **Select**                                         |                                                                                                                                                                                                                                                                                                                   Capitalize. Use to refer to the *Select key*.                                                                                                                                                                                                                                                                                                                   |
+|                                         **Shift**                                          |                                                                                                                                                                                                                                                                                                                   Capitalize. Use to refer to the *Shift key*.                                                                                                                                                                                                                                                                                                                    |
+|                                        **Spacebar**                                        |                                                                                                                                                                                                                                                                         Capitalize. Use to refer to the *Spacebar*. Always precede with *the* except in procedures, key combinations, and key sequences.                                                                                                                                                                                                                                                                          |
+|                                          **Tab**                                           |                                                                                                                                                                                                                                                                                Capitalize. Use to refer to the *Tab key*. Always use *the* and *key* except in key combinations and key sequences.                                                                                                                                                                                                                                                                                |
+|                                    **Windows logo key**                                    |                                                                                                                                                                                                                                                                                                           Capitalize *Windows*. Use to refer to the *Windows logo key*.                                                                                                                                                                                                                                                                                                           |
+
+## Special character names
+
+Because special character names could be confused with an action (such as \+) or be difficult to see, always spell out the following special character names: *Plus sign, Minus sign, Hyphen, Period,* and *Comma*.
+
+To avoid confusion, it's OK to add the character in parentheses after spelling out the name.<br />**Example** <br />Plus sign (+)
+
+Use discretion. This might not be necessary for commonly used characters, such as the period (.).
+
+To show a key combination that includes punctuation requiring use of the Shift key, such as the question mark, use *Shift* and the name or symbol of the shifted key. Using the name of the unshifted key, such as *4* rather than *$,* could be confusing or even wrong. For example, the *?* and */* characters aren't shifted keys on every keyboard. Always spell out *Plus sign, Minus sign, Hyphen, Period,* and *Comma*.
+
+**Examples**<br />Ctrl+Shift+? <br />Ctrl+Shift+\* <br />Ctrl+Shift+Comma
+
+**See also** Special character term collection
diff --git a/.claude/skills/microsoft-writing-style-guide/references/numbers-acronyms-capitalization.md b/.claude/skills/microsoft-writing-style-guide/references/numbers-acronyms-capitalization.md
new file mode 100755
index 000000000..4386e6dbe
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/numbers-acronyms-capitalization.md
@@ -0,0 +1,339 @@
+# Numbers, acronyms, and capitalization
+
+## Numbers
+
+Be consistent
+in your use of numbers. When you write about numbers used in
+examples or UI, duplicate them exactly as they appear in the UI. In
+all other content, follow the guidelines below.
+
+## Numerals vs. words
+
+  - In body text, spell out whole numbers from zero through nine, and use numerals for 10 or greater. It's OK to use numerals for zero through nine when you have limited space, such as in tables and UI.<br />
+    **Examples**  
+    10 screen savers  
+    five databases  
+    zero probability  
+    7,990,000  
+    1,000  
+
+  - Spell out zero through nine and use numerals for 10 or greater for days, weeks, and other units of time.<br />
+    **Examples**  
+    seven years  
+    28 days  
+    12 hrs  
+
+  - If one item requires a numeral, use numerals for all the other items of that type.<br />
+    **Examples**  
+    One article has 16 pages, one has 7 pages, and the third has only 5 pages.  
+    Microsoft Inspire is only one month and 12 days away.  
+
+  - When two numbers that refer to different things must appear together, use a numeral for one and spell out the other.<br />
+    **Example**  
+    fifteen 20-page articles
+
+  - Don't start a sentence with a numeral. Add a modifier before the number, or spell the number out if 
+  you can't rewrite the sentence. It's OK to start list items with numerals—use your judgment.<br />
+    **Examples**  
+    More than 10 apps are included.  
+    Eleven apps are included.   
+
+  - Use numerals in these situations.
+
+| **Use numerals for** | **Examples** |
+|---|---|
+| Measurements of distance, temperature, volume, size, weight, pixels, points, and so on—even if the number is less than 10. | 3 feet, 5 inches <br /> 1.76 lb <br /> 80 × 80 pixels <br /> 0.75 grams <br /> 3 centimeters <br /> 3 cm |
+| A number the customer is directed to enter. | Enter **5**. |
+| A round number of 1 million or more. | 7 million |
+| Dimensions. Spell out _by,_ except for tile sizes, screen resolutions, and paper sizes. For those, use the multiplication sign (×). Use a space before and after the multiplication sign. | 10-foot cable <br /> 4 × 4 tile <br /> 8.5&quot; × 11&quot; paper <br /> 1280 × 1024 |
+| Time of day. Include _AM_ or _PM._<br /> **Exception** Don't use numerals for _12∶00_. Use _noon_ or _midnight_ instead.<br /> Include the time zone if you're discussing an event, and customers beyond the local time zone may see it. Time stamps in UI and websites usually display local time and date automatically. | 10∶45 AM<br /> 6∶30 PM<br /> The meeting is at noon. <br /> The event starts at 5∶00 PM Pacific Time. <br /> The date changes at midnight. |
+| Percentages, no matter how small. Use the percent sign (%) with numerals. Use _percentage_ when you don't specify a quantity. | At least 50% of your system resources should be available.<br /> Only 1% of the test group was unable to complete the task.<br /> A large percentage of system resources should be available. |
+| Coordinates of tables or worksheets and numbered sections of documents. | row 3, column 4 <br /> Volume 2 <br /> Chapter 10 <br /> Part 5 <br /> step 1 |
+
+## Commas in numbers
+
+  Use commas in numbers that have four or more digits.<br />
+  **Examples**  
+  $1,024  
+  1,093 MB  
+
+  **Exception** When designating years, pixels, or baud, use commas only when the number has five or more digits.<br />
+  **Examples**  
+  2500 B.C.  
+  10,000 B.C.  
+  1920 × 1080 pixels  
+  10,240 × 4320 pixels  
+  9600 baud  
+  14,400 baud
+
+  Don't use commas in page numbers, addresses, or after the decimal point in decimal fractions.<br />
+  **Examples**  
+  page 1091  
+  15601 NE 40<sup>th</sup> Street  
+  1.06377 units  
+
+## Numbers in dates
+
+  Don't use ordinal numbers, such as *June* *first* or *October twenty-eighth,* for dates. Use a numeral instead: *June 1, October 28.*
+
+  **Global tip** To avoid confusion, always spell out the name of the month. The positions of the month and day vary by country. For example, 6/12/2017 might be June 12, 2017 or December 6, 2017.
+  
+## Phone numbers 
+
+Use hyphens—not parentheses, periods, spaces, or anything else—to separate the parts of a phone number. 
+
+Example 612-555-0175 
+
+**Global tip** For information about how to format phone numbers in a region outside the United States and Canada, refer to the localization style guide for that region. 
+
+## Negative numbers
+
+  Form a negative number with a minus sign, not an en dash:<br />
+  **Example**  
+  &minus;79
+
+## Compound numbers
+
+  Hyphenate compound numbers when they're spelled out.<br />
+  **Examples**  
+  twenty-five fonts  
+  the twenty-first day  
+
+## Fractions and decimals
+
+  - Express fractions in words, as symbols, or as decimals, whichever is most appropriate.  
+  
+  - In tables, align decimals on the decimal point.  
+  
+  - Add a zero before the decimal point for decimal fractions less than one, unless the customer is asked to enter the value.<br />
+    **Examples**  
+    0.5 cm  
+    enter **.75"**  
+
+  - Don't use numerals separated by a slash to express fractions.
+
+    **Exception**
+    When an equation occurs in text, it's OK to use a slash between the numerator and the denominator. Or, in Microsoft Word, go to the **Insert** tab, and select **Equation** to format the equation automatically.<br />
+    **Example**  
+    ½ + ½ = 1  
+
+  - Hyphenate spelled-out fractions. Connect the numerator and denominator with a hyphen unless either already contains a hyphen.<br />
+    **Examples**  
+    one-third of the page  
+    two-thirds completed  
+    three sixty-fourths  
+
+  - In
+  measurements where the unit of measure is spelled out, use the plural
+  form when the quantity is a decimal fraction. Use the singular form only
+  when the quantity is 1.<br />
+    **Examples**  
+    0.5 inches  
+    0 inches  
+    1 inch  
+    5 inches  
+
+## Ordinal numbers
+
+  - Always spell out ordinal numbers.<br />
+    **Examples**  
+    the first row  
+    the twenty-first anniversary  
+
+  - Don't use ordinal numbers, such as *June first,* for dates.  
+  
+  - Don't add -*ly* to an ordinal number, as in *firstly* or *secondly*.
+
+## Ranges of numbers
+
+  - In most cases, use *from* and *through* to describe a range of numbers.<br />
+    **Example**  
+    from 9 through 17
+
+    **Exceptions** <br />
+    Use an en dash in a range of pages or where space is an issue, such as in tables and UI. For example, *2016–2020* and *pages 112–120.*<br />
+    Use *to* in a range of times. For example, *10∶00 AM to 2∶00 PM.*  
+
+  - Don't use *from* before a range indicated by an en dash, such as *10–15*. 
+  
+## Abbreviations
+  
+  In general, don't abbreviate *thousand, million,* and *billion* as *K, M,* and *B.* Spell out *thousand, 
+  million,* and *billion,* or use the entire number.<br />
+  **Examples**  
+  Fabrikam, Inc., employs more than 65,000 people.  
+  Total cost to the enterprise: 300,000 hours and $30 million per year
+
+  In UI, avoid the abbreviations unless space is too limited to spell out the number.
+  
+  **Global tip** Machine translation might not translate these abbreviations correctly. Also, an abbreviated form 
+  might not be available or might be longer in the target language, so allow space for expansion in localized content.
+  
+  If you must use the abbreviations, follow these guidelines:  
+  - Capitalize *K, M,* and *B.*  
+  - Don't put a space between the number and the abbreviation.  
+  - Use the decimal form of a number only if it really will save space. In particular, avoid the use of a decimal 
+  with *K*—*8.21K* has the same number of characters as *8,210.*   
+
+**See also**  
+[Date and time term collection](/style-guide/a-z-word-list-term-collections/term-collections/date-time-terms)  
+[Units of measure term collection](/style-guide/a-z-word-list-term-collections/term-collections/units-of-measure-terms)  
+[Bits and bytes term collection](/style-guide/a-z-word-list-term-collections/term-collections/bits-bytes-terms)  
+[Em dashes, en dashes, hyphens, and minus signs](/style-guide/punctuation/dashes-hyphens/index)  
+[Percent, percentage](/style-guide/a-z-word-list-term-collections/p/percent-percentage)
+## Acronyms
+
+Acronyms and abbreviations can have an adverse effect on clarity, voice, and
+findability. Although some acronyms are widely understood and preferred to the
+spelled-out term, others aren't well known or are familiar only to a
+specific group of customers. 
+
+## Don't create acronyms from product or feature names
+
+Always spell out Microsoft product and feature names.
+
+## Only use acronyms that your audience is familiar with
+
+The A–Z word list has guidelines for many common acronyms, and some acronyms are so widely used that they're in *[Merriam-Webster Dictionary](https://merriam-webster.com/).*
+
+## If you have to use an acronym, also spell out the term for clarity
+
+In general, include the acronym in parentheses following the spelled-out
+term. On subsequent mentions in the same article, page, or screen, you can
+use the acronym without spelling it out. 
+
+Some acronyms, like *USB, FAQ,* and *URL,* are more well known than the spelled-out term. Don't spell out the term if the acronym is listed in *[Merriam-Webster Dictionary](https://merriam-webster.com/)* or if the A–Z word list
+says to use the acronym without spelling it out. If you're sure your
+audience is familiar with an acronym, it's OK to use it without spelling
+it out.
+
+**Examples**  
+Conversation as a platform (CaaP) has the potential to make booking a flight as easy as sending a text message. Developers are also looking to CaaP to make computing more accessible to users of all abilities.   
+Learn how to connect a USB device to your Microsoft Surface.
+
+## Don't introduce acronyms that are used just once
+
+If
+an acronym will appear only once in your content, just spell out the
+term. Don't introduce it in parentheses after the spelled-out version.
+
+**Exception** It's OK to use both the spelled-out term and the acronym if both are needed for SEO, even if the acronym is used only once.
+
+## Be careful with acronyms in titles and headings
+
+Avoid using an acronym for the first time in a title or heading, unless it's a
+keyword that you need to place in the title or heading for SEO. If the
+first use of the acronym is in a title or heading, introduce the acronym
+(in parentheses, following the spelled-out term) in the following body
+text. 
+
+## Lowercase the spelled-out term
+
+Lowercase all words in the spelled-out form of an acronym except for proper
+nouns. The names of many protocols and specifications are considered
+proper nouns and are capitalized when spelled out.
+
+**Examples**  
+infrastructure as a service (IaaS)  
+dynamic-link library (DLL)<br>High-Definition Multimedia Interface (HDMI)
+
+## Use *a* or *an,* depending on pronunciation
+
+Which article (*a* or *an*) you use depends on whether you pronounce the acronym like a word or pronounce each letter.
+
+**Examples**  
+a DLL  
+an ISP  
+a URL  
+a SQL database
+
+**Add *s* to make an acronym plural**
+
+Form the plural of an acronym like you would any other noun. If the acronym stands for a singular noun, add a lowercase *s* to make it plural. If an acronym stands for a plural noun, don’t add an *s.*
+
+**Examples**  
+three APIs  
+Microsoft Foundation Classes (MFC)
+
+## Avoid the possessive form
+
+Unless an acronym refers to a person or an organization, avoid using the possessive form.
+
+**Examples**  
+the IDE enhancements  
+the purpose of the FAQ  
+the CEO’s blog
+
+**Global tip** In machine-translated content, be careful with acronyms that form common English words, like *RAM.* If the acronym appears outside of the parentheses and without the spelled-out version, it might be translated incorrectly.
+
+**See also** [Bits and bytes term collection](/style-guide/a-z-word-list-term-collections/term-collections/bits-bytes-terms), [Units of measure term collection](/style-guide/a-z-word-list-term-collections/term-collections/units-of-measure-terms)
+## Capitalization
+
+Microsoft style uses sentence-style capitalization. That means everything is lowercase except the first word and proper nouns, which include the names of brands, products, and services. (Microsoft has more than 500 offerings. To help customers recognize, find, and buy them, reserve capitalization for product and service names.)
+
+Follow these guidelines in Microsoft content:
+
+  - Use sentence-style capitalization most of the time. That means: 
+      - Capitalize the first word of a sentence, heading, title, UI label (such as
+the name of a button or checkbox), or standalone phrase.
+      - Capitalize proper nouns. To learn more about proper nouns, see Nouns and pronouns.
+      - Use lowercase for everything else.  
+      
+  - Always capitalize the first word of a new sentence. Rewrite sentences
+that start with a word that's always lowercase.
+    
+  - Don't use all uppercase for emphasis. (It's OK to use italic sparingly for emphasis.)  
+  
+  - Don't use all lowercase as a design choice. Although all uppercase is used occasionally as a design element, don't use it in text.
+
+<!-- end list -->
+
+  - Don't use internal capitalization (such as *AutoScale* or *e-Book*) unless it's part of a brand name.  
+  
+  - Don't capitalize the spelled-out form of an acronym unless it's a proper noun.  
+  
+  - When words are joined by a slash, capitalize the word after the slash if the word before the slash is capitalized.  
+**Examples** Country/Region Turn on the On/Off toggle.
+
+  - For information on capitalization in hyphenated compound words see Hyphens.
+  
+**Learn more** To learn more about capitalization, see *The Chicago Manual of Style*.  If you're not sure whether to capitalize a term, check the A–Z word list and *Merriam-Webster Dictionary.*
+
+For information about capitalizing UI labels in instructions, see Formatting text in instructions.
+
+## Sentence-style capitalization in titles and headings
+
+Use sentence-style capitalization in most titles and headings: capitalize the first word and lowercase the rest. **Exceptions** Proper nouns, including brand, product, and service names, are always capitalized. If a title or heading includes a colon, capitalize the first word after it.
+
+Titles of blog posts, documentation articles, and press releases use sentence-style capitalization.<br /> **Examples** Watch your favorite HD movies, TV shows, and more 1 TB of cloud storage Choose the Office version that's right for you Available for Microsoft partners and commercial and public-sector customers Can a search engine predict the World Cup winner? Block party: Communities use Minecraft to create public spaces
+
+## Title-style capitalization
+
+Occasionally, title-style capitalization—capitalizing most words—is appropriate. For example, product and service names, the names of blogs, book and song titles, article titles in citations, white paper titles, and titles of people (*Vice President* or *Director of Marketing*) require title-style capitalization. In a tweet, it's OK to use title-style capitalization to highlight the name of a quoted article.
+
+On the rare occasions when title-style capitalization is required, follow these guidelines:
+
+  - Always capitalize the first and last words.<br />
+**Example** A Home to Go Back To
+    
+  - Don't capitalize *a, an,* or *the* unless it's the first word.  
+**Examples** Microsoft on the Issues The Official Microsoft Blog
+    
+  - Don't capitalize prepositions of four or fewer letters (such as *on, to, in, up, down, of,* and *for*) unless the preposition is the first or last word.  
+**Examples** How to Personalize Windows To Personalize Windows Ryse: Son of Rome Achieving Excellence in the Classroom Through Technology OneNote Class Notebooks for Teachers The Teaching Tool You're Looking For
+    
+  - Don't capitalize *and, but, or, nor, yet,* or *so* unless it's the first word or the last word.  
+**Example** Monitoring and Operating a Private or Hybrid Cloud
+    
+  - Capitalize all other words, including nouns, verbs (including *is* and other forms of *be*), adverbs (including *very* and *too*), adjectives, and pronouns (including *this, that,* and *its*).  
+**Examples** Enterprise Agility Is Not an Oxymoron This Is All There Is Teaching Math Over and Over Again, in Less Time Than Before
+    
+  - Capitalize the word after a hyphen if it would be capitalized without the hyphen or it's the last word.  
+**Examples** Self-Paced Training for Microsoft Visual Studio Microsoft Management Console: Five Essential Snap-Ins Five Essential Snap-ins for Microsoft Management Console Copy-and-Paste Support in Windows Apps
+    
+  - Capitalize the first word of labels and terms that appear in
+UI and APIs unless they're always lowercase (for example, *fdisk*).
+    
+  - In programming languages, follow the traditional capitalization of keywords and other special terms.
+
+**See also** Formatting titles
diff --git a/.claude/skills/microsoft-writing-style-guide/references/punctuation.md b/.claude/skills/microsoft-writing-style-guide/references/punctuation.md
new file mode 100755
index 000000000..b8091917d
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/punctuation.md
@@ -0,0 +1,446 @@
+# Punctuation
+
+## Punctuation
+
+Punctuation provides vital clues for reader understanding. It's governed by well-documented rules. For example, every English sentence requires end punctuation (unless it's a title or a heading). Within those rules are stylistic choices, which we'll cover here.
+
+**Writing tip** The more punctuation you add, the more complex a sentence becomes. If a sentence contains more than a comma or two and ending punctuation, consider rewriting it to make it crisp and clear.
+
+**Learn more** Refer to *The Chicago Manual of Style* to learn more about specific punctuation.
+
+This section covers:
+
+- Formatting punctuation in text describing interaction with the UI, parentheses, and brackets.
+- Apostrophes in possessives and contractions.
+- Colons in lists and to elaborate on a statement.
+- Commas in series, clauses, and dates.
+- Em dashes, en dashes, hyphens, and minus signs, including em dashes to set off phrases, en dashes in ranges of numbers or dates, hyphens in words and spelled-out numbers, and minus signs for subtraction operations and negative numbers.
+- Ellipses in syntax and for omissions. 
+- Exclamation points, used sparingly.
+- Periods in sentences and lists.
+- Question marks, used sparingly.
+- Quotation marks for quotations only.
+- Semicolons between independent clauses, contrasting statements, and items in a list.
+- Slashes in phrases, file paths, and URLs.
+
+## Formatting punctuation
+
+In general, format punctuation in the same font style as the main content of a sentence or phrase.
+
+## Text describing interaction with the UI
+
+In instructions that reference elements such as commands, options, keywords, placeholders, links, pop-up text, and user input:
+
+  - If the punctuation
+is part of the element, such as punctuation that the customer must type, format the punctuation the same as the element. <br /> **Example** Enter **Balance due:** in cell A14. (In this example, the colon is bold because the customer types the colon.)
+
+  - If the punctuation is not part of the element, format the punctuation the same as the main text. <br />
+**Examples** On the **Insert** menu, go to **Pictures**, and then select **From File**. (In this example, the comma following *Pictures* and the period following *File* aren't bold because the punctuation isn't part of the UI labels.) Select **Accounts**  \> **Other accounts** \> **Add an account**. (In this example, brackets aren't bold because they aren't part of the UI labels.)
+
+## Parentheses and brackets
+
+Format parentheses and brackets in the font style of the main text, not of the text in the parentheses or brackets. **Example** Open any Office app and select **File** \> **Account**. (If you're doing this in Outlook, select **File** \> **Office Account**.) (In this example, the opening and closing parentheses aren't bold, to match the main text.)
+
+Use the same font style for the closing parenthesis or bracket that you use for the opening parenthesis or bracket.
+
+## Apostrophes
+
+## Use an apostrophe
+
+  - To form the possessive case of nouns. For singular nouns, add an apostrophe and an *s,* even if the noun ends in *s, x,* or *z.* To form the possessive of plural nouns that end in *s,* add only an apostrophe.  
+**Examples** insider's guide the box's contents the CSS's flexibility Berlioz's opera an OEM's product users' passwords the Joneses' computer
+    
+  - To indicate a missing letter in a contraction.  
+**Examples** can't don't it's
+
+## Don’t use an apostrophe
+
+  - For the possessive form of *it*.  
+**Example** <br />Replace a formula with its calculated value.
+    
+  - With a possessive pronoun.  
+**Example** <br />The choice is yours.
+    
+  - To form the plural of a singular noun.  
+**Example** <br />Play your favorite games on all your devices.
+
+**Note**  Don't use the possessive form of Microsoft trademarks and product, service, or feature names.
+
+## Colons
+
+Avoid using a colon to introduce a clarification or amplification of a sentence's main statement within the sentence itself. In most cases, you can make the sentence more direct and readable by rephrasing it or breaking it into multiple sentences. Alternatively, consider replacing the colon with a comma or an em dash, depending on the context. If the text after the colon has multiple parts, consider using a list instead. If you do use a colon within a sentence, the word after it should be lowercase unless it's a proper noun or the first word of a direct quotation.
+
+**Examples**
+
+| **Preferred (without a colon)** | **Acceptable (with a colon)** |
+|---------------------------------|-------------------------------|
+| The company is considering Los Angeles, Munich, and Tokyo for the event. | The company is considering three cities for the event: Los Angeles, Munich, and Tokyo. |
+| If Exchange ActiveSync doesn't recognize the device, the device isn't properly connected, or it isn't a smartphone.<br><br>OR<br><br>Exchange ActiveSync doesn't recognize the device for one of two reasons:<br>• The device isn't properly connected.<br>• The device isn't a smartphone. | Exchange ActiveSync doesn't recognize the device for one of two reasons: the device isn't properly connected, or it isn't a smartphone. |
+| The cells of a worksheet can store different types of information—numbers, formulas, or text. | The cells of a worksheet can store different types of information: numbers, formulas, or text. |
+| If you updated at least one value that requires approval, the Action Pane has two extra buttons, Proposed changes and Workflow. | If you updated at least one value that requires approval, the Action Pane has two extra buttons: Proposed changes and Workflow. |
+
+## In titles and headings
+
+Don't use a colon at the end of titles or headings. However, you can use a colon *within* a title, heading, or similar content (for example, an email subject line) to divide it into two parts that are analogous to a title and a subtitle. Always capitalize the word after the colon.
+
+**Examples**
+
+- Block party: Communities use Minecraft to create public spaces
+- Get started with Azure IoT: An interactive developer guide
+
+## Before images, tables, and code samples
+
+Don't use a colon at the end of a phrase that directly precedes and introduces an image, a table, or a code sample. Use a period instead.
+
+## Before lists
+
+You can often use a colon at the end of a phrase that directly precedes and introduces a bulleted or numbered list, based on how strongly it looks ahead to the list items.
+
+- If the phrase forms a complete sentence by itself:
+  - You can typically use a colon when the sentence makes direct reference to the list items through expressions such as "here are," "these," "the following," or "as follows," or by stating the number of items.
+  - Otherwise, use a period.
+- If the phrase is a fragment:
+  - Use a colon if at least one list item can be read immediately after the fragment to form a complete sentence.
+  - Otherwise, don't add end punctuation to the fragment. In this case, you might consider formatting the fragment as a heading.
+
+**Example** <br> Make the transition easier by creating a backup of important things, such as:
+- Installed apps
+- Account passwords
+- Call history
+
+To learn more, see Lists.
+
+## In UI
+
+In UI, don't use a colon at the end of headings, input labels, command names, or the labels for buttons, checkboxes, and other options.
+
+> [!NOTE]
+> Even if a colon is used in UI, don't include it when you refer to the UI element by name in documentation.
+
+To learn more, see  Formatting text in instructions.
+
+## Commas
+
+## Use a comma
+
+  - Before the conjunction in a list of three or more items. (The comma that comes before the conjunction is known as the Oxford or
+serial comma.)<br /> **Examples** Outlook includes Mail, Calendar, People, and Tasks. Save your file to a hard drive, an external drive, or OneDrive.
+
+**Writing tip** If a series contains more than three items or the items are long, consider a bulleted list to improve readability.
+
+  - Following an introductory phrase. <br />
+**Example** <br />With the Skype app, you can call any phone.
+
+  - To join independent clauses with a conjunction, such as *and, or, but,* or *so.*<br />
+**Example** <br />Select **Options**, and then select **Enable fast saves**.
+
+**Writing tip** If the sentence is long or complex, consider rewriting as two sentences.
+
+  - In a series of two or more adjectives that precede a noun, if the order of the adjectives can be reversed or if 
+they can be separated by *and* without changing the meaning.<br /> **Examples** Adjust the innovative, built-in Kickstand and Type Cover. PlayFab is a complete back-end platform.
+
+**Writing tip** Consider rewriting for a friendlier, more conversational tone. For example, say, "Build mixed-reality apps that support collaboration across platforms," not "Build collaborative, cross-platform mixed-reality apps."
+
+  - To surround the year when you use a complete date within a sentence.<br />
+**Example** <br />See the product reviews in the February 4, 2015, issue of the *New York Times.*
+
+For information about using commas in numbers, see Numbers.
+
+## Don't use a comma
+
+  - To join independent clauses when you don't use a conjunction. (Use a semicolon instead.)<br />
+**Example** <br />Select **Options**; then select **Enable fast saves.**
+
+  - Between verbs in a compound predicate (when two verbs apply to a single subject).<br />
+**Example** <br />The program evaluates your computer system and then copies the essential files to the target location.
+
+**Writing tip** Consider replacing a compound predicate with two sentences. Or add a subject for the second verb.<br /> **Examples** The program evaluates your computer system. Then it copies the essential files to the target location. The program evaluates your computer system, and then it copies the essential files to the target location.
+
+  - Between the month and the year when a specific date isn't mentioned.
+
+## Ellipses
+
+In general, don’t use an ellipsis (…) except in the situations described here or to indicate omitted code in technical content.
+
+It's OK to use an ellipsis to indicate a pause in conversational UI messages. **Example** *(Hmm ... looks like that link is broken.)*
+
+When there's an ellipsis in UI, don’t include it in instructions or procedures. **Example** Select **Safety**, and then **Delete browsing history**.
+
+In quoted material, use an ellipsis to indicate omitted text.
+
+  - If the ellipsis replaces text within a sentence, include a space before and after the ellipsis.<br />
+**Example** The quick brown fox … lazy dog.
+
+  - If
+the ellipsis replaces the end of a quoted sentence, include a space before the ellipsis and follow it with a closing period, with no intervening space. <br /> **Example** The quick brown fox ….
+
+It’s OK to use an ellipsis in multiple-part callouts, especially with screenshots or graphics in documentation.
+
+**Figure** A two-part callout reads, “When you apply a design template … formatting and items change ….”
+
+  - Ensure that the path through the callouts is clear. Document each step.  
+  
+  - Insert a space and then an ellipsis at the end of a phrase that continues later.
+Insert an ellipsis followed by a space at the beginning of a phrase that's continued from a previous phrase.
+    
+  - If
+the callout ends with additional punctuation, such as a period or comma, insert a space between the punctuation mark and the ellipsis.
+
+If you're using a font that doesn't have the ellipsis character, use three periods with no space between them.
+
+## Em dashes, en dashes, hyphens, and minus signs
+
+Em dashes (—), en dashes (–), hyphens (-), and minus signs (&minus;) aren't interchangeable symbols. Follow these guidelines to help you use them the right way, in the right places.
+
+- **Em dashes**: Use to signal a break in thought, or to set off some immediate clarification, amplification, or parenthetical remark that you want to add within a sentence. Em dashes can be an effective alternative to colons, semicolons, and parentheses, but don't overuse them. Like colons, semicolons, and parentheses, em dashes can affect readability if they are used excessively, by interrupting the flow of the text and making sentences overly long and complex. Don't use spaces around em dashes.
+- **En dashes**: Use in ranges of numbers and dates, such as in time and date stamps in UI. An en dash can also be used instead of a hyphen in some compound words (see Hyphens for details). Don't use in place of the minus sign. Don't use spaces around en dashes.
+
+**Exception** Use spaces around an en dash when it's used in a time stamp appearing in UI, or in a date range that includes two times and two dates.
+
+- Hyphens: Use to join words and connect prefixes to stem words. Don't use multiple hyphens in place of an em dash.
+- **Minus signs**: Use to represent subtraction operations and negative numbers. For accessibility reasons, don't substitute an en dash for the minus sign.
+
+**Examples**
+
+Em dash to set off clarifying or amplifying text: The information in your worksheet—numbers, formulas, and text—is stored in cells.
+
+En dash for a date range: 2015–2017
+
+Hyphen in a compound modifier: Azure-supported features
+
+En dash instead of a hyphen in a compound modifier containing an "open compound": AI Builder–supported features
+
+En dash for a time stamp in UI: 2:15 PM – 4:45 PM
+
+En dash for a range that includes both times and dates: 2:15 PM 12/1/17 – 4:45 PM 4/1/18
+
+Minus sign for a negative number: The temperature was &minus;12&deg;F.
+
+Minus sign for a subtraction operation: 12 &minus; 3 = 9
+
+**See also** Hyphens
+
+## Hyphens
+
+For information about hyphenating specific technology words, see the A–Z word list. For information about hyphenating common words, see Merriam-Webster Dictionary and The Chicago Manual of Style.
+
+## Predicate adjectives
+
+Don't hyphenate a predicate adjective (an adjective that complements the subject of a sentence and follows a linking verb) unless this style guide specifically recommends it. Check the A–Z word list to find out.
+
+**Examples** The text is left aligned. The camera is built in. Many viruses are memory-resident.
+
+## Noun modifiers
+
+In compound words that precede and modify a noun as a unit, don't hyphenate:
+
+- *Very,* when it precedes another modifier.  
+
+**Example** Very fast test
+
+- An adverb ending in *-ly,* such as *completely,* when it precedes another modifier. Check Merriam-Webster Dictionary if you're not sure whether the word ending in *-ly* is an adverb.
+  
+**Examples** extremely stylized image highly graphical interface
+
+**Note**: Use adverbs sparingly. They usually aren't necessary.
+
+Hyphenate two or more words that precede and modify a noun as a unit if:
+
+- Confusion might result without the hyphen.
+
+**Examples** built-in drive high-level-language compiler read-only memory lower-left corner floating-point decimal line-by-line scrolling scrolling line by line up-to-date information
+
+- One of the words is a past or present participle (a verb form ending in *-ed* or *-ing* and used as an adjective or noun).
+
+**Examples** left-aligned text free-flowing form well-defined schema The schema is well defined.
+
+- The modifier is a number or single letter plus a noun or participle.
+
+**Examples** two-sided arrow 5-point star y-coordinate values
+
+## Suspended compound modifiers
+
+Don't use suspended compound modifiers, such as *left- and right-aligned text,* unless space is limited. Instead, spell out the entire phrase.
+
+**Example** upper-right or lower-right corner
+
+If you use a suspended compound modifier, include a hyphen with both adjectives. The first hyphen is followed by a space.
+
+**Example** upper- or lower-right corner
+
+Don't form suspended compound modifiers from one-word adjectives.
+
+**Example** uppercase and lowercase letters
+
+## Compound nouns
+
+Hyphenate compound nouns when one of the words is abbreviated.
+
+**Examples** e-book e-commerce
+
+**Exception** email
+
+## Compound numerals and fractions
+
+Hyphenate compound numerals and fractions.
+
+**Examples** a twenty-fifth anniversary one-third of the page
+
+Use an en dash (–) instead of a hyphen in a compound adjective when:
+
+- The compound adjective includes an open compound.
+
+**Example** Windows 10–compatible products
+
+- Two or more of the elements are made up of hyphenated compounds (a rare occurrence).
+
+## Prefixes
+
+Avoid creating new words by adding prefixes to existing words. Rewrite to avoid creating a new word. If a word with a prefix is listed in Merriam-Webster Dictionary or the A–Z word list, it's OK to use in Microsoft content.
+
+In general, don't include a hyphen after the following prefixes:
+
+- auto-
+- co-
+- cyber-
+- exa-
+- giga-
+- kilo-
+- mega-
+- micro-
+- non-
+- pre-
+- re-
+- sub-
+- tera-
+- un-
+
+However, use a hyphen between a prefix and a stem word:
+
+- If a confusing word results without the hyphen.
+
+**Examples** non-native pre-provisioned
+  
+- If the lack of a hyphen would cause confusion with other words.
+
+**Examples** co-op re-create re-sent re-sign
+
+- If the stem word begins with a capital letter.
+
+**Example** non-XML
+
+A prefix affects a word, not a phrase. For example, instead of *non-security related,* use *unrelated to security*.
+
+When adding a prefix to a stem word results in a double vowel and each vowel is pronounced, don't use a hyphen.
+
+**Examples** reenter cooperate
+
+For more information about using prefixes, see The Chicago Manual of Style.
+
+## Capitalization in hyphenated compound words
+
+Capitalize any part of a hyphenated compound word that would be capitalized if there were no hyphen.
+
+**Examples**
+
+| Compound word              | Example sentence                                                                                                              |
+| -------------------------- |-------------------------------------------------------------------------------------------------------------------------------|
+| Customer-friendly          | Customer-friendly content is brief, accurate, and to the point.                                                               |
+| E-Book                     | Bisson, Guillermo. *The App E-Book*. Redmond, WA: Lucerne Publishing, 2015.                                                   |
+| Add-ins                    | Bisson, Guillermo. *Programming Office 365 Applications, SharePoint Add-ins, and More*. Redmond, WA: Lucerne Publishing, 2015.|
+
+**See also** Capitalization
+
+## Exclamation points
+
+Use exclamation points sparingly. Save them for when they count.
+
+## Periods
+
+Don't use periods in headlines, headings, subheadings, UI titles, UI text, or simple lists (three or fewer words per item).
+
+End all sentences with a period, even if they're only two words. Put one space, not two, after a period.
+
+For information about how to use periods in bulleted lists and numbered lists, see Lists.
+
+**Headline example** Be brief—make every word count
+
+**Text example** Be brief. Make every word count.
+
+When a phrase that ends with a colon introduces a bulleted list:
+
+- If one or more list elements complete the introductory phrase that precedes the colon, use a period after every list element.
+  
+- If all list elements are short phrases (three words or fewer), don't end them with periods, even if they form a complete sentence together with the list introduction.
+
+- If one or more list elements are complete sentences, use a period after every element, even if a list element contains three or fewer words.
+
+## Question marks
+
+Use questions sparingly. In general, customers want *us* to give *them* answers.
+
+When a customer needs to make a decision, a question is appropriate.<br /> **Examples** If you forgot your password, provide your secret answer. More nature themes are available online. Do you want to save your changes?
+
+## Quotation marks
+
+Use single quotation marks (' ') to indicate quoted material within a quotation. Double and single straight quotation marks can also be used to indicate feet and inches, respectively.
+
+Place closing quotation marks:
+
+  - Outside commas and periods.
+  - Inside other punctuation.
+    
+**Exception** If punctuation is part of the quoted material, place it inside the quotation marks.
+
+**Examples** One type of malware is called a "trojan clicker." He explained: "One type of malware, called a 'trojan clicker,' uses your PC to 'click' online ads.' Use an 8.5" x 11" sheet of paper.
+
+**Quotation marks in Segoe** Use straight quotation marks (" "). Segoe Sans, the Microsoft font family, does not have a curly quotation mark option.
+
+**Preferred terms**
+
+Refer to *quotation marks, opening quotation marks,* and *closing quotation marks.* Don't call them *quote marks, quotes, open* or *close quotation marks,* or *beginning* or *ending quotation marks.*
+
+## Semicolons
+
+Sentences that contain semicolons are often complex. Try to simplify the sentence—break it into multiple sentences or a list—to eliminate the semicolon.
+
+Use semicolons:
+
+  - Between two independent clauses that aren't joined by a conjunction.  
+**Example** <br />Select **Options**; then select **Automatic backups**.
+
+  - Between contrasting statements that aren't joined by a conjunction.  
+**Example** <br />What’s considered powerful changes over time; today’s advanced feature might be commonplace tomorrow.
+
+  - To separate items in a series that contains commas or other punctuation. Even better, break out 
+a complex series of items into a list. **Examples** <br />In this tutorial, you’ll learn how to construct an interface; implement both single-document interface and multiple-document interface applications; implement features that until now were considered difficult, such as printing, toolbars, scrolling, splitter windows, print preview, and context-sensitive Help; and take advantage of many built-in components of the class library.
+
+In this tutorial, you'll learn how to:
+    *  Construct an interface.
+    *  Implement both single-document interface and multiple-document interface applications.
+    *  Implement features that until now were considered difficult, such as printing, toolbars, scrolling, splitter windows, print preview, and context-sensitive Help.
+    *  Take advantage of many built-in components of the class library.
+
+## Slashes
+
+When necessary, differentiate between a *slash* for URLs and a *backslash* for servers and folders.
+
+When you instruct customers to enter a slash, always include the spelled-out term (*backslash* or *slash*) first, followed by the symbol in parentheses.<br />**Example** <br />Enter two backslashes (\\\\) ....
+
+**See also**<br />Numbers<br />Special character term collection<br />URLs and web addresses
+
+Use a slash:
+
+  - To imply a combination. Capitalize the word after the slash if the word before the slash is capitalized. For example, if *country/region* is used as a label in a form, capitalize it as *Country/Region.*<br />**Examples**<br />client/server<br />TCP/IP<br />CD/DVD drive<br />Use the on/off switch to turn your mouse off when you're not using it.<br />Turn on the On/Off toggle.
+
+  - To separate parts of an internet address. Use two slashes after the protocol name. <br />**Example** <br />ftp://example.com/downloads
+
+  - In server, folder, and file names.<br />**Example** <br />\\\\mslibrary\\catalog\\collect.doc
+
+  - Between the numerator and denominator of fractions in equations that occur in text.<br />**Examples**<br />a/x + b/y = 1<br />x + 2/3(y) = m
+
+Don't use a slash as a substitute for *or,* like *product/service.* If the UI uses a slash in this way, follow the interface in describing the label, but use *or* to describe the action in text. **Examples**<br />Select **Automatic trapping** to add or remove a check mark.<br />To turn the purchasing workflow on or off ....
+
+**Exception** It's OK to use *country/region* and *ZIP Code/postal code* where space is limited.
+
+**See also**<br />and/or<br />country or region<br />either/or
diff --git a/.claude/skills/microsoft-writing-style-guide/references/scannable-content-and-procedures.md b/.claude/skills/microsoft-writing-style-guide/references/scannable-content-and-procedures.md
new file mode 100755
index 000000000..3f9ca231d
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/scannable-content-and-procedures.md
@@ -0,0 +1,691 @@
+# Scannable content, and procedures and instructions
+
+## Scannable content
+
+The volume of content available to customers is overwhelming. Part of a writer's job is to help readers find what they need quickly, or recognize just as quickly when they're not where they need to be. Writing to facilitate scanning will help.
+
+Organize text into discrete components to support scanning. This section describes some of the methods you can use:
+
+  - Headings
+  - Lists
+  - Pull quotes
+  - Sidebars
+  - Tables
+
+How you write is equally important to scanning.
+
+## Put first things first
+
+Content on the first screen (also called *above the fold*) is the most likely to be read. Many readers won’t scroll further without a compelling reason. So as always, keep it short, and lead with what’s most important to the customer. Keep in mind that what appears above the fold varies by device and screen resolution.
+
+Numerous studies have shown that readers look at specific areas of a page first. In left-to-right languages, people read in an F shape, giving the most attention to the upper-left corner of a page. Put your most important information there. Or try placing an offer or a Buy or Download button there. If the navigation is on the left, put your most important information in the upper-left corner of the text pane.
+
+## Be brief, be bold, be clear
+
+Long spans of dense text are daunting and unapproachable to readers. Write short headings, short sentences, and short paragraphs that are easy to read—and more visually appealing.
+
+1.  Use short, simple words. 
+2.  Get to the point.
+3.  Then stop.
+
+## Include navigation within long documents
+
+In general, keep web content short. When you have a great, customer-focused reason to create longer content, provide readers with at least one way to navigate within it, so they can quickly get to what they need.
+
+  - If
+you're developing content for a collection, break the content up into sections so that information is easy to find in the library navigation.
+    
+  - In
+a longer document that's likely to be read online, even if it’s a downloadable Word document or PDF file, include a table of contents with links to subheadings.
+    
+  - Add *Back to top* links at the end of sections.
+
+## Establish patterns in content
+
+Consistent writing, design, and formatting create patterns, which help readers comprehend more efficiently. Apply these tactics throughout your content to create familiar landmarks for your readers:
+
+  - Lead
+with what's most important. Place important keywords near the beginning of headings, table entries, and paragraphs so they're easy to spot.
+    
+  - Use text formatting consistently, such as using bold in procedures to identify UI labels. To learn more, see Text formatting.  
+  
+  - Apply
+the same sentence structures to similar information. For example, use prepositional phrases consistently in procedures to help customers navigate menus and dialog boxes. And use the same syntax for cross-references and other common content elements.
+
+**Writing tip** When comparing things, use parallel sentence structures to describe each thing. Write headlines and bulleted list items using the same sentence structure, too.
+
+## Give paragraphs room—and keep them short
+
+Paragraphs usually have extra space between them. How much extra space depends on the size of the font. The minimum is usually 50 percent of the line spacing, or at least half the font size.
+
+Short paragraphs, like this one, help to break up long passages of text. Three to seven lines is about the right length for a paragraph.
+
+It’s also fine to have a single-line paragraph now and then.
+
+## Headings
+
+Headings provide both structure and visual points of reference to help readers scan content. If
+you can break text logically into smaller sections, the extra
+spacing and distinct fonts associated with headings
+will help readers scan content and find entry points.
+
+In any type of content—whether it's UI, web content, marketing, or advertising—use headings consistently. 
+
+## Writing headings
+
+**Think of headings as an outline,** only more interesting—pithy, even. If readers don't read the headings, they probably won't read the text that follows, either. 
+
+  - Top-level
+    headings communicate what's most important and divide content into
+    major subjects. Make them as specific as you can to catch the
+    reader's attention.
+    
+  - When
+    there's a lot to say under a top-level heading, look for two or
+    more distinct topics, and use second-level headings (subheads) to
+    break up the large section into more scannable chunks. If you can't find
+    at least two distinct topics, skip the second-level headings.  
+    
+  - Avoid having two headings in a row without text in between—that might indicate a problem with 
+    organization or that the headings are redundant. But don't insert filler text just to separate the headings.
+    
+  - Each new heading represents a new or more specific topic. The heading should introduce the topic in an interesting way.
+
+**Use headings judiciously.** One heading level is usually plenty for a page or two of content. For long content, you might need to use additional heading levels. For example, this guide uses four heading levels.
+
+**Keep headings as short as possible,** and put the most important idea at the beginning. This is especially critical in blogs and social media.
+
+**Be as specific as you can,** and
+be even more detailed with lower-level headings. For example, a
+second-level heading should be more specific than a first-level
+heading.
+
+**Focus on what matters to customers,** and
+choose words they'd use themselves. In most cases, don't talk
+about products, features, or commands in headings. Concentrate
+on what customers can achieve or what they need to know.
+
+**Use parallel sentence structure** for all
+headings at the same level. For example, use noun phrases for
+first-level headings, verb phrases for second-level headings, and
+infinitive phrases for headings in instructions.<br />
+**Examples**  
+**Source data**  
+
+&nbsp;&nbsp;Prepare headings  
+
+&nbsp;&nbsp;&nbsp;&nbsp;*To create a heading*  
+
+&nbsp;&nbsp;Scrub data   
+
+&nbsp;&nbsp;&nbsp;&nbsp;*To remove blank rows*  
+
+**PivotTable reports**  
+
+**Report filters**
+
+**Consider infinitive phrases,** such as *To create a heading,* for headings and titles related to tasks. For headings that aren't related to tasks, use a noun phrase such as *Headings,* if possible. 
+
+**Don’t use ampersands (&) or plus signs (+)** in headings unless you're referring to UI that contains them or space is limited. 
+
+**Avoid hyphens** in headings if you can. In resized windows or mobile devices, they can result in awkward line breaks.
+
+**Use *vs.,* not *v*.** or *versus,* in headings.
+
+## Formatting headings
+
+**Use sentence-style capitalization** for headings. That means that you capitalize the first word, 
+any proper nouns, and the first word after a colon (if there is one). Everything else is lowercase. To learn
+more, see [Capitalization](/style-guide/capitalization).<br />
+**Examples**  
+Say hello to Surface Pro  
+Set up the deployment environment  
+Templates and themes for Office Online  
+My account  
+Find a store  
+Can a search engine predict the winner of a sports tournament?  
+Block party: Communities use Minecraft to create public spaces  
+
+**Don't end headings with a period.** A question mark or (rarely) an exclamation point can be used if it's needed for meaning.<br />
+**Examples**  
+Not seeing what you want?  
+What can we help you find?  
+
+**Use italic** if it would be required in body text.
+
+**Break two-line headings carefully.**
+Unless you're writing content for a responsive design (which
+breaks lines dynamically to fit the screen), break the heading in a way
+that makes sense and balances the length of the two lines. (Shift +
+Enter inserts a manual line break in many authoring tools.)
+
+  - Keep adjectives and prepositions with the words they modify.
+  
+  - Keep hyphenated words and multiple-word proper nouns (such as *New York*) on the same line.  
+  
+  - Break after punctuation.  
+  
+  - Break naturally, at the end of a complete phrase, if possible. 
+  
+  - If you can't fit a headline on two lines, rewrite it.
+
+**Use vertical spacing to make headings stand out.** Headings
+typically have extra space above them and often less space below
+them. Close proximity between the heading and the text that
+follows it communicates to the reader that they're related. Heading
+spacing is built into heading styles in most templates. Use those
+styles to control spacing in a consistent way. 
+
+**Don't use extra line breaks to increase heading spacing,** especially in web content. In responsive
+web design, the layout and screen elements (including headings) adjust
+to the screen size automatically, whether they're viewed on mobile
+devices, tablets, laptops, or desktops. Extra line breaks might detract
+from the content appearance on mobile devices. 
+
+**Learn more** [Using type](/style-guide/text-formatting/using-type/index)  
+
+## Using run-in headings
+
+If
+you regularly highlight specific types of content, such as
+benefits, feature highlights, tips, notes, warnings, or
+cross-references, consider using a special kind of heading
+for them. Although they don't add white space to a document, bold run-in headings,
+like the ones you see in this article, draw the reader's eye to
+interesting information. Because they're part of the paragraph,
+run-in headings have less impact than separate headings but
+require much less space—so they're ideal for packaging blurbs, web content, screen callouts, and the like. 
+
+When you use bold formatting for run-in headings:
+
+  - Make sure the first few words of the paragraph are interesting and introduce the paragraph contents. 
+  
+  - Consider repeating common phrases, such as *Tip, Note,* and *See also,* as
+    run-in headings to call attention to helpful information,
+    interesting but nonessential information, or
+    cross-references, respectively.  
+    
+  - Use
+    a character style, rather than manual formatting, to make your
+    headings consistent, easy to apply, and easy to maintain. You can
+    apply character
+    styles to any selected words in a document without changing the
+    paragraph style. In Microsoft Word, character styles, such as **Subtle Emphasis,** are designated by an *a*
+    next to the style name. To create a new character style in a
+    document, select the characters, and then add the style.
+    
+    ![Screenshot of the Style Name dropdown menu with the Subtle Emphasis option being highlighted.](/style-guide/scannable-content/media/headings/190123509.png)
+## Lists
+
+Lists are a great way to present complex text in a way that's easy to scan.
+
+A list should have at least two items but (if possible) no more than seven items. Each item should be fairly short—the reader should be able to see at least two, and preferably three, list items at a glance. It's OK to have a couple of short paragraphs in a list item, but don't exceed that length too often.
+
+Make all the items in a list consistent in structure. For example, each item should be a noun or a phrase that starts with a verb.
+
+## Bulleted lists
+
+Use a bulleted list for things that have something in common but don't need to appear in a particular order.
+
+**Examples**
+
+The database owner can:
+
+- Create and delete a database.
+- Add, delete, or modify a document.
+- Add, delete, or modify any information in the database. 
+
+Bring your customers into focus:
+
+- Own your customer relationship.
+- Create raving fans.
+- Engage in new ways.
+
+## Numbered lists
+
+Use a numbered list for sequential items (like a procedure) or prioritized items (like a top 10 list).
+
+**Example**
+
+To sign on to a database:
+
+1.  On the **File** menu, select **Open database**.
+2.  In **Username**, enter your name.
+3.  In **Password**, enter your password, and then select **OK**. 
+
+## Term lists
+
+If you must define, describe, or explain a set of terms or concepts, a common alternative to a table is a list where each item consists of a term followed by a definition.
+
+For the sake of consistency across documentation, use this format:
+
+- Use a bulleted list. Use numbering only if the sequence is important or you're referring to callouts in a figure.
+- For the term, use sentence case and bold. But if the term is link text, use only link formatting (not bold).
+- Use a period between the term and the definition. The period is in plain text.
+- Whether the definition is a fragment or a complete sentence, start it with a capital letter and end it with a period.
+
+The use of bold in term lists is an exception to the general guideline of using italic for emphasis.
+
+**Example**
+
+Documents have four possible statuses:
+
+- **Draft**. You created the document, but you're still working on it.
+- **In review**. You submitted the document for review and approval.
+- **Rejected**. The document was rejected during the review process.
+- **Approved**. The document was approved during the review process.
+
+## Introductory text
+
+Make sure the purpose of the list is clear. Introduce the list with a heading, a complete sentence, or a fragment that ends with a colon.
+
+If you introduce a list with a heading, don't use explanatory text after the heading. Also, don't use a colon or period after the heading.
+
+## Capitalization 
+
+Begin each item in a list with a capital letter unless there's a reason not to (for example, it's a command that's always lowercase). If necessary, rewrite the list so that all items begin with capital letters or all items begin with lowercase words.
+
+## Punctuation
+
+Don't use semicolons, commas, or conjunctions (like *and* or *or*) at the end of list items.
+
+Don't use a period at the end of list items unless they're complete sentences or they complete the introductory sentence.
+
+**Global tip**: If your content will be localized, avoid lists where the list items complete an introductory fragment. They can be difficult to translate.
+
+**Examples**
+
+The recall affects these devices:
+
+ - Original Surface Pro
+ - Surface Pro 2
+ - Surface Pro 3
+
+Limitations on meeting organizers:
+
+- Only invited presenters can be selected as breakout room managers.
+- The number of breakout room managers is limited to 10.
+- Breakout room managers can't be assigned to specific rooms, but they can move freely between rooms.
+
+Knowledge managers can:
+
+- Confirm or remove topics that were discovered in your tenant.
+- Create new topics manually as needed.
+- Edit existing topic pages.
+
+**Exception**: Don't use periods if all items have three or fewer words or if the items are UI labels, headings, subheadings, strings, or similar types of text.
+  
+The administrative templates for Microsoft Edge are:
+
+- msedge.admx
+- msedgeupdate.admx
+
+The topic answer displays:
+
+- The topic name
+- Alternate names
+- The definition
+
+## In UI
+
+Often, lists are a series of radio buttons or checkboxes inside dialog boxes or settings pages. Unless they're complete sentences, don't use punctuation for the list items. If punctuation is necessary for clarity, make sure punctuation is used consistently in the list and in other lists within the same section or screen.
+
+## Pull quotes
+
+
+Pull quotes are short sentences—usually a quote from someone important to the story, but sometimes just a short, interesting sentence—set off from body text to grab the reader’s attention. 
+
+![Screenshot of a pull quote reading If it's not fun, you're doing it wrong.](/style-guide/scannable-content/media/pull-quotes/pull-quote.png)
+
+Pull quotes
+should be short—from a few words to a few lines. If the quote is
+from a person or publication, include the author’s name, title, and
+organization with the pull quote.
+
+**Exception** If the content is entirely about the person being quoted, you don’t need to include the attribution.
+
+Use pull quotes sparingly.
+## Sidebars
+
+Sidebars are useful in longer articles or documents to call out interesting sections and break up long spans of text. The content you put in a sidebar should be fairly short, interesting, and related but not crucial to the article.
+
+Typically people read sidebars before or after the rest of the page, so don’t use sidebars for information that should be read in sequence with the main text.
+
+**Figure** An article sidebar provides statistics that accompany the written content.
+
+## Tables
+
+Tables make complex information easier to understand by presenting it in a clear structure. In a table, data is arranged into two or more rows (plus a header row) and two or more columns. Don't use a table just to present a list of items that are similar. Use a list instead.
+
+|        **Tables are sometimes useful for**         |                     **Example**                      |
+| ------------------------------------------------- | -------------------------------------------------------------- |
+| Data or values                                    | Text formats and their associated HTML codes                   |
+| Simple instructions                               | User interface actions and their associated keyboard shortcuts |
+| Categories of things with examples                | SKUs and the products they include                             |
+| Collections of things with two or more attributes | Event dates with times and locations                           |
+
+  
+## Content
+
+Make sure the purpose of the table is clear. If necessary, include a table title or brief introduction.
+
+Place information that identifies the contents of a row in the leftmost column of the table. For example, in a table that describes commands, put the command names in the left column.
+
+Make entries in a table parallel. For example, make all the items within a column a noun or a phrase that starts with a verb.
+
+**Example**
+
+| Function                | Description                                                                                                        |
+| ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| AddUsersToEncryptedFile | Adds user keys to the specified encrypted file                                                                     |
+| Cancello                | Cancels all pending input and output (I/O) operations that are issued by the calling thread for the specified file |
+| CancelloEx              | Marks any outstanding I/O operations for the specified file handle                                                 |
+| GetTempFileName         | Creates a name for a temporary file                                                                                |
+
+Don’t leave a cell blank or use an em dash to indicate there’s no entry for that cell. Instead, use *Not applicable* or *None.*
+
+Keep responsive design in mind. Limit the number of columns and keep the text in each cell brief—ideally one line. To learn more, see Responsive content.
+
+Balance row height by increasing the width of text-heavy columns and reducing the width of columns with minimal text.
+
+## Header rows
+
+If the first row of your table contains column headers, you have a header row. Distinguish the text in the header row from the rest of the text in the table. For example, make it larger, bolder, or a different color.
+
+Column headers identify the data each column contains. Make headers precise for usability. For example, don't use "Name". Instead, make column headers specific as in "Group" or "Employee". (While screen readers use header information to identify rows and columns, specificity helps all users find the information they're looking for.)
+
+Don’t organize a table so that the column header forms a complete sentence when combined with the cell contents. This can make the table difficult to localize.
+
+In long tables, make sure the header row is always visible. For example, on the web, use a fixed header row that stays in place during scrolling. Or, in a downloadable document, occasionally repeat the header row. Some authoring tools provide a way to do this automatically. In Microsoft Word, select the header row. On the **Layout** tab under **Table Tools**, select **Repeat Header Rows**.
+
+## Capitalization
+
+Use sentence-style capitalization for the table title and each column header. Use sentence-style capitalization for the text in cells unless there’s a reason not to (for example, keywords that must be lowercase).
+
+## Punctuation
+
+If there’s text that introduces the table, it should be a complete sentence and end with a period, not a colon.
+
+Don’t use ellipses at the end of column headers.
+
+For the text in cells, use periods or other end punctuation only if the cells contain complete sentences or a mixture of fragments and sentences.
+
+## Procedures and instructions
+
+The best procedure is the one you don’t need. If the UI is crystal
+clear and leads the customer through a task, a procedure
+isn’t necessary. Start there.
+
+Some tasks are more complex. When you need to provide a procedure, look for the clearest way to present it. That might be:
+
+  - A picture, an illustration, a poster, or an infographic  
+    ![A screenshot of two columns. The left, blue column reads In SharePoint Server 2013 on-premise. The right, red column reads in Office 365.](/style-guide/procedures-instructions/media/index/1980906142.png)  
+  - A video.
+
+    ![Screenshot of a paused video under a description of an article with a header reading Getting started with Internet Explorer 11.](/style-guide/procedures-instructions/media/index/774741777.png)
+
+  - A one-sentence instruction.
+
+    ![Screenshot of an article header reading Call a friend followed by a one-sentence instruction and various examples of the instruction.](/style-guide/procedures-instructions/media/index/1713306812.png)
+
+  - A numbered
+    procedure, which might include pictures, videos, and links or
+    buttons that take customers where they need to go.
+
+    ![Screenshot of an article with the Adding your files to OneDrive header followed by four numbered steps, each with an accompanying image.](/style-guide/procedures-instructions/media/index/541572162.png)
+
+When
+a procedure is the best approach, use the guidelines in this
+section to create consistent instructions that are easy to follow:
+
+  - [Writing step-by-step instructions](/style-guide/procedures-instructions/writing-step-by-step-instructions) describes several ways to write simple and complex instructions.  
+  
+  - [Describing interactions with UI](/style-guide/procedures-instructions/describing-interactions-with-ui) provides a list of input-neutral verbs you can use to write instructions that work with any input method.  
+  
+  - [Describing alternative input methods](/style-guide/procedures-instructions/describing-alternative-input-methods) explains how to describe customer interactions with UI using mouse, keyboard, joystick, pen, touch, and sensor input—and how to consolidate more than one method in instructions.  
+  
+  - [Formatting text in instructions](/style-guide/procedures-instructions/formatting-text-in-instructions) lists the formatting conventions for elements commonly used in instructions.
+
+**Note** Document all the ways that customers can interact with your UI to support customers of all abilities. This includes mouse,
+keyboard, voice recognition, game controller, gesture, and any
+other input method or device that the product or service supports. The
+easiest way to approach this is to fully document interactions using
+each input method, and then write procedures that
+use input-neutral verbs.
+## Writing step-by-step instructions
+
+These guidelines help you create clear, easy-to-follow instructions.
+
+**See also** Formatting text in instructions Formatting punctuation
+
+## Scannability
+
+- Consider using headings to help customers find instructions quickly. The headings should concisely describe what the instructions help customers do.
+
+- Use parallel structure in headings. That is, use a consistent phrasing style.
+
+**Example** Create a profile Add an account
+
+- If you use a sentence to introduce a procedure, make sure that the information is necessary. An introductory sentence shouldn't just repeat what the heading says.
+
+## Multiple-step procedures
+
+- Use a numbered list.
+
+- If there's a chance of confusion, provide an introductory step that tells customers where to perform the action (for example, application, tool, or location in the UI).
+
+- Use a separate step for each instruction. It's OK to combine short steps that occur in the same place in the UI.
+
+- Most of the time, include actions that complete a procedure, such as selecting an **OK** or **Apply** button.  
+  
+- Don't overwhelm customers with too many steps in a single procedure. Try to fit all the steps on the same screen.
+
+**Example** To create a group of tiles:
+
+1. On the **Start** screen, select the tiles that you want to group together.
+2. Drag the tiles to an open space. When a gray bar appears behind them, release them to create the new group.
+
+## Single-step procedures
+
+A single step might not require list formatting. If you want to use a format that's consistent with step-by-step instructions in the same documentation, use a bullet instead of a number.
+
+**Example** To move a group of tiles:
+
+- On the **Start** screen, zoom out and drag the group to where you want it.
+
+## Tips for writing steps
+
+- Use a complete sentence. Capitalize the first word and use a period at the end.  
+
+- If you need to make sure that customers begin in the right place, provide a brief phrase at the beginning of the step. The rest of the time, start each sentence with an imperative verb.
+
+**Examples** On the ribbon, go to the **Design** tab. Open Photos.
+
+- Make sure that customers know where the action should take place before you describe the action.
+
+**Examples** For **Alignment**, select **Left**. On the **Design** tab, select **Header Row**.
+
+- Consider abbreviating simple sequences by using right angle brackets. Include a space before and after each bracket, and don't make the brackets bold.
+
+**Example** Select **Accounts** \> **Other accounts** \> **Add an account**.
+
+**Accessibility tip** Screen readers might skip over brackets and read instructions such as **Menu** \> **Go To** \> **Folders** as *Menu Go To Folders,* which might confuse customers. Check with an accessibility expert before you use this approach.
+
+## Describing interactions with the UI
+
+Customers interact with products by using various input methods: keyboard, mouse, touch, voice, and more. So use generic verbs that work with any input method. Don't use input-specific verbs, such as *click* or *swipe*. Instead, use the verbs listed here.
+
+**See also** Formatting text in instructions
+
+|            **Verb**             |                                                                                                                                                                                                                                                                                     **Use for**                                                                                                                                                                                                                                                                                     |                                                                                                                                                                                                                                                                                                            **Examples**                                                                                                                                                                                                                                                                                                             |
+|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|            **Open**             |                                                                                                                      <ul><li>Apps and programs.</li></ul> <ul><li>Panes.</li></ul> <ul><li>File Explorer.</li></ul> <ul><li>Files and folders.</li></ul> <ul><li>Shortcut menus.</li></ul> <ul><li>Websites and webpages, when necessary to match the UI. Otherwise, use <em>go to</em>.</li></ul> <br>Don't use for commands and menus.                                                                                                                      |                                                                                                                                  <ul><li>Open Photos.</li></ul> <ul><li>Open the Reader app.</li></ul> <ul><li>Select <strong>Users + groups</strong> to open the pane.</li></ul> <ul><li>Open the <em>Filename</em> file.</li></ul> <ul><li>To open the document in Outline view, select <strong>View</strong> > <strong>Outline</strong>.</li></ul> <ul><li>In <em>WindowName</em>, open the shortcut menu for <em>ItemName</em>.</li></ul>                                                                                                                                  |
+|            **Close**            |                                                                                                                <ul><li>Apps and programs.</li></ul> <ul><li>Panes.</li></ul> <ul><li>Dialogs.</li></ul> <ul><li>Files and folders.</li></ul> <ul><li>Notifications and alerts.</li></ul> <ul><li>Tabs.</li></ul> <ul><li>The action that a program or app takes when it encounters a problem and can't continue. (Don't confuse with <em>stop responding</em>.)</li></ul>                                                                                                                |                                                                                                                                                                    <ul><li>Close the Alarms app.</li></ul> <ul><li>Close Excel.</li></ul> <ul><li>Close the pane.</li></ul> <ul><li>Close the <strong>Users + groups</strong> pane.</li></ul> <ul><li>Save and close the document.</li></ul> <ul><li>Closing Excel also closes all open worksheets.</li></ul>                                                                                                                                                                     |
+|            **Leave**            |                                                                                                                                                                                                                                                                                Websites and webpages.                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                    Select **Submit** to complete the survey and leave this page.                                                                                                                                                                                                                                                                                    |
+|            **Go to**            |                                                                                                                                    <ul><li>Opening a menu.</li></ul> <ul><li>Going to a tab or another particular place in the UI.</li></ul> <ul><li>Going to a website or webpage.</li></ul> <br>It's OK to use <em>On the</em> <strong><em>XXX</em></strong> <em>tab</em> if the instruction is brief and continues immediately.                                                                                                                                    | <ul><li>Go to Search :::image type="icon" source="media/describing-interactions-with-ui/721771267.png":::, enter the word <strong>settings</strong>, and then select <strong>Settings</strong>. </li></ul> <ul><li>Go to <strong>File</strong>, and then select <strong>Close</strong>.</li></ul> <ul><li>On the ribbon, go to the <strong>Design</strong> tab. </li></ul> <ul><li>Go to the <strong>Deploy</strong> tab. In the <strong>Configuration</strong> list … </li></ul> <ul><li>On the <strong>Deploy</strong> tab, in the <strong>Configuration</strong> list … </li></ul> <ul><li>Go to Example.com to register.</li></ul> |
+|           **Select**            | Instructing the customer to select a specific item, including:<br /><ul><li>Selecting an option, such as a button.</li></ul> <ul><li>Selecting a checkbox.</li></ul> <ul><li>Selecting a value from a list box.</li></ul> <ul><li>Selecting link text to go to a link.</li></ul> <ul><li>Selecting an item on a menu or shortcut menu.</li></ul> <ul><li>Selecting an item from a gallery.</li></ul> <ul><li>Selecting keys and keyboard shortcuts. (Document keyboard shortcuts only if they're the most likely way the customer will accomplish a task or as an alternative input method, usually in a separate keyboard shortcuts article.)</li></ul> |                                                                        <ul><li>Select the <strong>Modify</strong> button.</li></ul> <ul><li>For <strong>Alignment</strong>, select <strong>Left</strong>. </li></ul> <ul><li>Select the text, open the shortcut menu, and then select <strong>Font</strong>.</li></ul> <ul><li>Select <strong>Open in new tab</strong>.</li></ul> <ul><li>Select the <strong>LinkName</strong> link.</li></ul> <ul><li>Select **F5**.</li></ul> <ul><li>Select **Shift+Enter**.</li></ul> <ul><li>Select **Ctrl+Alt+Delete**.</li></ul>                                                                         |
+|       **Select and hold, select and hold (or right-click)**       |                                                                                                                                                                                                   Pressing and holding an element in the UI. It's OK to use *right-click* with *select and hold* when the instruction isn't specific to touch devices.                                                                           |                                                                                                                                                                                                                                                                <ul><li>To flag a message that you want to deal with later, select and hold it, and then select **Set flag**.</li></ul> <ul><li>Select and hold (or right-click) the Windows taskbar, and then select **Cascade windows**.</li></ul> <ul><li>Select and hold (or right-click) the **Start** :::image type="icon" source="media/describing-interactions-with-ui/967781121.png"::: button, and then select **Device Manager**.</li></ul>                                                                                                                             |
+|              **>**              |                                                                                                   Separating sequential steps.<br /><br />Use this approach only when there's a clear and obvious path through the UI and the selection method is the same for each step. For example, don't mix things that require opening, selecting, and choosing.<br /><br />Don't use bold on the greater-than symbol. Include a space before and after the symbol.                                                                                                   |                                                                                                                                                                                                                                                                                       Select **Accounts** > **Other accounts** > **Add an account**.                                                                                                                                                                                                                                                                                        |
+|            **Clear**            |                                                                                                                                                                                                                                                                      Clearing the selection from a checkbox.                                                                                                                                                                                                                                                                       |                                                                                                                                                                                                                                                                                                 Clear the **Header row** checkbox.                                                                                                                                                                                                                                                                                                 |
+|           **Choose**            |                                                                                                                                                                                                                                                     Choosing an option, based on the customer's preference or desired outcome.<br /><br />Selecting something that begins with the word **Select**, to avoid a repeated word.                                                                                                                                                                                                                                                      |                                                                                                                                                                                                                                                                                          <ul><li>On the **Font** tab, choose the effects that you want. </ul></li>  <ul><li> Choose **Select users**.</ul></li>                                                                                                                                                                                                                                                                                       |
+|           **Switch, turn on, turn off**            |                                                                                                                                                                                                                                                     Turning a toggle key or toggle switch on or off.                                                                                                                                                                                                                                                      |                                                                                                                                                                                                                                                                                          <ul><li>Use the **Caps lock** key to switch from typing capital letters to typing lowercase letters.  </li></ul> <ul><li>To switch between Normal, Outline, and Slide Sorter views, use the buttons on the <strong>View</strong> tab.  </li></ul> <ul><li>To make text and apps easier to see, turn on the toggle under <strong>Turn on high contrast</strong>. </li></ul> <ul><li>To keep all applied filters, turn on the <strong>Pass all filters</strong> toggle.</li></ul>                                                                                                                                                                                                                                                                   |
+|            **Enter**            |                                                                                                                                                                                                                                                            Instructing the customer to type or otherwise insert a value, or to type or select a value in a combo box.                                                                                                                                                                                                                                                            |                                                                                                                                                                                                                                                                                                      <ul><li>In the search box, enter…</li></ul> <ul><li>In the **Tab stop position** box, enter the location where you want to set the new tab.</li></ul> <ul><li>In the **Deployment script name** box, enter a name for this script.</li></ul>                                                                                                                                                                                                                                                                                  |
+|         **Move, drag**          |                                                                                                                   Moving anything from one place to another by dragging, cutting and pasting, or another method. Use for tiles and any open window (including apps, dialogs, files, and panes).<br /><br />Use *move through* to describe moving around on a page, moving through screens or pages in an app, or moving up, down, right, and left in a UI.                                                                                                                    |                                                                                                                                           <ul><li>Drag the <em>Filename</em> file to the <em>Foldername</em> folder. </li></ul> <ul><li>Move the tile to the new section.  </li></ul> <ul><li>Drag the Snipping Tool out of the way, if necessary, and then select the area that you want to capture.  </li></ul> <ul><li>If the <strong>Apply Styles</strong> task pane is in your way, just move it.</li></ul>                                                                                                                                           |
+|   **Zoom, zoom in, zoom out**   |                                                                                                                                                                                                                                        Changing the magnification of the screen or window.                                                                                                                                                                                                                                        |                                                                                                                                                                                                                    <ul><li>Zoom in to see more details on the map.</li></ul> <ul><li>Zoom out to see a larger geographic area on the map.</li></ul> <ul><li>Zoom in or out to see more or less detail.</li></ul>                                                                                                                                                                                                                    |
+
+## Describing alternative input methods
+
+If you use input-neutral methods in instructions, provide an article
+that explains how to interact with the product using each available
+input method. (The article can be in the product or included in
+documentation or Help.) To support customers regardless of their
+ability or the device they use, include mice, keyboards, voice
+recognition devices, game controllers, touch, and other interaction
+methods.
+
+**Learn more** To learn more about creating accessible content, see [Accessibility guidelines and requirements](/style-guide/accessibility/accessibility-guidelines-requirements).
+
+## Mouse procedures
+
+Be consistent in how you list mouse procedures. For example,
+always list the mouse method before the keyboard method if
+you document both. Don't combine keyboard and
+mouse actions as if they were keyboard shortcuts unless space is
+limited. For example, don't use *Shift+click.* Instead, use *Select Shift while clicking ….*
+
+**See also** [Mouse and mouse interaction term collection](/style-guide/a-z-word-list-term-collections/term-collections/mouse-mouse-interaction-terms)
+
+## Joystick procedures
+
+Assume that the mouse is the primary input device. Include joystick
+information in a table along with other alternative input devices. 
+
+Refer to joystick *controls,* not *options,* when you provide specific joystick procedures.
+
+## Keyboard procedures
+
+Always document keyboard procedures for accessibility, even if they're indicated in UI (for example, by underlined letters).
+
+**See also** [Keys and keyboard shortcuts term collection](/style-guide/a-z-word-list-term-collections/term-collections/keys-keyboard-shortcuts) 
+
+## Pen-computing and touch procedures
+
+Use *tap* and *double-tap* instead of *click* and *double-click* when writing content specific to touching a screen or using a tablet pen. *Tap* means to press the screen with a finger or pen tip and then to lift it, usually quickly.
+
+| **Term** | **Usage** |
+|---|---|
+| **tap** | Use to describe selecting a button, icon, or other element on the screen with a finger or the pen by tapping it once. Don't use <em>tap on.</em> |
+| **double-tap** | Use to describe selecting an item by tapping twice in rapid succession. Hyphenate. Don't use <em>double-tap on.</em> |
+| **tap and hold** | Use only if the app requires it to complete a specific interaction. Don't use <em>touch and hold</em>. |
+| **pan** | Use to describe moving the screen in multiple directions at a controlled rate, as you would <em>pan</em> a camera to see different views. For contact gestures, use <em>pan</em> to refer to moving a finger, hand, or pen on the device surface to move through screens or menus at a controlled rate, rather than quickly skipping through content using the flick gesture. Don't use <em>drag</em> or <em>scroll</em> as a synonym for <em>pan</em>. |
+| **flick** | Use to describe moving one or more fingers to scroll through items on the screen. Don't use <em>scroll</em>. |
+| **swipe** | Use to describe a short, quick movement in the direction opposite to how the page scrolls. For example, if the page scrolls left or right, swipe an item up or down to select it.  |
+
+**See also** [Touch and pen interaction term collection](/style-guide/a-z-word-list-term-collections/term-collections/touch-pen-interaction-terms)
+
+## Multiple input methods and branching within procedures
+
+You can document multiple input methods in various
+ways, depending on the content design, space restrictions, and
+other considerations. Some approaches are discussed below. 
+
+**List the steps in a table,** and provide a separate column for each input method.<br />
+**Example**  
+**Choose colors to use on webpages**  
+To make webpages easier to see, you can change the text, background, link, and hover colors in Internet Explorer.
+
+| **Mouse actions** | **Keyboard actions** |
+|---|---|
+|On the **Start** menu: <br /><ul><li> Click **Internet Explorer**.</li></ul> | Display the **Start** menu by pressing the Windows logo key: <br /><ul><li>Select **Internet Explorer** by using the arrow keys, then press **Enter**.</li> |
+|In Internet Explorer:<br />1. Click the **Tools** menu. <br />2. Click **Internet Options**.</li></ul> | In Internet Explorer:<br /> 1. Select the **Tools** menu by pressing **Alt+T**. <br />2. Select **Internet Options** by pressing **O**.</li></ul> |
+
+**Document the primary input method,** and provide the alternative instructions in parentheses or separate sentences after the main instructions. <br />
+**Examples**  
+To pan, slide one finger in any direction (or drag the mouse pointer, or use the arrow keys).  
+To copy the selection, click **Copy** on the toolbar. You can also press **Ctrl+C**.  
+
+**If there are multiple ways to perform an entire procedure and you must describe each one,** use a table to detail the alternatives. This approach helps the customer decide when to use which method.<br />
+**Example**  
+This table describes two ways to save a file.
+
+| **To** | **Do this** |
+|---|---|
+| Save changes to the file and continue working. | On the **File** menu, click **Save**. |
+| Save changes to the file and close the program. | On the **File** menu, click **Exit**. If a dialog asks whether you want to save changes, click **Yes**. |
+
+**If one step has an alternative,** make
+that alternative a separate paragraph in the step. In a
+single-step procedure, an alternative can be separated by the word *or* to make it clear that an alternative is available.<br />
+**Examples**    
+Press the key for the underlined letter in the menu name. You can also use the **Left arrow** key or the **Right arrow** key to move to another menu.
+
+  - Press **Alt**+the key for the underlined letter in the menu name. 
+
+or 
+
+  - Use the **Left arrow** key or the **Right arrow** key to move to another menu. 
+
+**For several choices within one procedure step,** use a bulleted list.<br />
+**Example**    
+1\. Select the text that you want to move or copy.
+ Do one of the following:
+
+  - To remove the selection, click **Cut** on the Quick Access Toolbar.
+  - To copy the selection, click **Copy** on the Quick Access Toolbar. 
+
+2\. Right-click where you want to insert the text, then click **Paste** on the Quick Access Toolbar.
+## Formatting text in instructions
+
+Consistent text formatting helps readers locate and interpret information. Follow these conventions for formatting elements that frequently appear in instructions (also called procedures).
+
+**See also** Describing interactions with UI Capitalization Formatting common text elements Formatting developer text elements
+
+## In documentation and technical content
+
+Use these conventions in instructions that appear in documentation and technical content.
+
+|                        **Element**                         |                                                                                                                                                                                                                                          **Convention**                                                                                                                                                                                                                                           |                                                                                                                              **Example**                                                                                                                               |
+|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|        **Buttons, checkboxes, and other options**         | Avoid talking about UI elements. Instead, describe what the customer needs to do. <br /> When you must refer to a button, checkbox, or other option, use bold formatting for the name. <br /> Use sentence-style capitalization unless you need to match the UI. If an option label ends with a colon or an ellipsis, don't include that end punctuation in instructions. <br /> Don't include the type of UI element, such as *button* or *checkbox,* unless including it adds needed clarity. |                                             Select **Save as** (*not* Select **Save as…** or Select the **Save as** button). <br /> Select **Allow row to break across pages**. <br /> Clear the **Match case** checkbox.                                             |
+|                 **Command-line commands**                  |                                                                                                                                                                                                                                       Code style.                                                                                                                                                                                                                                        |                                                                                                                                `copy`                                                                                                                                |
+| **Command-line options (also known as switches or flags)** |                                                                                                                                                                                                                        Code style. Capitalize the way the option must be typed.                                                                                                                                                                                                                         |                                                                                                                          `/a`<br />`/Aw`                                                                                                                           |
+|                        **Commands**                        |                                                                                                   Use bold formatting for command names.<br />Use sentence-style capitalization unless you need to match the UI. If a command label ends with a colon or an ellipsis, don't include that end punctuation in instructions.<br />Don't include the word *command* unless it adds needed clarity.                                                                                                    |                                                                   Go to **Tools**, and select **Change language**.<br /> On the **Design** menu, select **Colors**, and then select a color scheme.                                                                    |
+|                     **Database names**                    |                                                                                                                                                                                                                        Bold. Code style if using in code syntax. The capitalization of database names varies.                                                                                                                                                                                                                         |                                                                                                                        **WingtipToys** database<br /> Enter the command `USE WingtipToys;`                                                                                                                        |
+|                 **Device and port names**                  |                                                                                                                                                                                                                                          All uppercase.                                                                                                                                                                                                                                           |                                                                                                                                  USB                                                                                                                                   |
+|                      **Dialog boxes**                      |                     In general, avoid talking about UI. Instead, talk about what the customer needs to do. <br />When you need to refer to the UI element, use *dialog*. Don't use *pop-up window*, *dialog box*, or *dialogue box*.<br />When you must refer to a dialog by name, use bold formatting for its name. <br /> Use sentence-style capitalization unless you need to match the UI. If a dialog label ends with a colon or an ellipsis, don't include that end punctuation in instructions. <br />                      |            Select **Upload**, and then select a file to upload.<br /> In **Properties**, select **Details**, and then select **Remove Properties and Personal Information**.<br /> In the **Protect document** dialog, clear the **Shapes** checkbox.             |
+|                     **Error messages**                     |                                                                                                                                                                                             Sentence-style capitalization. Enclose error messages in quotation marks when you're referring to them in text.                                                                                                                                                                                              |                       Looks like that's a broken link.<br /> If you see the error message "Check scanner status and try again," use Windows Update to check for the latest drivers for your device.<br />                       |
+|                    **File attributes**                     |                                                                                                                                                                                                                                          All lowercase.                                                                                                                                                                                                                                           |                                                                                                     To remove the hidden attribute from all files in a folder ....                                                                                                     |
+|                  **File name extensions**                  |                                                                                                                                                                                                                                          All lowercase.                                                                                                                                                                                                                                           |                                                                                                                            .mdb <br /> .doc                                                                                                                            |
+|           **File names (user-defined examples)**           |                                                                                                                            Title-style capitalization. It's OK to use internal capital letters in file names for readability. Use bold formatting for file names in procedures if you're directing the customer to select, type, or otherwise interact with the name. Apply code style if using in code syntax.                                                                                                                  |                                                                                                My Taxes for 2025 <br /> Enter **MyTaxesFor2025**. <br /> `copy MyTaxesFor2025.txt`                                                                                                |
+|   **Folder and directory names (user-defined examples)**   |                                                                                                                     Sentence-style capitalization. It's OK to use internal capital letters in folder and directory names for readability. In procedures, use bold formatting for names if you're directing the customer to select, type, or otherwise interact with the name. Apply code style if using in code syntax.                                                                                                                    |                                                                                     Vacation and Sick Pay <br /> MyFiles\Accounting\Payroll\VacPay<br /> Select **Documents** <br /> `cd MyFiles\Projects`                                                                                      |
+|         **Key names, combinations, and sequences**         |                                                                                                                                        Capitalize. Use bold formatting for key names and keyboard shortcuts in instructions. Don't put a space around the plus sign (+) in keyboard shortcuts. <br />To learn how to refer to keyboard shortcuts and specific keys, see Keys and keyboard shortcuts term collection.                                                                                                                                        |                                                                                            Shift, F7 <br /> Ctrl+Alt+Del <br /> Alt, F, O <br /> Spacebar <br /> Select the **F1** key. <br /> To open the **Preview** tab, select **Alt+3**.                                                                                             |
+|                         **Macros**                         |                                                                                                                                                                                          Usually all uppercase. Use bold formatting if predefined. Might be code style if user-defined or in code-related content. Treatment varies.                                                                                                                                                                                          |                                                                                                                      **LOWORD** <br /> `MASKROP`                                                                                                                       |
+|            **Markup language elements (tags)**             |                                                                                                                                                                                                                                   Code style. Capitalization varies.                                                                                                                                                                                                                                    |                                                                                          `<img>` <br /> `<input type="text">`                                                                                            |
+|          **Mathematical constants and variables**          |                                                                                                                                                                                                                                              Italic.                                                                                                                                                                                                                                              |                                                                                                                             *a2 + b2 = c2*                                                                                                                             |
+|                         **Menus**                          |                                                                                       Avoid talking about menus. Instead, describe what the customer needs to do. <br /> When you must refer to a menu by name, use bold formatting for the name of the menu. <br /> Use sentence-style capitalization unless you need to match the UI. <br /> Don't include the word *menu* unless it adds needed clarity.                                                                                       |                                                                   Go to **Tools**, and select **Change language**. <br /> On the **Design** menu, select **Colors**, and then select a color scheme.                                                                   |
+|                       **New terms**                        |                                                                                                                                                                                                    Italicize the first mention of a new term if you're going to define it immediately in text.                                                                                                                                                                                                    |                                                                                                 Microsoft Exchange consists of both *server* and *client* components.                                                                                                  |
+|                         **Palettes**                          |                                                                                       Avoid talking about palettes. Instead, describe what the customer needs to do. <br /> When you must refer to a palette by name, use bold formatting for the name of the palette. <br /> Use sentence-style capitalization unless you need to match the UI. <br /> Don't include the word *palette* unless it adds needed clarity.                                                                                       |                                                            In **Colors**, let Windows pull an accent color from your background, or choose your own color. <br /> In the **Color** palette, select a color for the object outline.                                                                   |
+|                         **Panes**                          |                                                                                       Avoid talking about panes. Instead, describe what the customer needs to do. <br /> When you must refer to a pane by name, use bold formatting for the name of the pane. <br /> Use sentence-style capitalization unless you need to match the UI. <br /> Don't include the word *pane* unless it adds needed clarity.                                                                                       |                                             Select the arrow next to the **Styles** gallery, select **Apply styles**, and then select a style to modify. <br /> If the **Apply Styles** pane is in your way, just move it.                                             |
+|       **Placeholders (in syntax and in user input)**       |                                                                                                                                                                                                                                              Italic when the placeholder element is UI text. Use angle brackets for code placeholders when angle brackets aren't part of the language syntax.                                                                                                                                                                                                                                             |                                                                                                                Enter *password*. <br />`/v: <version>`                                                                                                                 |
+|        **Products, services, apps, and trademarks**        |                                                                                                                                                Usually title-style capitalization. Check the Microsoft trademark list for capitalization of trademarked names.                                                                                                                                                |                                                             Microsoft Arc Touch Mouse <br /> Microsoft Word <br /> Surface Pro <br /> Notepad <br /> Network Connections <br /> Makefile <br /> RC program                                                             |
+|                        **Slashes**                         |                                                                                                                                                                        When you're instructing customers to enter a slash, include the spelled-out term (*backslash* or *slash*), followed by the symbol in parentheses.                                                                                                                                                                         |                                                                                                                   Enter two backslashes (\\\\) ....                                                                                                                    |
+|                        **Strings**                         |                                                                                                                                                  When you're referring to strings in code, a document, a website, or UI, use sentence-style capitalization unless the text you're referring to is capitalized differently. Enclose in quotation marks, or use code style when you're referring to a code string.                                                                                                                                                    |                                                                                      Select "Now is the time." <br /> Find `font-family:Segoe UI Semibold` in the code.                                                                                      |
+|                          **Tabs**                          |                                                                                         Avoid talking about tabs. Instead, describe what the customer needs to do. <br /> When you must refer to a tab by name, use bold formatting for the name of the tab. <br /> Use sentence-style capitalization unless you need to match the UI. <br /> Don't include the word *tab* unless it adds needed clarity.                                                                                         |                                       Select the table, and then select **Design** &gt; **Header row**. <br /> On the **Design** tab, select **Header row**. <br /> Go to the **Deploy** tab. In the **Configuration** list, ….                         |
+|                          **Toggles**                          |                                                                                         Avoid talking about toggles. Instead, describe what the customer needs to do. <br /> When you must refer to a toggle by name, use bold formatting for the name of the toggle. <br /> Use sentence-style capitalization unless you need to match the UI. <br /> Include the word *toggle* if it adds needed clarity.                                                                                         |                                       To make text and apps easier to see, turn on the toggle under **Turn on high contrast**. <br /> To keep all applied filters, turn on the **Pass all filters** toggle.                                        |
+|                          **URLs**                          |                                                                                                                                                              All lowercase for complete URLs. If necessary, line-break long URLs before a slash. Don't hyphenate. <br /> See also URLs and web addresses.                                                                                                                                                              |                                                                                                   www<span></span>.microsoft.com <br /> www<span></span>.microsoft.com/download                                                                                                          |
+|                       **User input**                       |                                                                                                                                                                 Usually lowercase, unless case sensitive. Bold or italic, depending on the element. If the user input string contains placeholder text, use italic for that text.                                                                                                                                                                 |                                                                                                          Enter **hello world** <br /> Enter *password*                                                                                                          |
+|                        **Windows**                         |                                             Avoid talking about windows. Instead, focus on what the customer needs to do.<br /> When you must refer to a window by name, use bold formatting for the name of the window. Use sentence-style capitalization unless you need to match the UI.<br /> Use *window* only as a generic term for an area on a PC screen where apps and content appear. Don't use *window* to refer to a specific dialog box, pane, or similar UI element.                                             |                                     To embed the new object, switch to the source document. <br /> Easily switch between open windows. <br /> Open a new Microsoft Edge tab in a new window so you can look at tabs side by side.                                      |
+|                  **XML schema elements**                   |                                                                                                                                                                                                                                   Code style. Often surrounded by angle brackets. Capitalization varies.                                                                                                                                                                                                                                    |                                                                                                         `ElementType` element <br /> `<xml:space>`                                                                                                         |
+
+## In the UI and general content
+
+Instructions can also appear in the UI itself and in content other than documentation, such as blogs and marketing. In this content, avoid bold and italic formatting. The goal is to be readable and friendly but also clearly set off the UI label or other text element from the surrounding text.
+
+Choose one of the following approaches and use it consistently.
+
+| **Option** | **Example** |
+|---|---|
+| Describe the action without referring to a specific UI label. | Choose the group or groups that you want to assign services to. |
+| Use wording that clearly sets off the name of the element. | Assign services to the Business data only group. <br /> By selecting the Create my database button, you agree Microsoft can use entity and field names you create to help improve our common data model. <br /> Choose how often you want to refresh data in Schedule refresh. |
+| Use quotation marks. Quotation marks can make text cluttered, so use them sparingly and only when necessary for clarity. | Assign services to the "No business data allowed" group. |
+| Use bold formatting. | Assign services to either the **Business data only** or **No business data allowed** group. |
diff --git a/.claude/skills/microsoft-writing-style-guide/references/source-manifest.md b/.claude/skills/microsoft-writing-style-guide/references/source-manifest.md
new file mode 100755
index 000000000..222f60ba9
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/source-manifest.md
@@ -0,0 +1,65 @@
+# Source manifest
+
+## Authoritative source
+
+| Field | Value |
+|---|---|
+| Repository | `MicrosoftDocs/microsoft-style-guide-pr` |
+| Repository URL | https://github.com/MicrosoftDocs/microsoft-style-guide-pr |
+| Pinned commit | `c78a330b932812a342be2ebca0ec8bc3d01fbac2` |
+| Commit timestamp | 2026-07-16T18:50:11Z |
+| Local synchronization date | 2026-08-22 |
+| Latest guide change represented | 2026-07-02 |
+
+The pinned commit is the source of truth for this snapshot. If a local rule
+conflicts with that source, use the pinned source. Check the live guide before
+relying on this snapshot for a rule changed after the synchronization date.
+
+## Distribution source
+
+| Field | Value |
+|---|---|
+| Repository | `msbrettorg/microsoft-writing-style` |
+| Repository URL | https://github.com/msbrettorg/microsoft-writing-style |
+| Pinned commit | `d9227efa6c984c13260e3bf869f4b6132cfb3c19` |
+| Skill tree | `73d4edd9337016a22a9918497b1ba377449894fb` |
+
+This FinOps Toolkit copy includes the distribution repository's `LICENSE`,
+`LICENSE-CONTENT`, and `NOTICE.md`. It also applies review fixes that replace
+unresolved image placeholders with text descriptions, make the validator's
+text handling explicitly UTF-8, and reject unresolved placeholders. Additional
+review fixes align percentage guidance, correct alt-text grammar, and make
+damaged-distribution validation return errors instead of raising exceptions.
+
+## Coverage
+
+| Source surface | Authoritative count | Local status |
+|---|---:|---|
+| TOC-linked non-term pages | 109 | 105 substantive reference-page headings are present in the reference files; brand voice and Top 10 guidance are in `SKILL.md`; Welcome and What's new are source metadata |
+| A-Z term pages | 870 | Present across the six `a-z-term-list-*.md` files |
+| Shared include files | 45 | Resolved in place; zero `!INCLUDE` directives remain |
+| Canonical reference files | 19 | Preserved |
+
+## Resolution policy
+
+* Include payloads retain authoritative prose, examples, tables, and links.
+* Source frontmatter and include directives are omitted because they are build
+  metadata rather than writing guidance.
+* The existing consolidated reference organization is preserved to support
+  selective loading.
+* `term-index.tsv` is generated from the pinned TOC and maps authoritative
+  terms to their consolidated local reference files.
+* Two TOC labels lag their page titles. The index uses the authoritative page
+  titles `drive resource` and `storage, storage space` while retaining the TOC
+  source paths `disk-resource.md` and `storage-storage-device.md`.
+
+## Support artifacts
+
+| Artifact | Role |
+|---|---|
+| `term-index.tsv` | Canonical A-Z term inventory and local routing |
+| `../scripts/validate.py` | Offline structural and freshness validation |
+| `../evals/evals.json` | Representative behavior evaluations |
+| `../LICENSE` | MIT license for original repository contributions |
+| `../LICENSE-CONTENT` | CC BY 4.0 license for Microsoft-derived content |
+| `../NOTICE.md` | Source attribution and modification notice |
diff --git a/.claude/skills/microsoft-writing-style-guide/references/term-collections-numbers-symbols.md b/.claude/skills/microsoft-writing-style-guide/references/term-collections-numbers-symbols.md
new file mode 100755
index 000000000..d931f94ff
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/term-collections-numbers-symbols.md
@@ -0,0 +1,514 @@
+# Term collections, and numbers and symbols
+
+Grouped word-usage guidance for related sets of terms. For individual alphabetical terms, see the a-z-term-list-*.md files. For keyboard key names and shortcuts, see keys-and-keyboard-shortcuts.md.
+
+## Term collections
+
+### Accessibility terms
+
+In general, use people-first language (refer first to the person, followed by the disability). To ensure clarity and consistency, this should be the default unless you know a specific audience prefers otherwise.
+
+In some cases, however, identity-first language can be used, because some people and communities take pride in recognizing their disability as an integral part of their identity and feel that person-first language is marginalizing. Always make an effort to know the preferences expressed by a person with a disability or a disability community and defer to these.
+
+In all cases, don't use language that has offensive or insensitive connotations, such as *maimed* or *impaired*.
+
+The following table lists examples of people-first language (preferred), identity-first language (acceptable, context-dependent), and offensive or insensitive language (never allowed).
+
+| Preferred (people-first) | Acceptable (identity-first) | Do not use (offensive/insensitive) |
+|---|---|---|
+| Person who is blind, person with low vision | Blind person | Sight-impaired, vision-impaired |
+| Person who is deaf, person with a hearing disability | Deaf person | Hearing-impaired |
+| Person with limited mobility, person who has a mobility or physical disability | Physically disabled person, wheelchair user | Crippled, lame, handicapped |
+| Is unable to speak, uses sign language, uses synthetic speech | | Dumb, mute, non-verbal |
+| Has multiple sclerosis, cerebral palsy, a seizure disorder, or muscular dystrophy | | Affected by, stricken with, suffers from, a victim of, an epileptic |
+| Person without a disability | Non-disabled person, able-bodied person | Normal person, healthy person |
+| Person with a prosthetic limb, person with a limb difference, person with an amputation | Amputee | Maimed, missing a limb, birth defect |
+| Person with a disability | Disabled person | People with handicaps, the handicapped |
+| Person with cognitive disabilities, developmental disabilities, learning disabilities, or dyslexia | Learning disabled, dyslexic person | Slow learner, mentally handicapped, differently abled, Special Ed person, stupid, special needs |
+| Person with autism | Autistic person, neurodivergent person | Asperger's |
+| functional needs (or paraphrase according to the specific disability) | | special needs |
+
+For an overview of Microsoft accessibility policies, see Accessibility guidelines and requirements.
+
+To learn more about writing that conveys respect to all people and promotes equal opportunities, see the Guidelines for Inclusive Language from the Linguistic Society of America.
+
+### AI and bot terms
+
+Avoid talking about AI and bot technology. Instead, focus on the benefits of the technology or what the customer wants to do with it. When it's necessary to talk about the technology itself—such as in content for developers or in event presentations, or to make it clear that the customer is chatting with a bot, not a person—use the terms below.
+
+Before you invent a term, make sure a suitable term doesn't already exist. For more information about creating new terms or using emerging terminology, see Use technical terms carefully.
+
+**Learn more** See Chatbots and virtual agents for guidelines for creating a new chatbot.
+
+|                 **Term**                 |                                                                                                                                                                                                                                                                                    **Usage**                                                                                                                                                                                                                                                                                     |
+|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|     **AI**     |                                                                                                                                                                                To refer to the technology itself, use *AI* for all audiences and in most content, including blogs, websites, and email. Don't spell out *artificial intelligence.*<br /><br /> Use *intelligent* or *intelligence* to describe or talk about the benefits of AI.<br /><br /> **Examples**<br />Power BI realizes the promise of AI in intelligent features such as image recognition, text analytics, and automated machine learning.<br />From document translation to intelligent threat detection, AI is enhancing the productivity of more than 120 million commercial Office 365 users.                                                               |
+|                 **bot, chatbot, virtual agent**                  |                                                                   Use *bot* to refer to an app that performs automated tasks or engages with humans through a conversational interface.<br /><br />If necessary, it's OK to use *chatbot* to clarify that the bot uses conversation to interact with the customer or *virtual agent* if the bot provides customer or technical support. After that, use *bot.*<br /><br />Never refer to Cortana as a *bot, chatbot,* or *virtual agent.* Use *personal digital assistant* instead.                                                                                                            |
+|  **conversation as a platform (CaaP)**   | Don't use in content for a general audience.<br /><br />OK to use if it's necessary to refer to the computing model in which two or more people or other entities exchange messages. Define the term on the first use, if necessary, to make sure the meaning is clear to your audience.<br /><br />Spell out *conversation as a platform* whenever possible. If the term appears often, it's OK to use *CaaP* after the abbreviation is introduced in parentheses. Don't capitalize as *CAAP.*<br /><br />Don't hyphenate *conversation as a platform* when used as a modifier. |
+| **conversational user interface (CUI)**  |                            Avoid the term in customer-facing communications.<br /><br />OK to use if it's necessary to refer to a computing model where people interact with a system in a conversational manner, using text or voice input. Define the term on the first use, if necessary, to make sure the meaning is clear to your audience.<br /><br />Spell out *conversational user interface* or *conversational UI* on the first use. Use *CUI* after the abbreviation is introduced in parentheses.                             |
+| **intelligent, intelligence, intelligent technology** |                                                                                                                                                            For all audiences and in most content, use *intelligent* or *intelligence* to describe or talk about the benefits of AI.<br /><br />In UI, use *intelligent technology* to describe the underlying technology that powers AI features.<br /><br />Don't use *smart technology.*<br /><br />**Examples**<br />To help people do their best work, Microsoft is making AI available to everyone by building intelligent features into our core products.<br />Enhance your sales performance and planning with intelligent applications like Microsoft Dynamics 365 AI for Sales.<br />From document translation to intelligent threat detection, AI is enhancing the productivity of more than 120 million commercial Office 365 users.<br />**Figure** A PowerPoint **What's New** notification includes **Present in multiple languages** and **Convert SVG icons to shapes**.                                                                                                                               |
+|      **Microsoft AI**      |                                                                                                                                                                                  Use only to refer to the initiative that Microsoft is undertaking to accelerate AI capabilities and infuse intelligence into our offerings.<br /><br />Microsoft AI isn't a technology, feature, product, or service. Don't say things like "Powered by Microsoft AI." Don't spell out *artificial intelligence* in references to Microsoft AI.                                                                                                                                                              |
+|      **personal digital assistant**      |                                                                                                                                                                                                                                       Use to refer to a type of bot that has a name, a semblance of a personality, knowledge of a customer's needs and preferences, and the ability to act on those needs and preferences.<br /><br />Use instead of *agent, virtual assistant,* or *intelligent personal assistant* to refer to Cortana.                                                                                                                                            |
+| **social chatbot, relationship chatbot** |                                                                                                                                                                Use instead of *emotional chatbot* or *personified chatbot* to refer to a chatbot that people have conversations with for entertainment. Social chatbots often have a name and persona. Zo, Xiaoice, and Rinna are the Microsoft social chatbots.                                                                                                                                                                 |
+|        **voice-activated device**        |                                                                                                                                                                                                                         OK when it's necessary to refer to the category of devices, such as the Harman Kardon voice-activated speaker, that use Cortana.                                                                                                                                                                                                                         |
+|      **voice user interface (VUI)**      |                                         Avoid the term in customer-facing communications.<br /><br />OK to use if it's necessary to refer to a computing model where people use voice input to interact with a system, similar to a conversation. Define the term on the first use, if necessary, to make sure the meaning is clear to your audience.<br /><br />Spell out *voice user interface* or *voice UI* whenever possible. If the term appears often, it's OK to use *VUI* after the abbreviation is introduced in parentheses.                                          |
+
+### Bit and byte terms
+
+In general, spell out *bit* and *byte* terms on the first mention unless:
+
+- Your audience is familiar with the abbreviation.
+- You're working on UI text.
+
+In those cases, or after you've spelled out the term on the first mention, it's OK to use the abbreviation.
+
+- Use abbreviations only with numbers in specific measurements.
+
+**Examples** 128 TB measured in terabytes
+
+- Insert a space between the abbreviation and the numeral, or hyphenate if the measurement modifies a noun.
+
+**Examples** 512 gigabytes (GB) of RAM from 1 GB to a maximum of 2 GB 23 MB/day up to 2 TB of physical memory with 8 TB of address space 200 MB of available hard-drive space a 650-MB limit
+
+- In measurements, when the unit of measure isn't abbreviated, use the singular form of the unit of measure when the number is 1. Use the plural form for all other measurements.
+
+**Examples** 0 megabits 0.5 megabits 1 megabit 15 megabits
+
+- Use *of* to add a modifier to a measurement used as a noun.
+
+**Example** The operation requires 200 MB of available hard-drive space.
+
+- Use commas in numbers that have four or more digits, regardless of how the numbers appear in the UI.
+
+**Example** 1,024 MB
+
+| Term | Abbreviation | Usage |
+| ---- | ------------ | ----- |
+| **bits per pixel** | bpp | |
+| **bits per second** | bps | Don't use as a synonym for *baud*. See Units of measure term collection for information about *baud*. |
+| **byte** | B | Don't abbreviate, unless in UI. |
+| **exabyte** | EB | Don't use *E*, *E byte*, or *EByte*. |
+| **gibibyte** | GiB | |
+| **gigabit** | Gb | Don't abbreviate, unless in UI. |
+| **gigabits per second** | Gbps | Don't spell out as *Gb per second*. |
+| **gigabyte** | GB | Don't use *G*, *G byte*, or *GByte*. |
+| **kibibyte** | KiB | |
+| **kilobit** | Kb | Don't abbreviate, unless in UI. |
+| **kilobits per second** | Kbps | Don't spell out as *KB per second*. |
+| **kilobyte** | KB | Don't use *K*, *K byte*, or *KByte*. |
+| **kilobytes per second** | KBps | Don't spell out as *KB per second*. |
+| **mebibyte** | MiB | |
+| **megabit** | Mb | Don't abbreviate, unless in UI. |
+| **megabits per second** | Mbps | Don't spell out as *Mb per second*. |
+| **megabyte** | MB | Don't use *M*, *meg*, *M byte*, or *MByte*. |
+| **megabytes per second** | MBps | Don't spell out as *MB per second*. |
+| **petabyte** | PB | Don't use *P*, *P byte*, or *PByte*. |
+| **tebibyte** | TiB | |
+| **terabyte** | TB | Don't use *T*, *T byte*, or *TByte*. |
+| **zettabyte** | ZB | Don't use *Z*, *Z byte*, or *ZByte*. |
+
+### Cloud-computing terms
+
+As cloud computing evolves, the consistent use of its terminology across Microsoft content presents a clear story to customers.
+
+This section covers common cloud-computing terms.
+
+For more information about creating new terms or using emerging terminology, see Use technical terms carefully.
+
+|                       Term                        |                                                                                                                                                                                                                                                                                         Usage                                                                                                                                                                                                                                                                                         |
+|-------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                       **as a service (-aaS)**                       |                                                                                                                                                                               Use only *as a service (-aaS)* terms included in this term list.<br /><br />Don’t create new *as a service* terms or *-aaS* acronyms. Instead, describe the service and what it provides the customer.
+|                       **cloud, the cloud**                       |                                                                                                                                                                                Don't capitalize *cloud* except in references to the Microsoft Cloud or when it's part of a product name.<br /><br />Use *cloud* mostly as an adjective. Use sparingly as a noun—instead of *the cloud*, talk about *cloud computing*, *cloud services*, or a specific service or functionality and what the customer can do with it.                                                                                                                                                                                 |
+|                       **cloud bursting, cloud-bursting**                       |                                                                                                                                                                                It’s OK to use *cloud bursting* for technical audiences to mean when a private cloud taps into additional resources on the public cloud to meet a spike in demand. Define on the first mention.<br /><br />Hyphenate *cloud-bursting* as an adjective preceding a noun, as in *cloud-bursting configuration*. 
+|          **cloud computing, cloud platform, cloud services**           |                                                                                                                                                                                                               Use *cloud computing*, not *the cloud*, to refer generally to the delivery of computing services over the internet.<br /><br />Use *cloud platform* only in content for a technical audience, such as content about Azure.<br /><br />Use *cloud services* to refer to the services provided via the cloud—such as servers, storage, databases, and software.<br /><br />All terms are two words and lowercase.                                                                                                                                                                                                                |
+|                  **cloud native, cloud-native**                  |                                                                                                                                                                                                                                                    In content for a technical audience, it’s OK to use *cloud native* to describe technologies that are built originally for the cloud and therefore optimized for cloud scale and performance.<br /><br /> Lowercase. Hyphenate *cloud-native* as an adjective preceding a noun, as in *cloud-native app*. Don’t hyphenate in other instances.<br /><br />Don’t use *born in the cloud*, *cloud-born*, or similar phrases.             
+|                  **cloud OS**                  |                                                                                                                                                                                                                                                    Don’t use. Use *platform as a service (PaaS)* instead.             
+|                  **community cloud**                  |                                                                                                                                                                                                                                                    Never use. Use *hybrid cloud*, *private cloud*, or *hosted private cloud* instead.                                                                                                                                                                                                                                                     |
+|             **content delivery network**              |                                                                                                                                                                                                                                                                    Lowercase when referring in general to a distributed network of servers that deliver web content. Always spell out; don’t use *CDN*.                                                                                                                                                                                                                                                                     |
+|             **cross-tenant**              |                                                                                                                                                                                                  Hyphenate in all positions.                                                                                                                                                                                                   |
+|             **edge, edge computing**              |                                                                                                                                                                                                                                                                    It’s OK to use these terms to refer to computing that shifts most data processing from a centralized system closer to a device or system that requires data quickly. Include short definitions of *the edge* and *edge computing* unless you’re sure your audience is familiar with the terms.<br /><br />Lowercase.<br /><br />Use *at the edge*—not *on the edge*—in references to edge computing. 
+|                  **elastic computing, elastic cloud computing**                   |                                                                                                                                                                                                                    In general, avoid using these terms and instead talk about what the customer can do with this technology.<br /><br />If your meaning is unclear without the terms, it’s OK to use them to talk about the use of cloud computing to quickly expand or decrease computer processing, memory, and storage resources to meet changing demands. Use *elastic cloud computing* when you need to clarify that cloud services are used.<br /><br />Define these terms on the first mention unless you’re sure that your audience is familiar with them.
+|                  **hosted service**                   |                                                                                                                                                                                                                    Use this term to describe a service, an IT solution, or an application that's hosted by a service provider and made available to customers over the internet.                                                                                                                                                                                                                    |
+|             **hosting provider, hoster**              |                                                                                                                                                                                                               It's OK to use *cloud hosting provider* and *web hosting provider* if you need to distinguish cloud service providers from web hosts. Don't use *hoster*.                                                                                                                                                                                                                |
+|                   **hybrid cloud**                    |                                                                                                                                                                                                            OK to use for technical audiences who are comfortable with cloud technology, but define on the first mention. For other audiences, just talk about a hybrid model.                                                                                                                                                                                                             |
+|        **infrastructure as a service (IaaS)**         |                                                                                                                         Use for technical audiences only.<br /><br />It’s OK to use *IaaS* after the term has been spelled out on the first mention with the abbreviated form in parentheses.<br /><br />Don't capitalize as *IAAS.*<br /><br />Don't hyphenate as a modifier.                                                                                                                         |
+|              **IT as a service (ITaaS)**              |                                                                                                                         Use for technical or business-decision-maker audiences only.<br /><br />In content for a general audience, refer to the specific type of service, such as applying software updates, in a cloud-computing model.<br /><br />It’s OK to use *ITaaS* after the term has been spelled out on the first mention with the abbreviated form in parentheses.<br /><br />Don't capitalize as *ITAAS*.<br /><br />Don't hyphenate as a modifier.                                                                                                                          |
+|                 **the Microsoft Cloud**                  |                                                                                                                                                                                                                                              Use this term to describe the entire Microsoft cloud platform—not just Azure, but also the cloud on which all Microsoft cloud offerings run, including Dynamics 365, Microsoft Power Platform, and Microsoft 365.<br /><br />When used in this meaning, *Microsoft Cloud* is capitalized.<br /><br />Include the article (*the*) before *Microsoft Cloud*.<br /><br />It’s OK to add a modifier between *the* and *Microsoft Cloud*—for example, “the trusted Microsoft Cloud.”                                                                                                                                                                                                                                               |
+|     **multicloud**      | It's OK to use *multicloud* in content for technical audiences to refer to the use of multiple cloud-computing services from more than one cloud provider (including private and public clouds), in a heterogeneous environment.<br /><br />One word, no hyphen. |
+|     **multitenant, multitenancy**     |                                                                               It's OK to use these terms in content for a technical audience, but in content for a general audience, try to use friendlier language—for example, say *services used by multiple tenants* rather than *multitenant services*.<br /><br />One word, no hyphen.                                                                               |
+|             **on-premises, off-premises**             |                                                                                                                                                                                                          Hyphenate in all positions. <br /><br />*Premises* is plural. Don't use *on-premise*, *off-premise*. <br /><br />Don't use *on-premises cloud* or *off-premises cloud.*                                                                                                                                                                                                          |
+|           **platform as a service (PaaS)**            |                                                                                                                                                                    Use for technical audiences only. <br /><br />It’s OK to use *PaaS* after the term has been spelled out on the first mention with the abbreviated form in parentheses.<br /><br />Don't capitalize as *PAAS*.<br /><br />Don't hyphenate as a modifier.                                                                                                                                                                    |
+| **private cloud, hosted private cloud** |                                                                                                                                                                                                                                                                         Define these terms on the first mention.                                                                                                                                                                                                                                                                          |
+|           **serverless**           |                                                                                                                                                                                                                                           One word, no hyphen.                                                                                                                                                                                                                                            |
+|           **software as a service (SaaS)**            |                                                                                                                                                                         It’s OK to use *SaaS* after the term has been spelled out on the first mention with the abbreviated form in parentheses.<br /><br />Don't capitalize as *SAAS*.<br /><br />Don't hyphenate as a modifier.                                                                                                                                                                          |
+
+### Computer and device terms
+
+In the modern world, customers get things done with whatever device is handy. When you write, focus on what the customer wants to accomplish. If you must write about the device itself, use the most general term that works—usually, that's *device*. Sometimes, it's *computer,* *phone,* or *wearable device*. Occasionally, it's *laptop,* *smartphone,* or *fitness band.*
+
+### Device interaction terms
+
+Use these verbs to talk about using devices and peripheral devices:
+
+  - Use *turn on* and *turn off,* not *power on,* *power off, switch on,* or *switch off.*
+  - Use *set up* to describe preparing hardware or software for first use.
+  - Use *install* and *uninstall* to refer to adding and removing hardware drivers and apps. 
+  - Use *connect* and *disconnect* to
+refer to establishing a relationship between devices (direct or wireless) and connecting a device to a network or the internet.
+
+### Preferred device terms
+
+|              Term               |                                                                                                                                                                                                  Usage                                                                                                                                                                                                  |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|      **device, mobile device**      |                                                                      Use *device* to refer collectively to all types of computers, phones, and other devices. <br /><br />Use *mobile device* only when you need to call out the mobility.<br /><br />It's OK to modify *device* when it matters. For example, *point-of-sale device*.                                                                      |
+|          **computer, PC**           | Use *computer* when you need to talk about a computing device other than a phone, wearable device, or gaming console.<br /><br />It's OK to use *PC* when space is a constraint, but don't switch between *PC* and *computer*.<br /><br />Don't use *mobile computer,* *portable computer,* or *mobile PC.* |
+| **phone, mobile phone, smartphone** |                                                             Use *phone* most of the time. <br /><br />If you need to call out the mobility, use *mobile phone*.<br /><br />Use *smartphone* only if you need to distinguish a smartphone from other types of phones. <br /><br />Don't use *wireless phone,* *cell phone,* or *cellular phone.*                                                             |
+|         **tablet, laptop**          |                                                     Use a more generic term unless you're talking about a specific class of computers. Use *tablet* only to refer to a touchscreen computer without a permanently attached keyboard. Use *laptop* to refer to a portable computer with a permanently attached keyboard, with or without a touchscreen.<br /><br />Don't use *slate* or *notebook.*                                                      |
+|  **wearable device, fitness band**  |                                                                                Use only when it's necessary to differentiate devices that are meant to be worn from other devices.<br /><br />Avoid using *wearable* as a noun.                                                                                 |
+
+### Acceptable terms for specific references
+
+Use the following terms only when you need to be more specific than you can be by using the preferred terms.
+
+|      **Term**       |                                                                                                                                                           **Usage**                                                                                                                                                           |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **handheld device** | Use only to refer to a small, limited-use device that accesses, captures, and updates information in real time, such as the devices often used in line-of-business (LOB) applications. If possible, just use *device*. <br /><br />Don't use *handheld* as a noun.<br /><br />Don't use *handheld PC* or *handheld computer*. |
+|    **desktop**     |  Use only to refer to a type of computer that isn't portable or a server computer.<br /><br />Don't use *desktop* as a synonym for *computer* or *PC.*                                                                                                                                                           |
+|     **machine**     |                     Most of the time, don't use *machine* to mean a computer. Use *computer* instead. It's OK to use *machine* in content for a technical audience and in content about virtualization to describe both physical machines and virtual machines.<br />**Examples**<br />Updates help to enhance the security and performance of your computer.<br />Move virtual machines from one physical server to another to balance the load among physical servers.<br />A signed machine certificate uniquely identifies the computer.                                                                         |
+| **client, server**  |        Use *client* or *server* only if it's clear to the reader whether the client or server discussed is hardware or software.<br /><br />Use *client computer* or *server computer* if you need to clarify that you're discussing hardware.<br /><br />Don't use *box* in reference to client and server hardware.         |
+
+### **Peripheral devices and hardware components**
+
+In general, use the most generic term that describes a peripheral device or hardware component.
+
+|                                **Term**                                 |                                                                                                                                                                                                                                                                                                                                                        **Usage**                                                                                                                                                                                                                                                                                                                                                         |
+|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                               **adapter**                               |                                                                                                                                                                                                                                                                                                                                                Use instead of *adaptor*.                                                                                                                                                                                                                                                                                                                                                 |
+|                                **disc**                                 |                                                                                                                                                                                                                                                                                                                                     Use *disc,* not *disk,* to refer to a CD or DVD.                                                                                                                                                                                                                                                                                                                                     |
+|                                **disk**                                 |                                                                                                                                                                                                                                              Use *disk* only in the context of Azure cloud storage and virtual machines.<br /><br />Use *hard drive,* not *disk, fixed disk, hard disk,* or *disk drive* to refer to the drive on a PC where programs are typically stored.                                                                                                                                                                                                                                              |
+|                      **display, screen, monitor**                       |                                                                                                                                                    Use *display* as a general term for any visual output device, including the built-in display on a computing device and an external monitor or projector.<br /><br />Use *screen* to distinguish the usable portion of the display from its edges.<br /><br />Use *monitor* only when you need to refer specifically to a standalone desktop or mounted display device that can be connected to a computing device.                                                                                                                                                    |
+|                                **drive**                                | Avoid talking about drives in content for a general audience. It's usually enough to prompt customers to save a file, picture, song, and so on. <br /><br />Use *drive* as the general term for any type of device where a customer can save or retrieve files, including *hard drive,* *CD drive,* *DVD drive,* *USB flash drive,* or any other removable storage device. Use *hard drive* when necessary to refer to a drive on a PC where programs are typically stored. Avoid referring to the type of drive if you can. <br /><br />Use *drive C,* not *drive C:,* *drive C>,* or *C: drive,* when necessary. <br /><br />Use *network drive,* not *remote drive,* to refer to a logical network drive name. <br />**Example** <br /> network drive X |
+| **mouse, pen, controller, joystick, touchpad, trackball** |                                                          In general, don't talk about specific input devices. Most of the time, talk about how the customer interacts with the app or game by selecting, choosing, and so on. To learn more, see Describing interactions with UI.<br /><br />When you must discuss interacting with a specific type of device, don't use *pointing device* or *input device.* Instead, use the specific term for that device: *mouse, pen, controller, joystick, touchpad,* or *trackball.* Use *tablet pen* on the first mention, and *pen* thereafter. Don't use *stylus.*<br /><br /> Joysticks have *controls* (not *options*) for controlling movement on the screen.                                                   |
+|                           **network adapter**                           |                        Use instead of *network card* to describe hardware that supports connecting a computer to a network.                                                                                                                      |
+|                             **touchscreen**                             |                         One word. Use sparingly. Most of the time, talk about how the customer interacts with the app or product by selecting, choosing, and so on. See Describing interactions with UI to learn more.                                                                               |
+|                                 **USB**                                 |                        Don't spell out. Use only as an adjective. <br />**Examples**<br />USB drive<br />USB hub<br />USB 3.0 port                                                                                                                           |
+
+### Date and time terms
+
+This section covers usage for terms related to time and date.
+
+|                                                               Term                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                               **24/7**                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         Don't use. Use *all day, every day, always,* or something similar.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|                                                              **AM, PM**                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            Use *AM* and *PM* (preceded by a space). Use capital letters for *AM* and *PM*.<br />**Examples**<br />10:45 AM<br />6:30 PM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       
+|                                                              **Dates**                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          Use the following format for dates: *month day, year,* as in *July 31, 2016*. Don't use *day month year,* as in *31 July 2016*.<br /><br />In UI, it's OK to use numbers and slashes for dates if the code supports that format and automatically displays the appropriate date format for different locales.<br /><br />Don't use ordinal numbers (such as 1st, 12th, or 23rd) to indicate a date.<br />**Examples**<br />February 16, 2016<br />2/16/16 (in UI)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|                                                              **Days of the week: Sunday–Saturday**                                   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          Capitalize the days of the week. Don't use abbreviations unless space is extremely limited. Don't include a period with the abbreviations.<br /><br />Three-letter abbreviations are preferred:<br />*Sun, Mon, Tue, Wed, Thu, Fri,* and *Sat*<br /><br />In calendars and date picker UI controls, it's OK to use two-letter or one-letter abbreviations:<br />*Su, Mo, Tu, We, Th, Fr,* and *Sa*<br />*S, M, T, W, T, F,* and *S*<br /><br />For the three-letter and two-letter abbreviations, use sentence-style capitalization (*Su*), not all uppercase (*SU*).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|                                                          **midnight, noon**                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              Use *noon* and *midnight*. Don't use *12:00 noon* and *12:00 midnight*.<br /><br />Midnight is the beginning of the new day, not the end of the old one.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|                                                     **Months: January–December**                                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  Capitalize the names of months and their abbreviations.<br /><br />Don't use abbreviations unless space is extremely limited. <br />Use three-letter abbreviations when necessary: <br />*Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov,* and *Dec* <br />Don't include a period with the abbreviations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|                                          **Seasons: autumn, winter, spring, summer**                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             Don't refer to seasons if you can avoid it. Talk about months or calendar quarters instead. If you must mention a specific season, identify the hemisphere, too. (Summer in the northern hemisphere is winter in the southern hemisphere.)  <br /><br />Don't capitalize the seasons except to designate an issue of a publication, such as *Spring 2017*.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|                                                       **Time, ranges of time**                                                       |                                                                                                                                                                                                                                                                                                                                           Use numerals for times of day: 2:00, 4:15, 7:30. Always include *AM* and *PM*. <br /><br />Include the time zone if you're discussing an event that customers beyond the local time zone might see or attend. <br /><br />In text, use *to* in a range of times.<br />**Example** <br />10:00 AM to 2:00 PM <br /><br />In a schedule or listing, use an en dash with no spaces around it. <br />**Example** <br />10:00 AM–2:00 PM<br /><br />**Exception**<br />In a date range that includes two times and two dates, add spaces around the en dash. Lead with whatever is most important to the customer within the context: time of day or date. <br />**Examples**<br />2:15 AM–4:45 PM 4/1/16 (time range on a single day)<br />12/1/17 2:15 PM – 4/1/18 4:45 PM (time plus date range)                                                                                                                                                                                                                                                                                                                                            |
+| **Time zones: Eastern Time, Central Time, Mountain Time, Pacific Time, Coordinated Universal Time (UTC), Greenwich Mean Time (GMT)** | Capitalize time zones. Don't abbreviate unless space is severely limited. If you must abbreviate, use *ET, CT, MT,* and *PT*.<br /><br />Don't specify *standard time or daylight saving time* unless you're providing information about a specific event where that information matters.<br /><br />If you're referring to a time zone as a geographical area, call it a zone. <br />**Example** <br />in the Pacific Time zone  <br /><br />Not all time zones have names, and some time-zone names are used in more than one geographical area. If you're talking about a particular place, clarify the country or reference Coordinated Universal Time (UTC). Don't include spaces around the plus sign (+) or hyphen (-).<br />**Examples**<br />Eastern Time (UTC-5)<br />Eastern Time (UTC+10)<br />Eastern Time (Australia)<br /><br />For time zones without names, refer to the offset from Coordinated Universal Time. <br />**Example** <br />UTC+7<br /><br />Don't abbreviate *Coordinated Universal Time* in text unless space is severely limited. Use *UTC,* never *CUT*. (It's OK to use UTC in references to a specific time zone, such as *UTC+7*.) Don't use *Universal Time Coordinate or Universal Time Coordinated*.<br /><br />Don't use *Greenwich Mean Time* or *GMT* by itself unless you have no other choice. Use *Coordinated Universal Time* instead. On the first mention, it's OK to refer to *Coordinated Universal Time (Greenwich Mean Time)*. |
+
+### Abbreviating units of time
+
+|           **Unit**            |                         **Abbreviation**                          |
+|-------------------------------|-------------------------------------------------------------------|
+|         **day, days**         |  d<br />Spell out except in UI or when space is extremely tight.  |
+|        **hour, hours**        |                                 h                                 |
+|        **microsecond**        |                         Don't abbreviate.                         |
+| **millisecond, milliseconds** |                                ms                                 |
+|      **minute, minutes**      |                                min                                |
+|       **month, months**       | mo <br />Spell out except in UI or when space is extremely tight. |
+|        **nanosecond**         |                         Don't abbreviate.                         |
+|      **second, seconds**      |                                sec                                |
+|        **week, weeks**        | wk <br />Spell out except in UI or when space is extremely tight. |
+|        **year, years**        | yr <br />Spell out except in UI or when space is extremely tight. |
+
+### Mouse and mouse interaction terms
+
+Most of the time, don't talk about the mouse, mouse actions, or the pointer unless it's necessary to avoid confusion. Instead, talk about customer interactions with the UI. To learn more, see Describing interactions with UI.
+
+When you need to talk specifically about the mouse, mouse interactions, or the pointer, use these terms.
+
+### Mouse actions
+
+|      **Term**      |                                                                                                  **Usage**                                                                                                  |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|     **click**      |                                                     Use to describe selecting an item with the mouse by clicking the mouse once. Don't use *click on*.                                                      |
+|    **click in**    |                                                        Use only to refer to clicking in a general area within a page, window, or other UI location.                                                         |
+|  **double-click**  |                                         Use to describe selecting an item by clicking the mouse twice in rapid succession. Hyphenate. Don't use *double-click on*.                                          |
+|      **drag**      | Use to describe holding down a button while moving the mouse, and then releasing the button. Don't use *click and drag* or *drag and drop*. It's OK to use *drop* by itself if *drag* isn't precise enough. |
+|    **hover over, point to**    |    To describe moving the mouse pointer over an area of the UI without selecting it, use *hover over* or *point to,* as appropriate for your audience. Use *hover* or *hovering* as the adjective and noun form.<br />**Examples**<br > In Microsoft Edge, when you hover over a link, the URL appears in the lower-left corner. <br />The hover image is displayed when the user points to the button. <br />To program the pop-up action that's triggered by hovering …. <br />Pop-up windows that appear on hover <br /><br />Don't use *mouse over* or *move the mouse pointer to.* It's OK to use *move the mouse pointer to* in content that teaches beginning skills.                       |
+| **press and hold** |                                                                             Use only in content that teaches beginning skills.                                                                              |
+|  **right-click**   |                                    Use to describe clicking an item by using the secondary mouse button (the right button by default, but the user can customize this).                                     |
+|  **scroll**   |                                    Use only in content that teaches beginning skills. In other content, use a phrase such as *move through.*                                     |
+
+### Devices
+
+|        **Term**        |                                                                                                                   **Usage**                                                                                                                   |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|       **mouse**        |                                               Use *mouse* to refer to one mouse. If you need to refer to more than one mouse, use *mice.*                                                 |
+|    **mouse button**    | Use to refer to the left mouse button. Use *left mouse button* only to teach beginning skills or when not doing so would cause confusion. When more than one mouse button is used in a procedure, name the least frequently used button only. |
+| **right mouse button** |                         Use to refer to the secondary mouse button. By default, this is the right mouse button. Customers who change the default understand that *right mouse button* indicates the secondary button.                         |
+|    **wheel button**    |                                                              Use to refer to the third or middle button on the mouse. Customers *rotate* the wheel and *click* the wheel button.                                                              |
+
+### On-screen pointers
+
+When you must talk about the appearance of the pointer on the screen, include a picture of the pointer if possible. Don't use a picture instead of the word *pointer*—use both<em>.</em>
+
+|**Term**|**Usage**|
+|---|---|
+|**busy pointer**|Use to describe the pointer when it consists only of an activity indicator.|
+|**double-headed arrow**|Use to describe how the pointer looks over a split line (:::image type="icon" source="media/mouse-mouse-interaction-terms/1502439723.png":::). Don't use *double-headed arrow* as a name for the pointer. <br />**Example**<br />When the pointer becomes a :::image type="icon" source="media/mouse-mouse-interaction-terms/1502439723.png":::, drag the pointer to move the split line.|
+|**pointer**|Use to refer to the pointer on the screen. Use *cursor* only for a technical audience or when it's necessary to describe the point where text or graphics will be inserted. Don't use *insertion point*.|
+|**working in background pointer**|Use to describe the pointer when it consists of both the pointer and an activity indicator.|
+
+### Security terms
+
+This section describes usage for specific security terms. For definitions of security terms, see the [Microsoft Malware Protection Glossary](https://www.microsoft.com/security/portal/mmpc/shared/glossary.aspx).
+
+| Term | Usage |
+|---|---|
+| **anti-malware** | Use only as an adjective to describe a category of software used to detect and respond to malicious software, such as viruses, worms, trojans, and sometimes spyware and adware. |
+| **antiphishing** | Use only as an adjective to describe practices or a category of software used to detect and respond to phishing scams, which are attempts to trick individuals into revealing sensitive information, such as passwords or credit card numbers. |
+| **antispyware** | Use only as an adjective to describe software that detects and sometimes removes spyware. |
+| **antivirus** | Use only as an adjective to describe software that detects and responds to malware.<br />Use *antivirus* instead of *anti-malware* to differentiate between antispyware and other anti-malware programs. <br />**Example**<br />Microsoft Security Essentials has both antivirus and antispyware capabilities. |
+| **black hat hacker** | Consider alternatives where possible.<br />**Examples**<br />computer criminal<br />unauthorized user<br />malicious hacker |
+| **bullet-proof** | Don't use. |
+| **deceptive software** | Don't use. Use *unwanted software* instead. |
+| **hacker, hack** | Use *malicious hacker* to refer to an unauthorized user who accesses a system with the intent to cause harm. If the unauthorized user's intent isn't known or isn't malicious, use *unauthorized user*.<br /><br />Don't use *hacker* in content for a general audience. In general use, the term often has negative connotations.<br /><br />It's OK to use *hack* and *hacker* in content for developers or in contexts where positive outcomes are involved, such as hackathons. <br /><br />Don't use *hacker* to mean an amateur programmer. Don't use *hack* to mean improvising a solution to a programming problem unless the positive context is well understood. |
+| **insecure** | Don't use to mean *not secure*. |
+| **lock** | Don't use to mean *protect*. |
+| **malicious code** | Don't use. Use *malware* or *malicious software* instead. |
+| **malicious user** | Don't use. Use *malicious hacker* instead. |
+| **malware, malicious software** | Use *malware* instead of *malicious software* to describe unwanted software installed without adequate user consent. Viruses, worms, and trojans are malware.<br /><br />If your audience might not be familiar with the term *malware,* define it as *malicious software* on the first mention. <br />**Example**<br />The security filter helps prevent malware (malicious software) from damaging your computer. |
+| **spyware** | Before using the term *spyware* to describe specific software, be certain the software has been identified as spyware. |
+| **trojan horse, trojan** | In content for a technical audience, it's OK to shorten to *trojan*. |
+| **unwanted software** | Use as a general term for spyware, adware, and similar software. |
+| **vulnerability** | Don't use to describe intentional software behavior. For example, don't describe trusting a domain administrator to control any other domain within a forest as a vulnerability.<br /><br />On the first mention, use a modifier to identify the type of vulnerability:<br /> <ul><li>Product vulnerability is a set of conditions that violates an implied or explicit security policy. A product vulnerability is usually addressed by a Microsoft security bulletin or service pack.</li><li>Administrative vulnerability is the failure to observe administrative best practices. For example, using a weak password or logging on to an account that has more user rights than needed to perform a specific task.</li><li>Physical vulnerability is the failure to provide physical security for a computer. For example, leaving an unlocked computer running and unattended in a public area.</li></ul>After the first mention, it's OK to use the modifier only occasionally.<br />For other security issues, use the most specific term that describes the issue. Define the term if the audience might be unfamiliar with it. If no specific term exists, use *security issue*. |
+| **white hat hacker** | Consider alternatives where possible.<br />**Example**<br />computer security expert |
+### Special characters
+
+Use the following terms to describe special characters.
+
+**See also** [Keys and keyboard shortcuts term collection](/style-guide/a-z-word-list-term-collections/term-collections/keys-keyboard-shortcuts)
+
+|Character|Name|Notes|
+|---|---|---|
+|<div><b>´</b></div>|acute accent|Don't use *accent acute*.|
+|<div><b>&amp;</b></div>|ampersand|Don't use in place of *and*.<br /><br />**See** [ampersand (&amp;)](/style-guide/a-z-word-list-term-collections/a/ampersand)|
+|<div><b>&lt; &gt;</b></div>|angle brackets|The set consists of a *left angle bracket* and a *right angle bracket*.|
+|<div><b>'</b></div>|apostrophe|This is the same character as a *single quotation mark*.<br /><br />**See** [Apostrophes](/style-guide/punctuation/apostrophes)|
+|<div><b>*</b></div>|asterisk|It's OK to use *star* to refer to the key on a phone keypad.|
+|<div><b>@</b></div>|at sign||
+|<div><b>&#92;</b></div>|backslash|**See** [Slashes](/style-guide/punctuation/slashes)|
+|<div><b>{ }</b></div>|braces|Don't use *curly brackets*.<br /><br />The set consists of an *opening brace* and a *closing brace*.|
+|<div><b>[ ]</b></div>|brackets|The set consists of an *opening bracket* and a *closing bracket*.|
+|<div><b>^</b></div>|caret, circumflex|Don't use *accent circumflex*.|
+|<div><b>¢</b></div>|cent sign||
+|<div><b>« »</b></div>|chevrons|Microsoft term, seldom used, especially in documentation. Also called *merge field characters* in Word.<br /><br />The set consists of an *opening chevron* and a *closing chevron*.|
+|<div><b>&copy;</b></div>|copyright symbol||
+|<div><b>†</b></div>|dagger||
+|<div><b>°</b></div>|degree symbol||
+|<div><b>÷</b></div>|division sign||
+|<div><b>$</b></div>|dollar sign||
+|<div><b>[[ ]]</b></div>|double brackets|The set consists of an *opening double bracket* and a *closing double bracket*.|
+|<div><b>…</b></div>|ellipsis|One set of three dots is called an *ellipsis* (singular). Use the plural form *ellipses* only when you're referring to multiple sets of three dots.<br /><br />Don't add space between ellipsis dots.<br /><br />**See** [Ellipses](/style-guide/punctuation/ellipses)|
+|<div><b>—</b></div>|em dash|**See** [Em dashes, en dashes, hyphens, and minus signs](/style-guide/punctuation/dashes-hyphens)|
+|<div><b>–</b></div>|en dash|**See** [Em dashes, en dashes, hyphens, and minus signs](/style-guide/punctuation/dashes-hyphens)|
+|<div><b>=</b></div>|equal sign|Don't use *equals sign*.|
+|<div><b>&euro;</b></div>|euro symbol|**See** [euro](/style-guide/a-z-word-list-term-collections/e/euro)|
+|<div><b>!</b></div>|exclamation point|Don't use *exclamation mark*.<br /><br />**See** [Exclamation points](/style-guide/punctuation/exclamation-points)|
+|<div><b>\`</b></div>|grave accent or backtick|Don't use *accent grave*.|
+|<div><b>≥</b></div>|greater than or equal to sign||
+|<div><b>&gt;</b></div>|greater than sign|This is the same character as a *right angle bracket* (used in code).|
+|<div><b>-</b></div>|hyphen|**See** [Em dashes, en dashes, hyphens, and minus signs](/style-guide/punctuation/dashes-hyphens)|
+|<div><b>&quot;</b></div>|inch mark|This is the same character as a *quotation mark*.|
+|<div><b>≤</b></div>|less than or equal to sign||
+|<div><b>&lt;</b></div>|less than sign|This is the same character as a *left angle bracket* (used in code).|
+|<div><b>&minus;</b></div>|minus sign|Don't use an en dash.<br /><br />**See** [Em dashes, en dashes, hyphens, and minus signs](/style-guide/punctuation/dashes-hyphens)|
+|<div><b>×</b></div>|multiplication sign|Use an asterisk (\*) or the letter *x* instead if necessary to match software.<br /><br />**See** [multiplication sign (×)](/style-guide/a-z-word-list-term-collections/m/multiplication-sign)|
+|<div><b>≠</b></div>|not equal to sign||
+|<div><b>#</b></div>|number sign, hashtag, pound key|In general, use *number sign* instead of *pound sign* to refer to the symbol.<br /><br />In social media, use *hashtag*.<br /><br />Use *pound key* when you're referring to the phone keypad button.|
+|<div>¶</div>|paragraph mark||
+|<div><b>( )</b></div>|parentheses|The set consists of an *opening parenthesis* and a *closing parenthesis*.<br /><br />**See** [parenthesis, parentheses](/style-guide/a-z-word-list-term-collections/p/parenthesis-parentheses)|
+|<div><b>%</b></div>|percent sign|**See** [percent, percentage](/style-guide/a-z-word-list-term-collections/p/percent-percentage)|
+|<div><b>π</b></div>|pi||
+|<div><b>\|</b></div>|pipe, vertical bar, or `OR` logical operator||
+|<div><b>+</b></div>|plus sign|Don't use to replace words like *and*, *over*, or *plus*.<br /><br />**See** [plus sign (+)](/style-guide/a-z-word-list-term-collections/p/plus-sign)|
+|<div><b>±</b></div>|plus or minus sign||
+|<div><b>?</b></div>|question mark|**See** [Question marks](/style-guide/punctuation/question-marks)|
+|<div><b>&quot; &quot;</b></div>|quotation marks|Don't use *quotes* or *quote marks*.<br /><br />The set consists of an *opening quotation mark* and a *closing quotation mark*.<br /><br />**See** [Quotation marks](/style-guide/punctuation/quotation-marks)|
+|<div><b>&reg;</b></div>|registered trademark symbol||
+|<div><b>§</b></div>|section sign||
+|<div><b>' '</b></div>|single quotation marks|Don't use *single quotes* or *single quote marks*.<br /><br />The set consists of an *opening single quotation mark* and a *closing single quotation mark*.<br /><br />**See** [Quotation marks](/style-guide/punctuation/quotation-marks)|
+|<div><b>/</b></div>|slash|Don't use *virgule*.<br /><br />**See** [Slashes](/style-guide/punctuation/slashes)|
+|<div><b>~</b></div>|tilde|Don't use in place of *about* or *approximately.*|
+|<div><b>&trade;</b></div>|trademark symbol||
+|<div><b>_</b></div>|underscore|**See** [underline vs. underscore](/style-guide/a-z-word-list-term-collections/u/underline-vs-underscore)|
+
+## Accessibility considerations for special characters
+
+Screen readers skip over some symbols and other nonalphabetic characters without reading them or indicating their presence. This situation can cause accessibility problems:
+
+- Users of a document or webpage lack important information.
+- Users of a website or web app can't determine the purpose of buttons and other UI elements.
+
+Be aware of this possibility whenever you write content that users will access in electronic form. Consider the following solutions.
+
+### General approaches
+
+Whenever you can, write out the words that you mean instead of using special characters. For example, write "1 through 10" instead of "1–10."
+
+If you must use special characters, use the correct character for the purpose, as outlined in the preceding table. For example, unless you must match what appears in the UI, use a multiplication sign (×) instead of an asterisk (*) or the letter *x* to represent a multiplication operation.
+
+### Content in HTML and related formats: Character entity references
+
+In content written in HTML or a related language (including Markdown), you can improve the accessibility of *some* special characters by inserting a character entity reference instead of the character itself. This type of reference begins with an ampersand (&) and ends with a semicolon (;).
+
+For example, for a copyright symbol, you can enter `&copy;` instead of the symbol in your code. A screen reader that skips over the symbol itself should read out something like "copyright" for the entity reference, giving users information that they would otherwise lack.
+
+However, because of the way screen readers work, the use of entity references for *all* special characters doesn't necessarily yield a better user experience.
+
+### UI elements: `aria-label` attributes
+
+For UI elements, such as for a website or web app, an alternative to character entity references is the `aria-label` attribute. This attribute is part of Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA). WAI-ARIA is a set of roles and attributes that define ways to make web content and web applications more accessible to people with disabilities.
+
+The `aria-label` attribute is applicable only to:
+
+- Interactive elements, such as buttons, text boxes, and checkboxes.
+- Images.
+- So-called *landmarks*, such as a page's header, footer, menu, and main content area.
+
+It isn't intended—or widely supported—for static, non-UI textual content.
+
+If the label text of an applicable UI element includes a special character from the preceding table, but you're not using the specified entity reference, add an `aria-label` attribute to the element to improve accessibility. A screen reader will then read out the attribute's value instead of the element's label text.
+
+The value that you provide for the attribute should give the full name of the element, including the name of the special character as it should be read.
+
+### Example
+
+Assume that an app includes buttons for selecting the number of degrees to rotate an image. The label text for these buttons must include a degree symbol (°). Here are the accessible ways to handle this situation:
+
+- Character entity reference in label text: `<button>90&deg;</button>`
+- Character in label text, `aria-label` on element: `<button aria-label="90 degrees">90°</button>`
+
+In both cases, a screen reader should correctly read out "ninety degrees."
+### Touch and pen interaction terms
+
+Today's customer can interact with UI in a variety of ways. This section covers terms for UI interactions done with gestures of the hand or body and tablet pen.
+
+In general, use input-neutral terms, which support all input methods. If you're writing content specific to touching a screen or using a pen, use *tap* and *double-tap* instead of *click* and *double-click*. *Tap* means to press the screen with a finger or pen tip and then to lift it, usually quickly.
+
+**Learn more** For information about input-neutral terms, see Describing interactions with UI.
+
+When you need to write specifically about touch and pen UI interactions, use these terms.
+
+|             Term             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                               Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|             **tap**              |                                                                                                                                                                                                                                                                                                                                                                                                   Use to describe selecting, opening, or activating a button, icon, or other element on the screen with a finger or the pen by tapping it once. Don’t use *tap on*.                                                                                                                                                                                                                                                                                                                                                                                                   |
+|          **double-tap**          |                                                                                                                                                                                                                                                                                                                                                                                             Use to describe selecting, opening, or activating a button, icon, or other element on the screen by tapping twice in rapid succession. Hyphenate. Don’t use *double-tap on*.                                                                                                                                                                                                                                                                                                                                                                                              |
+|         **tap and hold**         |                                                                                                                                                                                                                                                                                                                                                                                                                                     Use only if required by the program to achieve a specific result. Don’t use *touch and hold*.                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|            **flick**             |                                                                                                                                                                                                                                                                                                                                                                                                                                 Use to describe moving one or more fingers to scroll through items on the screen. Don’t use *scroll*.                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|             **pan**              |                                                                                                                                                                                                                                                                    Use to describe moving the screen in multiple directions at a controlled rate, as you would pan a camera to see different views in the environment. For contact gestures, use to refer to moving a finger, hand, or pen on the device surface to move through screens or menus at a controlled rate, rather than quickly skipping through content using the flick gesture. Don’t use *drag* or *scroll* as a synonym for *pan*.                                                                                                                                                                                                                                                                    |
+|    **pinch, stretch to zoom**    |                                                                                                                                                                                                                                                                                                                                                                                 Use to describe touching the screen or a UI element with two or more fingers, and then moving the fingers toward each other (*pinch*) or away from each other (*stretch*) to zoom the view in or out.                                                                                                                                                                                                                                                                                                                                                                                 |
+|            **rotate**            |                                                                                                                                                                                                                                                                                                                                                                                                           Use to describe putting two or more fingers on a UI element and then turning the hand. This action rotates the item in the direction of the turn.                                                                                                                                                                                                                                                                                                                                                                                                           |
+|            **select**            |                                                                                                                                                                                                                                                                                                                                                                                                                                      Use to describe pressing hardware buttons and keys on the keyboard (on-screen or physical).                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|       **select and hold**        |                                                                                                                                                                                                                                                                                                                                                                                             Use to describe pressing and holding an element in the UI.                                                                                                                                                                                                                                                               |
+|            **slide**             |                                                                                                                                                                                                                                                                                                                                       For touch UI, use to describe pressing and briefly dragging an element in the direction opposite to the way the page scrolls, and then moving it to a new location. For example, if the page scrolls left or right, the item is dragged up or down. The item is released to relocate it.                                                                                                                                                                                                                                                                                                                                        |
+|            **swipe**             |                                                                                                                                                                                                                                                                                                                                                                              For touch UI, use to describe a short, quick movement in the direction opposite to the way the page scrolls. For example, if the page scrolls left or right, an item is selected by swiping it up or down.                                                                                                                                                                                                                                                                                                                                                                               |
+| **swipe or slide from the edge** | Use to describe swiping a finger quickly or sliding across the screen from an edge. This action may:<br /> <ul><li>Open charms. (Swipe from the right edge.)</ul></li> <ul><li>Open a recently used app or switch between recently used apps. (Swipe from the left edge.)</ul></li> <ul><li>Open another app at the same time. (Slide from the left edge without lifting your finger, and drag the app until a divider appears. Then move the app where you want it, and slide the divider to adjust the app.)</ul></li> <ul><li>Show a list of recently used apps. (Slide in from the left edge without lifting your finger, and then push the app back toward the left edge.)</ul></li> <ul><li>Show commands for the current app, such as **New** or **Refresh**. (Swipe in from the top or bottom edge.)</ul></li> <ul><li>Close an app. (Slide down from the top edge without lifting your finger, and then drag the app to the bottom of the screen.)</ul></li> |
+
+### Units of measure terms
+
+This section covers usage and abbreviations for a variety of terms related to measurement. For other units of measure not covered here, see *The Chicago Manual of Style*.
+
+- Use numerals for measurements of distance, temperature, volume, size, weight, pixels, points, and so on—even if the number is less than 10\. Add a zero before the decimal point for decimal fractions less than one, unless the customer is asked to enter the value.
+
+**Examples** 3 ft, 5 in. 1.76 lb 80 × 80 pixels 0.75 grams enter **.75**" 3 centimeters 3 cm
+
+- Insert a space between the unit of measure and the numeral, or hyphenate if the measurement modifies a noun.
+
+**Examples** 13.5 inches 13.5-inch display 8.0 MP 8.0-MP camera
+
+- Use abbreviations only with numbers in specific measurements, such as 20 MP, and don't follow the abbreviation with a period.
+
+**Exception** Follow *in* with a period when used as an abbreviation for *inch.*
+
+- Use commas in numbers that have four or more digits, regardless of how the numbers appear in the UI: 1,093 MB.
+
+**Exceptions** For years, pixels, and baud use commas only when the number has five or more digits: *1920 × 1080 pixels, 10,240 × 4320 pixels, 9600 baud, 14,400 baud.* Don't use commas after the decimal point in decimal fractions.
+
+- When the unit of measure is spelled out, use the singular form when the number is 1. Use the plural form for all other measurements.
+
+**Examples** 0 points 0.5 points 1 point 12 points
+
+- Spell out *by* in dimensions, except for tile sizes, screen resolutions, and paper sizes. For those, use the multiplication sign (×). Use a space before and after the multiplication sign.
+
+**Examples** 10 by 12 ft room 3" by 5" image 4 × 4 tile 8.5" × 11" paper 1280 × 1024
+
+| **Category** | **Term** | **Abbreviation and usage** |
+|--|--|--|
+| **Distance and length** | centimeters | cm |
+|  | feet | ft |
+|  | inches | in. (or " if space is limited). Always include a period to avoid confusion with the preposition *in.*<br /><br />Hyphenate *half-inch* as an adjective. Use instead of *half an inch* or *one-half inch.*<br /><br />When space is limited or the measurement needs to be specific, use *0.5 in.* <br /><br />Use the abbreviated form sparingly in content that will be translated or localized. It may be translated incorrectly as a preposition. |
+|  | kilometers | km |
+|  | meters | m |
+|  | miles | mi |
+|  | millimeters | mm |
+| **Weight** | grams | g |
+|  | kilograms | kg |
+|  | ounces | oz |
+|  | pounds | lb |
+| **Area** | square foot | sq ft |
+|  | square meter | m<sup>2</sup> |
+| **Volume** | cubic foot | cu ft |
+|  | cubic meter | m<sup>3</sup> |
+| **Type and fonts** | points | pt |
+| **UI, display resolution, and digital imaging** | pixels | Don't use the abbreviation *px* in the context of screen or camera resolution.<br /><br />It's OK to abbreviate as *px* in content about online design when space is limited. <br /><br />**Examples**<br />48 × 48 px <br />The application icon should be 62 × 62 pixels and PNG format. |
+|  | pixels per inch | It's OK to use the acronym *PPI* in content about creating digital applications, when space is limited, and when you're certain that readers will understand it. <br /><br />**Examples**<br />72 pixels per inch  <br />At 72 PPI, …. |
+|  | megapixels | MP |
+| **Print and display resolution** | dots per inch | It's OK to use the acronym *dpi* to refer to print and display resolution when you're certain that readers will understand it. |
+| **Speed and frequency** | baud | Don't abbreviate. Don't use *baud rate*—it's redundant. When designating baud, use commas when the number has five (not four) or more digits. <br /><br />**Examples**<br /> 2400 baud <br/> In 1991, 14.4 K modem had a 2400 baud. |
+|  | gigahertz | GHz. Spell out on the first mention. After that, it's OK to use the abbreviation as a measurement with numerals. |
+|  | Hertz | Hz. Spell out on the first mention. After that, it's OK to use the abbreviation as a measurement with numerals. Capitalize the word and the abbreviation. |
+|  | kilohertz | kHz. Spell out on the first mention. After that, it's OK to use the abbreviation as a measurement with numerals. |
+|  | megahertz | MHz. Spell out on the first mention. After that, it's OK to use the abbreviation as a measurement with numerals. |
+| **Other** | degrees | ° (for temperature)<br />deg (for angle) |
+|  | dialog units | Don't abbreviate.<br /><br />**Example**<br />Converting from MFC dialog units (used in resource files to specify height/width) to pixels …. |
+
+### See also
+
+- Bits and bytes term collection, Numbers
+
+## Numbers and symbols
+
+### 2D, two-dimensional
+
+Spell out on the first mention if your audience may be unfamiliar with the term. On subsequent mentions, use *2D*.
+
+Always hyphenate *two-dimensional*.
+
+### 3D, three-dimensional
+
+Use *3D* most of the time.
+
+Spell out *three-dimensional* on the first mention if your audience may be unfamiliar with the acronym. Always hyphenate *three-dimensional*.
+
+### 8.5" × 11" paper
+
+Use instead of *8.5-by-11-inch, 8.5 × 11-inch, 8 1/2 by 11-inch,* or other ways of referring to the paper size. Use a straight quotation mark (") to signify inches. Use a multiplication sign (×), not the letter *x.*
+
+### @mentions
+
+A feature that enables users to draw someone's attention to a message, comment, or calendar meeting or event by adding the @ symbol followed by the person's name to the body of the message or item.
+
+When this happens, the person is automatically notified that they were mentioned.
+
+Example
+
+@SanjibSahu, could you look at this?
+
+### 24/7
+
+**See** Date and time term collection
diff --git a/.claude/skills/microsoft-writing-style-guide/references/term-index.tsv b/.claude/skills/microsoft-writing-style-guide/references/term-index.tsv
new file mode 100755
index 000000000..d6f895c7a
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/term-index.tsv
@@ -0,0 +1,871 @@
+term	file	source_path
+abort, abortion	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/abort-abortion.md
+above	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/above.md
+access	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/access.md
+access key	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/access-key.md
+accessible	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/accessible.md
+achievement	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/achievement.md
+actionable	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/actionable.md
+active player, active user	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/active-player-active-user.md
+adapter	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/adapter.md
+add	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/add.md
+add-in, add-on	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/add-in-add-on.md
+adjacent selection	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/adjacent-selection.md
+administer	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/administer.md
+administrator, admin	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/administrator-admin.md
+afterward	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/afterward.md
+against	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/against.md
+AI (artificial intelligence)	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/artificial-intelligence-ai.md
+alarm	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/alarm.md
+alert	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/alert.md
+alias	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/alias.md
+allow, allows	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/allow-allows.md
+allow list	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/allow-list.md
+alphabetical	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/alphabetical.md
+alphanumeric	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/alphanumeric.md
+AM, PM	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/am-pm.md
+ampersand (&)	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/ampersand.md
+and so on	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/and-so-on.md
+and/or	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/and-or.md
+antialiasing	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/antialiasing.md
+anti-malware	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/anti-malware.md
+antispyware	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/antispyware.md
+antivirus	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/antivirus.md
+app, application	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/app-application.md
+appendix, appendices	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/appendix-appendices.md
+applet	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/applet.md
+application developer, app developer	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/application-developer-app-developer.md
+application file, app file	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/application-file-app-file.md
+application icon, app icon	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/application-icon-app-icon.md
+application window, app window	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/application-window-app-window.md
+argument vs. parameter	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/argument-vs-parameter.md
+arrow	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/arrow.md
+arrow keys	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/arrow-keys.md
+as well as	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/as-well-as.md
+ask	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/ask.md
+assembly language	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/assembly-language.md
+assistive	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/assistive.md
+assure, ensure, insure	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/assure-ensure-insure.md
+asterisk (*)	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/asterisk.md
+at sign (@)	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/at-sign.md
+attribute	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/attribute.md
+audiobook	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/audiobook.md
+author	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/author.md
+auto-	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/auto.md
+avg	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/a/avg.md
+back end, back-end	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/back-end.md
+back up, backup	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/back-up-backup.md
+backbone	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/backbone.md
+backlight	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/backlight.md
+backspace	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/backspace.md
+backtab	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/backtab.md
+badge	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/badge.md
+baseline	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/baseline.md
+baud	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/baud.md
+beep	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/beep.md
+below	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/below.md
+beta	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/beta.md
+bi-	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bi.md
+big data	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/big-data.md
+big-endian, little-endian	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/big-endian-little-endian.md
+billion, B	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/billion-b.md
+bio	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bio.md
+bitmap	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bitmap.md
+bits per second	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bits-per-second.md
+black box	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/black-box.md
+black hat hacker	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/black-hat-hacker.md
+blacklist	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/blacklist.md
+blade	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/blade.md
+blank	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/blank.md
+block list	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/block-list.md
+blog, blogger, blogroll, weblog	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/blog-blogger-blogroll-weblog.md
+blue screen, bluescreen	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/blue-screen-bluescreen.md
+Bluetooth	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bluetooth.md
+Blu-ray Disc	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/blu-ray-disc.md
+board	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/board.md
+bold	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bold.md
+bookmark	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bookmark.md
+Boolean	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/boolean.md
+boot	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/boot.md
+bot	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bot.md
+bottom left, bottom right	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bottom-left-bottom-right.md
+bounding outline	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bounding-outline.md
+box	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/box.md
+bps	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bps.md
+breakpoint	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/breakpoint.md
+broadcast	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/broadcast.md
+browse	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/browse.md
+bug fix	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bug-fix.md
+build	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/build.md
+bulk	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/bulk.md
+button	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/button.md
+by (publisher or company name)	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/b/by.md
+C, C++, C#	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/c-cplusplus-csharp.md
+cable	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cable.md
+cabling	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cabling.md
+cache vs. disk cache	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cache-vs-disk-cache.md
+calendar	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/calendar.md
+call back, callback	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/call-back-callback.md
+call out, callout	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/call-out-callout.md
+can, may	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/can-may.md
+cancel, canceled, canceling, cancellation	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cancel-canceled-canceling-cancellation.md
+carry out vs. run	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/carry-out-vs-run.md
+Cascading Style Sheets (CSS)	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cascading-style-sheets-css.md
+catalog	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/catalog.md
+category axis	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/category-axis.md
+cell phone, cellular phone	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cell-phone-cellular-phone.md
+cellular	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cellular.md
+center on	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/center-on.md
+character set	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/character-set.md
+chart	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/chart.md
+chat	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/chat.md
+chatbot	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/chatbot.md
+check, checkbox, check mark	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/check-checkbox-check-mark.md
+check in	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/check-in.md
+child folder	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/child-folder.md
+choose	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/choose.md
+clear	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/clear.md
+click	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/click.md
+clickstream	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/clickstream.md
+clickthrough	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/clickthrough.md
+client	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/client.md
+client side, client-side	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/client-side.md
+client/server	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/client-server.md
+clipboard	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/clipboard.md
+close	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/close.md
+Close button	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/close-button.md
+cloud	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cloud.md
+cloud native, cloud-native	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cloud-native.md
+cloud platform	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cloud-platform.md
+cloud services	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cloud-services.md
+co-	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/co.md
+code page	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/code-page.md
+code point	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/code-point.md
+codec	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/codec.md
+color map	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/color-map.md
+column format	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/column-format.md
+combo box	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/combo-box.md
+command	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/command.md
+command button	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/command-button.md
+command line, command-line	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/command-line.md
+command prompt	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/command-prompt.md
+community cloud	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/community-cloud.md
+company vs. organization	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/company-vs-organization.md
+compile	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/compile.md
+compute	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/compute.md
+computer	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/computer.md
+connect	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/connect.md
+console	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/console.md
+context menu	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/context-menu.md
+context-sensitive	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/context-sensitive.md
+contiguous selection	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/contiguous-selection.md
+control	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/control.md
+Control Panel	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/control-panel.md
+controller	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/controller.md
+control-menu box	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/control-menu-box.md
+conversation as a platform (CaaP)	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/conversation-as-a-platform-caap.md
+conversational user interface (CUI)	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/conversational-user-interface-cui.md
+-core	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/dash-core.md
+corrupted	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/corrupted.md
+country or region	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/country-or-region.md
+crash	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/crash.md
+cut, cut-and-paste	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cut-and-paste.md
+cyber-	a-z-term-list-a-c.md	styleguide/a-z-word-list-term-collections/c/cyber.md
+dark mode	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dark-mode.md
+data, datum	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/data-datum.md
+data binding	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/data-binding.md
+data record	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/data-record.md
+database	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/database.md
+datacenter	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/datacenter.md
+datagram	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/datagram.md
+datasheet	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/datasheet.md
+deaf or hard-of-hearing	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/deaf-or-hard-of-hearing.md
+debug	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/debug.md
+deceptive software	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/deceptive-software.md
+decrement	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/decrement.md
+default	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/default.md
+defragment	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/defragment.md
+deinstall	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/deinstall.md
+delete	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/delete.md
+demilitarized zone (DMZ)	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/demilitarized-zone-dmz.md
+deprecated	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/deprecated.md
+depress, depressed	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/depress-depressed.md
+deselect	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/deselect.md
+desktop	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/desktop.md
+destination	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/destination.md
+destination drive, destination file	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/destination-drive-destination-file.md
+device	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/device.md
+device driver, driver	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/device-driver-driver.md
+DevOps	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/devops.md
+dialog box, dialog, dialogue	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dialog-box-dialog-dialogue.md
+dial-up	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dial-up.md
+different	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/different.md
+dimmed	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dimmed.md
+direction keys	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/direction-keys.md
+directory	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/directory.md
+disable, disables, disabled (functionality)	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/disable-disabled.md
+disabled (person)	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/disabled-(person).md
+disc	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/disc.md
+disjoint selection	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/disjoint-selection.md
+disk	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/disk.md
+drive resource	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/disk-resource.md
+disk space	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/disk-space.md
+display	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/display.md
+display adapter, display driver	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/display-adapter-display-driver.md
+DNS	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dns.md
+document	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/document.md
+domain	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/domain.md
+dot-com	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dot-com.md
+dotted rectangle	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dotted-rectangle.md
+double buffering	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/double-buffering.md
+double-click, double-clicking	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/double-click-double-clicking.md
+downgrade	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/downgrade.md
+download	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/download.md
+drag, drag and drop	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/drag-and-drop.md
+drill down, drill up, drill through	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/drill-down-drill-up-drill-through.md
+drive	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/drive.md
+drive name	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/drive-name.md
+dropdown	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dropdown.md
+DVD	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dvd.md
+dynamic-link library (DLL)	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dynamic-link-library-dll.md
+dynamic service capacity	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/d/dynamic-service-capacity.md
+e.g.	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/eg.md
+earlier	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/earlier.md
+e-book	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/e-book.md
+e-commerce	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/e-commerce.md
+e-discovery	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/e-discovery.md
+edutainment	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/edutainment.md
+e-form, form	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/e-form-form.md
+either/or	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/either-or.md
+elastic service capacity	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/elastic-service-capacity.md
+e-learning	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/e-learning.md
+ellipsis button	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/ellipsis-button.md
+email	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/email.md
+embed	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/embed.md
+emoji, emoticons	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/emoticons-emoji.md
+enable, enables, enabled	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/enable-enables.md
+end	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/end.md
+endline	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/endline.md
+endpoint	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/endpoint.md
+End-User License Agreement (EULA)	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/end-user-license-agreement-eula.md
+ensure, insure, assure	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/ensure-insure-assure.md
+enter	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/enter.md
+enterprise	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/enterprise.md
+entry field	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/entry-field.md
+environment variable	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/environment-variable.md
+erase	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/erase.md
+e-sports	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/e-sports.md
+et al.	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/et-al.md
+etc.	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/etc.md
+euro	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/euro.md
+e-words	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/e-words.md
+executable, .exe	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/executable-exe.md
+execute	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/execute.md
+exit	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/exit.md
+expand, collapse	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/expand-collapse.md
+expose	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/expose.md
+extend	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/extend.md
+extension, file name extension	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/e/extension-file-name-extension.md
+fail	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/fail.md
+fail over, fail back, failover, failback	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/fail-over-fail-back-failover-failback.md
+FALSE	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/FALSE.md
+family	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/family.md
+Far East	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/far-east.md
+far-left, far-right	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/far-left-far-right.md
+favorite	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/favorite.md
+fax	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/fax.md
+field	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/field.md
+file	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/file.md
+file attributes	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/file-attributes.md
+File Explorer	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/file-explorer.md
+file name	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/file-name.md
+file name extension, extension	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/file-name-extension-extension.md
+finalize	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/finalize.md
+find and replace	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/find-replace.md
+first line, first-line	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/first-line.md
+fitness band	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/fitness-band.md
+fixed disk	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/fixed-disk.md
+flick	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/flick.md
+flush, flush to	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/flush-flush-to.md
+flyout	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/flyout.md
+folder, folder icon	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/folder-folder-icon.md
+following	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/following.md
+font, font style	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/font-font-style.md
+foo, foobar, fubar	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/foo-foobar-fubar.md
+footer	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/footer.md
+foreground program	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/foreground-program.md
+format, formatted, formatting	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/format-formatted-formatting.md
+fourth-generation language	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/fourth-generation-language.md
+frameset	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/frameset.md
+freeze, frozen	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/freeze-frozen.md
+friendly name	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/friendly-name.md
+from vs. on	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/from-vs-on.md
+front end, front-end	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/front-end.md
+full screen, full-screen	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/full-screen.md
+function	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/f/function.md
+gallery	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/gallery.md
+game pad	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/game-pad.md
+garbage collection, garbage collector	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/garbage-collection-garbage-collector.md
+General Data Protection Regulation (GDPR)	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/general-data-protection-regulation-gdpr.md
+general protection fault, GP fault	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/general-protection-fault-gp-fault.md
+gigabit, Gbit	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/gigabit.md
+gigabyte, GB, G, G byte, Gbyte	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/gigabyte.md
+gigahertz, GHz	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/gigahertz.md
+given	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/given.md
+global	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/global.md
+glyph	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/glyph.md
+go to	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/go-to.md
+graphic, graphics, graphical	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/graphic-graphics-graphical.md
+graphics adapter	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/graphics-adapter.md
+gray, grayed out	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/gray-grayed-out.md
+greater, better	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/greater-better.md
+greylist	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/greylist.md
+gridline	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/gridline.md
+group box	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/group-box.md
+group, newsgroup	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/group-newsgroup.md
+grow	a-z-term-list-d-g.md	styleguide/a-z-word-list-term-collections/g/grow.md
+hack, hacker	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hack-hacker.md
+half inch	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/half-inch.md
+handheld, handheld device	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/handheld-handheld-device.md
+handle	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/handle.md
+handshake	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/handshake.md
+hang	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hang.md
+hard copy	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hard-copy.md
+hard drive	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hard-drive.md
+hard-code, hard-coded, hard-coding	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hard-code-hard-coded-hard-coding.md
+hard-of-hearing	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hard-of-hearing.md
+hardwired	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hardwired.md
+HDMI (High-Definition Multimedia Interface)	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hdmi.md
+header	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/header.md
+heading	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/heading.md
+hearing-impaired	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hearing-impaired.md
+Help	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/help.md
+he/she	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/he-she.md
+hexadecimal	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hexadecimal.md
+hierarchical menu	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hierarchical-menu.md
+higher	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/higher.md
+high-level-language compiler	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/high-level-language-compiler.md
+high-quality	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/high-quality.md
+high-resolution	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/high-resolution.md
+hint	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hint.md
+hit	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hit.md
+home directory	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/home-directory.md
+home, home page	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/home-home-page.md
+honeypot	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/honeypot.md
+host name	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/host-name.md
+hosted service	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hosted-service.md
+hosting provider	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hosting-provider.md
+hot key	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hot-key.md
+hot link	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hot-link.md
+hot spot, hotspot	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hot-spot-hotspot.md
+hover over, hovering	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hover-over-hovering.md
+how to, how-to	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/how-how-to.md
+HTML	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/html.md
+HTTP, HTTPS	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/http-https.md
+hybrid cloud	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hybrid-cloud.md
+hyperlink	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/h/hyperlink.md
+icon	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/icon.md
+iconize	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/iconize.md
+i.e.	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/ie.md
+if vs. whether vs. when	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/if-vs-whether-vs-when.md
+illegal	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/illegal.md
+image map	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/image-map.md
+imbed	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/imbed.md
+impact	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/impact.md
+inactive, inactive state	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/inactive-inactive-state.md
+inbound	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/inbound.md
+incoming, outgoing	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/incoming-outgoing.md
+increment	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/increment.md
+indent, outdent	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/indent-outdent.md
+index, indexes, indices	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/index-indexes-indices.md
+info	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/info.md
+infrastructure as a service (IaaS)	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/infrastructure-as-a-service.md
+initialize	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/initialize.md
+initiate	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/initiate.md
+inline	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/inline.md
+input	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/input.md
+input/output, I/O, input/output control	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/input-output.md
+insecure	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/insecure.md
+inside	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/inside.md
+install	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/install.md
+instant message, IM	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/instant-message-im.md
+instantiate	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/instantiate.md
+insure, assure, ensure	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/insure-assure-ensure.md
+intelligence, intelligent technology	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/intelligence-intelligent-technology.md
+interface	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/interface.md
+internet, intranet, extranet	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/internet-intranet-extranet.md
+Internet Connection Sharing	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/internet-connection-sharing.md
+Internet Explorer	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/internet-explorer.md
+Internet of Things (IoT)	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/internet-of-things-iot.md
+internet service provider (ISP)	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/internet-service-provider.md
+invalid, not valid	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/invalid-not-valid.md
+invite	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/invite.md
+invoke	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/invoke.md
+IP address	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/ip-address.md
+issue	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/issue.md
+IT pro, IT professional	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/it-pro-it-professional.md
+italic	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/italic.md
+its vs. it's	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/i/its-vs-its.md
+Java, JScript, JavaScript	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/j/java-jscript-javascript.md
+join	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/j/join.md
+joystick	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/j/joystick.md
+jump	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/j/jump.md
+justify, justified	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/j/justify-justified.md
+Kerberos protocol	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/kerberos-protocol.md
+key combination	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/key-combination.md
+key performance indicator (KPI)	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/key-performance-indicator-(KPI).md
+key sequence	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/key-sequence.md
+keyboard shortcut	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/keyboard-shortcut.md
+keypad	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/keypad.md
+keypress, keystroke	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/keypress-keystroke.md
+kilobit, Kbit	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/kilobit.md
+kilobits per second, Kbps	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/kilobits-per-second.md
+kilobyte, KB, K, K byte, Kbyte	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/kilobyte.md
+kilobytes per second, KBps	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/kilobytes-per-second.md
+kilohertz, kHz	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/kilohertz.md
+knowledge base, Knowledge Base	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/k/knowledge-base.md
+labeled, labeling	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/labeled-labeling.md
+laptop	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/laptop.md
+later	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/later.md
+launch	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/launch.md
+lay out, laid out, layout	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/lay-out-laid-out-layout.md
+leading	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/leading.md
+leave	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/leave.md
+left, leftmost, left-hand	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/left-leftmost-left-hand.md
+left align, left-aligned	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/left-align-left-aligned.md
+left justify, left-justified	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/left-justify-left-justified.md
+left mouse button	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/left-mouse-button.md
+legacy	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/legacy.md
+legal	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/legal.md
+less vs. fewer vs. under	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/less-vs-fewer-vs-under.md
+let, lets	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/let-lets.md
+leverage	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/leverage.md
+license terms	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/license-terms.md
+lifecycle	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/lifecycle.md
+-like	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/like.md
+line	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/line.md
+line of business, line-of-business	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/line-of-business.md
+link	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/link.md
+list box	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/list-box.md
+load	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/load.md
+lock	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/lock.md
+lock up	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/lock-up.md
+log on, log off	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/log-on-log-off.md
+lower	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/lower.md
+lower left, lower-left, lower right, lower-right	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/lower-left-lower-right.md
+lowercase	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/lowercase.md
+low-resolution	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/l/low-resolution.md
+machine	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/machine.md
+machine learning	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/machine-learning.md
+main document	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/main-document.md
+makefile	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/makefile.md
+malicious code	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/malicious-code.md
+malicious user	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/malicious-user.md
+malware, malicious software	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/malware-malicious-software.md
+management information systems	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/management-information-systems.md
+manipulate	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/manipulate.md
+marquee	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/marquee.md
+master/slave	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/master-slave.md
+mathematical	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/mathematical.md
+matrix, matrices	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/matrix-matrices.md
+Maximize button, maximize	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/maximize-button-maximize.md
+medium, media	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/medium-media.md
+megabit, Mb, Mbit	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/megabit.md
+megabits per second, Mbps	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/megabits-per-second.md
+megabyte, MB, meg, M, M byte, Mbyte	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/megabyte.md
+megahertz, MHz	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/megahertz.md
+member function	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/member-function.md
+memory	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/memory.md
+memory-resident	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/memory-resident.md
+menu item	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/menu-item.md
+message	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/message.md
+metafile	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/metafile.md
+micro-	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/micro.md
+microprocessor	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/microprocessor.md
+Microsoft	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/microsoft.md
+Microsoft account	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/microsoft-account.md
+Microsoft AI	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/microsoft-ai.md
+Microsoft Software License Terms	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/software-license-terms.md
+Microsoft Store	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/microsoft-store.md
+midnight	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/midnight.md
+million, M	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/million-m.md
+Minimize button, minimize	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/minimize-button-minimize.md
+MIP mapping	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/mip-mapping.md
+mission critical, mission-critical	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/mission-critical.md
+mixed reality, mixed-reality	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/mixed-reality.md
+mobile device, mobile phone	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/mobile-device-mobile-phone.md
+monitor	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/monitor.md
+monospace	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/monospace.md
+more than vs. over	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/more-than-vs-over.md
+mouse	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/mouse.md
+mouse over	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/mouse-over.md
+movable	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/movable.md
+move	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/move.md
+MPEG	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/mpeg.md
+multi-	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/multi.md
+multifactor authentication	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/multifactor-authentication.md
+multiple selection	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/multiple-selection.md
+multiplication sign (×)	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/multiplication-sign.md
+multitask, multitasking	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/multitask-multitasking.md
+multithreaded	a-z-term-list-h-m.md	styleguide/a-z-word-list-term-collections/m/multithreaded.md
+n	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/n.md
+namespace	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/namespace.md
+nanosecond	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/nanosecond.md
+native language	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/native-language.md
+natural user interface, NUI	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/natural-user-interface-nui.md
+navigate, navigation	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/navigate.md
+near real time, near-real-time	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/near-real-time.md
+need	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/need.md
+.NET	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/net.md
+network	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/network.md
+network adapter	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/network-adapter.md
+network administrator	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/network-administrator.md
+network connection	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/network-connection.md
+network drive	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/network-drive.md
+newsreader	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/newsreader.md
+non-	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/non.md
+nonadjacent selection	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/nonadjacent-selection.md
+noncontiguous selection	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/noncontiguous-selection.md
+nonprintable, nonprinting	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/nonprintable-nonprinting.md
+normal, normally	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/normal-normally.md
+notification	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/notification.md
+notification area	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/notification-area.md
+null, NULL, Null	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/null.md
+null-terminated, null-terminating	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/null-terminated-null-terminating.md
+number sign (#)	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/number-sign.md
+numeric	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/n/numeric.md
+object	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/object.md
+objectives and key results (OKR)	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/objectives-and-key-results-(OKR).md
+obsolete	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/obsolete.md
+of	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/of.md
+offline	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/offline.md
+off-premises, on-premises	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/off-premises-on-premises.md
+OK, okay	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/ok-okay.md
+on	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/on.md
+on demand, on-demand	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/on-demand.md
+on the fly	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/on-the-fly.md
+onboarding	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/onboarding.md
+once	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/once.md
+online	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/online.md
+online services	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/online-services.md
+on-screen	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/on-screen.md
+on-screen keyboard	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/on-screen-keyboard.md
+onto	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/onto.md
+opcode	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/opcode.md
+open	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/open.md
+open source, open-source	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/open-source.md
+operating environment, operating system	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/operating-environment-operating-system.md
+opt in, opt out	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/opt-in-opt-out.md
+option, option button	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/option-button.md
+org, organization	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/org-organization.md
+output	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/output.md
+outside	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/outside.md
+over	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/over.md
+overwrite	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/o/overwrite.md
+page	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/page.md
+palette	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/palette.md
+pan	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pan.md
+pane	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pane.md
+parameter	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/parameter.md
+parent/child	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/parent-child.md
+parenthesis, parentheses	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/parenthesis-parentheses.md
+passwordless	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/passwordless.md
+path	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/path.md
+PC	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pc.md
+p-code	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/p-code.md
+pen	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pen.md
+per	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/per.md
+percent, percentage	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/percent-percentage.md
+perimeter network	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/perimeter-network.md
+peripheral	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/peripheral.md
+permissions	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/permissions.md
+personal digital assistant	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/personal-digital-assistant.md
+phone, phone number	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/phone.md
+photo	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/photo.md
+pin, unpin	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pin-unpin.md
+pinch	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pinch.md
+ping, PING	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/ping-ping.md
+pipe	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pipe.md
+placeholder	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/placeholder.md
+plaintext, plain text	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/plaintext-plain-text.md
+platform	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/platform.md
+platform as a service (PaaS)	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/platform-as-a-service.md
+playlist	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/playlist.md
+please	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/please.md
+Plug and Play, plug and play	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/plug-and-play.md
+plugin	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/plug-in.md
+plus sign (+)	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/plus-sign.md
+point to	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/point-to.md
+pointer	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pointer.md
+pop-up	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pop-up.md
+port	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/port.md
+postal code	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/postal-code.md
+pound key, pound sign (#)	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pound-key-pound-sign.md
+power cord	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/power-cord.md
+power down, power up, power off, power on	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/power-down-power-up-power-off-power-on.md
+power user	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/power-user.md
+pre-	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pre.md
+preceding	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/preceding.md
+press, press and hold	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/press-and-hold.md
+preview	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/preview.md
+print, printout	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/print-printout.md
+print queue, printer queue	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/print-queue-printer-queue.md
+private cloud, hosted private cloud	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/private-cloud-hosted-private-cloud.md
+privileges	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/privileges.md
+profile	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/profile.md
+program	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/program.md
+program file	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/program-file.md
+prompt, prompting	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/prompt.md
+prop	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/prop.md
+property	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/property.md
+property sheet, property page	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/property-sheet-property-page.md
+protected mode	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/protected-mode.md
+public cloud	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/public-cloud.md
+pull down, pull-down	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/pull-down.md
+purge	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/purge.md
+push button, push-button	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/p/push-button.md
+quality, high-quality	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/q/quality-high-quality.md
+quit	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/q/quit.md
+radio button	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/radio-button.md
+ragged right	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/ragged-right.md
+RAM	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/ram.md
+range selection	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/range-selection.md
+re-	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/re.md
+read-only	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/read-only.md
+read/write, read/write permission	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/read-write-read-write-permission.md
+real time, real-time	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/real-time.md
+reboot	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/reboot.md
+recommend	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/recommend.md
+Recycle Bin, recycle bin	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/recycle-bin.md
+refresh	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/refresh.md
+registry, registry settings	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/registry-registry-settings.md
+reinitialize	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/reinitialize.md
+relationship chatbot	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/relationship-chatbot.md
+REM statement	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/rem-statement.md
+remote	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/remote.md
+remove	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/remove.md
+replace	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/replace.md
+restart	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/restart.md
+restore	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/restore.md
+reverse video	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/reverse-video.md
+right, rightmost, right-hand	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/right-rightmost-right-hand.md
+right align, right-aligned	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/right-align-right-aligned.md
+right justify, right-justified	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/right-justify-right-justified.md
+right mouse button	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/right-mouse-button.md
+right-click	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/right-click.md
+rights	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/rights.md
+ROM	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/rom.md
+Roman	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/roman.md
+root directory	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/root-directory.md
+rotate	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/rotate.md
+run vs. execute	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/run-vs-execute.md
+running foot, running head	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/running-foot-running-head.md
+runs vs. runs on	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/runs-vs-runs-on.md
+runtime	a-z-term-list-n-r.md	styleguide/a-z-word-list-term-collections/r/runtime.md
+(s), (es)	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/s-es.md
+sample vs. preview	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/sample-vs-preview.md
+save	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/save.md
+scan line	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/scan-line.md
+screen	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/screen.md
+screen reader	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/screen-reader.md
+screen resolution	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/screen-resolution.md
+screened subnet	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/screened-subnet.md
+screenshot	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/screenshot.md
+script, scriptlet	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/script-scriptlet.md
+scroll	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/scroll.md
+scroll bar, scroll arrow, scroll box	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/scroll-bar-scroll-arrow-scroll-box.md
+search, search and replace	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/search-and-replace.md
+search box	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/search-box.md
+secondary menu	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/secondary-menu.md
+see, see also, and similar phrases	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/see-see-also-and-similar-phrases.md
+select	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/select.md
+server	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/server.md
+service-level agreement (SLA)	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/service-level-agreement-sla.md
+service-oriented architecture (SOA)	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/service-oriented-architecture-soa.md
+set, specify	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/set-specify.md
+set up, setup, Setup	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/set-up-setup.md
+setting, value	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/setting-value.md
+set-top box	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/set-top-box.md
+shaded	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/shaded.md
+shell	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/shell.md
+ship	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/ship.md
+shortcut, shortcut menu	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/shortcut-shortcut-menu.md
+should vs. must	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/should-vs-must.md
+shut down, shutdown	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/shut-down-shutdown.md
+sign in, sign out	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/sign-in-sign-out.md
+simply	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/simply.md
+single sign-on (SSO)	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/single-sign-on-sso.md
+site	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/site.md
+site map	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/site-map.md
+size, resize	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/size-resize.md
+SKU	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/sku.md
+sleep	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/sleep.md
+slider	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/slider.md
+slideshow	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/slideshow.md
+small caps	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/small-caps.md
+smart card, Smart Card	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/smart-card.md
+smartphone	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/smartphone.md
+smb	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/smb.md
+snap-in	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/snap-in.md
+social chatbot	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/social-chatbot.md
+soft copy	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/soft-copy.md
+software as a service (SaaS)	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/software-as-a-service-saas.md
+software-plus-services	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/software-plus-services.md
+sorry	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/sorry.md
+spam	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/spam.md
+specification	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/specification.md
+spell checker	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/spell-checker.md
+spin box	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/spin-box.md
+split bar, split box	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/split-bar-split-box.md
+spoofing	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/spoofing.md
+spreadsheet vs. workbook	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/spreadsheet-vs-workbook.md
+spyware	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/spyware.md
+SQL, SQL Server	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/sql-sql-server.md
+start, restart	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/start-restart.md
+Start button, Start menu	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/start-button-start-menu.md
+start page	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/start-page.md
+start up, startup	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/start-up-startup.md
+status bar	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/status-bar.md
+stop, stop responding	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/stop-stop-responding.md
+storage, storage space	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/storage-storage-device.md
+store, marketplace, gallery	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/store-marketplace-gallery.md
+stream, streaming	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/stream-streaming.md
+stretch	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/stretch.md
+struct, structure	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/struct-structure.md
+style sheet	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/style-sheet.md
+sub-	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/sub.md
+subaddress	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/subaddress.md
+subclass	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/subclass.md
+subnet, subnetwork	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/subnet.md
+surf	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/surf.md
+swipe	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/swipe.md
+switch	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/switch.md
+symbol	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/symbol.md
+sync	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/sync.md
+system administrator	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/system-administrator.md
+system prompt	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/system-prompt.md
+system software	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/system-software.md
+system tray	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/s/system-tray.md
+tab	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/tab.md
+table of contents	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/table-of-contents.md
+tablet	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/tablet.md
+tap, double-tap, tap and hold	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/tap-double-tap-tap-and-hold.md
+target drive, target file	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/target-drive-target-file.md
+taskbar	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/taskbar.md
+terabyte, TB	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/terabyte.md
+terminate	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/terminate.md
+text, text message	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/text-text-message.md
+text box	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/text-box.md
+thanks, thank you	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/thanks-thank-you.md
+that vs. which	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/that-vs-which.md
+thousand, K	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/thousand-k.md
+tile, Live Tile	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/tile-live-tile.md
+time stamp	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/time-stamp.md
+timeout, time out	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/time-out.md
+toast	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/toast.md
+to-do	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/to-do.md
+toggle	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/toggle.md
+tone	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/tone.md
+tool	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/tool.md
+toolkit	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/toolkit.md
+tooltip	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/tooltip.md
+top left, top right	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/top-left-top-right.md
+top-level folder	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/top-level-folder.md
+touchpad	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/touchpad.md
+touchscreen	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/touchscreen.md
+touch-sensitive	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/touch-sensitive.md
+toward	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/toward.md
+trackball	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/trackball.md
+trailing	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/trailing.md
+trojan horse, trojan	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/trojan-horse-trojan.md
+turn on, turn off	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/turn-on-turn-off.md
+turnkey	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/turnkey.md
+type	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/t/type.md
+UK	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/uk.md
+Ultrabook	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/ultrabook.md
+un-	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/un.md
+unavailable	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/unavailable.md
+uncheck, unmark, unselect	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/uncheck-unmark-unselect.md
+undelete	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/undelete.md
+underline vs. underscore	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/underline-vs-underscore.md
+undo	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/undo.md
+uninstall	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/uninstall.md
+unregister	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/unregister.md
+unwanted software	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/unwanted-software.md
+upgrade	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/upgrade.md
+upload	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/upload.md
+UPnP	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/upnp.md
+upper left, upper right	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/upper-left-upper-right.md
+uppercase	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/uppercase.md
+upsize	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/upsize.md
+upward	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/upward.md
+URI	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/uri.md
+URL	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/url.md
+US	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/us.md
+usable	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/usable.md
+USB	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/usb.md
+use terms	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/use-terms.md
+user, end user	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/user-end-user.md
+user rights	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/user-rights.md
+using, by using, with	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/using-by-using-with.md
+utility	a-z-term-list-s-u.md	styleguide/a-z-word-list-term-collections/u/utility.md
+value axis	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/value-axis.md
+versus, vs.	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/versus-vs.md
+video call, videoconference	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/video-call-videoconference.md
+video card	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/video-card.md
+video display	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/video-display.md
+video driver	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/video-driver.md
+video game, video-game	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/video-game.md
+virtual	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/virtual.md
+virtual agent	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/virtual-agent.md
+virtualize	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/virtualize.md
+visit	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/visit.md
+voice user interface (VUI)	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/voice-user-interface-vui.md
+voice-activated device	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/voice-activated-device.md
+voicemail	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/voicemail.md
+vulnerability	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/v/vulnerability.md
+W3C	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/w3c.md
+want	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/want.md
+we	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/we.md
+wearable, wearable device	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/wearable-wearable-device.md
+web, World Wide Web, WWW	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/web-world-wide-web-www.md
+web services	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/web-services.md
+wellbeing	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/wellbeing.md
+where	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/where.md
+while	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/while.md
+white hat hacker	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/white-hat-hacker.md
+white paper	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/white-paper.md
+white space	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/white-space.md
+whitelist	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/whitelist.md
+who vs. that	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/who-vs-that.md
+Wi-Fi	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/wi-fi.md
+wildcard character	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/wildcard-character.md
+window	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/window.md
+Windows, Windows-based	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/windows-windows-based.md
+Windows 10, Windows 11	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/windows-10-windows-11.md
+Windows Explorer	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/windows-explorer.md
+wireframe	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/wireframe.md
+wireless	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/wireless.md
+wizard	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/wizard.md
+word processing, word-processing	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/word-processing.md
+wordwrap, wordwrapping	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/wordwrap-wordwrapping.md
+work area, workspace	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/work-area-workspace.md
+work style	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/work-style.md
+workgroup	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/workgroup.md
+working memory	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/working-memory.md
+workstation	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/workstation.md
+workstream	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/workstream.md
+worldwide vs. international	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/worldwide-vs-international.md
+write-only	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/write-only.md
+write-protect, write-protected	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/w/write-protect-write-protected.md
+x	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/x/x.md
+x-axis	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/x/x-axis.md
+x-coordinate	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/x/x-coordinate.md
+XON/XOFF	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/x/xon-xoff.md
+y-axis	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/y/y-axis.md
+y-coordinate	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/y/y-coordinate.md
+z-	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/z/z.md
+z-axis	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/z/z-axis.md
+zero, zeros	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/z/zero-zeros.md
+ZIP Code	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/z/zip-code.md
+zoom in, zoom out	a-z-term-list-v-z.md	styleguide/a-z-word-list-term-collections/z/zoom-in-zoom-out.md
diff --git a/.claude/skills/microsoft-writing-style-guide/references/text-formatting.md b/.claude/skills/microsoft-writing-style-guide/references/text-formatting.md
new file mode 100755
index 000000000..8e2481fba
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/text-formatting.md
@@ -0,0 +1,133 @@
+# Text formatting
+
+## Text formatting
+
+Type treatment is a key component in great design. The
+thoughtful use of fonts, text formatting, capitalization,
+alignment, and spacing creates a first impression, reinforces the
+Microsoft brand, and improves readability.
+
+The
+consistent formatting of text elements, such as command names and
+URLs, reduces ambiguity and helps customers find and
+interpret information easily. Text-formatting guidelines
+are sometimes called *document conventions.*
+
+This section covers:
+
+  - [Using type](/style-guide/text-formatting/using-type/index)
+  - [Formatting common text elements](/style-guide/text-formatting/formatting-common-text-elements)
+  - [Formatting titles](/style-guide/text-formatting/formatting-titles)
+
+**See also**  
+[Formatting developer text elements](/style-guide/developer-content/formatting-developer-text-elements)  
+[Reference documentation](/style-guide/developer-content/reference-documentation)  
+[Procedures and instructions](/style-guide/procedures-instructions/index)
+## Using type
+
+Beautiful typography is a cornerstone of modern design. The guidelines in this section will help you achieve it. 
+
+  - [Use sentence-style capitalization](/style-guide/text-formatting/using-type/use-sentence-style-capitalization)
+  - [Use left alignment](/style-guide/text-formatting/using-type/use-left-alignment)
+  - [Don't compress line spacing](/style-guide/text-formatting/using-type/dont-compress-line-spacing)
+## Use sentence-style capitalization
+
+In sentence-style capitalization, you capitalize only the first word of a sentence or phrase and proper nouns. **Example** <br />This sentence and the subhead of this section both use sentence-style capitalization.
+
+Although all-uppercase text is used occasionally on webpages, in advertising, and in other marketing communications, don’t use it in text. A mix of uppercase and lowercase characters gives words familiar shapes that help readers scan more efficiently. All-uppercase text just looks like a rectangle, so it’s harder to read. **Example** <br />THIS SENTENCE IS ALL UPPERCASE AND NOT VERY EASY TO READ, DON’T YOU AGREE?
+
+Don’t use all-lowercase text. Capital letters help readers recognize that a new section or thought is beginning. All-lowercase text takes away that helpful cue. **Example** <br />this sentence is all lowercase. or is it a sentence? it's hard to tell with no capital letters.
+
+**Learn more** To learn more about proper nouns, see Nouns and pronouns. To learn more about capitalization, see Capitalization.
+
+## Use left alignment
+
+Left-aligned text has an even left margin and an erratic (ragged) right margin.
+
+Don't center text.
+
+Avoid these awkward situations in text:
+
+  - Orphans, which occur when the first line of a paragraph appears by itself at the bottom of a page or column  
+
+  - Widows, which occur when the last line of a paragraph contains only one word or appears alone on the next page or column  
+
+  - Lines that end with hyphens
+
+In Word and PowerPoint, you can manage these situations without using manual line breaks.
+
+|                              **To**                              |                                                                                                                         **Do this**                                                                                                                          |
+|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|    Keep a hyphenated word from breaking at the end of a line     |                                                                                                    Insert a nonbreaking hyphen by pressing **Ctrl+Shift+_**.                                                                                                     |
+| Keep the last word of a paragraph with the word that precedes it |                                                                                                   Insert a nonbreaking space by pressing **Ctrl+Shift+Space**.                                                                                                   |
+|                Control widows and orphans in Word                | Select a paragraph formatted with Normal style. On the context menu, select **Styles > Apply Styles**. In the **Apply Styles** pane, select **Modify**. Select **Format > Paragraph**. On the **Line and page breaks** tab, select **Widow/Orphan control**. |
+
+## Don't compress line spacing
+
+The amount of vertical space between lines of text in a paragraph, called *line spacing,*
+can help or hinder reading. Adequate line spacing helps readers
+find their way from the end of one line to the beginning of the next. 
+
+If
+you’re using a template, don’t change the line spacing. If you’re
+not, ask a designer for advice if you can.
+
+If you
+need to modify line spacing later, change it in the styles, not in
+individual paragraphs, so spacing remains consistent throughout
+the content. Never reduce line spacing to fit more text on a slide or page. Edit the text instead.
+
+| **Font size** | **Line spacing** |
+|---|---|
+| Body text (up to 14 points) | 120% minimum |
+| Subheadings (14–36 points) | 110% minimum |
+| Headings (36 points or larger) | 120% maximum |
+## Formatting common text elements
+
+Consistent text formatting helps readers locate and interpret information. Follow these formatting conventions for common text elements.
+
+For information about referring to UI elements, see Formatting text in instructions. For guidance on referring to these elements in developer contexts, see Formatting developer text elements.
+
+**See also** Capitalization Procedures and instructions <br /><br />
+
+|                 **Element**                  |                                                                                           **Convention**                                                                                            |                                                                      **Example**                                                                      |
+|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+|              **Database names**              |                                                                         Bold. The capitalization of database names varies.                                                                          |                                                                 **Contoso** database                                                                  |
+|                 **Emphasis**                 |                                                                      It's OK to use italic formatting sparingly for emphasis.                                                                       | Cybercriminals might call you and claim to be from Microsoft. Be aware that Microsoft will *never* call you to charge for security or software fixes. |
+|              **Error messages**              |                                                                                   Sentence-style capitalization. Enclose in quotation marks when referencing error messages in text.                          |                                                        We can't find a scanner. <br />  Hmm … looks like that's a broken link. <br /> If you see the error message, "Check scanner status and try again," use Windows Update to check for the latest drivers for your device.                                                       |
+|             **File attributes**              |                                                                                           All lowercase.                                                                                            |                         hidden<br />system<br />read-only<br />To remove the hidden attribute from all files in a folder ....                         |
+|           **File name extensions**           |                                                                                           All lowercase.                                                                                            |                                                                    .mdb<br />.doc                                                                     |
+|                **File names**                |                                                       Title-style capitalization. It's OK to use internal caps in file names for readability.                                                       |                                                         My Taxes for 2016<br />MyTaxesFor2016                                                         |
+|        **Folder and directory names**        |                                        Sentence-style capitalization. It's OK to use internal capital letters in folder and directory names for readability.                                        |                                             Vacation and sick pay<br />MyFiles\Accounting\Payroll\VacPay                                              |
+|   **Mathematical constants and variables**   |                                                                                               Italic.                                                                                               |                                                                    *a2 + b2  = c2*                                                                    |
+|                **New terms**                 |                                                     Italicize the first mention of a new term if you're going to define it immediately in text.                                                     |                                         Microsoft Exchange consists of both *server* and *client* components.                                         |
+|                  **Ports**                   |                                                                                           All uppercase.                                                                                            |                                                                         LPT1                                                                          |
+| **Products, services, apps, and trademarks** | Usually title-style capitalization. Check the Microsoft trademark list for capitalization of trademarked names. |                        Microsoft Arc Touch Mouse<br />Microsoft Word<br />Surface Pro <br />Notepad <br />Network Connections                         |
+|                 **UI text or strings**                  |                                                                                   Sentence-style capitalization.                                                                                    |                                                        Find on page <br /> Read aloud <br /> Hide selected items                                       |
+|                   **URLs**                   |              All lowercase for complete URLs. If necessary, line-break long URLs before a slash. Don't hyphenate.<br />**See also** URLs and web addresses              |                                                  www<span></span>.microsoft.com<br />msdn.microsoft.com/downloads                                                  |
+
+## Formatting titles
+
+In general, use sentence-style casing (that is, only capitalize the first word of a title, like at the beginning of a sentence), as this makes content more readable and ensures better localizability.
+
+Use bold font instead of italics for titles to enhance readability and accessibility.
+
+There are some notable exceptions to sentence-casing. These include:
+
++ The titles of books (including e-books), white papers, and reports: 
+
+**Unraveling HTML5, CSS3, and JavaScript**
+
+**Backup and Recovery Overview for Azure Customers**
+
++ Games: 
+
+Some of the top games on Microsoft Store include **Sea of Thieves 2023 Edition** and **Stardew Valley**.
+
++ Events and webinars: 
+
+The **Microsoft Envision AI Tour** is for decision-makers and developers, with events curated for each audience.
+
+**OneNote Best Practices for Educators and Students with Mike Tholfsen**
+
+**See also** Capitalization, Headings
diff --git a/.claude/skills/microsoft-writing-style-guide/references/word-choice.md b/.claude/skills/microsoft-writing-style-guide/references/word-choice.md
new file mode 100755
index 000000000..1518d2add
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/references/word-choice.md
@@ -0,0 +1,188 @@
+# Word choice
+
+## Word choice
+
+To improve readability and comprehension, choose your words wisely and use them consistently. If you mean the same thing, use the same word.
+
+This section provides tips for choosing the right words for the job:
+
+  - Use contractions
+  - Use simple words, concise sentences
+  - Don’t use common words in new ways
+  - Use technical terms carefully
+  - Avoid jargon
+  - Use US spelling and avoid non-English words
+
+For information about specific words and phrases, refer to the A–Z word list and *Merriam-Webster Dictionary*.
+
+## Use contractions
+
+Write using the same, everyday words you use in conversation.
+
+  - Use common contractions, such as *it’s, you’re, that's,* and *don’t,* to create a friendly, informal tone.  
+  
+  - Don't mix contractions and their spelled-out equivalents in UI text. For example, don’t use *can’t* and *cannot* in the same UI.  
+  
+  - Never form a contraction from a noun and a verb, such as *Microsoft’s developing a lot of new cloud services.*  
+  
+  - Avoid ambiguous or awkward contractions, such as *there’d, it’ll,* and *they’d.*
+
+## Use simple words, concise sentences
+
+Make every word count. Concise, clear sentences save space, are easy to understand, and facilitate scanning. Use simple words with precise meanings, and remove words that don’t add substance. Use your judgment to avoid sounding abrupt or unfriendly.
+
+- Choose simple verbs without modifiers. Whenever you can, avoid weak or vague verbs, such as *be, have, make,* and *do.*   
+**Examples**
+
+  | **Use this** |         **Not this**          |
+  |--------------|-------------------------------|
+  |     use      |     utilize, make use of      |
+  |    remove    | extract, take away, eliminate |
+  |     tell     |       inform, let know        |
+
+- Don’t use two or three words when one will do.  
+**Examples**
+
+  | **Use this** |        **Not this**        |
+  |--------------|----------------------------|
+  |      to      | in order to, as a means to |
+  |     also     |        in addition         |
+  |   connect    |   establish connectivity   |
+
+- Whenever possible, choose words that have one clear meaning.  
+**Examples**
+
+  |                    **Use this**                     |                   **Not this**                    |
+  |-----------------------------------------------------|---------------------------------------------------|
+  | *Because* you created the table, you can change it. | *Since* you created the table, you can change it. |
+
+- Omit unnecessary adverbs—words that describe how, when, or where.
+Unless they're important to the meaning of a statement, leave them out. **Examples** quite very quickly easily effectively
+
+- Use one term consistently to represent one concept.  
+
+- Use words that can be both nouns and verbs carefully—*file, post, mark, screen, record,* and *report,* for example. Use the sentence structure and context to eliminate ambiguity.
+
+## Don't use common words in new ways
+
+Most people know the common definition of words—usually the one that appears first in the dictionary. Refer to *Merriam-Webster Dictionary* if you have any doubts. Use words in the most familiar sense, or define them if you can’t.
+
+  - Don’t create a new word from an existing word.  
+**Example** Don’t use *bucketize* to mean *group*.
+    
+  - Don't apply a new meaning to an ordinary word.  
+**Example** Don’t use *graveyard* to mean *archive*.
+    
+  - Be
+careful with common words that have industry-specific uses. Assume customers know the common definition of the word, not the industry-specific definition. If you must use the industry-specific definition, define the word in context. **Writing tip** Sometimes industry-specific usage, such as *hacker*, becomes part of everyday speech. Know your customer and the language they use. When in doubt, use a simple word with a well-understood meaning.
+    
+  - Don’t use verbs as nouns or nouns as verbs.  
+**Examples**
+    
+    |**Use this**|**Not this**|
+    |--|--|
+    |affect performance|impact performance|
+    |download the paper|get the download|
+    |respond to the request|respond to the ask|
+
+## Use technical terms carefully
+
+Technical terms come in a variety of shapes and sizes. Sometimes they're everyday words that are given new meanings, like *cloud, batch,* or *dashboard*. Other times, common words are combined to create technical terms, like *telemedicine* or *email.* Over
+time, some technical terms become widely understood, but before
+that happens, they can be confusing to people who aren't
+familiar with them. Use technical terms when they're the clearest way to communicate your message, but use them with care. 
+
+## Use common words whenever possible
+
+Don't use a technical term when an everyday term will do. For example, don't use *rip* to refer to copying files from a CD if you can use *copy* instead.
+
+## Don’t assume everyone will understand technical terms
+
+When you must use technical terms for precise communication, define them in context.
+
+## Use technical terms consistently
+
+When you've decided to use a technical term, use that term consistently across products and services, tools, websites, and marketing communications. Aim for one term, one concept.
+
+## Use industry-specific terms for professional audiences
+
+Many
+industries and professions have their own terminology: banking,
+healthcare, construction, IT, and project management, for example.
+
+If
+you're writing for an industry or profession, use the words your
+audience uses. First, verify Microsoft and industry usage. Check
+the A–Z word list and *[Merriam-Webster Dictionary](https://merriam-webster.com/).* Then look to authoritative industry resources: 
+
+  - Terminology websites, such as [Webopedia.com](https://www.webopedia.com/), and [Whatis.TechTarget.com](https://whatis.techtarget.com/).  
+  
+  - Industry standard sites, such as [W3C](https://www.w3.org/standards/xml) and [IEEE](https://www.ieee.org/index.html).  
+  
+  - Industry research organizations, such as Forrester Research and Gartner.  
+  
+  - Domain books, such as the *[PMI Lexicon of Project Management Terms](https://www.pmi.org/PMBOK-Guide-and-Standards/PMI-lexicon.aspx)* or the [FDIC List of Abbreviations and Glossary of Terms (Appendix B)](https://www.fdic.gov/bank/historical/managing/documents/history-consolidated.pdf).
+
+## Don’t create a new term if one already exists
+
+Don't
+create a new term if an existing one serves your purpose. If you
+must create a new term, verify that it isn’t already being
+used to mean something else.  
+
+## Research emerging terminology
+
+Technology
+changes at light speed, and customers expect us to use the latest
+technical terms. But it's crucial to use them correctly and
+consistently across our products, services, documents, packaging, and
+marketing. Before you adopt a new term in your content, find
+out whether other groups are using it, and how. 
+
+  - First, check *[Merriam-Webster Dictionary](https://merriam-webster.com/).*
+  
+  - Research the term on *edited* industry websites, such as [Forrester Research](https://www.forrester.com/home/), [Gartner](https://www.gartner.com/technology/home.jsp), [CNET](https://www.cnet.com/), [Recode](https://www.recode.net/), [Mashable](https://mashable.com/), [TechCrunch](https://techcrunch.com/), [WIRED](https://www.wired.com/), [Gizmodo](https://gizmodo.com/), [HuffPost Tech](https://www.huffingtonpost.com/tech/), and [Engadget](https://www.engadget.com/). For emerging industry terminology, check reputable business and trade websites, such as [Fast Company](https://www.fastcompany.com/), [Entrepreneur](https://www.entrepreneur.com/magazine/index.html), [Business Insider](https://www.businessinsider.com/), [Healthcare IT News](https://www.healthcareitnews.com/), [American Banker](https://www.americanbanker.com/bank-technology/), and [GameSpot](https://www.gamespot.com/news/).
+## Avoid jargon
+
+In the right context, for a particular audience, jargon serves as shorthand for well-understood concepts. But for less technical audiences, jargon can impede understanding.
+
+Don’t use jargon if:
+
+  - You can use a more familiar term, such as *symbol* instead of *glyph.*  
+  
+  - The term is familiar to only a small segment of your readers.  
+  
+  - The term isn't specific to software, networking, cloud services, and so on. 
+
+Avoid business, marketing, and journalistic jargon, such as using *leverage* to mean *take advantage of.*
+
+## Testing for jargon
+
+Differentiating jargon from technical terminology is tricky. First, check the A–Z word list. If you don’t find the term, the following checklist can help.
+
+  - If you think a term is jargon, it probably is.  
+  
+  - If it’s an acronym or abbreviation, it may be jargon. Spell it out for clarity.  
+  
+  - If a reviewer questions your use of a term, it may be jargon.  
+  
+  - If the term is used in *The Wall Street Journal* or *The New York Times,* or in general-interest magazines, such as *Time* or *Newsweek,* it might be appropriate for some audiences.  
+  
+  - If the term is used in technical periodicals such as *CNET* or *Recode,* it's probably OK to use for technical audiences.
+
+## Use US spelling and avoid non-English words
+
+When the spelling of English words varies by locale, use the US spelling. For example, use *license,* not *licence.*
+
+Avoid non-English words or phrases, such as *de facto* or *ad hoc*.
+
+Avoid Latin abbreviations for common English phrases.
+
+**Exception** It’s OK to use *etc.,* in situations where space is limited. Otherwise, see and so on for alternatives.
+
+| **Use this** | **Instead of this** |
+|--------------|---------------------|
+| for example  |        e.g.         |
+|   that is    |        i.e.         |
+|    namely    |        viz.         |
+|  therefore   |        ergo         |
diff --git a/.claude/skills/microsoft-writing-style-guide/scripts/validate.py b/.claude/skills/microsoft-writing-style-guide/scripts/validate.py
new file mode 100755
index 000000000..706425869
--- /dev/null
+++ b/.claude/skills/microsoft-writing-style-guide/scripts/validate.py
@@ -0,0 +1,388 @@
+#!/usr/bin/env python3
+"""Validate the Microsoft Writing Style Guide skill without network access."""
+
+from __future__ import annotations
+
+import argparse
+import csv
+import hashlib
+import json
+import re
+import shutil
+import sys
+import tempfile
+import unicodedata
+from pathlib import Path
+
+
+ROOT = Path(__file__).resolve().parents[1]
+PINNED_COMMIT = "c78a330b932812a342be2ebca0ec8bc3d01fbac2"
+TERM_COUNT = 870
+TERM_SHA256 = "aad58a61c045534da05987d34f12a011c17bdc9f19552e538ea768f9a374c212"
+PATH_SHA256 = "e18b479add127d835865d787c2d86ee1ab5f2ca59fa7810d3f8e2cb5b90b76c2"
+CANONICAL_REFERENCES = {
+    "a-z-term-list-a-c.md",
+    "a-z-term-list-d-g.md",
+    "a-z-term-list-h-m.md",
+    "a-z-term-list-n-r.md",
+    "a-z-term-list-s-u.md",
+    "a-z-term-list-v-z.md",
+    "accessibility-and-bias-free-communication.md",
+    "checklists.md",
+    "content-planning-and-process.md",
+    "developer-and-bot-content.md",
+    "global-communications.md",
+    "grammar-and-parts-of-speech.md",
+    "keys-and-keyboard-shortcuts.md",
+    "numbers-acronyms-capitalization.md",
+    "punctuation.md",
+    "scannable-content-and-procedures.md",
+    "term-collections-numbers-symbols.md",
+    "text-formatting.md",
+    "word-choice.md",
+}
+
+
+def normalize(value: str) -> str:
+    value = unicodedata.normalize("NFKC", value).lower()
+    value = re.sub(r"<[^>]*>", "", value)
+    value = re.sub(r"\\([#*_-])", r"\1", value)
+    value = (
+        value.replace("’", "'")
+        .replace("‘", "'")
+        .replace("“", '"')
+        .replace("”", '"')
+    )
+    value = re.sub(r"[*_`]", "", value)
+    return re.sub(r"\s+", " ", value).strip()
+
+
+def digest(values: list[str]) -> str:
+    payload = "\n".join(sorted(values)) + "\n"
+    return hashlib.sha256(payload.encode()).hexdigest()
+
+
+def validate_skill(root: Path) -> list[str]:
+    errors: list[str] = []
+    skill_path = root / "SKILL.md"
+    references = root / "references"
+    index_path = references / "term-index.tsv"
+    manifest_path = references / "source-manifest.md"
+    eval_path = root / "evals" / "evals.json"
+    required_distribution_files = {
+        "LICENSE": "MIT License",
+        "LICENSE-CONTENT": "Attribution 4.0 International",
+        "NOTICE.md": "MicrosoftDocs/microsoft-style-guide-pr",
+    }
+
+    if not skill_path.is_file():
+        return ["SKILL_MISSING: SKILL.md is missing"]
+
+    skill = skill_path.read_text(encoding="utf-8")
+    frontmatter = re.match(r"\A---\n(.*?)\n---\n", skill, re.S)
+    if not frontmatter:
+        errors.append("SKILL_FRONTMATTER: valid YAML frontmatter is missing")
+    else:
+        metadata = frontmatter.group(1)
+        if not re.search(r"^name: microsoft-writing-style-guide$", metadata, re.M):
+            errors.append("SKILL_NAME: frontmatter name is incorrect")
+        if not re.search(r"^description: .+", metadata, re.M):
+            errors.append("SKILL_DESCRIPTION: frontmatter description is missing")
+
+    if len(skill.splitlines()) > 250:
+        errors.append("SKILL_LENGTH: SKILL.md exceeds 250 lines")
+
+    for filename, expected in required_distribution_files.items():
+        path = root / filename
+        if not path.is_file():
+            errors.append(f"DISTRIBUTION_FILE_MISSING: {filename}")
+        elif expected not in path.read_text(encoding="utf-8"):
+            errors.append(f"DISTRIBUTION_FILE_CONTENT: {filename}")
+
+    required_skill_text = (
+        "## Choose a mode",
+        "## Source precedence",
+        "## Load only what you need",
+        "### Write",
+        "### Rewrite",
+        "### Review",
+        "## Guardrails",
+    )
+    for expected in required_skill_text:
+        if expected not in skill:
+            errors.append(f"SKILL_WORKFLOW: missing {expected!r}")
+
+    markdown_references = {
+        path.name
+        for path in references.glob("*.md")
+        if path.name != "source-manifest.md"
+    }
+    if markdown_references != CANONICAL_REFERENCES:
+        missing = sorted(CANONICAL_REFERENCES - markdown_references)
+        unexpected = sorted(markdown_references - CANONICAL_REFERENCES)
+        errors.append(
+            f"REFERENCE_INVENTORY: missing={missing}, unexpected={unexpected}"
+        )
+
+    for path in [skill_path, *sorted(references.glob("*.md"))]:
+        text = path.read_text(encoding="utf-8")
+        if re.search(r"!INCLUDE\s*\[", text):
+            errors.append(f"UNRESOLVED_INCLUDE: {path.relative_to(root)}")
+        if re.search(r"!(?!\[)(?:image|screenshot)\b", text, re.I):
+            errors.append(f"UNRESOLVED_IMAGE: {path.relative_to(root)}")
+        if "ms.topic: include" in text:
+            errors.append(f"INCLUDE_FRONTMATTER: {path.relative_to(root)}")
+
+    if not manifest_path.is_file():
+        errors.append("MANIFEST_MISSING: references/source-manifest.md is missing")
+    else:
+        manifest = manifest_path.read_text(encoding="utf-8")
+        for expected in (
+            PINNED_COMMIT,
+            "2026-08-22",
+            "| A-Z term pages | 870 |",
+            "| Shared include files | 45 |",
+        ):
+            if expected not in manifest:
+                errors.append(f"MANIFEST_CONTENT: missing {expected!r}")
+
+    rows: list[dict[str, str]] = []
+    if not index_path.is_file():
+        errors.append("TERM_INDEX_MISSING: references/term-index.tsv is missing")
+    else:
+        with index_path.open(encoding="utf-8", newline="") as stream:
+            reader = csv.DictReader(stream, delimiter="\t")
+            if reader.fieldnames != ["term", "file", "source_path"]:
+                errors.append(
+                    f"TERM_INDEX_HEADER: found {reader.fieldnames!r}"
+                )
+            else:
+                rows = list(reader)
+
+    if rows:
+        terms = [normalize(row["term"]) for row in rows]
+        source_paths = [row["source_path"] for row in rows]
+        if len(rows) != TERM_COUNT:
+            errors.append(f"TERM_COUNT: expected {TERM_COUNT}, found {len(rows)}")
+        if len(set(terms)) != len(terms):
+            errors.append("TERM_DUPLICATE: normalized term identities aren't unique")
+        if len(set(source_paths)) != len(source_paths):
+            errors.append("TERM_SOURCE_DUPLICATE: source paths aren't unique")
+        if digest(terms) != TERM_SHA256:
+            errors.append("TERM_IDENTITY_HASH: authoritative term identities differ")
+        if digest(source_paths) != PATH_SHA256:
+            errors.append("TERM_PATH_HASH: authoritative source paths differ")
+
+        heading_cache: dict[str, set[str]] = {}
+        for row in rows:
+            filename = row["file"]
+            target = references / filename
+            if not target.is_file():
+                errors.append(f"TERM_TARGET_FILE: {filename!r} doesn't exist")
+                continue
+            if filename not in heading_cache:
+                heading_cache[filename] = {
+                    normalize(heading)
+                    for heading in re.findall(
+                        r"^### (.+)$", target.read_text(encoding="utf-8"), re.M
+                    )
+                }
+            if normalize(row["term"]) not in heading_cache[filename]:
+                errors.append(
+                    f"TERM_TARGET_HEADING: {row['term']!r} isn't in {filename}"
+                )
+
+    sentinels = {
+        references / "a-z-term-list-n-r.md": (
+            "### plugin",
+            "In generative AI experiences",
+            "use one word (no hyphen)",
+        ),
+        references / "a-z-term-list-v-z.md": (
+            "### visit",
+            "More of a suggestion than a required action",
+            "staying for a while and browsing around",
+        ),
+        skill_path: (
+            "Omit periods and colons from most titles, headings, and short UI text",
+        ),
+    }
+    for path, expected_values in sentinels.items():
+        if not path.is_file():
+            errors.append(
+                f"FRESHNESS_SENTINEL: {path.relative_to(root)} is missing"
+            )
+            continue
+        text = path.read_text(encoding="utf-8")
+        for expected in expected_values:
+            if expected not in text:
+                errors.append(
+                    f"FRESHNESS_SENTINEL: {path.relative_to(root)} lacks {expected!r}"
+                )
+
+    if not eval_path.is_file():
+        errors.append("EVAL_MISSING: evals/evals.json is missing")
+    else:
+        try:
+            data = json.loads(eval_path.read_text(encoding="utf-8"))
+        except json.JSONDecodeError as exc:
+            errors.append(f"EVAL_JSON: {exc}")
+        else:
+            if not isinstance(data, dict):
+                errors.append("EVAL_SHAPE: evals/evals.json root isn't an object")
+            else:
+                if data.get("skill_name") != "microsoft-writing-style-guide":
+                    errors.append("EVAL_SKILL_NAME: skill_name is incorrect")
+                evaluations = data.get("evals")
+                if not isinstance(evaluations, list) or len(evaluations) < 12:
+                    errors.append("EVAL_COUNT: at least 12 evaluations are required")
+                else:
+                    ids = []
+                    for position, evaluation in enumerate(evaluations, start=1):
+                        if not isinstance(evaluation, dict):
+                            errors.append(
+                                f"EVAL_SHAPE: evaluation {position} isn't an object"
+                            )
+                            continue
+                        ids.append(evaluation.get("id"))
+                        for key in ("prompt", "expected_output"):
+                            if (
+                                not isinstance(evaluation.get(key), str)
+                                or not evaluation[key]
+                            ):
+                                errors.append(
+                                    f"EVAL_SHAPE: evaluation {position} has invalid {key}"
+                                )
+                        if not isinstance(evaluation.get("files"), list):
+                            errors.append(
+                                f"EVAL_SHAPE: evaluation {position} has invalid files"
+                            )
+                    if ids != list(range(1, len(evaluations) + 1)):
+                        errors.append("EVAL_IDS: IDs must be unique and sequential")
+
+    return errors
+
+
+def run_self_check(root: Path) -> list[str]:
+    failures: list[str] = []
+    include_fixtures = {
+        "canonical": "[!INCLUDE [self-check](../includes/self-check.md)]",
+        "blockquoted": "> [!INCLUDE [self-check](../includes/self-check.md)]",
+    }
+    for name, fixture in include_fixtures.items():
+        with tempfile.TemporaryDirectory() as directory:
+            candidate = Path(directory) / "skill"
+            shutil.copytree(root, candidate)
+            checklist = candidate / "references" / "checklists.md"
+            checklist.write_text(
+                checklist.read_text(encoding="utf-8") + f"\n{fixture}\n",
+                encoding="utf-8",
+            )
+            if not any(
+                error.startswith("UNRESOLVED_INCLUDE")
+                for error in validate_skill(candidate)
+            ):
+                failures.append(
+                    f"SELF_CHECK_INCLUDE: {name} include wasn't detected"
+                )
+
+    with tempfile.TemporaryDirectory() as directory:
+        candidate = Path(directory) / "skill"
+        shutil.copytree(root, candidate)
+        checklist = candidate / "references" / "checklists.md"
+        checklist.write_text(
+            checklist.read_text(encoding="utf-8")
+            + "\n!Screenshot unresolved image placeholder\n",
+            encoding="utf-8",
+        )
+        if not any(
+            error.startswith("UNRESOLVED_IMAGE")
+            for error in validate_skill(candidate)
+        ):
+            failures.append(
+                "SELF_CHECK_IMAGE: unresolved image placeholder wasn't detected"
+            )
+
+    with tempfile.TemporaryDirectory() as directory:
+        candidate = Path(directory) / "skill"
+        shutil.copytree(root, candidate)
+        (candidate / "LICENSE").unlink()
+        if not any(
+            error.startswith("DISTRIBUTION_FILE_MISSING")
+            for error in validate_skill(candidate)
+        ):
+            failures.append(
+                "SELF_CHECK_LICENSE: missing distribution license wasn't detected"
+            )
+
+    with tempfile.TemporaryDirectory() as directory:
+        candidate = Path(directory) / "skill"
+        shutil.copytree(root, candidate)
+        (candidate / "references" / "a-z-term-list-n-r.md").unlink()
+        if not any(
+            error.startswith("FRESHNESS_SENTINEL")
+            for error in validate_skill(candidate)
+        ):
+            failures.append(
+                "SELF_CHECK_SENTINEL: missing sentinel file wasn't detected"
+            )
+
+    with tempfile.TemporaryDirectory() as directory:
+        candidate = Path(directory) / "skill"
+        shutil.copytree(root, candidate)
+        (candidate / "evals" / "evals.json").write_text("[]\n", encoding="utf-8")
+        if not any(
+            error.startswith("EVAL_SHAPE") for error in validate_skill(candidate)
+        ):
+            failures.append(
+                "SELF_CHECK_EVAL_SHAPE: non-object eval root wasn't detected"
+            )
+
+    with tempfile.TemporaryDirectory() as directory:
+        candidate = Path(directory) / "skill"
+        shutil.copytree(root, candidate)
+        index = candidate / "references" / "term-index.tsv"
+        lines = index.read_text(encoding="utf-8").splitlines()
+        index.write_text(
+            "\n".join([lines[0], *lines[2:]]) + "\n",
+            encoding="utf-8",
+        )
+        errors = validate_skill(candidate)
+        if not any(error.startswith("TERM_COUNT") for error in errors):
+            failures.append("SELF_CHECK_COUNT: missing index row wasn't detected")
+        if not any(error.startswith("TERM_PATH_HASH") for error in errors):
+            failures.append("SELF_CHECK_HASH: changed authoritative set wasn't detected")
+
+    return failures
+
+
+def main() -> int:
+    parser = argparse.ArgumentParser()
+    parser.add_argument(
+        "--self-check",
+        action="store_true",
+        help="Verify that critical failure detectors trigger",
+    )
+    args = parser.parse_args()
+
+    errors = validate_skill(ROOT)
+    if not errors and args.self_check:
+        errors = run_self_check(ROOT)
+
+    if errors:
+        for error in errors:
+            print(f"ERROR {error}")
+        return 1
+
+    if args.self_check:
+        print("PASS validator self-check")
+    else:
+        print(
+            "PASS skill validation: "
+            "45 includes resolved, 870 authoritative terms indexed"
+        )
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/AGENTS.md b/AGENTS.md
index e96e4a56a..20e915af7 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -104,7 +104,7 @@ Key patterns:
 
 ### PowerShell Module Structure
 
-- **`Public/`** - User-facing cmdlets (Get-_, Set-_, New-\*, etc.)
+- **`Public/`** - User-facing cmdlets (Get-*, Set-*, New-\*, etc.)
 - **`Private/`** - Internal utilities and helpers
 - **`Tests/Unit/`** - Pester unit tests with mocking
 - **`Tests/Integration/`** - End-to-end Azure integration tests
@@ -209,7 +209,7 @@ This repository supports production infrastructure managing significant revenue.
 ### Coding Standards
 
 - Always follow the content and coding standards defined in `docs-wiki/Coding-guidelines.md`
-- Content (text strings): Follow the Microsoft style guide and always use sentence casing except for proper nouns
+- Content (text strings): Always use the Microsoft style guide skill `.claude/skills/microsoft-writing-style-guide/SKILL.md` and always use sentence casing except for proper nouns
 - Bicep: Follow Azure Bicep style guide
 - PowerShell: Use PowerShell best practices and approved verbs
 - KQL: Never use `tolower()`/`toupper()` in comparison position — KQL string operators are already case-insensitive (`_cs` variants are the case-sensitive ones). Use `has` for whole terms and path phrases, `=~`/`!~` for equality, `in~`/`has_any` for sets. Reserve `contains` for genuine substring matching (needle fused inside a larger token) and justify it in the allowlist in `src/powershell/Tests/Unit/HubsKqlOperators.Tests.ps1`, which enforces both rules on every PR. See the KQL section of `docs-wiki/Coding-guidelines.md`