doc: clarify examples section in REPL doc

The current examples presented at the bottom
of the REPL doc have two issues:
 - they look like they're part of the section
   above (on how to run multiple REPL instances
   in the same process) but they are not
 - the alert informing readers not to use the
   second example in production environments
   can be wrongly interpreted as to refer to
   both examples
The changes here address both these issues

Author: dario-piotrowicz

doc/api/repl.md

@@ -909,20 +909,22 @@ to connect to both Unix and TCP sockets.
 By starting a REPL from a Unix socket-based server instead of stdin, it is
 possible to connect to a long-running Node.js process without restarting it.
 
-For an example of running a "full-featured" (`terminal`) REPL over
-a `net.Server` and `net.Socket` instance, see:
+### Examples
+
+- running a "full-featured" (`terminal`) REPL over
+a `net.Server` and `net.Socket` instance:
 <https://gist.github.com/TooTallNate/2209310>.
 
-For an example of running a REPL instance over [`curl(1)`][], see:
+- running a REPL instance over [`curl(1)`][]:
 <https://gist.github.com/TooTallNate/2053342>.
 
-This example is intended purely for educational purposes to demonstrate how
-Node.js REPLs can be started using different I/O streams.
-It should **not** be used in production environments or any context where security
-is a concern without additional protective measures.
-If you need to implement REPLs in a real-world application, consider alternative
-approaches that mitigate these risks, such as using secure input mechanisms and
-avoiding open network interfaces.
+  **Note**: This example is intended purely for educational purposes to demonstrate how
+  Node.js REPLs can be started using different I/O streams.
+  It should **not** be used in production environments or any context where security
+  is a concern without additional protective measures.
+  If you need to implement REPLs in a real-world application, consider alternative
+  approaches that mitigate these risks, such as using secure input mechanisms and
+  avoiding open network interfaces.
 
 [TTY keybindings]: readline.md#tty-keybindings
 [ZSH]: https://en.wikipedia.org/wiki/Z_shell