New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated contributing.rst #3127
Merged
Merged
Updated contributing.rst #3127
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,7 +6,7 @@ Contributing to Scrapy | |
|
||
.. important:: | ||
|
||
Double check you are reading the most recent version of this document at | ||
Double check that you are reading the most recent version of this document at | ||
https://doc.scrapy.org/en/master/contributing.html | ||
|
||
There are many ways to contribute to Scrapy. Here are some of them: | ||
|
@@ -18,7 +18,7 @@ There are many ways to contribute to Scrapy. Here are some of them: | |
* Report bugs and request features in the `issue tracker`_, trying to follow | ||
the guidelines detailed in `Reporting bugs`_ below. | ||
|
||
* Submit patches for new functionality and/or bug fixes. Please read | ||
* Submit patches for new functionalities and/or bug fixes. Please read | ||
:ref:`writing-patches` and `Submitting patches`_ below for details on how to | ||
write and submit a patch. | ||
|
||
|
@@ -80,8 +80,8 @@ guidelines when reporting a new bug. | |
Writing patches | ||
=============== | ||
|
||
The better written a patch is, the higher chance that it'll get accepted and | ||
the sooner that will be merged. | ||
The better written a patch is, higher is the chance that it'll get accepted and | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This line wasn't, and isn't, very idiomatic English. I would rephrase as "The better a patch is written, the higher the chances that it'll get accepted, and the sooner it will be merged". |
||
sooner it will be merged. | ||
|
||
Well-written patches should: | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a native speaker, but https://english.stackexchange.com/questions/196590/functionality-vs-functionalities-are-both-correct-and-idiomatic seems to suggest "functionality" is ok here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, either is fine I think. :)