   writing a new backend is a matter of creating an event
   handler, as described in the `GenEvent` module.
 
-  From now on, we will be using event handler to refer to
-  your custom backend, as we head into implementation details.
-
-  The `add_backend/1` function is used to start a new
-  backend, which installs the given event handler to the
-  Logger event manager. This event handler is automatically
-  supervised by Logger.
-
-  Once added, the handler should be able to handle events
+  From now on, we will be using the term "event handler" to refer
+  to your custom backend, as we head into implementation details.
+
+  Once Logger starts, it installs all event handlers under
+  the `:backends` configuration into Logger event manager.
+  The event manager and all added event handlers are
+  automatically supervised by Logger.
+
+  Once initialized, the handler should be able to handle events
   in the following format:
 
       {level, group_leader,

  The initial backends are loaded via the `:backends` configuration,
  which must be set before the logger application is started. However,
  backends can be added or removed dynamically via the `add_backend/2`,
  `remove_backend/1` and `configure_backend/2` functions. Note though
  that dynamically added backends are not restarded in case of crashes.

  ### Console backend


  the group leader is in a different node than the one
  the handler is installed.

  Furthermore, backends can be configured via the
  `configure_backend/2` function which requires event handlers
  to handle calls of the following format:

      {:configure, options}

  where options is a keyword list. The result of the call is
  the result returned by `configure_backend/2`. The recommended
  return value for successful configuration is `:ok`.

  It is recommended that backends support at least the following
  configuration values:
