Skip to content
This repository was archived by the owner on Apr 24, 2025. It is now read-only.

Commit 25bcb56

Browse files
authored
Merge branch 'Mrinank-Bhowmick:main' into main
2 parents 0b6083b + 4d04c7f commit 25bcb56

207 files changed

Lines changed: 46525 additions & 635 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

CONTRIBUTING.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,23 +6,23 @@ First of all, thank you for taking the time to contribute to this project. We've
66
### Check out the projects folder
77

88
We have some awesome projects available on the repository.
9-
If you would like to contribute some more projects which is not there in this repository , feel free to contribute.
9+
If you would like to contribute some more projects which is not there in this repository, feel free to contribute.
1010
If you found a bug please open an issue.
11-
We are looking for better documention and optimization of code.
11+
We are looking for better documentation and optimization of code.
1212

1313

1414
### Writing some code!
1515

16-
Contributing to a project on Github is pretty straight forward. If this is your first time, these are the steps you should take.
16+
Contributing to a project on GitHub is pretty straightforward. If this is your first time, these are the steps you should take.
1717

1818
- Fork this repo.
1919

2020
And that's it! Read the code available and change the part you don't like! Your change should not break the existing code.
2121

22-
If you're adding a new functionality, start from the branch **main**. It would be a better practice to create a new branch and work in there.
22+
If you're adding a new functionality, start from the branch **main**. It would be a better practice to create a new branch and work there.
2323

24-
When you're done, submit a pull request and for one of the maintainers to check it out. We would let you know if there is any problem or any changes that should be considered.
24+
When you're done, submit a pull request asking for one of the maintainers to check it out. We will let you know if there are any problems or changes that should be considered.
2525

2626
### Documentation
2727

28-
Every chunk of code that may be hard to understand has some comments above it. If you write some new code or change some part of the existing code in a way that it would not be functional without changing it's usages, it needs to be documented.
28+
Any piece of code that might be challenging to understand is accompanied by comments. If you add new code or modify existing code in a way that affects its functionality or requires changes in its usage, you must document these changes.

0 commit comments

Comments
 (0)