Skip to content

Commit adbfd90

Browse files
authored
Merge pull request #164 from sushant-varanasi/patch-1
Update CONTRIBUTING.md
2 parents 86f68a0 + 4c26380 commit adbfd90

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

CONTRIBUTING.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Contributing Guidelines
22

3-
For anyone looking to get involved to this project, we are glad to hear from you. Here are a few types of contributions
3+
For anyone looking to get involved in this project, we are glad to hear from you. Here are a few types of contributions
44
that we would be interested in hearing about.
55

66
* Bug fixes
@@ -12,14 +12,12 @@ that we would be interested in hearing about.
1212
- If you'd like to accomplish something in the library that it doesn't already do, describe the problem in a new
1313
Github Issue.
1414
- Issues that have been identified as a feature request will be labelled `enhancement`.
15-
- If you'd like to implement the new feature, please wait for feedback from the project maintainers before spending
16-
too much time writing the code. In some cases, `enhancement`s may not align well with the project objectives at
17-
the time.
15+
- If you'd like to implement the new feature, please wait for feedback from the project maintainers before spending too much time writing the code. In some cases, `enhancement`s may not align well with the project objectives at the time.
1816
* Tests, Documentation, Miscellaneous
1917
- If you think the test coverage could be improved, the documentation could be clearer, you've got an alternative
20-
implementation of something that may have more advantages, or any other change we would still be glad hear about
18+
implementation of something that may have more advantages or any other change we would still be glad to hear about
2119
it.
22-
- If its a trivial change, go ahead and send a Pull Request with the changes you have in mind
20+
- If it's a trivial change, go ahead and send a Pull Request with the changes you have in mind
2321
- If not, open a Github Issue to discuss the idea first.
2422

2523
## Requirements
@@ -37,7 +35,7 @@ continue to add more commits to the branch you have sent the Pull Request from.
3735

3836
1. Fork this repository on GitHub.
3937
1. Clone/fetch your fork to your local development machine.
40-
1. Create a new branch (e.g. `issue-12`, `feat.add_foo`, etc) and check it out.
38+
1. Create a new branch (e.g. `issue-12`, `feat.add_foo`, etc.) and check it out.
4139
1. Make your changes and commit them. (Did the tests pass?)
4240
1. Push your new branch to your fork. (e.g. `git push myname issue-12`)
4341
1. Open a Pull Request from your new branch to the original fork's `master` branch.

0 commit comments

Comments
 (0)