From 007e48e9e109da6c8fb4d9a4cc4f9f9b90062e64 Mon Sep 17 00:00:00 2001
From: Erick Zhao <erickzhao@electronjs.org>
Date: Thu, 14 Nov 2024 12:14:24 -0800
Subject: [PATCH] fix: update macOS keychain doc link

---
 guides/code-signing/code-signing-macos.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guides/code-signing/code-signing-macos.md b/guides/code-signing/code-signing-macos.md
index 44e9dba..7e68047 100644
--- a/guides/code-signing/code-signing-macos.md
+++ b/guides/code-signing/code-signing-macos.md
@@ -183,7 +183,7 @@ module.exports = {
 
 #### Option 3: Using a keychain
 
-Instead of providing environment variables to the Forge config passed to `notarytool`, you can choose to use a macOS [keychain](https://support.apple.com/en-ca/guide/mac-help/mchlf375f392/mac) containing either set of credentials (either Option 1 or Option 2 above).
+Instead of providing environment variables to the Forge config passed to `notarytool`, you can choose to use a macOS [keychain](https://support.apple.com/en-ca/guide/keychain-access/welcome/mac) containing either set of credentials (either Option 1 or Option 2 above).
 
 You can do this directly in your terminal via the `notarytool store-credentials` command. For usage information, you can refer to the man page for `notarytool`: