From ac630e350359b9bf9fc4a3491727212eeee203b0 Mon Sep 17 00:00:00 2001
From: Tane Morgan <464864+tanem@users.noreply.github.com>
Date: Mon, 16 Feb 2026 08:50:15 +1300
Subject: [PATCH] Tidy comments

---
 .../components/NavigationProgress.tsx               | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/examples/next-app-router/components/NavigationProgress.tsx b/examples/next-app-router/components/NavigationProgress.tsx
index 9a74941d3..286dff135 100644
--- a/examples/next-app-router/components/NavigationProgress.tsx
+++ b/examples/next-app-router/components/NavigationProgress.tsx
@@ -30,9 +30,9 @@ export function useNavigationProgress() {
   return context
 }
 
-// Watches pathname/searchParams changes to detect when
-// navigation has completed. Wrapped in Suspense because
-// useSearchParams() requires a Suspense boundary.
+// Watches pathname/searchParams changes to detect when navigation has
+// completed. Wrapped in Suspense because useSearchParams() requires a Suspense
+// boundary.
 function NavigationComplete({ onComplete }: { onComplete: () => void }) {
   const pathname = usePathname()
   const searchParams = useSearchParams()
@@ -49,10 +49,9 @@ function NavigationComplete({ onComplete }: { onComplete: () => void }) {
   return null
 }
 
-// Provides navigation progress state to the component
-// tree. Navigation start is signalled via the onNavigate
-// prop on a <ProgressLink>, and completion is detected by
-// watching usePathname()/useSearchParams().
+// Provides navigation progress state to the component tree. Navigation start is
+// signalled via the onNavigate prop on a <ProgressLink>, and completion is
+// detected by watching usePathname()/useSearchParams().
 export default function NavigationProgress({
   children,
 }: {