diff --git a/docs/components/scroll-restoration.md b/docs/components/scroll-restoration.md
index f3f73d043f..d3dd20fab3 100644
--- a/docs/components/scroll-restoration.md
+++ b/docs/components/scroll-restoration.md
@@ -7,6 +7,8 @@ new: true
 
 This component will emulate the browser's scroll restoration on location changes after loaders have completed to ensure the scroll position is restored to the right spot, even across domains.
 
+<docs-warning>This feature only works if using a data router, see [Picking a Router][pickingarouter]</docs-warning>
+
 You should only render one of these and it's recommended you render it in the root route of your app:
 
 ```tsx [1,7]
@@ -97,3 +99,4 @@ Server Rendering frameworks can prevent scroll flashing because they can send a
 
 [remix]: https://remix.run
 [preventscrollreset]: ../components/link#preventscrollreset
+[pickingarouter]: ../routers/picking-a-router
diff --git a/docs/route/action.md b/docs/route/action.md
index 676ae54a00..0754ac5f61 100644
--- a/docs/route/action.md
+++ b/docs/route/action.md
@@ -7,7 +7,7 @@ new: true
 
 Route actions are the "writes" to route [loader][loader] "reads". They provide a way for apps to perform data mutations with simple HTML and HTTP semantics while React Router abstracts away the complexity of asynchronous UI and revalidation. This gives you the simple mental model of HTML + HTTP (where the browser handles the asynchrony and revalidation) with the behavior and UX capabilities of modern SPAs.
 
-<docs-error>This feature only works if using a data router like [`createBrowserRouter`][createbrowserrouter]</docs-error>
+<docs-warning>This feature only works if using a data router, see [Picking a Router][pickingarouter]</docs-warning>
 
 ```tsx
 <Route
@@ -144,4 +144,4 @@ For more details and expanded use cases, read the [errorElement][errorelement] d
 [workingwithformdata]: ../guides/form-data
 [useactiondata]: ../hooks/use-action-data
 [returningresponses]: ./loader#returning-responses
-[createbrowserrouter]: ../routers/create-browser-router
+[pickingarouter]: ../routers/picking-a-router
diff --git a/docs/route/error-element.md b/docs/route/error-element.md
index cd60b68f34..c77499b35d 100644
--- a/docs/route/error-element.md
+++ b/docs/route/error-element.md
@@ -7,7 +7,7 @@ new: true
 
 When exceptions are thrown in [loaders][loader], [actions][action], or component rendering, instead of the normal render path for your Routes (`<Route element>`), the error path will be rendered (`<Route errorElement>`) and the error made available with [`useRouteError`][userouteerror].
 
-<docs-error>This feature only works if using a data router like [`createBrowserRouter`][createbrowserrouter]</docs-error>
+<docs-warning>This feature only works if using a data router, see [Picking a Router][pickingarouter]</docs-warning>
 
 ```tsx
 <Route
@@ -213,4 +213,4 @@ The project route doesn't have to think about errors at all. Between the loader
 [response]: https://developer.mozilla.org/en-US/docs/Web/API/Response
 [isrouteerrorresponse]: ../utils/is-route-error-response
 [json]: ../fetch/json
-[createbrowserrouter]: ../routers/create-browser-router
+[pickingarouter]: ../routers/picking-a-router
diff --git a/docs/route/should-revalidate.md b/docs/route/should-revalidate.md
index 0210816a5d..8448a17f3a 100644
--- a/docs/route/should-revalidate.md
+++ b/docs/route/should-revalidate.md
@@ -7,6 +7,8 @@ new: true
 
 This function allows you opt-out of revalidation for a route's loader as an optimization.
 
+<docs-warning>This feature only works if using a data router, see [Picking a Router][pickingarouter]</docs-warning>
+
 There are several instances where data is revalidated, keeping your UI in sync with your data automatically:
 
 - After an [`action`][action] is called from a [`<Form>`][form].
@@ -76,3 +78,4 @@ interface ShouldRevalidateFunction {
 [loader]: ./loader
 [useloaderdata]: ../hooks/use-loader-data
 [params]: ./route#dynamic-segments
+[pickingarouter]: ../routers/picking-a-router