Update leandrocfe-filament-v4-beta-feature-overview.md

Author: danharrin

content/articles/leandrocfe-filament-v4-beta-feature-overview.md

@@ -28,7 +28,7 @@ There are many new features and improvements in Filament v4 Beta, but here are s
 - [**Tailwind CSS v4**](#tailwind-css-v4): The framework now uses Tailwind CSS v4, which brings a reworked configuration system, improved customization, and faster builds.
 - [**Built-in multi-factor authentication (MFA)**](#multi-factor-authentication): Filament v4 includes built-in support for multi-factor authentication, enhancing security beyond standard email/password login.
 - [**Nested resources**](#nested-resources): Resources can now be deeply nested within each other, allowing their breadcrumb and URL structure to reflect their hierarchy.
-- **New form fields**: Filament v4 introduces new form fields like the [TipTap rich editor](#new-rich-editor), [slider](#slider), [code editor](#code-editor), and [table repeater](#table-repeater).
+- **New form fields**: Filament v4 introduces new form fields like the [TipTap rich editor](#new-rich-editor), [slider](#slider), [code editor](#code-editor), and [table repeater](#table-repeater). The rich editor specifically has seen many new features, including support for [custom blocks](#custom-blocks), [merge tags](#merge-tags), and dynamically generated temporary private image URLs.
 - **Tools to reduce network requests**: New methods like [`hiddenJs()`](#hiddenjs-and-visiblejs) and [`afterStateUpdatedJs()`](#afterstateupdatedjs) allow you to minimize network requests by using JavaScript to control field visibility and state updates. [Partial rendering](#partial-rendering) allows you to re-render only specific components on a page to reduce the server rendering time of requests.
 - [**Tables with custom data**](#tables-with-custom-data): Tables can now be backed by custom data sources, allowing you to render external or computed data without relying on Eloquent models.
 - [**Improved bulk action system**](#bulk-actions): Authorize individual records in bulk actions, use notifications to inform users of bulk action results with success and failure counts grouped by failure reason, and benefit from improved performance through chunked processing of selected records.