From 506ccd48e7cd8a3aae82515c85ed5200dc1db25f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Anders=20S=C3=B8gaard?= <andershagbard@gmail.com>
Date: Tue, 16 May 2023 13:21:11 +0200
Subject: [PATCH] Correct link to Customizing Turbopack

---
 docs/pages/pack/docs/comparisons/webpack.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/pages/pack/docs/comparisons/webpack.mdx b/docs/pages/pack/docs/comparisons/webpack.mdx
index cac267fca0412..8a0600a36cf5b 100644
--- a/docs/pages/pack/docs/comparisons/webpack.mdx
+++ b/docs/pages/pack/docs/comparisons/webpack.mdx
@@ -63,4 +63,4 @@ In a 1,000 module application, Turbopack can react to file changes **<DocsBenchm
 
 webpack has an extraordinary collection of [plugins](https://webpack.js.org/plugins/) to customize its behavior. Composing plugins lets you create custom toolchains which can support a huge variety of bundler features.
 
-As of Next.js 13.2, Turbopack introduced a compatibility layer to support webpack's loaders and resolve aliases. See [Customizing Turbopack](features/customizing-turbopack) for how to configure them. In the future, we plan to make Turbopack just as extensible as webpack - though likely with an altered API.
+As of Next.js 13.2, Turbopack introduced a compatibility layer to support webpack's loaders and resolve aliases. See [Customizing Turbopack](../features/customizing-turbopack) for how to configure them. In the future, we plan to make Turbopack just as extensible as webpack - though likely with an altered API.