doc: fixup odd formatting issue

Author: jasnell

doc/contributing/large-pull-requests.md

@@ -35,7 +35,7 @@ change (lines added minus lines deleted). This threshold applies across all
 files in the pull request, including changes in `deps/`, `test/`, `doc/`,
 `lib/`, `src/`, and `tools/`.
 
-Any pull request that adds a new subsystem, e.g. `node:foo` or `node:foo/bar`,
+Any pull request that adds a new subsystem, e.g. `node:foo` or `node:foo/bar`,
 is automatically considered a large pull request and subject to the same rules.
 
 Changes in `deps/` are included in this count. Dependency changes are
@@ -60,7 +60,7 @@ Large pull requests may only be opened by existing
 [collaborators](https://github.com/nodejs/node/#current-project-team-members).
 Non-collaborators are strongly discouraged from opening pull requests of this size.
 Large pull requests from non-collaborators will be closed unless it has been discussed
-in an issue and has a collaborator to champion the work.
+in an issue and has a collaborator to champion the work.
 
 ## Requirements
 
@@ -129,7 +129,7 @@ to stand on its own.
 
 ### Strategies for reducing the review length in single pull requests
 
-Large pull requests may involve a longer review process that becomes practically
+Large pull requests may involve a longer review process that becomes practically
 impossible to track on GitHub due to UI limitations. These strategies help reduce
 the review length in a single pull request.