Update new-core-contributors-guide.md (#579)

punctuation, title case

docs/contributing/leadership/new-core-contributors-guide.md

@@ -4,11 +4,11 @@ So you've been invited to join the core contributor team. What next? What is exp
 
 The level of your involvement is up to yourself. We do not assign specific roles or responsibilities but instead allow people to choose what they want to work on. For example:
 
-- Trevor is leading the responsive mobile app efforts;
-- Jed helped set up the new donation systems and the new website (among a lot of other things);
-- Matiss is mostly reviewing PRs and fixing issues here and there;
-- Rich created and maintained the documentation;
-- Paul is helping with the product direction;
+- Trevor is leading the responsive mobile app efforts.
+- Jed helped set up the new donation systems and the new website (among a lot of other things).
+- Matiss is mostly reviewing PRs and fixing issues here and there.
+- Rich created and maintained the documentation.
+- Paul is helping with the product direction.
 
 Your specific contribution is up to yourself.
 
@@ -20,25 +20,25 @@ Overall: try to enjoy your time here. We value you and the effort you are puttin
 
 If we boil it down to a simple list:
 
-- find an area where you would like to contribute;
-- review the work of other contributors;
-- share your thoughts and opinions;
-- be open and humble;
+- Find an area where you would like to contribute.
+- Review the work of other contributors.
+- Share your thoughts and opinions.
+- Be open and humble.
 
-## PR review guidelines
+## PR Review Guidelines
 
-- Remember that the PRs coming in are from **unpaid volunteers**, so be respectful of that
-- However, this does NOT mean we review and approve everything: our time is valuable too, so it is OK to ask clarification questions or push back if the proposed change is too large or just doesn't fit well in the product
-- Be polite and helpful - many of the changes come from first-time contributors or newcomers to the React tech stack
-- If a seemingly controversial change is being proposed, but you are OK with it - feel free to approve it, but give it a few more days for others to review it too before merging
-- For non-controversial changes (for example: adding TypeScript types) - feel free to approve and merge straight away
+- Remember that the PRs coming in are from **unpaid volunteers**, so be respectful of that.
+- However, this does NOT mean we review and approve everything: our time is valuable too, so it is OK to ask clarification questions or push back if the proposed change is too large or just doesn't fit well in the product.
+- Be polite and helpful - many of the changes come from first-time contributors or newcomers to the React tech stack.
+- If a seemingly controversial change is being proposed, but you are OK with it - feel free to approve it, but give it a few more days for others to review it too before merging.
+- For non-controversial changes (for example: adding TypeScript types) - feel free to approve and merge straight away.
 
 ## Disagreements
 
 We're all passionate about Actual. Sometimes this leads to differences in opinion.
 
 When this happens we usually follow this framework:
 
-1. the two people having a disagreement try to come to an agreement first;
-2. if they cannot come to an agreement - they bring it to the contributor team for discussion;
-3. if the bigger contributor team cannot agree - we bring it to a public vote.
+1. The two people having a disagreement try to come to an agreement first.
+2. If they cannot come to an agreement - they bring it to the contributor team for discussion.
+3. If the bigger contributor team cannot agree - we bring it to a public vote.