diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md
index 5346f8194516b1..c61aad6e7d4f31 100644
--- a/COLLABORATOR_GUIDE.md
+++ b/COLLABORATOR_GUIDE.md
@@ -501,8 +501,7 @@ commit logs, ensure that they are properly formatted, and add
 
 <a name="metadata"></a>
 * Modify the original commit message to include additional metadata regarding
-  the change process. (If you use Chrome or Edge, [`node-review`][] fetches
-  the metadata for you.)
+  the change process. ([`node-core-utils`][] fetches the metadata for you.)
 
   * Required: A `PR-URL:` line that references the *full* GitHub URL of the
     original pull request being merged so it's easy to trace a commit back to
@@ -681,4 +680,4 @@ LTS working group and the Release team.
 [Stability Index]: doc/api/documentation.md#stability-index
 [Enhancement Proposal]: https://github.com/nodejs/node-eps
 [git-username]: https://help.github.com/articles/setting-your-username-in-git/
-[`node-review`]: https://github.com/evanlucas/node-review
+[`node-core-utils`]: https://github.com/nodejs/node-core-utils
diff --git a/doc/onboarding.md b/doc/onboarding.md
index 41df0d00bd93b3..09cbb432a2bb85 100644
--- a/doc/onboarding.md
+++ b/doc/onboarding.md
@@ -158,7 +158,7 @@ onboarding session.
   * After one or two approvals, land the PR.
     * Be sure to add the `PR-URL: <full-pr-url>` and appropriate `Reviewed-By:` metadata!
     * [`core-validate-commit`][] helps a lot with this – install and use it if you can!
-    * If you use Chrome or Edge, [`node-review`][] fetches the metadata for you.
+    * [`node-core-utils`][] fetches the metadata for you.
 
 ## Final notes
 
@@ -180,4 +180,4 @@ onboarding session.
 
 [Code of Conduct]: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md
 [`core-validate-commit`]: https://github.com/evanlucas/core-validate-commit
-[`node-review`]: https://github.com/evanlucas/node-review
+[`node-core-utils`]: https://github.com/nodejs/node-core-utils