Skip to content

docs: fix typo errors #800

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
snitin315 merged 3 commits into from
May 19, 2025
Merged

docs: fix typo errors #800

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bedbee9
docs: fix typo errors
ersachin3112 May 18, 2025
d7dd928
docs: fix typos and improve clarity in contribution guidelines
ersachin3112 May 18, 2025
96e68dd
Update .github/CONTRIBUTING.md
snitin315 May 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions .github/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ format that includes a **type**, a **scope** and a **subject**:

The **header** is mandatory and the **scope** of the header is optional.

No line in the commit message should exceed 100 characters! This makes the message easier to read on GitHub as well as in various git tools.
No line in the commit message should exceed 100 characters! This makes the message easier to read on GitHub as well as in various Git tools.

The footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.

Expand Down Expand Up @@ -115,10 +115,9 @@ The body should include the motivation for the change and contrast it with previ

### Footer

The footer should include any information about **Breaking Changes** and is also the place to
reference GitHub issues that this commit **Closes**.
The footer should include any information about **Breaking Changes** and is also the place to reference GitHub issues that this commit **Closes**.

**Breaking Changes** must start with the word `BREAKING CHANGE:` followed by a space or two newlines. The rest of the breaking change details should be provided after this.
**Breaking Changes** must start with the word `BREAKING CHANGE:` followed by a space or two new lines. The rest of the breaking change details should be provided after this.

Example

Expand Down
Loading