From dabc251e88ca3172d4fd89fcad57740841e3a85e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tobias=20Nie=C3=9Fen?= Date: Mon, 22 May 2023 20:35:22 +0000 Subject: [PATCH] doc: fix typo in crypto legacy streams API section --- doc/api/crypto.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/api/crypto.md b/doc/api/crypto.md index 370e6859a31b5b..2419634dc9bfe1 100644 --- a/doc/api/crypto.md +++ b/doc/api/crypto.md @@ -5561,7 +5561,7 @@ When passing strings to cryptographic APIs, consider the following factors. The Crypto module was added to Node.js before there was the concept of a unified Stream API, and before there were [`Buffer`][] objects for handling -binary data. As such, the many of the `crypto` defined classes have methods not +binary data. As such, many `crypto` classes have methods not typically found on other Node.js classes that implement the [streams][stream] API (e.g. `update()`, `final()`, or `digest()`). Also, many methods accepted and returned `'latin1'` encoded strings by default rather than `Buffer`s. This