Update doc/contributing/collaborator-guide.md

Co-authored-by: Tobias Nießen <tniessen@tnie.de>

Author: sxa

doc/contributing/collaborator-guide.md

@@ -269,9 +269,9 @@ request, try the "🔄 Re-run all jobs" button, on the right-hand side of the
 
 If there are Jenkins CI failures unrelated to the change in the pull
 request, try "Resume Build".  It is in the left navigation of the relevant
-`node-test-pull-request` job (Do not be tempted to do this on the lower
+`node-test-pull-request` job. (Do not be tempted to do this on the lower
 level `node-test-commit` job as it will not report the updated result back
-to the PR).  It will preserve all the green results from the current job but
+to the PR.)  It will preserve all the green results from the current job but
 re-run everything else.  Start a fresh CI by pressing "Retry" if more than
 seven days have elapsed since the original failing CI as the compiled
 binaries for the Windows and ARM platforms are only kept for seven days.