Repository: vercel/next.js
Pull request: [turbopack] Fix a few references to caching configuration as it is no longer canary guarded



Closes PACK-5666

Changed files:
filename: docs/01-app/03-api-reference/05-config/01-next-config-js/turbopackFileSystemCache.mdx
patch: @@ -2,16 +2,13 @@
 title: Turbopack FileSystem Caching
 nav_title: turbopackFileSystemCache
 description: Learn how to enable FileSystem Caching for Turbopack builds
-version: canary
 ---
 
 ## Usage
 
 Turbopack FileSystem Cache enables Turbopack to reduce work across `next dev` or `next build` commands. When enabled, Turbopack will save and restore data to the `.next` folder between builds, which can greatly speed up subsequent builds and dev sessions.
 
-> **Warning:** FileSystem Cache is still under development and is not yet stable. Users adopting should expect some stability issues.
-
-> **Good to know**: Note that while `next dev` and `next build` can share cached data with each other, most cache entries are command-specific due to different configuration and environment variables.
+> **Good to know:** The FileSystem Cache feature is Beta and is still under development. Users adopting should expect some stability issues. We recommend first adopting it for development.
 
 ```ts filename="next.config.ts" switcher
 import type { NextConfig } from 'next'
@@ -44,7 +41,7 @@ module.exports = nextConfig
 
 ## Version Changes
 
-| Version   | Changes                                     |
-| --------- | ------------------------------------------- |
-| `v16.0.0` | Separate flags for build and dev.           |
-| `v15.5.0` | Persistent caching released as experimental |
+| Version   | Changes                                                        |
+| --------- | -------------------------------------------------------------- |
+| `v16.0.0` | Beta release with separate flags for build and dev             |
+| `v15.5.0` | Persistent caching released as experimental on canary releases |

filename: docs/01-app/03-api-reference/08-turbopack.mdx
patch: @@ -152,9 +152,12 @@ We are planning to offer an equivalent to the Inner Graph Optimization in Turbop
 
 ### Build Caching
 
-Webpack supports [disk build caching](https://webpack.js.org/configuration/cache/#cache) to speed up builds. We are planning to support an analogous feature in Turbopack but it is not ready yet. On the `next@canary` release you can experiment with our solution by enabling the [`experimental.turbopackFileSystemCacheForDev`/`experimental.turbopackFileSystemCacheForBuild` flags](/docs/app/api-reference/config/next-config-js/turbopackFileSystemCache).
+Webpack supports [disk build caching](https://webpack.js.org/configuration/cache/#cache) to improve build performance. Turbopack provides a similar opt-in feature, currently in beta. Starting with Next 16, you can enable Turbopack’s filesystem cache by setting the following experimental flags:
 
-> **Good to know:** For this reason, when comparing webpack and Turbopack performance, make sure to delete the `.next` folder between builds to see a fair comparison.
+- [`experimental.turbopackFileSystemCacheForDev`](/docs/app/api-reference/config/next-config-js/turbopackFileSystemCache)
+- [`experimental.turbopackFileSystemCacheForBuild`](/docs/app/api-reference/config/next-config-js/turbopackFileSystemCache)
+
+> **Good to know:** For this reason, when comparing webpack and Turbopack performance, make sure to delete the `.next` folder between builds to see a fair comparison or enable the turbopack filesystem cache feature.
 
 ### Webpack plugins