From 6c09eec74946a75d8429a78b7fdb8e38676e2700 Mon Sep 17 00:00:00 2001
From: Donnie Goodson <49205731+donnie-msft@users.noreply.github.com>
Date: Wed, 27 Nov 2024 11:39:24 -0800
Subject: [PATCH] update hyperlink URL

---
 docs/localizability.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/localizability.md b/docs/localizability.md
index 57fa5780f24..cb06451679c 100644
--- a/docs/localizability.md
+++ b/docs/localizability.md
@@ -24,7 +24,7 @@ Unfortunately, NuGet.Client does not use OneLocBuild, and any resource comments
 Although the steps below are for the dev branch, the process is similar for release branches.
 
 1. A PR merges into the dev branch.
-1. A NuGet.Client build generates a `localizationArtifacts` artifact.  This artifact contains newly built Authenticode-signed assemblies [(see PR#6170)](https://github.com/NuGet/NuGet.Client/pull/6170) containing English resources and .lcg files.
+1. A NuGet.Client build generates a `localizationArtifacts` artifact.  This artifact contains newly built Authenticode-signed assemblies [(see PR#6170)][12]) containing English resources and .lcg files.
 The .lcg files contain information extracted from .resx files and are the primary input for later localization.
 1. The localization team grabs the `localizationArtifacts` artifact from a NuGet.Client build.
 1. The localization team localizes strings.