code review

doc/api/events.md

@@ -1249,13 +1249,13 @@ target.addEventListener('foo', handler4, { once: true });
 When a registered event listener throws (or returns a Promise that rejects),
 by default the error is treated as an uncaught exception on
 `process.nextTick()`. This means uncaught exceptions in `EventTarget`s will
-crash the Node.js process by default.
+terminate the Node.js process by default.
 
 Throwing within an event listener will *not* stop the other registered handlers
 from being invoked.
 
 The `EventTarget` does not implement any special default handling for `'error'`
-type events like `EventEmitter` does in order to be spec compliant.
+type events like `EventEmitter`.
 
 Currently errors are first forwarded to the `process.on('error')` event
 before reaching `process.on('uncaughtException')` - this behaviour is