From 7a983f5f1dff5d2104cfe8c4ef9d3aa7aba714b0 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Sun, 9 Aug 2020 14:29:00 -0700 Subject: [PATCH] doc: remove "is recommended from crypto legacy API text MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The text for the legacy API sends mixed signals. It's legacy, but still supported, so not deprecated, but not recommended. Let's begin to clarify this by removing "not recommended". If we want to not-recommend it, let's doc-deprecate it properly, or at least include an explanation as to why it's not recommended. PR-URL: https://github.com/nodejs/node/pull/34697 Reviewed-By: James M Snell Reviewed-By: Ujjwal Sharma Reviewed-By: Tobias Nießen --- doc/api/crypto.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/api/crypto.md b/doc/api/crypto.md index e25b808258547d..e0f398044ca172 100644 --- a/doc/api/crypto.md +++ b/doc/api/crypto.md @@ -106,9 +106,8 @@ console.log(Certificate.verifySpkac(Buffer.from(spkac))); ### Legacy API -As a still supported legacy interface, it is possible (but not recommended) to -create new instances of the `crypto.Certificate` class as illustrated in the -examples below. +As a still supported legacy interface, it is possible to create new instances of +the `crypto.Certificate` class as illustrated in the examples below. #### `new crypto.Certificate()`