From 30fb54f5ca84a9637d91594bab3f10ad9256b2c8 Mon Sep 17 00:00:00 2001
From: Steven <steven@ceriously.com>
Date: Fri, 21 Jul 2023 13:57:46 -0400
Subject: [PATCH] chore(docs): fix broken link

---
 .../01-routing/03-linking-and-navigating.mdx                    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/02-app/01-building-your-application/01-routing/03-linking-and-navigating.mdx b/docs/02-app/01-building-your-application/01-routing/03-linking-and-navigating.mdx
index 32ac43e3e4a1c..37c7491220375 100644
--- a/docs/02-app/01-building-your-application/01-routing/03-linking-and-navigating.mdx
+++ b/docs/02-app/01-building-your-application/01-routing/03-linking-and-navigating.mdx
@@ -4,7 +4,7 @@ description: Learn how navigation works in Next.js, and how to use the Link Comp
 related:
   description: Learn more about statically typed links with TypeScript.
   links:
-    - app/building-your-application/configuring/typescript#statically-typed-links
+    - app/building-your-application/configuring/typescript
 ---
 
 The Next.js router uses [server-centric routing](/docs/app/building-your-application/routing#server-centric-routing-with-client-side-navigation) with [client-side navigation](#how-navigation-works). It supports [instant loading states](/docs/app/building-your-application/routing/loading-ui-and-streaming) and [concurrent rendering](https://react.dev/reference/react/startTransition). This means navigation maintains client-side state, avoids expensive re-renders, is interruptible, and doesn't cause race conditions.