   `{:ok, reply, new_state}` except the process is hibernated. See
   `handle_event/2` for more information on hibernation.
 
-  Returning `{:remove_handler, reply}` sends `reply` as a reponse to the call,
+  Returning `{:remove_handler, reply}` sends `reply` as a response to the call,
   removes the handler from the `GenEvent` loop and calls `terminate/2` with
   reason `:remove_handler` and state `state`.
   """


  ## Learn more and compatibility

  If you wish to find out more about gen events, Elixir getting started
  guides provide a tutorial-like introduction. The documentation and links
  in Erlang can also provide extra insight.

    * [Introduction to Mix – Elixir's Getting Started Guide](http://elixir-lang.org/getting-started/mix-otp/introduction-to-mix.html)
    * [`:gen_event` module documentation](http://www.erlang.org/doc/man/gen_event.html)
    * [Event Handlers – Learn You Some Erlang for Great Good!](http://learnyousomeerlang.com/event-handlers)



  ## Modes

  GenEvent supports three different notifications.

  On `GenEvent.ack_notify/2`, the manager acknowledges each event,
  providing backpressure, but processing of the message happens
