This rule enforces Microsoft's style guidelines by flagging specific words and phrases that should be avoided in technical documentation. The rule helps maintain consistency, clarity, and professionalism in writing by eliminating problematic or outdated terminology.
The motivation behind this rule is that certain terms can be ambiguous, redundant, or may not align with modern technical writing best practices. Using clearer, more precise alternatives helps improve readability and maintains a professional tone throughout the documentation.
Examples
The rule flags the following terms (with suggested alternatives):
- "abortion" (consider using "cancel" or "stop" instead)
- "and so on" (be specific or use "etc.")
- "and/or" (use either "and" or "or", not both)
- "app developer" / "application developer" (use "developer" instead)
- "application file" (use "file" or be more specific)
- "application program" (use "app" or "program")
- "as well as" (use "and" instead)
- "backbone" (use more precise technical terminology)
- "backend" (use "back end" or be more specific)
When these terms appear in text (regardless of case), Vale will flag them as errors and suggest avoiding their use.