Skip to content

Commit 0cae504

Browse files
docs: fix typo errors (#800)
* docs: fix typo errors * docs: fix typos and improve clarity in contribution guidelines * Update .github/CONTRIBUTING.md --------- Co-authored-by: Nitin Kumar <[email protected]>
1 parent e4fd967 commit 0cae504

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

.github/CONTRIBUTING.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ format that includes a **type**, a **scope** and a **subject**:
6161

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

64-
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.
64+
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.
6565

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

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

116116
### Footer
117117

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

121-
**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.
120+
**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.
122121

123122
Example
124123

0 commit comments

Comments
 (0)