From 80afc587cd4d71dec3037399d59abd66a9255ab0 Mon Sep 17 00:00:00 2001 From: Robert Nagy Date: Fri, 10 Sep 2021 09:50:34 +0200 Subject: [PATCH] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 6106327636b..c7b66a0bcb5 100644 --- a/README.md +++ b/README.md @@ -168,15 +168,15 @@ This is [experimental](https://nodejs.org/api/documentation.html#documentation_s #### Specification Compliance -This section documents parts of the [fetch specification](https://fetch.spec.whatwg.org) which Undici does +This section documents parts of the [Fetch Standard](https://fetch.spec.whatwg.org) which Undici does not support or does not fully implement. ##### Garbage Collection * https://fetch.spec.whatwg.org/#garbage-collection -The fetch specification allows users to skip consuming the response body by relying on -garbage collection to release connection resources. Undici does the same. However, +The [Fetch Standard](https://fetch.spec.whatwg.org) allows users to skip consuming the response body by relying on +[garbage collection](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_Management#garbage_collection) to release connection resources. Undici does the same. However, garbage collection in Node is less aggressive and deterministic (due to the lack of clear idle periods that browser have through the rendering refresh rate) which means that leaving the release of connection resources to the garbage collector