Merge branch 'canary' into patch-1

.github/CODEOWNERS

@@ -2,7 +2,7 @@
 # https://help.github.com/en/articles/about-code-owners
 
 
-*                                             @timneutkens @ijjk @shuding @huozhi @feedthejim @ztanner
+*                                             @timneutkens @ijjk @shuding @huozhi @feedthejim @ztanner @wyattjoh
 /.git*                                        @vercel/next-js @vercel/devex
 /docs/                                        @vercel/next-js @vercel/devex
 /errors/                                      @vercel/next-js @vercel/devex

Cargo.toml

@@ -46,11 +46,11 @@ swc_core = { version = "0.79.70" }
 testing = { version = "0.33.24" }
 
 # Turbo crates
-turbopack-binding = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230825.2" }
+turbopack-binding = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230829.2" }
 # [TODO]: need to refactor embed_directory! macro usages, as well as resolving turbo_tasks::function, macros..
-turbo-tasks = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230825.2" }
+turbo-tasks = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230829.2" }
 # [TODO]: need to refactor embed_directory! macro usage in next-core
-turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230825.2" }
+turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230829.2" }
 
 # General Deps
 

docs/02-app/01-building-your-application/01-routing/03-linking-and-navigating.mdx

@@ -184,7 +184,7 @@ This means on navigation, the cache is reused as much as possible, instead of ma
 
 Learn more about how the [Router Cache](/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#caching-data) works and how to configure it.
 
-#### 3. Partial Rendering
+### 3. Partial Rendering
 
 Partial rendering means only the route segments that change on navigation re-render on the client, and any shared segments are preserved.
 
@@ -200,10 +200,10 @@ For example, when navigating between two sibling routes, `/dashboard/settings` a
 
 Without partial rendering, each navigation would cause the full page to re-render on the server. Rendering only the segment that changes reduces the amount of data transferred and execution time, leading to improved performance.
 
-#### 4. Soft Navigation
+### 4. Soft Navigation
 
 By default, the browser performs a hard navigation between pages. This means the browser reloads the page and resets React state such as `useState` hooks in your app and browser state such as the user's scroll position or focused element. However, in Next.js, the App Router uses soft navigation. This means React only renders the segments that have changed while preserving React and browser state, and there is no full page reload.
 
-#### 5. Back and Forward Navigation
+### 5. Back and Forward Navigation
 
 By default, Next.js will maintain the scroll position for backwards and forwards navigation, and re-use route segments in the [Router Cache](/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#caching-data).