add date

docs/src/pages/blog/index.mdx

@@ -7,7 +7,7 @@ import StayUpdated from '@/components/StayUpdated.mdx';
   <BlogPostLink
     href="/blog/next-intl-4-0"
     title="next-intl 4.0 beta"
-    date="Dec XX, 2024"
+    date="Dec 23, 2024"
     author="By Jan Amann"
   />
   <BlogPostLink

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

@@ -7,9 +7,9 @@ import StayUpdated from '@/components/StayUpdated.mdx';
 
 # next-intl 4.0 beta
 
-<small>Dec XX, 2024 · by Jan Amann</small>
+<small>Dec 23, 2024 · by Jan Amann</small>
 
-After a year of feature development, this release focuses on streamlining the API surface while maintaining the lean core architecture of `next-intl`. While many major improvements were already released in [previous minor versions](/blog/next-intl-3-22), this update introduces several valuable enhancements that will improve your development experience and make working with internationalization even more seamless.
+After a year of feature development, this release focuses on streamlining the API surface while maintaining the core architecture of `next-intl`. With many major improvements already released in [previous minor versions](/blog/next-intl-3-22), this update introduces several enhancements that will improve your development experience and make working with internationalization even more seamless.
 
 Here's what's new in `[email protected]`:
 
@@ -20,7 +20,7 @@ Here's what's new in `[email protected]`:
 5. [**Modernized build output**](#modernized-build-output)
 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).
+Please also have a look at the [other breaking changes](#other-breaking-changes) listed below before you upgrade.
 
 ## Revamped augmented types
 
@@ -200,7 +200,7 @@ This led to three minor changes:
 
 1. If you don't already have a `NextIntlClientProvider` in your app that wraps all Client Components that use `next-intl`, you now have to add one (see [PR #1541](https://github.com/amannn/next-intl/pull/1541) for details).
 2. If you're using `format.relativeTime` in Client Components, you may need to provide the `now` argument explicitly now (see [PR #1536](https://github.com/amannn/next-intl/pull/1536) for details).
-3. If you're using i18n routing, make sure you've updated to [`await requestLocale`](https://next-intl.dev/blog/next-intl-3-22#await-request-locale) (introduced in `[email protected]`). The previously deprecated `locale` argument will serve an edge case in the future once `rootParams` is a thing (see [PR #1625](https://github.com/amannn/next-intl/pull/1625/) for details).
+3. If you're using i18n routing, make sure you've updated to [`await requestLocale`](https://next-intl.dev/blog/next-intl-3-22#await-request-locale) that was introduced in `[email protected]`. The previously deprecated `locale` argument will serve an edge case in the future once `rootParams` is a thing (see [PR #1625](https://github.com/amannn/next-intl/pull/1625/) for details).
 
 While the mentioned Next.js features are still under development and may change, these changes seem reasonable to me in any case—and ideally will be all that's necessary to adapt for `next-intl` to get the most out of these upcoming capabilities.
 
@@ -213,7 +213,7 @@ I'm particularly excited about the announcement of `rootParams`, as it seems lik
 3. Automatically inherit formats when `NextIntlClientProvider` is rendered from a Server Component (see [PR #1191](https://github.com/amannn/next-intl/pull/1191))
 4. Require locale to be returned from `getRequestConfig` (see [PR #1486](https://github.com/amannn/next-intl/pull/1486))
 5. Disallow passing `null`, `undefined` or `boolean` as an ICU argument (see [PR #1561](https://github.com/amannn/next-intl/pull/1561))
-6. Bump minimum required typescript version to 5 for projects using TypeScript (see [PR #1481](https://github.com/amannn/next-intl/pull/1481))
+6. Bump minimum required TypeScript version to 5 for projects using TypeScript (see [PR #1481](https://github.com/amannn/next-intl/pull/1481))
 7. Remove deprecated APIs (see [PR #1479](https://github.com/amannn/next-intl/pull/1479))
 8. Remove deprecated APIs pt. 2 (see [PR #1482](https://github.com/amannn/next-intl/pull/1482))
 
@@ -227,8 +227,6 @@ Afterwards, you can upgrade by running:
 npm install next-intl@v4-beta
 ```
 
-If you need help, you can refer to the [examples](/examples) which have all been updated.
-
 I'd also invite you to share your experiences with `[email protected]` in the [discussions](https://github.com/amannn/next-intl/discussions/1631).
 
 ## Thank you!