docs: blog post wording

Author: amannn

docs/src/components/StayUpdated.mdx

@@ -2,6 +2,5 @@
 
 **Let's keep in touch:**
 
-- [GitHub releases](https://github.com/amannn/next-intl/releases)
 - [Bluesky (Jan Amann)](https://bsky.app/profile/amann.work)
 - [X (Jan Amann)](https://x.com/jamannnnnn)

docs/src/pages/blog/next-intl-4-0.mdx

@@ -20,7 +20,7 @@ Here's what's new in `next-intl@4.0`:
 3. [**Strictly-typed ICU arguments**](#strictly-typed-icu-arguments)
 4. [**GDPR compliance**](#gdpr-compliance)
 5. [**Modernized build output**](#modernized-build-output)
-6. [**Preparation for upcoming Next.js features**](#nextjs-ppr-dynamicio)
+6. [**Preparation for upcoming Next.js features**](#nextjs-future)
 
 Please also have a look at the [other breaking changes](#other-breaking-changes) before you [upgrade](#upgrade-now).
 
@@ -194,7 +194,7 @@ The build output of `next-intl` has been modernized and now leverages the follow
 
 With these changes, the bundle size of `next-intl` has been reduced by ~7% ([all details](https://github.com/amannn/next-intl/pull/1470)).
 
-## Preparation for `ppr` and `dynamicIO` [#nextjs-ppr-dynamicio]
+## Preparation for upcoming Next.js features [#nextjs-future]
 
 To ensure that the sails of `next-intl` are set for a steady course in the upcoming future, I've investigated the implications of upcoming Next.js features like [Partial Prerendering](https://nextjs.org/docs/app/api-reference/next-config-js/ppr) and [`dynamicIO`](https://nextjs.org/docs/canary/app/api-reference/config/next-config-js/dynamicIO) for `next-intl`.