doc: remove cryptoStream API reference

Author: JonasBa

doc/api/deprecations.md

@@ -6,16 +6,16 @@
 
 Node.js APIs might be deprecated for any of the following reasons:
 
-* Use of the API is unsafe.
-* An improved alternative API is available.
-* Breaking changes to the API are expected in a future major release.
+- Use of the API is unsafe.
+- An improved alternative API is available.
+- Breaking changes to the API are expected in a future major release.
 
 Node.js uses four kinds of deprecations:
 
-* Documentation-only
-* Application (non-`node_modules` code only)
-* Runtime (all code)
-* End-of-Life
+- Documentation-only
+- Application (non-`node_modules` code only)
+- Runtime (all code)
+- End-of-Life
 
 A Documentation-only deprecation is one that is expressed only within the
 Node.js API docs. These generate no side-effects while running Node.js.
@@ -156,17 +156,17 @@ API usability issues that can lead to accidental security issues.
 As an alternative, use one of the following methods of constructing `Buffer`
 objects:
 
-* [`Buffer.alloc(size[, fill[, encoding]])`][alloc]: Create a `Buffer` with
+- [`Buffer.alloc(size[, fill[, encoding]])`][alloc]: Create a `Buffer` with
   _initialized_ memory.
-* [`Buffer.allocUnsafe(size)`][alloc_unsafe_size]: Create a `Buffer` with
+- [`Buffer.allocUnsafe(size)`][alloc_unsafe_size]: Create a `Buffer` with
   _uninitialized_ memory.
-* [`Buffer.allocUnsafeSlow(size)`][]: Create a `Buffer` with _uninitialized_
+- [`Buffer.allocUnsafeSlow(size)`][]: Create a `Buffer` with _uninitialized_
   memory.
-* [`Buffer.from(array)`][]: Create a `Buffer` with a copy of `array`
-* [`Buffer.from(arrayBuffer[, byteOffset[, length]])`][from_arraybuffer] -
+- [`Buffer.from(array)`][]: Create a `Buffer` with a copy of `array`
+- [`Buffer.from(arrayBuffer[, byteOffset[, length]])`][from_arraybuffer] -
   Create a `Buffer` that wraps the given `arrayBuffer`.
-* [`Buffer.from(buffer)`][]: Create a `Buffer` that copies `buffer`.
-* [`Buffer.from(string[, encoding])`][from_string_encoding]: Create a `Buffer`
+- [`Buffer.from(buffer)`][]: Create a `Buffer` that copies `buffer`.
+- [`Buffer.from(string[, encoding])`][from_string_encoding]: Create a `Buffer`
   that copies `string`.
 
 Without `--pending-deprecation`, runtime warnings occur only for code not in
@@ -940,7 +940,7 @@ changes:
 
 Type: End-of-Life
 
-The [`tls.CryptoStream`][] class was removed. Please use
+The `tls.CryptoStream` class was removed. Please use
 [`tls.TLSSocket`][] instead.
 
 ### DEP0043: `tls.SecurePair`
@@ -1402,9 +1402,9 @@ The `util.log()` API has been removed because it's an unmaintained
 legacy API that was exposed to user land by accident. Instead,
 consider the following alternatives based on your specific needs:
 
-* **Third-Party Logging Libraries**
+- **Third-Party Logging Libraries**
 
-* **Use `console.log(new Date().toLocaleString(), message)`**
+- **Use `console.log(new Date().toLocaleString(), message)`**
 
 By adopting one of these alternatives, you can transition away from `util.log()`
 and choose a logging strategy that aligns with the specific
@@ -1897,19 +1897,19 @@ Since Node.js versions 4.4.0 and 5.2.0, several modules only intended for
 internal usage were mistakenly exposed to user code through `require()`. These
 modules were:
 
-* `v8/tools/codemap`
-* `v8/tools/consarray`
-* `v8/tools/csvparser`
-* `v8/tools/logreader`
-* `v8/tools/profile_view`
-* `v8/tools/profile`
-* `v8/tools/SourceMap`
-* `v8/tools/splaytree`
-* `v8/tools/tickprocessor-driver`
-* `v8/tools/tickprocessor`
-* `node-inspect/lib/_inspect` (from 7.6.0)
-* `node-inspect/lib/internal/inspect_client` (from 7.6.0)
-* `node-inspect/lib/internal/inspect_repl` (from 7.6.0)
+- `v8/tools/codemap`
+- `v8/tools/consarray`
+- `v8/tools/csvparser`
+- `v8/tools/logreader`
+- `v8/tools/profile_view`
+- `v8/tools/profile`
+- `v8/tools/SourceMap`
+- `v8/tools/splaytree`
+- `v8/tools/tickprocessor-driver`
+- `v8/tools/tickprocessor`
+- `node-inspect/lib/_inspect` (from 7.6.0)
+- `node-inspect/lib/internal/inspect_client` (from 7.6.0)
+- `node-inspect/lib/internal/inspect_repl` (from 7.6.0)
 
 The `v8/*` modules do not have any exports, and if not imported in a specific
 order would in fact throw errors. As such there are virtually no legitimate use
@@ -2849,8 +2849,7 @@ async function openAndClose() {
   try {
     filehandle = await fsPromises.open('thefile.txt', 'r');
   } finally {
-    if (filehandle !== undefined)
-      await filehandle.close();
+    if (filehandle !== undefined) await filehandle.close();
   }
 }
 ```
@@ -2982,8 +2981,9 @@ When looking for the CommonJS modules that have required the current one,
 `require.cache` and `module.children` can be used:
 
 ```js
-const moduleParents = Object.values(require.cache)
-  .filter((m) => m.children.includes(module));
+const moduleParents = Object.values(require.cache).filter((m) =>
+  m.children.includes(module)
+);
 ```
 
 ### DEP0145: `socket.bufferSize`
@@ -3985,7 +3985,6 @@ When an `args` array is passed to [`child_process.execFile`][] or [`child_proces
 [`timeout.ref()`]: timers.md#timeoutref
 [`timeout.refresh()`]: timers.md#timeoutrefresh
 [`timeout.unref()`]: timers.md#timeoutunref
-[`tls.CryptoStream`]: tls.md#class-tlscryptostream
 [`tls.SecureContext`]: tls.md#tlscreatesecurecontextoptions
 [`tls.TLSSocket`]: tls.md#class-tlstlssocket
 [`tls.checkServerIdentity()`]: tls.md#tlscheckserveridentityhostname-cert

doc/api/tls.md

@@ -553,29 +553,6 @@ appends a hint suggesting that if the root CA is installed locally,
 try running with the `--use-system-ca` flag to direct developers towards a
 secure solution, to prevent unsafe workarounds.
 
-## Class: `tls.CryptoStream`
-
-<!-- YAML
-added: v0.3.4
-deprecated: v0.11.3
--->
-
-> Stability: 0 - Deprecated: Use [`tls.TLSSocket`][] instead.
-
-The `tls.CryptoStream` class represents a stream of encrypted data. This class
-is deprecated and should no longer be used.
-
-### `cryptoStream.bytesWritten`
-
-<!-- YAML
-added: v0.3.4
-deprecated: v0.11.3
--->
-
-The `cryptoStream.bytesWritten` property returns the total number of bytes
-written to the underlying socket _including_ the bytes required for the
-implementation of the TLS protocol.
-
 ## Class: `tls.Server`
 
 <!-- YAML