From b0a6da7e3cdc78fdac084d9820572121ccf7a8aa Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Thu, 20 Jun 2019 13:39:01 -0600 Subject: [PATCH] doc: remove "note that" from process.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Refs: https://github.com/nodejs/remark-preset-lint-node/pull/16 PR-URL: https://github.com/nodejs/node/pull/28329 Reviewed-By: Gus Caplan Reviewed-By: Trivikram Kamat Reviewed-By: Tobias Nießen Reviewed-By: Ruben Bridgewater --- doc/api/process.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/api/process.md b/doc/api/process.md index d75d935834be6c..752889b3f0ee03 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -242,7 +242,7 @@ console.log('This will not run.'); #### Warning: Using `'uncaughtException'` correctly -Note that `'uncaughtException'` is a crude mechanism for exception handling +`'uncaughtException'` is a crude mechanism for exception handling intended to be used only as a last resort. The event *should not* be used as an equivalent to `On Error Resume Next`. Unhandled exceptions inherently mean that an application is in an undefined state. Attempting to resume application @@ -922,7 +922,7 @@ process.emitWarning(myWarning); A `TypeError` is thrown if `warning` is anything other than a string or `Error` object. -Note that while process warnings use `Error` objects, the process warning +While process warnings use `Error` objects, the process warning mechanism is **not** a replacement for normal error handling mechanisms. The following additional handling is implemented if the warning `type` is @@ -1350,7 +1350,7 @@ the group access list, using all groups of which the user is a member. This is a privileged operation that requires that the Node.js process either have `root` access or the `CAP_SETGID` capability. -Note that care must be taken when dropping privileges: +Use care when dropping privileges: ```js console.log(process.getgroups()); // [ 0 ]