From d4fc5ca84a5038953537a95b75b5fbdbd3c5d82b Mon Sep 17 00:00:00 2001 From: Joyee Cheung Date: Thu, 25 Apr 2024 22:04:03 +0200 Subject: [PATCH] fixup! fixup! zlib: expose zlib.crc32() --- doc/api/zlib.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/api/zlib.md b/doc/api/zlib.md index bd7fb5b138935d..9e94a076f5478c 100644 --- a/doc/api/zlib.md +++ b/doc/api/zlib.md @@ -733,13 +733,13 @@ in data transmission. It's not suitable for cryptographic authentication. To be consistent with other APIs, if the `data` is a string, it will be encoded with UTF-8 before being used for computation. If users only -uses Node.js to compute and check the checksums, this works well with +use Node.js to compute and match the checksums, this works well with other APIs that uses the UTF-8 encoding by default. -Some third-party JavaScript libraries that compute the checksum on a +Some third-party JavaScript libraries compute the checksum on a string based on `str.charCodeAt()` so that it can be run in browsers. If users want to match the checksum computed with this kind of library -from the browser, it's better to use the same library in Node.js +in the browser, it's better to use the same library in Node.js if it also runs in Node.js. If users have to use `zlib.crc32()` to match the checksum produced by such a third-party library: