Skip to content

Commit b05bd69

Browse files
committed
Update CONTRIBUTING.md
1 parent 3a53de3 commit b05bd69

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ It's [Hacktoberfest month](https://blog.meilisearch.com/contribute-hacktoberfest
1616

1717
🚀 If your PR gets accepted it will count into your participation to Hacktoberfest!
1818

19-
✅ To be accepted it has either to have been merged, approved or tagged with the `hacktoberest-accepted` label.
19+
✅ To be accepted it has either to have been merged, approved or tagged with the `hacktoberfest-accepted` label.
2020

21-
🧐 Don't forget to check the [quality standards](https://hacktoberfest.digitalocean.com/resources/qualitystandards), otherwise your PR could be marked as `spam` or `invalid`, and it will not be counted toward your participation in Hacktoberfest.
21+
🧐 Don't forget to check the [quality standards](https://hacktoberfest.digitalocean.com/resources/qualitystandards)! Low-quality PRs might get marked as `spam` or `invalid`, and will not count toward your participation in Hacktoberfest.
2222

2323
## Assumptions
2424

@@ -127,7 +127,7 @@ Some notes on GitHub PRs:
127127

128128
- [Convert your PR as a draft](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request) if your changes are a work in progress: no one will review it until you pass your PR as ready for review.<br>
129129
The draft PR can be very useful if you want to show that you are working on something and make your work visible.
130-
- The branch related to the PR must be **up-to-date with `main`** before merging. Fortunately, this project [integrates a bot](https://github.com/meilisearch/integration-guides/blob/main/guides/bors.md) to automatically enforce this requirement without the PR author having to do it manually..
130+
- The branch related to the PR must be **up-to-date with `main`** before merging. Fortunately, this project [integrates a bot](https://github.com/meilisearch/integration-guides/blob/main/guides/bors.md) to automatically enforce this requirement without the PR author having to do it manually.
131131
- All PRs must be reviewed and approved by at least one maintainer.
132132
- The PR title should be accurate and descriptive of the changes. The title of the PR will be indeed automatically added to the next [release changelogs](https://github.com/meilisearch/meilisearch-rust/releases/).
133133

0 commit comments

Comments
 (0)