Feature Request - Add built-in spell checking to GitHub’s Markdown editor

[biswalneelam]

Select Topic Area

Product Feedback

Body

Problem

GitHub’s Markdown editor currently does not provide a reliable, built-in spell-checking experience when writing content such as issues, pull request descriptions, READMEs, discussions, or comments.

As a result, users often need to:

• Rely on inconsistent browser spell-check behavior, or
• Copy content into external editors just to catch spelling mistakes.

This breaks writing flow and makes it easy for simple errors to slip into documentation and discussions.

This feature request has already been discussed by multiple community members here:
https://github.com/orgs/community/discussions/138955

Use case

GitHub is not only used by developers writing code, but also by:

• Documentation writers
• Open-source contributors
• Community maintainers
• Non-native English speakers
• Product managers and designers contributing text content

For these users, clear and error-free written communication is essential, and spelling mistakes reduce clarity and professionalism.

Proposed solution

Provide an optional, built-in spell-checking feature in GitHub’s Markdown editor that:

• Highlights misspelled words while typing
• Offers correction suggestions (similar to standard text editors)
• Respects user language preferences
• Ignores code blocks and inline code by default

This could be a lightweight enhancement integrated directly into the existing editor UI.

Why this is needed

• Improves the quality and clarity of documentation and discussions
• Reduces friction caused by switching between tools
• Makes GitHub more inclusive and user-friendly for non-technical contributors
• Aligns GitHub’s writing experience with modern content platforms

Additional context

This request has already been discussed by multiple community members here:
https://github.com/orgs/community/discussions/138955

The discussion highlights real-world pain points and repeated interest in this capability.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[biswalneelam]

This feature request is based on recurring community feedback and would significantly improve the writing experience for documentation, issues, and discussions across GitHub.