NEXT-66966 fix title inconsistency with unstable_ functions in Docs (#66967)

add (Experimental) to title for `unstable_rethrow` to match all other
`unstable_` functions

### Fixing a bug

- Related issues linked using `fixes #66966`

<img width="1287" alt="image"
src="https://github.com/vercel/next.js/assets/147033096/5a790b63-30c9-4605-b0e8-73899afb8e59">

## For Maintainers

`unstable_rethrow` has a different title scheme compared to all other
`unstable_` functions this is just a quick fix for this since it was
bugging me.

Closes NEXT-66966
Fixes #66966

---------

Co-authored-by: Sam Ko <sam@vercel.com>

docs/02-app/01-building-your-application/03-rendering/01-partial-prerendering.mdx

@@ -1,5 +1,5 @@
 ---
-title: Partial Prerendering (Experimental)
+title: Partial Prerendering (experimental)
 description: Learn how to combine the benefits of static and dynamic rendering with Partial Prerendering.
 ---
 

docs/02-app/01-building-your-application/06-optimizing/05-scripts.mdx

@@ -123,7 +123,7 @@ Although the default behavior of `next/script` allows you to load third-party sc
 
 Refer to the [`next/script`](/docs/app/api-reference/components/script#strategy) API reference documentation to learn more about each strategy and their use cases.
 
-### Offloading Scripts To A Web Worker (Experimental)
+### Offloading Scripts To A Web Worker (experimental)
 
 > **Warning:** The `worker` strategy is not yet stable and does not yet work with the [`app`](/docs/app/building-your-application/routing/defining-routes) directory. Use with caution.
 

docs/02-app/01-building-your-application/07-configuring/05-mdx.mdx

@@ -756,7 +756,7 @@ The `remark` and `rehype` ecosystem contains plugins for [syntax highlighting](h
 
 When using `@next/mdx` as shown above, you **do not** need to use `remark` or `rehype` directly, as it is handled for you. We're describing it here for a deeper understanding of what the `@next/mdx` package is doing underneath.
 
-## Using the Rust-based MDX compiler (Experimental)
+## Using the Rust-based MDX compiler (experimental)
 
 Next.js supports a new MDX compiler written in Rust. This compiler is still experimental and is not recommended for production use. To use the new compiler, you need to configure `next.config.js` when you pass it to `withMDX`:
 

docs/02-app/01-building-your-application/10-deploying/01-production-checklist.mdx

@@ -45,7 +45,7 @@ While building your application, we recommend using the following features to en
 - **[Composition Patterns](/docs/app/building-your-application/rendering/composition-patterns):** Follow the recommended composition patterns for Server and Client Components, and check the placement of your [`"use client"` boundaries](/docs/app/building-your-application/rendering/composition-patterns#moving-client-components-down-the-tree) to avoid unnecessarily increasing your client-side JavaScript bundle.
 - **[Dynamic Functions](/docs/app/building-your-application/rendering/server-components#dynamic-functions):** Be aware that dynamic functions like [`cookies()`](/docs/app/api-reference/functions/cookies) and the [`searchParams`](/docs/app/api-reference/file-conventions/page#searchparams-optional) prop will opt the entire route into [Dynamic Rendering](/docs/app/building-your-application/rendering/server-components#dynamic-rendering) (or your whole application if used in the [Root Layout](/docs/app/building-your-application/routing/layouts-and-templates#root-layout-required)). Ensure dynamic function usage is intentional and wrap them in `<Suspense>` boundaries where appropriate.
 
-> **Good to know**: [Partial Prerendering (Experimental)](/blog/next-14#partial-prerendering-preview) will allow parts of a route to be dynamic without opting the whole route into dynamic rendering.
+> **Good to know**: [Partial Prerendering (experimental)](/blog/next-14#partial-prerendering-preview) will allow parts of a route to be dynamic without opting the whole route into dynamic rendering.
 
 </AppOnly>
 

docs/02-app/02-api-reference/04-functions/unstable_after.mdx

@@ -1,5 +1,5 @@
 ---
-title: unstable_after (Experimental)
+title: unstable_after (experimental)
 description: API Reference for the unstable_after function.
 ---
 

docs/02-app/02-api-reference/04-functions/unstable_cache.mdx

@@ -1,5 +1,5 @@
 ---
-title: unstable_cache (Experimental)
+title: unstable_cache (experimental)
 description: API Reference for the unstable_cache function.
 ---
 

docs/02-app/02-api-reference/04-functions/unstable_noStore.mdx

@@ -1,5 +1,5 @@
 ---
-title: unstable_noStore (Experimental)
+title: unstable_noStore (experimental)
 description: API Reference for the unstable_noStore function.
 ---
 

docs/02-app/02-api-reference/04-functions/unstable_rethrow.mdx

@@ -1,5 +1,5 @@
 ---
-title: unstable_rethrow
+title: unstable_rethrow (experimental)
 description: API Reference for the unstable_rethrow function.
 ---
 

docs/02-app/02-api-reference/05-next-config-js/ppr.mdx

@@ -1,6 +1,6 @@
 ---
-title: Partial Prerendering (Experimental)
+title: Partial Prerendering (experimental)
-nav_title: ppr (Experimental)
+nav_title: ppr (experimental)
 description: Learn how to enable Partial Prerendering (experimental) in Next.js 14.
 ---
 

docs/02-app/02-api-reference/05-next-config-js/reactCompiler.mdx

@@ -1,5 +1,5 @@
 ---
-title: reactCompiler (Experimental)
+title: reactCompiler (experimental)
 description: Enable the React Compiler to automatically optimize component rendering.
 ---
 

docs/02-app/02-api-reference/05-next-config-js/staleTimes.mdx

@@ -1,5 +1,5 @@
 ---
-title: staleTimes (Experimental)
+title: staleTimes (experimental)
 description: Learn how to override the invalidation time of the Client Router Cache.
 ---
 

docs/02-app/02-api-reference/05-next-config-js/turbo.mdx

@@ -1,5 +1,5 @@
 ---
-title: turbo (Experimental)
+title: turbo (experimental)
 nav_title: turbo
 description: Configure Next.js with Turbopack-specific options
 ---

docs/04-architecture/nextjs-compiler.mdx

@@ -282,7 +282,7 @@ module.exports = {
 
 Once enabled, swc will generate trace named as `swc-trace-profile-${timestamp}.json` under `.next/`. Chromium's trace viewer (chrome://tracing/, https://ui.perfetto.dev/), or compatible flamegraph viewer (https://www.speedscope.app/) can load & visualize generated traces.
 
-### SWC Plugins (Experimental)
+### SWC Plugins (experimental)
 
 You can configure swc's transform to use SWC's experimental plugin support written in wasm to customize transformation behavior.