doc: format try...catch consistently

PR-URL: nodejs#28481
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>

doc/api/addons.md

@@ -311,7 +311,7 @@ it is compiled (i.e. sometimes it may be in `./build/Debug/`), Addons can use
 the [bindings][] package to load the compiled module.
 
 While the `bindings` package implementation is more sophisticated in how it
-locates Addon modules, it is essentially using a try-catch pattern similar to:
+locates Addon modules, it is essentially using a `try…catch` pattern similar to:
 
 ```js
 try {

doc/api/errors.md

@@ -171,11 +171,10 @@ try {
 
 This will not work because the callback function passed to `fs.readFile()` is
 called asynchronously. By the time the callback has been called, the
-surrounding code, including the `try { } catch (err) { }` block, will have
-already exited. Throwing an error inside the callback **can crash the Node.js
-process** in most cases. If [domains][] are enabled, or a handler has been
-registered with `process.on('uncaughtException')`, such errors can be
-intercepted.
+surrounding code, including the `try…catch` block, will have already exited.
+Throwing an error inside the callback **can crash the Node.js process** in most
+cases. If [domains][] are enabled, or a handler has been registered with
+`process.on('uncaughtException')`, such errors can be intercepted.
 
 ## Class: Error
 

doc/api/fs.md

@@ -32,7 +32,7 @@ fs.unlink('/tmp/hello', (err) => {
 ```
 
 Exceptions that occur using synchronous operations are thrown immediately and
-may be handled using `try`/`catch`, or may be allowed to bubble up.
+may be handled using `try…catch`, or may be allowed to bubble up.
 
 ```js
 const fs = require('fs');