doc: add links in offboarding.md

PR-URL: #51440
Reviewed-By: Vinícius Lourenço Claro Cardoso <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>

doc/contributing/offboarding.md

@@ -3,7 +3,7 @@
 This document is a checklist of things to do when a collaborator becomes
 emeritus or leaves the project.
 
-* Remove the collaborator from the @nodejs/collaborators team.
+* Remove the collaborator from the [`@nodejs/collaborators`][] team.
 * Open a fast-track pull request to move the collaborator to the collaborator
   emeriti list in README.md.
 * Determine what GitHub teams the collaborator belongs to. In consultation with
@@ -15,6 +15,11 @@ emeritus or leaves the project.
   * When in doubt, especially if you are unable to get in contact with the
     collaborator, remove them from all teams. It is easy enough to add them
     back later, so we err on the side of privacy and security.
-* Open an issue in the [build](https://github.com/nodejs/build) repository
-  titled `Remove Collaborator from Coverity` asking that the collaborator
-  be removed from the Node.js coverity project if they had access.
+* Remove them from the [`@nodejs`](https://github.com/orgs/nodejs/people) GitHub
+  org unless they are members for a reason other than being a Collaborator.
+* [Open an issue](https://github.com/nodejs/build/issues/new) in the
+  nodejs/build repository titled `Remove Collaborator from Coverity` asking that
+  the collaborator be removed from the Node.js coverity project if they had
+  access.
+
+[`@nodejs/collaborators`]: https://github.com/orgs/nodejs/teams/collaborators/members