Updated Contributing to Jellyfin (markdown)

6 years ago · 725a413aaf
parent cc955a99af
commit 725a413aaf
1 changed files with 1 additions and 1 deletions
--- a/Contributing-to-Jellyfin.md
+++ b/Contributing-to-Jellyfin.md
@ -32,7 +32,7 @@ We adhere to a fairly standard fork-and-PR model of development:

 3. Submit a pull request from your feature branch back to the upstream `develop` branch. PRs that target `master` will be changed to target `develop`, so please double-check this when submitting.

-Please ensure you provide a detailed explanation, in each pull request discription, of what problems the PR solves (with action keywords ans links to issue numbers if at all possible), and how the PR solves them. This aids both in review, as well as in future understanding of why a given set of changes were made.
+Please ensure you provide a detailed explanation, in each pull request discription, of what problems the PR solves (with action keywords ans links to issue numbers if at all possible), and how the PR solves them. This aids both in review, as well as in future understanding of why a given set of changes were made. More detail is always better here.

 All PRs to the `develop` branch require review by at least 1 member of the core team. Once that is done, if the PR is not tagged with the WIP label, it should be merged by the reviewer if able. We do however encourage reviews from any contributor as more eyes always helps.