Skip to content

docs: fix typos in CONTRIBUTING.md#234

Open
Karushna wants to merge 1 commit into
DhanushNehru:mainfrom
Karushna:fix/contributing-typos
Open

docs: fix typos in CONTRIBUTING.md#234
Karushna wants to merge 1 commit into
DhanushNehru:mainfrom
Karushna:fix/contributing-typos

Conversation

@Karushna
Copy link
Copy Markdown

PR Fixes

  • Fixed typos in CONTRIBUTING.md
  • Improved grammar and readability
  • Minor documentation cleanup

Checklist before requesting a review

  • I have pull latest changes from main branch
  • I have tested the changes locally
  • I have run npm run lint:fix locally
  • I have performed a self-review of my code
  • I assure there is no similar/duplicate pull request regarding same issue

@vercel
Copy link
Copy Markdown

vercel Bot commented May 16, 2026

@Karushna is attempting to deploy a commit to the Dhanush Nehru's projects Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates CONTRIBUTING.md to clean up typo and grammar issues in contributor guidance.

Changes:

  • Improves wording in the getting-started and bug-reporting sections.
  • Corrects “Asumming” to “Assuming” in bug and enhancement reporting guidelines.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread CONTRIBUTING.md

1. Perform a cursory search [here](https://github.com/DhanushNehru/CustomCodeEditor/issues) for whether the issue has already been reported.
2. Asumming no, please be as detailed as possible in describing the issue.
2. Assuming no, please be as detailed as possible in describing the issue.
Comment thread CONTRIBUTING.md
1. Perform a cursory search [here](https://github.com/DhanushNehru/CustomCodeEditor/issues) for whether the enhancement has already been suggested.
2. If it has already been suggested, add a comment to **that issue** instead of opening a new issue.
3. Asumming no, please do the following when describing the enhancements.
3. Assuming no, please do the following when describing the enhancements.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants