fixup!

Author: bjohansebas

src/content/blog/2026-03-22-webpack-5-106.mdx

@@ -21,7 +21,7 @@ Explore what's new in this release:
 
 Webpack adds a new top-level `validate` option and a `compiler.hooks.validate` hook that standardize how schema validation works across webpack configuration, plugins, and loaders.
 
-Until now, there was no unified way for plugins to integrate schema validation into the webpack build lifecycle. Each plugin handled validation on its own. The new `compiler.hooks.validate` hook gives plugin authors a standard API to register their validation logic, and `compiler.validate(...)` to run it. This means all validation (from webpack's core config to every plugin that adopts the hook) is controlled by a single `validate` flag and follows the same patterns:
+Until now, there was no unified way for plugins to integrate schema validation into the webpack build lifecycle. Each plugin handled validation on its own. The new `compiler.hooks.validate` hook gives plugin authors a standard API to register their validation logic, and `compiler.validate(...)` to run it. This means all validation from webpack's core config to every plugin that adopts the hook is controlled by a single `validate` flag and follows the same patterns:
 
 ```js
 module.exports = {
@@ -39,7 +39,7 @@ The default value depends on the build mode:
 | production  |           `false`            |       `true`       |
 | production  |            `true`            |      `false`       |
 
-For plugin authors, integrating validation is straightforward. Register a tap on `compiler.hooks.validate`, and webpack takes care of the rest — including skipping validation entirely when the user sets `validate: false`:
+For plugin authors, integrating validation is straightforward. Register a tap on `compiler.hooks.validate`, and webpack takes care of the rest, including skipping validation entirely when the user sets `validate: false`:
 
 ```js
 class MyPlugin {