diff --git a/docs/router/guide/not-found-errors.md b/docs/router/guide/not-found-errors.md
index 0cc84b5676..88b8767a00 100644
--- a/docs/router/guide/not-found-errors.md
+++ b/docs/router/guide/not-found-errors.md
@@ -27,7 +27,7 @@ Under the hood, both of these cases are implemented using the same `notFound` fu
 
 When TanStack Router encounters a **pathname** that doesn't match any known route pattern **OR** partially matches a route pattern but with extra trailing pathname segments, it will automatically throw a not-found error.
 
-Depending on the `notFoundMode` option, the router will handle these automatic errors differently::
+Depending on the `notFoundMode` option, the router will handle these automatic errors differently:
 
 - ["fuzzy" mode](#notfoundmode-fuzzy) (default): The router will intelligently find the closest matching suitable route and display the `notFoundComponent`.
 - ["root" mode](#notfoundmode-root): All not-found errors will be handled by the root route's `notFoundComponent`, regardless of the nearest matching route.