docs: Fix typo in example-app-router-mixed-routing README

Author: amannn

examples/example-app-router-mixed-routing/README.md

@@ -9,9 +9,9 @@ An example of how to achieve locale prefixes on public routes while reading the
 
 **Relevant parts in app code:**
 
-1. `src/middleware.ts`: Only run middleware on public pages that need to be localized.
-2. `src/i18n/request.ts`: Use the locale from the pathname segment for public routes or return a locale from the user profile for internal app routes.
-3. `src/navigation.public.ts`: These are the navigation APIs that automatically consider the `[locale]` segment for public routes. For internal app routes, the navigation APIs from Next.js should be used directly (see `PublicNavigation.tsx` vs `AppNavigation.tsx`).
+1. [`src/middleware.ts`](./src/middleware.ts): Only run middleware on public pages that need to be localized.
+2. [`src/i18n/request.ts`](./src/i18n/request.ts): Use the locale from the pathname segment for public routes or return a locale from the user profile for internal app routes.
+3. [`src/i18n/routing.public.ts`](./src/i18n/routing.public.ts): These are the navigation APIs that automatically consider the `[locale]` segment for public routes. For internal app routes, the navigation APIs from Next.js should be used directly (see `PublicNavigation.tsx` vs `AppNavigation.tsx`).
 
 Note that while this approach works fine, you can alternatively also consider a monorepo setup and build the public and internal app separately if you'd like to separate the code for the two apps.