fastify 5.8.5 → 5.9.0

package/SECURITY.md

@@ -71,7 +71,7 @@ Fastify falls under the [OpenJS CNA](https://cna.openjsf.org/).
 A CVE will be assigned as part of our responsible disclosure process.
 
 > ℹ️ Note:
-> Fastify's [HackerOne](https://hackerone.com/fastify) program is now closed.
+> Fastify's HackerOne program is closed.
 
 ### Strict measures when reporting vulnerabilities
 

package/SPONSORS.md

@@ -13,12 +13,14 @@ or [GitHub Sponsors](https://github.com/sponsors/fastify)!
 
 ## Tier 3
 
-- [Mercedes-Benz Group](https://github.com/mercedes-benz)
-- [Val Town, Inc.](https://opencollective.com/valtown)
 - [Handsontable - JavaScript Data Grid](https://handsontable.com/docs/react-data-grid/?utm_source=Fastify_GH&utm_medium=sponsorship&utm_campaign=library_sponsorship_2024)
 - [Lokalise - A Localization and Translation Software Tool](https://lokalise.com/?utm_source=Fastify_GH&utm_medium=sponsorship)
-- [TestMu AI](https://www.testmu.ai/)
+- [Val Town](https://www.val.town/)
+- [atagon GmbH](https://github.com/atagon-GmbH)
+- [Photon](https://github.com/photon-hq)
 
 ## Tier 2
 
-_Be the first!_
+- [Sent.dm](https://github.com/sentdm)
+- [Süddeutsche Zeitung](https://github.com/sueddeutsche)
+- [openclaw](https://github.com/openclaw)

package/docs/Guides/Database.md

@@ -149,34 +149,6 @@ fastify.listen({ port: 3000 }, err => {
 })
 ```
 
-### [LevelDB](https://github.com/fastify/fastify-leveldb)
-Install the plugin by running `npm i @fastify/leveldb`
-
-*Usage:*
-```javascript
-const fastify = require('fastify')()
-
-fastify.register(
-  require('@fastify/leveldb'),
-  { name: 'db' }
-)
-
-fastify.get('/foo', async function (req, reply) {
-  const val = await this.level.db.get(req.query.key)
-  return val
-})
-
-fastify.post('/foo', async function (req, reply) {
-  await this.level.db.put(req.body.key, req.body.value)
-  return { status: 'ok' }
-})
-
-fastify.listen({ port: 3000 }, err => {
-  if (err) throw err
-  console.log(`server listening on ${fastify.server.address().port}`)
-})
-```
-
 ### Writing plugin for a database library
 We could write a plugin for a database
 library too (e.g. Knex, Prisma, or TypeORM).

package/docs/Guides/Ecosystem.md

@@ -66,8 +66,6 @@ section.
   Fastify, internally uses [fast-jwt](https://github.com/nearform/fast-jwt).
 - [`@fastify/kafka`](https://github.com/fastify/fastify-kafka) Plugin to interact
   with Apache Kafka.
-- [`@fastify/leveldb`](https://github.com/fastify/fastify-leveldb) Plugin to
-  share a common LevelDB connection across Fastify.
 - [`@fastify/middie`](https://github.com/fastify/middie) Middleware engine for
   Fastify.
 - [`@fastify/mongodb`](https://github.com/fastify/fastify-mongodb) Fastify
@@ -206,6 +204,8 @@ section.
 - [`@inaiat/fastify-papr`](https://github.com/inaiat/fastify-papr)
   A plugin to integrate [Papr](https://github.com/plexinc/papr),
   the MongoDB ORM for TypeScript & MongoDB, with Fastify.
+- [`@inferdi/fastify`](https://github.com/inferdi/inferdi/tree/main/packages/fastify)
+  Type-safe dependency injection support for Fastify, powered by [InferDI](https://github.com/inferdi/inferdi).
 - [`@jerome1337/fastify-enforce-routes-pattern`](https://github.com/Jerome1337/fastify-enforce-routes-pattern)
   A Fastify plugin that enforces naming pattern for routes path.
 - [`@joggr/fastify-prisma`](https://github.com/joggrdocs/fastify-prisma)
@@ -232,6 +232,9 @@ section.
   Plugin to generate routes automatically with valid json content
 - [`@scalar/fastify-api-reference`](https://github.com/scalar/scalar/tree/main/integrations/fastify)
   Beautiful OpenAPI/Swagger API references for Fastify
+- [`@thecodepace/fastify-http-query`](https://github.com/TheCodePace/fastify-http-query)
+  Fastify plugin enabling the HTTP `QUERY` method (a safe, idempotent, cacheable
+  method with a body).
 - [`@trubavuong/fastify-seaweedfs`](https://github.com/trubavuong/fastify-seaweedfs)
   SeaweedFS for Fastify
 - [`@yeliex/fastify-problem-details`](https://github.com/yeliex/fastify-problem-details)
@@ -281,6 +284,9 @@ section.
   MySQL plugin with auto SQL injection attack prevention.
 - [`fastify-at-postgres`](https://github.com/mateonunez/fastify-at-postgres) Fastify
   Postgres plugin with auto SQL injection attack prevention.
+- [`fastify-ata`](https://github.com/ata-core/fastify-ata) Use
+  [`ata-validator`](https://github.com/ata-core/ata-validator) as the JSON Schema
+  validator, keeping Fastify's default error shape.
 - [`fastify-auth0-verify`](https://github.com/nearform/fastify-auth0-verify):
   Auth0 verification plugin for Fastify, internally uses
   [fastify-jwt](https://npm.im/fastify-jwt) and
@@ -539,6 +545,9 @@ middlewares into Fastify plugins
   OSM plugin to run overpass queries by OpenStreetMap.
 - [`fastify-override`](https://github.com/matthyk/fastify-override)
   Fastify plugin to override decorators, plugins and hooks for testing purposes
+- [`fastify-param-schema-validation`](https://github.com/Player1205/fastify-param-schema-validation)
+  Enforce strict parameter definitions in route validation schemas
+  to prevent missing parameter validation.
 - [`fastify-passkit-webservice`](https://github.com/alexandercerutti/fastify-passkit-webservice)
   A set of Fastify plugins to integrate Apple Wallet Web Service specification
 - [`fastify-peekaboo`](https://github.com/simone-sanfratello/fastify-peekaboo)
@@ -718,6 +727,8 @@ middlewares into Fastify plugins
   generator by directory structure.
 - [`fastify-flux`](https://github.com/Jnig/fastify-flux) Tool for building
   Fastify APIs using decorators and convert Typescript interface to JSON Schema.
+- [`fastify-intlayer`](https://intlayer.org/doc/environment/fastify)
+  i18n solution for error handling, email template
 - [`jeasx`](https://www.jeasx.dev)
   A flexible server-rendering framework built on Fastify
   that leverages asynchronous JSX to simplify web development.

package/docs/Guides/Serverless.md

@@ -451,9 +451,9 @@ You can add any valid `Dockerfile` that packages and runs a Node app. A basic
 docs](https://github.com/knative/docs/blob/2d654d1fd6311750cc57187a86253c52f273d924/docs/serving/samples/hello-world/helloworld-nodejs/Dockerfile).
 
 ```Dockerfile
-# Use the official Node.js 10 image.
+# Use the official Node.js LTS image.
 # https://hub.docker.com/_/node
-FROM node:10
+FROM node:lts
 
 # Create and change to the app directory.
 WORKDIR /usr/src/app

package/docs/Guides/Write-Plugin.md

@@ -53,7 +53,7 @@ Always put an example file in your repository. Examples are very helpful for
 users and give a very fast way to test your plugin. Your users will be grateful.
 
 ## Test
-A plugin **must** be thoroughly tested to verify that is working properly.
+A plugin **must** be thoroughly tested to verify that it is working properly.
 
 A plugin without tests will not be accepted to the ecosystem list. A lack of
 tests does not inspire trust nor guarantee that the code will continue to work

package/docs/Reference/Encapsulation.md

@@ -51,8 +51,8 @@ fastify.register(async function authenticatedContext (childServer) {
   childServer.route({
     path: '/one',
     method: 'GET',
-    handler (request, response) {
-      response.send({
+    handler (request, reply) {
+      reply.send({
         answer: request.answer,
         // request.foo will be undefined as it is only defined in publicContext
         foo: request.foo,
@@ -69,8 +69,8 @@ fastify.register(async function publicContext (childServer) {
   childServer.route({
     path: '/two',
     method: 'GET',
-    handler (request, response) {
-      response.send({
+    handler (request, reply) {
+      reply.send({
         answer: request.answer,
         foo: request.foo,
         // request.bar will be undefined as it is only defined in grandchildContext
@@ -85,8 +85,8 @@ fastify.register(async function publicContext (childServer) {
     grandchildServer.route({
       path: '/three',
       method: 'GET',
-      handler (request, response) {
-        response.send({
+      handler (request, reply) {
+        reply.send({
           answer: request.answer,
           foo: request.foo,
           bar: request.bar
@@ -114,12 +114,12 @@ original diagram:
 To see this, start the server and issue requests:
 
 ```sh
-# curl -H 'authorization: Bearer abc123' http://127.0.0.1:8000/one
-{"answer":42}
-# curl http://127.0.0.1:8000/two
-{"answer":42,"foo":"foo"}
-# curl http://127.0.0.1:8000/three
-{"answer":42,"foo":"foo","bar":"bar"}
+curl -H 'authorization: Bearer abc123' http://127.0.0.1:8000/one
+# {"answer":42}
+curl http://127.0.0.1:8000/two
+# {"answer":42,"foo":"foo"}
+curl http://127.0.0.1:8000/three
+# {"answer":42,"foo":"foo","bar":"bar"}
 ```
 
 [bearer]: https://github.com/fastify/fastify-bearer-auth
@@ -127,13 +127,14 @@ To see this, start the server and issue requests:
 ## Sharing Between Contexts
 <a id="shared-context"></a>
 
-Each context in the prior example inherits _only_ from its parent contexts. Parent
-contexts cannot access entities within their descendant contexts. If needed,
-encapsulation can be broken using [fastify-plugin][fastify-plugin], making
-anything registered in a descendant context available to the parent context.
+Each context in the previous example inherits _only_ from its parent contexts.
+Parent contexts cannot access entities within their descendant contexts.
+If needed, encapsulation can be broken using [fastify-plugin][fastify-plugin],
+making anything registered in a descendant context available
+to the parent context.
 
-To allow `publicContext` access to the `bar` decorator in `grandchildContext`,
-rewrite the code as follows:
+To allow `publicContext` to access the `bar` decorator from `grandchildContext`,
+update the code as follows:
 
 ```js
 'use strict'
@@ -151,8 +152,8 @@ fastify.register(async function publicContext (childServer) {
   childServer.route({
     path: '/two',
     method: 'GET',
-    handler (request, response) {
-      response.send({
+    handler (request, reply) {
+      reply.send({
         answer: request.answer,
         foo: request.foo,
         bar: request.bar
@@ -168,8 +169,8 @@ fastify.register(async function publicContext (childServer) {
     grandchildServer.route({
       path: '/three',
       method: 'GET',
-      handler (request, response) {
-        response.send({
+      handler (request, reply) {
+        reply.send({
           answer: request.answer,
           foo: request.foo,
           bar: request.bar
@@ -185,10 +186,10 @@ fastify.listen({ port: 8000 })
 Restarting the server and re-issuing the requests for `/two` and `/three`:
 
 ```sh
-# curl http://127.0.0.1:8000/two
-{"answer":42,"foo":"foo","bar":"bar"}
-# curl http://127.0.0.1:8000/three
-{"answer":42,"foo":"foo","bar":"bar"}
+curl http://127.0.0.1:8000/two
+# {"answer":42,"foo":"foo","bar":"bar"}
+curl http://127.0.0.1:8000/three
+# {"answer":42,"foo":"foo","bar":"bar"}
 ```
 
 [fastify-plugin]: https://github.com/fastify/fastify-plugin

package/docs/Reference/Errors.md

@@ -74,6 +74,7 @@
     - [FST_ERR_FORCE_CLOSE_CONNECTIONS_IDLE_NOT_AVAILABLE](#fst_err_force_close_connections_idle_not_available)
     - [FST_ERR_DUPLICATED_ROUTE](#fst_err_duplicated_route)
     - [FST_ERR_BAD_URL](#fst_err_bad_url)
+    - [FST_ERR_MAX_PARAM_LENGTH](#fst_err_max_param_length)
     - [FST_ERR_ASYNC_CONSTRAINT](#fst_err_async_constraint)
     - [FST_ERR_INVALID_URL](#fst_err_invalid_url)
     - [FST_ERR_ROUTE_OPTIONS_NOT_OBJ](#fst_err_route_options_not_obj)
@@ -82,6 +83,7 @@
     - [FST_ERR_ROUTE_MISSING_HANDLER](#fst_err_route_missing_handler)
     - [FST_ERR_ROUTE_METHOD_INVALID](#fst_err_route_method_invalid)
     - [FST_ERR_ROUTE_METHOD_NOT_SUPPORTED](#fst_err_route_method_not_supported)
+    - [FST_ERR_ROUTE_LOG_LEVEL_INVALID](#fst_err_route_log_level_invalid)
     - [FST_ERR_ROUTE_BODY_VALIDATION_SCHEMA_NOT_SUPPORTED](#fst_err_route_body_validation_schema_not_supported)
     - [FST_ERR_ROUTE_BODY_LIMIT_OPTION_NOT_INT](#fst_err_route_body_limit_option_not_int)
     - [FST_ERR_HANDLER_TIMEOUT](#fst_err_handler_timeout)
@@ -98,6 +100,7 @@
     - [FST_ERR_PLUGIN_TIMEOUT](#fst_err_plugin_timeout)
     - [FST_ERR_PLUGIN_NOT_PRESENT_IN_INSTANCE](#fst_err_plugin_not_present_in_instance)
     - [FST_ERR_PLUGIN_INVALID_ASYNC_HANDLER](#fst_err_plugin_invalid_async_handler)
+    - [FST_ERR_PLUGIN_DEPENDENCY_NOT_REGISTERED](#fst_err_plugin_dependency_not_registered)
     - [FST_ERR_VALIDATION](#fst_err_validation)
     - [FST_ERR_LISTEN_OPTIONS_INVALID](#fst_err_listen_options_invalid)
     - [FST_ERR_ERROR_HANDLER_NOT_FN](#fst_err_error_handler_not_fn)
@@ -209,16 +212,16 @@ fastify.setErrorHandler((error, request, reply) => {
 
 fastify.register((app, options, next) => {
   // Register child error handler
-  fastify.setErrorHandler((error, request, reply) => {
+  app.setErrorHandler((error, request, reply) => {
     throw error
   })
 
-  fastify.get('/bad', async () => {
-    // Throws a non-Error type, 'bar'
+  app.get('/bad', async () => {
+    // Throws a non-Error type, 'foo'
     throw 'foo'
   })
 
-  fastify.get('/good', async () => {
+  app.get('/good', async () => {
     // Throws an Error instance, 'bar'
     throw new Error('bar')
   })
@@ -349,6 +352,7 @@ Below is a table with all the error codes used by Fastify.
 | <a id="fst_err_force_close_connections_idle_not_available">FST_ERR_FORCE_CLOSE_CONNECTIONS_IDLE_NOT_AVAILABLE</a> | Cannot set forceCloseConnections to `idle` as your HTTP server does not support `closeIdleConnections` method. | Use a different value for `forceCloseConnections`. | [#3925](https://github.com/fastify/fastify/pull/3925) |
 | <a id="fst_err_duplicated_route">FST_ERR_DUPLICATED_ROUTE</a> | The HTTP method already has a registered controller for that URL. | Use a different URL or register the controller for another HTTP method. | [#2954](https://github.com/fastify/fastify/pull/2954) |
 | <a id="fst_err_bad_url">FST_ERR_BAD_URL</a> | The router received an invalid URL. | Use a valid URL. | [#2106](https://github.com/fastify/fastify/pull/2106) |
+| <a id="fst_err_max_param_length">FST_ERR_MAX_PARAM_LENGTH</a> | The router received an URL that exceed max param length. | Adjust the param length or increase the max param length to meet your needs. | [#2106](https://github.com/fastify/fastify/pull/6716) |
 | <a id="fst_err_async_constraint">FST_ERR_ASYNC_CONSTRAINT</a> | The router received an error when using asynchronous constraints. | - | [#4323](https://github.com/fastify/fastify/pull/4323) |
 | <a id="fst_err_invalid_url">FST_ERR_INVALID_URL</a> | URL must be a string. | Use a string for the URL. | [#3653](https://github.com/fastify/fastify/pull/3653) |
 | <a id="fst_err_route_options_not_obj">FST_ERR_ROUTE_OPTIONS_NOT_OBJ</a> | Options for the route must be an object. | Use an object for the route options. | [#4554](https://github.com/fastify/fastify/pull/4554) |
@@ -357,6 +361,7 @@ Below is a table with all the error codes used by Fastify.
 | <a id="fst_err_route_missing_handler">FST_ERR_ROUTE_MISSING_HANDLER</a> | Missing handler function for the route. | Add a handler function. | [#4554](https://github.com/fastify/fastify/pull/4554) |
 | <a id="fst_err_route_method_invalid">FST_ERR_ROUTE_METHOD_INVALID</a> | Method is not a valid value. | Use a valid value for the method. | [#4750](https://github.com/fastify/fastify/pull/4750) |
 | <a id="fst_err_route_method_not_supported">FST_ERR_ROUTE_METHOD_NOT_SUPPORTED</a> | Method is not supported for the route. | Use a supported method. | [#4554](https://github.com/fastify/fastify/pull/4554) |
+| <a id="fst_err_route_log_level_invalid">FST_ERR_ROUTE_LOG_LEVEL_INVALID</a> | `logLevel` must match a configured logger level. | Use one of the configured logger levels for the route. | [#6523](https://github.com/fastify/fastify/pull/6523) |
 | <a id="fst_err_route_body_validation_schema_not_supported">FST_ERR_ROUTE_BODY_VALIDATION_SCHEMA_NOT_SUPPORTED</a> | Body validation schema route is not supported. | Use a different different method for the route. | [#4554](https://github.com/fastify/fastify/pull/4554) |
 | <a id="fst_err_route_body_limit_option_not_int">FST_ERR_ROUTE_BODY_LIMIT_OPTION_NOT_INT</a> | `bodyLimit` option must be an integer. | Use an integer for the `bodyLimit` option. | [#4554](https://github.com/fastify/fastify/pull/4554) |
 | <a id="fst_err_handler_timeout">FST_ERR_HANDLER_TIMEOUT</a> | Request timed out. | Increase the `handlerTimeout` option or optimize the handler. | - |
@@ -372,6 +377,7 @@ Below is a table with all the error codes used by Fastify.
 | <a id="fst_err_plugin_timeout">FST_ERR_PLUGIN_TIMEOUT</a> | Plugin did not start in time. | Increase the timeout for the plugin. | [#3106](https://github.com/fastify/fastify/pull/3106) |
 | <a id="fst_err_plugin_not_present_in_instance">FST_ERR_PLUGIN_NOT_PRESENT_IN_INSTANCE</a> | The decorator is not present in the instance. | - | [#4554](https://github.com/fastify/fastify/pull/4554) |
 | <a id="fst_err_plugin_invalid_async_handler">FST_ERR_PLUGIN_INVALID_ASYNC_HANDLER</a> | The plugin being registered mixes async and callback styles. | - | [#5141](https://github.com/fastify/fastify/pull/5141) |
+| <a id="fst_err_plugin_dependency_not_registered">FST_ERR_PLUGIN_DEPENDENCY_NOT_REGISTERED</a> | The dependency of a plugin is not registered. | Register the missing dependency before registering this plugin. | [#6774](https://github.com/fastify/fastify/pull/6774) |
 | <a id="fst_err_validation">FST_ERR_VALIDATION</a> | The Request failed the payload validation. | Check the request payload. | [#4824](https://github.com/fastify/fastify/pull/4824) |
 | <a id="fst_err_listen_options_invalid">FST_ERR_LISTEN_OPTIONS_INVALID</a> | Invalid listen options. | Check the listen options. | [#4886](https://github.com/fastify/fastify/pull/4886) |
 | <a id="fst_err_error_handler_not_fn">FST_ERR_ERROR_HANDLER_NOT_FN</a> | Error Handler must be a function | Provide a function to `setErrorHandler`. | [#5317](https://github.com/fastify/fastify/pull/5317) | <a id="fst_err_error_handler_already_set">FST_ERR_ERROR_HANDLER_ALREADY_SET</a> | Error Handler already set in this scope. Set `allowErrorHandlerOverride: true` to allow overriding. | By default, `setErrorHandler` can only be called once per encapsulation context. | [#6097](https://github.com/fastify/fastify/pull/6098) |

package/docs/Reference/HTTP2.md

@@ -1,16 +1,16 @@
 <h1 align="center">Fastify</h1>
 
-## HTTP2
+## HTTP/2
 
-_Fastify_ supports HTTP2 over HTTPS (h2) or plaintext (h2c).
+_Fastify_ supports HTTP/2 over HTTPS (h2) or plaintext (h2c).
 
-Currently, none of the HTTP2-specific APIs are available through _Fastify_, but
+Currently, none of the HTTP/2-specific APIs are available through _Fastify_, but
 Node's `req` and `res` can be accessed through the `Request` and `Reply`
 interfaces. PRs are welcome.
 
 ### Secure (HTTPS)
 
-HTTP2 is supported in all modern browsers __only over a secure connection__:
+HTTP/2 is supported in all modern browsers __only over a secure connection__:
 
 ```js
 'use strict'
@@ -32,11 +32,11 @@ fastify.get('/', function (request, reply) {
 fastify.listen({ port: 3000 })
 ```
 
-[ALPN negotiation](https://datatracker.ietf.org/doc/html/rfc7301) allows
-support for both HTTPS and HTTP/2 over the same socket.
+[ALPN negotiation](https://datatracker.ietf.org/doc/html/rfc7301) enables
+both HTTPS and HTTP/2 over the same socket.
 Node core `req` and `res` objects can be either
 [HTTP/1](https://nodejs.org/api/http.html) or
-[HTTP/2](https://nodejs.org/api/http2.html). _Fastify_ supports this out of the
+[HTTP/2](https://nodejs.org/api/http2.html). _Fastify_ supports both out of the
 box:
 
 ```js
@@ -53,7 +53,7 @@ const fastify = require('fastify')({
   }
 })
 
-// this route can be accessed through both protocols
+// This route can be accessed through both protocols
 fastify.get('/', function (request, reply) {
   reply.code(200).send({ hello: 'world' })
 })
@@ -61,7 +61,7 @@ fastify.get('/', function (request, reply) {
 fastify.listen({ port: 3000 })
 ```
 
-Test the new server with:
+Test the server with:
 
 ```
 $ npx h2url https://localhost:3000
@@ -69,7 +69,7 @@ $ npx h2url https://localhost:3000
 
 ### Plain or insecure
 
-For microservices, HTTP2 can connect in plain text, but this is not
+For microservices, HTTP/2 can connect in plain text, but this is not
 supported by browsers.
 
 ```js

package/docs/Reference/Hooks.md

@@ -737,9 +737,9 @@ fastify.addHook('onResponse', (request, reply, done) => {
   done()
 })
 
-fastify.addHook('preParsing', (request, reply, done) => {
+fastify.addHook('preParsing', (request, reply, payload, done) => {
   // Your code
-  done()
+  done(null, payload)
 })
 
 fastify.addHook('preValidation', (request, reply, done) => {
@@ -790,9 +790,9 @@ fastify.route({
     // this hook will always be executed after the shared `onResponse` hooks
     done()
   },
-  preParsing: function (request, reply, done) {
+  preParsing: function (request, reply, payload, done) {
     // This hook will always be executed after the shared `preParsing` hooks
-    done()
+    done(null, payload)
   },
   preValidation: function (request, reply, done) {
     // This hook will always be executed after the shared `preValidation` hooks

package/docs/Reference/Index.md

@@ -3,12 +3,12 @@
 ## Core Documents
 <a id="reference-core-docs"></a>
 
-For the full table of contents (TOC), see [below](#reference-toc). The following
-list is a subset of the full TOC that detail core Fastify APIs and concepts in
-order of most likely importance to the reader:
+For the full table of contents, see [below](#reference-toc). The following list
+is a subset of the full table of contents that details core Fastify APIs and
+concepts, ordered by likely importance to the reader:
 
 + [Server](./Server.md): Documents the core Fastify API. Includes documentation
-  for the factory function and the object returned by the factory function.
+  for the factory function and the resulting server instance.
 + [Lifecycle](./Lifecycle.md): Explains the Fastify request lifecycle and
   illustrates where [Hooks](./Hooks.md) are available for integrating with it.
 + [Routes](./Routes.md): Details how to register routes with Fastify and how
@@ -25,8 +25,8 @@ order of most likely importance to the reader:
   Fastify plugins are built.
 + [Decorators](./Decorators.md): Explains the server, request, and response
   decorator APIs.
-+ [Hooks](./Hooks.md): Details the API by which Fastify plugins can inject
-  themselves into Fastify's handling of the request lifecycle.
++ [Hooks](./Hooks.md): Details the API that allows plugins to integrate with
+  the request lifecycle.
 
 
 ## Reference Documentation Table Of Contents
@@ -42,18 +42,17 @@ This table of contents is in alphabetical order.
   Fastify plugins are built.
 + [Errors](./Errors.md): Details how Fastify handles errors and lists the
   standard set of errors Fastify generates.
-+ [Hooks](./Hooks.md): Details the API by which Fastify plugins can inject
-  themselves into Fastify's handling of the request lifecycle.
-+ [HTTP2](./HTTP2.md): Details Fastify's HTTP2 support.
++ [Hooks](./Hooks.md): Details the API that allows plugins to integrate with
+  the request lifecycle.
++ [HTTP/2](./HTTP2.md): Details Fastify's HTTP/2 support.
 + [Lifecycle](./Lifecycle.md): Explains the Fastify request lifecycle and
   illustrates where [Hooks](./Hooks.md) are available for integrating with it.
 + [Logging](./Logging.md): Details Fastify's included logging and how to
   customize it.
-+ [Long Term Support](./LTS.md): Explains Fastify's long term support (LTS)
-  guarantee and the exceptions possible to the [semver](https://semver.org)
-  contract.
-+ [Middleware](./Middleware.md): Details Fastify's support for Express.js style
-  middleware.
++ [Long Term Support](./LTS.md): Explains Fastify's long-term support guarantee
+  and the possible exceptions to the [semver](https://semver.org) contract.
++ [Middleware](./Middleware.md): Details Fastify's support for
+  Express.js-style middleware.
 + [Plugins](./Plugins.md): Explains Fastify's plugin architecture and API.
 + [Reply](./Reply.md): Details Fastify's response object available to each
   request handler.
@@ -64,8 +63,7 @@ This table of contents is in alphabetical order.
 + [Server](./Server.md): Documents the core Fastify API. Includes documentation
   for the factory function and the object returned by the factory function.
 + [TypeScript](./TypeScript.md): Documents Fastify's TypeScript support and
-  provides recommendations for writing applications in TypeScript that utilize
-  Fastify.
+  provides recommendations for TypeScript application development.
 + [Validation and Serialization](./Validation-and-Serialization.md): Details
   Fastify's support for validating incoming data and how Fastify serializes data
   for responses.

package/docs/Reference/LTS.md

@@ -11,10 +11,10 @@ in this document:
    date. The release date of any specific version can be found at
    [https://github.com/fastify/fastify/releases](https://github.com/fastify/fastify/releases).
 2. Major releases will receive security updates for an additional six months
-   from the release of the next major release. After this period we will still
-   review and release security fixes as long as they are provided by the
-   community and they do not violate other constraints, e.g. minimum supported
-   Node.js version.
+   from the release of the next major release. After this period, Fastify maintainers
+   will still review and release security fixes as long as they are provided
+   by the community and they do not violate other constraints,
+   e.g., minimum supported Node.js version.
 3. Major releases will be tested and verified against all Node.js release lines
    that are supported by the [Node.js LTS
    policy](https://github.com/nodejs/Release) within the LTS period of that
@@ -24,7 +24,7 @@ in this document:
    and verified against alternative runtimes that are compatible with Node.js.
    The maintenance teams of these alternative runtimes are responsible for ensuring
    and guaranteeing these tests work properly.
-   1. [N|Solid](https://docs.nodesource.com/docs/product_suite) tests and
+   1. [N|Solid](https://docs.nodesource.com/docs/product_suite/) tests and
       verifies each Fastify major release against current N|Solid LTS versions.
       NodeSource ensures Fastify compatibility with N|Solid, aligning with the
       support scope of N|Solid LTS versions at the time of the Fastify release.
@@ -35,21 +35,21 @@ A "month" is defined as 30 consecutive days.
 > ## Security Releases and Semver
 >
 > As a consequence of providing long-term support for major releases, there are
-> occasions where we need to release breaking changes as a _minor_ version
-> release. Such changes will _always_ be noted in the [release
+> occasions when breaking changes must be released as a _minor_ version
+> release. Such changes will _always_ be documented in the [release
 > notes](https://github.com/fastify/fastify/releases).
 >
-> To avoid automatically receiving breaking security updates it is possible to
+> To avoid automatically receiving breaking security updates, it is possible to
 > use the tilde (`~`) range qualifier. For example, to get patches for the 3.15
 > release, and avoid automatically updating to the 3.16 release, specify the
 > dependency as `"fastify": "~3.15.x"`. This will leave your application
-> vulnerable, so please use it with caution.
+> vulnerable. Use this approach with caution.
 
 ### Security Support Beyond LTS
 
 Fastify's partner, HeroDevs, provides commercial security support through the
 OpenJS Ecosystem Sustainability Program for versions of Fastify that are EOL.
-For more information, see their [Never Ending Support][hd-link] service.
+For more information, see the [Never Ending Support][hd-link] service offered.
 
 ### Schedule
 <a id="lts-schedule"></a>
@@ -62,7 +62,7 @@ For more information, see their [Never Ending Support][hd-link] service.
 | 4.0.0   | 2022-06-08   | 2025-06-30      | 14, 16, 18, 20, 22 | v5(18), v5(20) |
 | 5.0.0   | 2024-09-17   | TBD             | 20, 22             | v5(20)         |
 
-### CI tested operating systems
+### CI Tested Operating Systems
 <a id="supported-os"></a>
 
 Fastify uses GitHub Actions for CI testing, please refer to [GitHub&#39;s
@@ -78,8 +78,7 @@ YAML workflow labels below:
 | Windows | `windows-latest`    | npm             | 20          | v5(20)        |
 | MacOS   | `macos-latest`      | npm             | 20          | v5(20)        |
 
-Using [yarn](https://yarnpkg.com/) might require passing the `--ignore-engines`
-flag.
+When using [yarn](https://yarnpkg.com/), the `--ignore-engines` flag may be required.
 
 [semver]: https://semver.org/
 

package/docs/Reference/Lifecycle.md

@@ -3,7 +3,7 @@
 ## Lifecycle
 <a id="lifecycle"></a>
 
-This schema shows the internal lifecycle of Fastify.
+This diagram shows the internal lifecycle of Fastify.
 
 The right branch of each section shows the next phase of the lifecycle. The left
 branch shows the corresponding error code generated if the parent throws an
@@ -41,10 +41,11 @@ Incoming Request
                                                                             └─▶ onResponse Hook
 ```
 
-When `handlerTimeout` is configured, a timer starts after routing. If the
-response is not sent within the allowed time, `request.signal` is aborted and
-a 503 error is sent. The timer is cleared when the response finishes or when
-`reply.hijack()` is called. See [`handlerTimeout`](./Server.md#factory-handler-timeout).
+When [`handlerTimeout`](./Server.md#factory-handler-timeout) is configured, a
+timer starts after routing. If the response is not sent within the allowed time,
+`request.signal` is aborted and a `503 Service Unavailable` error is sent.
+The timer is cancelled when the response completes
+or when `reply.hijack()` is called.
 
 Before or during the `User Handler`, `reply.hijack()` can be called to:
 - Prevent Fastify from running subsequent hooks and the user handler
@@ -61,8 +62,8 @@ When the user handles the request, the result may be:
 - In an async handler: it returns a payload or throws an `Error`
 - In a sync handler: it sends a payload or an `Error` instance
 
-If the reply was hijacked, all subsequent steps are skipped. Otherwise, when
-submitted, the data flow is as follows:
+If the reply is hijacked, all subsequent steps are skipped.
+Otherwise, the data flows as follows:
 
 ```
                         ★ schema validation Error
@@ -96,4 +97,4 @@ graceful shutdown sequence involving
 [`preClose`](./Hooks.md#pre-close) hooks, connection draining, and
 [`onClose`](./Hooks.md#on-close) hooks. See the
 [`close`](./Server.md#close) method documentation for the full step-by-step
-lifecycle.
+lifecycle.