message: Clean up fatal error handler docs wording
diff: @@ -271,19 +271,19 @@ Global Fatal Error Handler
  --------------------------
  The ``install`` method sets up a global listener for uncaught exceptions, and ``context`` and ``wrap`` can catch exceptions as well.
  -These are situations where Raven catches what would otherwise be a fatal process-ending exception; a process should generally not
  -continue to run after uncaught exceptions and similar such events (see `Node docs <http://nodejs.org/api/process.html#process_event_uncaughtexception>`_),
  -so Raven has a concept of a "fatal error handler". When Raven catches what would otherwise be a fatal process-ending exception,
  -it captures the exception and then calls the fatal error handler.
  +These are situations where Raven catches what would otherwise be a fatal process-ending exception. A process should generally not
  +continue to run after such events occur, (see `Node docs <http://nodejs.org/api/process.html#process_event_uncaughtexception>`_),
  +so Raven has a concept of a "fatal error handler". When Raven catches an otherwise-fatal exception, it will capture the exception
  +(send it to Sentry) and then call the fatal error handler.
  By default, the fatal error handler prints the error and then exits the process. If you want to do your own clean-up,
  -pre-exit logging, or other shutdown procedures, you can provide your own fatal error handler as a parameter to ``install()``.
  +pre-exit logging, or other shutdown procedures, you can provide your own fatal error handler as an argument to ``install()``.
  -The fatal error hander callback will be the last thing called before the process should shut down.
  +The fatal error handler callback will be the last thing called before the process should shut down.
  It can do anything necessary, including asynchronous operations, to make a best effort to clean up and shut down the process, but it should
  not throw, and it absolutely must not allow the process to keep running indefinitely. This means it should probably make an explicit ``process.exit()`` call.
  -After catching a fatal exception, Raven will first attempt to send it to Sentry before it calls the fatal exception handler.
  +After catching a fatal exception, Raven will make a best-effort attempt to send it to Sentry before it calls the fatal exception handler.
  If sending fails, a ``sendErr`` error object will be passed, and otherwise the ``eventId`` will be provided. In either case, the error object
  resulting in the shutdown is passed as the first parameter.
  