     * Provides debug, info, warn and error levels.
 
     * Supports multiple backends which are automatically
-      supervised when plugged into Logger.
+      supervised when plugged into `Logger`.
 
     * Formats and truncates messages on the client
-      to avoid clogging Logger backends.
+      to avoid clogging `Logger` backends.
 
     * Alternates between sync and async modes to remain
       performant when required but also apply backpressure

      error reports. This configuration allow developers to change
      how much and how the data should be inspected.

  For example, to configure the `:level` and `:truncate` in a
  `config/config.exs` file:

      config :logger,

      threshold, the `error_logger` enters discard mode for the
      remainder of that second. Defaults to 500 messages.

  For example, to configure `Logger` to redirect all `error_logger` messages
  using a `config/config.exs` file:

      config :logger,
        handle_otp_reports: true,
        handle_sasl_reports: true

  Furthermore, `Logger` allows messages sent by Erlang's `error_logger`
  to be translated into an Elixir format via translators. Translators
  can be dynamically added at any time with the `add_translator/1`
  and `remove_translator/1` APIs. Check `Logger.Translator` for more
