Repository: nodejs/node
Pull request: doc: added 'secure' event to tls.TLSSocket

Fixes #61060

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: doc/api/tls.md
patch: @@ -952,6 +952,18 @@ The listener callback is passed a single argument when called:
 Typically, the `response` is a digitally signed object from the server's CA that
 contains information about server's certificate revocation status.
 
+### Event: `'secure'`
+
+<!-- YAML
+added: v0.11.4
+-->
+
+The `'secure'` event is emitted after the TLS handshake has successfully
+completed and a secure connection has been established.
+
+This event is emitted on both client and server {tls.TLSSocket} instances,
+including sockets created using the `new tls.TLSSocket()` constructor.
+
 ### Event: `'secureConnect'`
 
 <!-- YAML
@@ -1530,7 +1542,7 @@ changes:
   * `requestCert`
 
 * `callback` {Function} If `renegotiate()` returned `true`, callback is
-  attached once to the `'secure'` event. If `renegotiate()` returned `false`,
+  attached once to the [`'secure'`][] event. If `renegotiate()` returned `false`,
   `callback` will be called in the next tick with an error, unless the
   `tlsSocket` has been destroyed, in which case `callback` will not be called
   at all.
@@ -2460,6 +2472,7 @@ added: v0.11.3
 [TLS recommendations]: https://wiki.mozilla.org/Security/Server_Side_TLS
 [`'newSession'`]: #event-newsession
 [`'resumeSession'`]: #event-resumesession
+[`'secure'`]: #event-secure
 [`'secureConnect'`]: #event-secureconnect
 [`'secureConnection'`]: #event-secureconnection
 [`'session'`]: #event-session