Terminology and Brand Name Consistency Rule

This rule enforces consistent capitalization and styling of technical terms, brand names, and common phrases in technical documentation. Maintaining consistent terminology is crucial for professionalism, clarity, and alignment with official brand guidelines. It helps ensure that product names, technologies, and technical terms are written correctly throughout the documentation, enhancing readability and credibility.

Examples:

• ❌ "I'm using github for version control" → ✅ "I'm using GitHub for version control"
• ❌ "The typescript code needs review" → ✅ "The TypeScript code needs review"
• ❌ "We built this with javascript and css" → ✅ "We built this with JavaScript and CSS"
• ❌ "Open it in VSCode" → ✅ "Open it in VS Code"
• ❌ "You can find the demo in codesandbox" → ✅ "You can find the demo in CodeSandbox"
• ❌ "This is a client side solution" → ✅ "This is a client-side solution"
• ❌ "A common use-case for this" → ✅ "A common use case for this"

The rule is case-insensitive and handles various common misspellings and incorrect formatting of technical terms, ensuring they match official styling guidelines (like npm being lowercase, JavaScript having a capital 'J' and 'S', etc.).