From 1274edb74a645a6d25f482cb896b5df2ad1d5b83 Mon Sep 17 00:00:00 2001
From: keienWang <42377006+keienWang@users.noreply.github.com>
Date: Mon, 29 Jan 2024 19:10:28 +0800
Subject: [PATCH] fix:Update outdated links in 2021-08-22-split-postmortem.md
 document

These changes aim to ensure that the links in the document are current, enhancing the quality of the documentation and the reader's experience.
---
 docs/postmortems/2021-08-22-split-postmortem.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/postmortems/2021-08-22-split-postmortem.md b/docs/postmortems/2021-08-22-split-postmortem.md
index 962aa51f64..0986f00b65 100644
--- a/docs/postmortems/2021-08-22-split-postmortem.md
+++ b/docs/postmortems/2021-08-22-split-postmortem.md
@@ -87,7 +87,7 @@ The blocks on the 'bad' chain were investigated, and Tim Beiko reached out to th
 
 ### Disclosure decision
 
-The geth-team have an official policy regarding [vulnerability disclosure](https://geth.ethereum.org/docs/vulnerabilities/vulnerabilities). 
+The geth-team have an official policy regarding [vulnerability disclosure](https://geth.ethereum.org/docs/developers/geth-developer/disclosures). 
 
 > The primary goal for the Geth team is the health of the Ethereum network as a whole, and the decision whether or not to publish details about a serious vulnerability boils down to minimizing the risk and/or impact of discovery and exploitation.