summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorcjihrig <cjihrig@gmail.com>2019-06-30 11:42:52 -0400
committercjihrig <cjihrig@gmail.com>2019-07-02 14:06:01 -0400
commitcce78bbdf5ca4e2fad2766978cb29a2ee9631647 (patch)
tree40478a2e85124616d982e3e974f9e374160a947b
parentea736668500d640783242186334c38a144501961 (diff)
downloadandroid-node-v8-cce78bbdf5ca4e2fad2766978cb29a2ee9631647.tar.gz
android-node-v8-cce78bbdf5ca4e2fad2766978cb29a2ee9631647.tar.bz2
android-node-v8-cce78bbdf5ca4e2fad2766978cb29a2ee9631647.zip
doc: format try...catch consistently
PR-URL: https://github.com/nodejs/node/pull/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>
-rw-r--r--doc/api/addons.md2
-rw-r--r--doc/api/errors.md9
-rw-r--r--doc/api/fs.md2
3 files changed, 6 insertions, 7 deletions
diff --git a/doc/api/addons.md b/doc/api/addons.md
index eb17650223..a75d287dce 100644
--- a/doc/api/addons.md
+++ b/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 {
diff --git a/doc/api/errors.md b/doc/api/errors.md
index 64cdb9eb57..6669623239 100644
--- a/doc/api/errors.md
+++ b/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
diff --git a/doc/api/fs.md b/doc/api/fs.md
index c6ae9a83ac..568e7447f0 100644
--- a/doc/api/fs.md
+++ b/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');