Skip to content

Commit b75957d

Browse files
vladdostersanket-deepsource
authored andcommitted
(docs) update README.md
- correct spelling - correct grammar
1 parent 35e6bd0 commit b75957d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@
1212

1313
Welcome! 👋🏼
1414

15-
**Good First Issue** is an initiaitive to curate easy pickings from popular projects, so developers who've never made a contribution to open-source can get started easily.
15+
**Good First Issue** is an initiative to curate easy pickings from popular projects, so developers who've never contributed to open-source can get started quickly.
1616

17-
Open-source maintainers are always looking to get more people involved, but new developers generally think it's difficult to become a contributor. We believe getting developers to fix super-easy issues removes the barrier for future contributions. This is why Good First Issue exists.
17+
Open-source maintainers are always looking to get more people involved, but new developers generally think it's challenging to become a contributor. We believe getting developers to fix super-easy issues removes the barrier for future contributions. This is why Good First Issue exists.
1818

1919
## Adding a new project
2020

@@ -24,7 +24,7 @@ Follow these simple steps:
2424

2525
- Our goal is to narrow down projects for new open-source contributors. To maintain the quality of projects in Good First Issue, please make sure your GitHub repository meets the following criteria:
2626

27-
- At least three issue with the `good first issue` label. This label is already present on all repositories by default. If not, you can follow the steps [here](https://help.github.com/en/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests).
27+
- At least three issues with the `good first issue` label. This label is already present on all repositories by default. If not, you can follow the steps [here](https://help.github.com/en/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests).
2828

2929
- Detailed setup instructions for the project.
3030

@@ -34,6 +34,6 @@ Follow these simple steps:
3434

3535
- Add your repository's path in [data/repositories.toml](data/repositories.toml).
3636

37-
- Create a new pull-request. Please add the link to the issues page of the repository in the PR description. Once the pull-request is merged, the changes will be live on [goodfirstissue.dev](https://goodfirstissue.dev/).
37+
- Create a new pull-request. Please add the link to the issues page of the repository in the PR description. Once the pull request is merged, the changes will be live on [goodfirstissue.dev](https://goodfirstissue.dev/).
3838

39-
We hangout in [DeepSource's User Group on Slack](https://deepsourceusers.slack.com). Feel free to ping us in `#good-first-issue` channel. 🙌🏼
39+
We hangout in [DeepSource's User Group on Slack](https://deepsourceusers.slack.com). Feel free to ping us in the `#good-first-issue` channel. 🙌🏼

0 commit comments

Comments
 (0)