From bbb3655f361b68596883b83b6377ea59608e6954 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9as=20Hanss?= <ScreamZ@users.noreply.github.com>
Date: Thu, 2 May 2024 14:18:25 +0200
Subject: [PATCH] Update typescript.mdx

---
 docs/pages/docs/workflows/typescript.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/pages/docs/workflows/typescript.mdx b/docs/pages/docs/workflows/typescript.mdx
index 22b741b74..2b8687b29 100644
--- a/docs/pages/docs/workflows/typescript.mdx
+++ b/docs/pages/docs/workflows/typescript.mdx
@@ -74,13 +74,13 @@ Using next-intl you can achieve similar behavior this way:
 // For the same of the exemple, this is created here but in a real app, this lives in another file.
 const { Link, redirect, usePathname, useRouter, getPathname } = createLocalizedPathnamesNavigation({ locales, localePrefix, pathnames });
 
-type NavLinkProps<T extends string> = {
+type NavLinkProps = {
   href: ComponentProps<typeof Link>["href"]; // Here is the magic
   title: string;
   icon?: React.ReactNode;
 };
 
-function NavLink<T extends string>({ href, icon, title }: NavLinkProps<T>) {
+function NavLink<T extends string>({ href, icon, title }: NavLinkProps) {
   return (
     <Link
       href={href}