diff --git a/docs/src/maintainer-guide/governance.md b/docs/src/maintainer-guide/governance.md
index 5ce0c3fa57a..70cf77c2306 100644
--- a/docs/src/maintainer-guide/governance.md
+++ b/docs/src/maintainer-guide/governance.md
@@ -117,7 +117,7 @@ A Reviewer is invited to become a TSC member by existing TSC members. A nominati
 
 1. Add the GitHub user to the "ESLint TSC" GitHub team
 1. Set the GitHub user to be have the "Owner" role for the ESLint organization
-1. Send a welcome email with a link to the [maintainer guide](./) and the [npm 2FA guide](./npm-2fa).
+1. Send a welcome email with a link to the [maintainer guide](./) and instructions for npm 2FA.
 1. Invite to the Discord TSC channel
 1. Make the TSC member an admin on the ESLint team mailing list
 1. Add the TSC member to the recurring TSC meeting event on Google Calendar
diff --git a/docs/src/maintainer-guide/releases.md b/docs/src/maintainer-guide/releases.md
index 5b8cdfbb4f0..caaf94c4cbc 100644
--- a/docs/src/maintainer-guide/releases.md
+++ b/docs/src/maintainer-guide/releases.md
@@ -21,7 +21,7 @@ A two-person release team is assigned to each scheduled release. This two-person
 
 The two-person team should seek input from the whole team on the Monday following a release to double-check if a patch release is necessary.
 
-At least one member of the release team needs to have access to [eslint's two-factor authentication for npm](./npm-2fa) in order to do a release.
+At least one member of the release team needs to have access to eslint's two-factor authentication for npm in order to do a release.
 
 ## Release Communication