Is your feature request related to a problem? Please describe.
I would like a CSV dictionary for Grammarly containing Chrome DevTools actions, advanced technical terminology, and common
Coverage-20260911T182120.json
programming terms and code-related keywords.
A clear and concise description of what you want to happen. Include any alternative solutions you've considered.
Here’s a complete version for the GitHub issue:
Title
Provide a CSV dictionary of .NET and Chrome DevTools terminology for Grammarly
Is your feature request related to a problem? Please describe.
Grammarly often flags valid programming terminology, command names, API names, and Chrome DevTools actions as spelling or writing errors. This creates unnecessary suggestions when writing technical documentation, bug reports, code reviews, and development notes related to .NET and browser debugging.
Describe the solution you’d like
Please provide an English CSV dictionary containing:
- .NET runtime, SDK, CLI, and VS Code extension terminology
- Chrome DevTools actions and debugging terminology
- Common programming keywords and code-related terms
- Framework, API, package, and tool names
- Frequently used abbreviations and technical acronyms
The CSV should be formatted so its terms can be imported into Grammarly or adapted for other spelling and proofreading tools.
Additional context
A maintained technical dictionary would reduce false spelling alerts and make Grammarly more useful for developers working with .NET, VS Code, and Chrome DevTools.
Describe the solution you'd like
I would like the extension to provide a downloadable English CSV dictionary containing .NET terminology, Chrome DevTools actions, debugging commands, programming keywords, API names, technical acronyms, and other code-related terms. The CSV should use a simple format compatible with Grammarly’s custom dictionary or be easy to convert for import.
Additional context
This dictionary would help developers avoid false spelling and grammar alerts when writing .NET documentation, GitHub issues, debugging notes, and technical reports. It would be especially useful when discussing the VS Code Runtime Extension alongside Chrome DevTools. The CSV could be maintained by the community as new APIs, commands, tools, and technical terms are introduced.
Is your feature request related to a problem? Please describe.
I would like a CSV dictionary for Grammarly containing Chrome DevTools actions, advanced technical terminology, and common
Coverage-20260911T182120.json
programming terms and code-related keywords.
A clear and concise description of what you want to happen. Include any alternative solutions you've considered.
Here’s a complete version for the GitHub issue:
Title
Provide a CSV dictionary of .NET and Chrome DevTools terminology for Grammarly
Is your feature request related to a problem? Please describe.
Grammarly often flags valid programming terminology, command names, API names, and Chrome DevTools actions as spelling or writing errors. This creates unnecessary suggestions when writing technical documentation, bug reports, code reviews, and development notes related to .NET and browser debugging.
Describe the solution you’d like
Please provide an English CSV dictionary containing:
The CSV should be formatted so its terms can be imported into Grammarly or adapted for other spelling and proofreading tools.
Additional context
A maintained technical dictionary would reduce false spelling alerts and make Grammarly more useful for developers working with .NET, VS Code, and Chrome DevTools.
Describe the solution you'd like
I would like the extension to provide a downloadable English CSV dictionary containing .NET terminology, Chrome DevTools actions, debugging commands, programming keywords, API names, technical acronyms, and other code-related terms. The CSV should use a simple format compatible with Grammarly’s custom dictionary or be easy to convert for import.
Additional context
This dictionary would help developers avoid false spelling and grammar alerts when writing .NET documentation, GitHub issues, debugging notes, and technical reports. It would be especially useful when discussing the VS Code Runtime Extension alongside Chrome DevTools. The CSV could be maintained by the community as new APIs, commands, tools, and technical terms are introduced.