From 947e9f1827fa28c96ac5f5b92b8acebfabb43346 Mon Sep 17 00:00:00 2001
From: Amel SELMANE <46314900+amel-selmane@users.noreply.github.com>
Date: Mon, 11 Dec 2023 11:11:54 +0100
Subject: [PATCH] Update ways-to-extend.md

Update ESLint Typescript Parser URL
---
 docs/src/extend/ways-to-extend.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/extend/ways-to-extend.md b/docs/src/extend/ways-to-extend.md
index 0432492b60e7..3bf8314e1afa 100644
--- a/docs/src/extend/ways-to-extend.md
+++ b/docs/src/extend/ways-to-extend.md
@@ -53,7 +53,7 @@ ESLint custom parsers are a way to extend ESLint to support the linting of new l
 
 ESLint ships with a built-in JavaScript parser (Espree), but custom parsers allow you to lint other languages or to extend the linting capabilities of the built-in parser.
 
-For example, the custom parser [@typescript-eslint/parser](https://typescript-eslint.io/architecture/parser/) extends ESLint to lint TypeScript code.
+For example, the custom parser [@typescript-eslint/parser](https://typescript-eslint.io/packages/parser) extends ESLint to lint TypeScript code.
 
 Custom parsers **cannot** be included in a plugin, unlike the other extension types.