Merge branch 'main' into release-next

Author: brophdawg11

contributors.yml

@@ -263,13 +263,15 @@
 - paulsmithkc
 - pavsoldatov
 - pcattori
+- penx
 - petersendidit
 - phildl
 - phryneas
 - pierophp
 - printfn
 - promet99
 - proshunsuke
+- pruszel
 - pwdcd
 - pyitphyoaung
 - refusado
@@ -297,6 +299,7 @@
 - senseibarni
 - sergiodxa
 - serranoarevalo
+- sevignator
 - sgalhs
 - sgrishchenko
 - shamsup

docs/api/components/Routes.md

@@ -20,7 +20,7 @@ import { Routes, Route } from "react-router"
 <Routes>
  <Route index element={<StepOne />} />
  <Route path="step-2" element={<StepTwo />} />
- <Route path="step-3" element={<StepThree />}>
+ <Route path="step-3" element={<StepThree />} />
 </Routes>
 ```
 

docs/api/hooks/useViewTransitionState.md

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

docs/start/modes.md

@@ -117,7 +117,7 @@ Every mode supports any architecture and deployment target, so the question isn'
 - have a data layer that either skips pending states (like local first, background data replication/sync) or has its own abstractions for them
 - are coming from Create React App (you may want to consider framework mode though)
 
-[→ Get Started with Declarative Mode](./library/installation).
+[→ Get Started with Declarative Mode](./declarative/installation).
 
 ## API + Mode Availability Table
 
@@ -175,7 +175,7 @@ This is mostly for the LLMs, but knock yourself out:
 | useRoutes                      | ✅        | ✅   | ✅          |
 | useSearchParams                | ✅        | ✅   | ✅          |
 | useSubmit                      | ✅        | ✅   |             |
-| useViewTransitionState         | ✅        | ✅   | ✅          |
+| useViewTransitionState         | ✅        | ✅   |             |
 | isCookieFunction               | ✅        | ✅   |             |
 | isSessionFunction              | ✅        | ✅   |             |
 | createCookie                   | ✅        | ✅   |             |

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].