doc: outline when origin is set to unhandledRejection

PR-URL: #35294 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Denys Otrishko <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Rich Trott <[email protected]>
nodejs · Sep 29, 2020 · 70ad69b · 70ad69b
1 parent 80eb221
commit 70ad69b
Showing 1 changed file with 5 additions and 2 deletions.
diff --git a/doc/api/process.md b/doc/api/process.md
@@ -237,7 +237,8 @@ changes:
 * `origin` {string} Indicates if the exception originates from an unhandled
  rejection or from an synchronous error. Can either be `'uncaughtException'` or
  `'unhandledRejection'`. The latter is only used in conjunction with the
- [`--unhandled-rejections`][] flag set to `strict` and an unhandled rejection.
+ [`--unhandled-rejections`][] flag set to `strict` or `throw` and
+ an unhandled rejection.
 
 The `'uncaughtException'` event is emitted when an uncaught JavaScript
 exception bubbles all the way back to the event loop. By default, Node.js
@@ -306,7 +307,9 @@ added: v13.7.0
 * `err` {Error} The uncaught exception.
 * `origin` {string} Indicates if the exception originates from an unhandled
  rejection or from synchronous errors. Can either be `'uncaughtException'` or
- `'unhandledRejection'`.
+ `'unhandledRejection'`. The latter is only used in conjunction with the
+ [`--unhandled-rejections`][] flag set to `strict` or `throw` and
+ an unhandled rejection.
 
 The `'uncaughtExceptionMonitor'` event is emitted before an
 `'uncaughtException'` event is emitted or a hook installed via