Update src/current/_includes/releases/v25.1/v25.1.0-alpha.3.md

Co-authored-by: Ryan Kuo <[email protected]>

src/current/_includes/releases/v25.1/v25.1.0-alpha.3.md

@@ -30,7 +30,7 @@ Release Date: January 15, 2025
 - If a row-level TTL job is scheduled to run and the previous scheduled job for that table is still running, the scheduled run will now be skipped rather than waiting for the previous job to complete. [#138336][#138336]
 - Schema object identifiers (e.g., database names, schema names, table names, and function names) are no longer redacted when logging statements in the `EXEC` or `SQL_SCHEMA` channels. If redaction of these names is required, then the new cluster setting `sql.log.redact_names.enabled` can be set to `true`. The default value of the setting is `false`. [#136897][#136897]
 - Object identifiers such as table names, schema names, function names, and type names are no longer redacted in the `SQL_SCHEMA` log channel. [#136897][#136897]
-- The default value of the cluster setting `admission.l0_file_count_overload_threshold` is changed to `4000`. [#138699][#138699]
+- Changed the default value of the cluster setting `admission.l0_file_count_overload_threshold` to `4000`. [#138699][#138699]
 - Introduced a metric, `sql.schema_changer.object_count`, that keeps track of the count of schema objects in the cluster. [#138786][#138786]
 - Renamed the `changefeed.min_highwater_advance` cluster setting to `changefeed.resolved_timestamp.min_update_interval` to more accurately reflect its function. Its description in the automatically generated documentation has also been updated. The previous name remains usable for backward compatibility. [#138673][#138673]