Refine CONTRIBUTING.md (#12742)

Co-authored-by: Subhramit Basu <[email protected]>

Author: koppor

CONTRIBUTING.md

@@ -159,21 +159,24 @@ We reserve the right to reject pull requests that contain little or no genuine a
 
 ### After submission of a pull request
 
-After you submitted a pull request, automated checks will run.
-You may see "Some checks were not successful".
-You can click on failing checks to see more information about why they failed.
-Then, please look into them and handle accordingly.
+Once you submit a pull request, automated checks will run and bots will perform a preliminary review on your code.
+You will get automated comments on your pull request within about 5 minutes.
+Acting on them in a timely manner is expected.
 
-Afterwards, you will receive comments on your pull request.
-Since JabRef is driven by volunteers in their spare time, reviews may take more time than a project with full time developers.
-The pull request may be approved immediatly, or a reviewer may request changes.
-In that case, please implement the requested changes.
+You may also see "Some checks were not successful".
+You can click on failing checks to see more information about why they failed.
+Please look into them and handle accordingly.
 
 After implementing changes, commit to the branch your pull request is *from* and push.
 The pull request will automatically be updated with your changes.
 To maintain a clean git history, your commits will also be automatically squashed upon acceptance of the pull request, during merging.
 Thus, no need to worry about WIP commits or [fixing git submodule issues](https://devdocs.jabref.org/code-howtos/faq.html#submodules), and force-pushing should be **avoided**.
 
+After all the basic checks are green, maintainers will look at your pull request.
+Since JabRef is driven by volunteers in their spare time, reviews may take more time than a project with full time developers.
+The pull request may be approved immediatly, or a reviewer may request changes and/or have discussions regarding your approach.
+In that case, you are expected to answer any questions and implement the requested changes.
+
 Please – **never ever close a pull request and open a new one** -
 This causes unessesary work on our side, and is not in the the style of the GitHub Open Source community.
 You can push any changes you need to make to the branch your pull request is *from*.