[pull] main from remix-run:main

contributors.yml

@@ -216,6 +216,7 @@
 - maruffahmed
 - marvinruder
 - mathpaquette
+- matmilbury
 - matt-harro
 - matthewlynch
 - maximevtush
@@ -295,6 +296,7 @@
 - senseibarni
 - sergiodxa
 - serranoarevalo
+- sevignator
 - sgalhs
 - sgrishchenko
 - shamsup

docs/api/hooks/useViewTransitionState.md

@@ -4,7 +4,7 @@ title: useViewTransitionState
 
 # useViewTransitionState
 
-[MODES: framework, data, declarative]
+[MODES: framework, data]
 
 ## Summary
 

docs/explanation/sessions-and-cookies.md

@@ -72,7 +72,7 @@ export async function action({
 }
 ```
 
-See the [Session API][session-api] for more all the methods available on the session object.
+See the [Session API][session-api] for all methods available on the session object.
 
 ### Login form example
 

docs/tutorials/address-book.md

@@ -344,7 +344,7 @@ Now the child route should be rendering through the outlet.
 
 ## Client Side Routing
 
-You may or may not have noticed, but when we click the links in the sidebar, the browser is doing a full document request for the next URL instead of client side routing, which completely remounts our app
+You may or may not have noticed, but when we click the links in the sidebar, the browser is doing a full document request for the next URL instead of client side routing, which completely remounts our app.
 
 Client side routing allows our app to update the URL without reloading the entire page. Instead, the app can immediately render new UI. Let's make it happen with [`<Link>`][link-component].
 

docs/upgrading/component-routes.md

@@ -343,7 +343,7 @@ The first few routes you migrate are the hardest because you often have to acces
 
 ## Enable SSR and/or Pre-rendering
 
-If you want to enable server rendering and static pre-rendering, you can do so with the `ssr` and `prerender` options in the bundler plugin. For SSR you'll need to also deploy the server build to a server. See [Deploying][deploying] for more information.
+If you want to enable server rendering and static pre-rendering, you can do so with the `ssr` and `prerender` options in the bundler plugin. For SSR you'll need to also deploy the server build to a server.
 
 ```ts filename=react-router.config.ts
 import type { Config } from "@react-router/dev/config";
@@ -357,7 +357,6 @@ export default {
 ```
 
 [upgrade-router-provider]: ./router-provider
-[deploying]: ../start/deploying
 [configuring-routes]: ../start/framework/routing
 [route-modules]: ../start/framework/route-module
 [type-safety]: ../how-to/route-module-type-safety

docs/upgrading/router-provider.md

@@ -422,7 +422,7 @@ You can checkout [Type Safety][type-safety] to learn how to fully setup and use
 
 ## Enable SSR and/or Pre-rendering
 
-If you want to enable server rendering and static pre-rendering, you can do so with the `ssr` and `prerender` options in the bundler plugin. For SSR you'll need to also deploy the server build to a server. See [Deploying][deploying] for more information.
+If you want to enable server rendering and static pre-rendering, you can do so with the `ssr` and `prerender` options in the bundler plugin. For SSR you'll need to also deploy the server build to a server.
 
 ```ts filename=react-router.config.ts
 import type { Config } from "@react-router/dev/config";
@@ -436,7 +436,6 @@ export default {
 ```
 
 [upgrade-component-routes]: ./component-routes
-[deploying]: ../start/deploying
 [configuring-routes]: ../start/framework/routing
 [route-modules]: ../start/framework/route-module
 [type-safety]: ../how-to/route-module-type-safety