 
   The given `opts` are merged into the existing values for `key`
   in the given `app`. Conflicting keys are overridden by the
-  ones specified in `opts`. For example, given the two configurations
-  below:
+  ones specified in `opts`. For example, the application
+  configuration below
 
       config :ecto, Repo,
         log_level: :warn,


  The most common use of `Mix.Config` is to define application
  configuration so that `Application.get_env/3` and other `Application`
  functions can be used to retrieve or change configuration.

  Such configurations are typically placed in the `config/` directory
  of your Mix projects. For example, the following config

      config :my_app, :key, "value"

  can be accessed in your application code as follows:

      "value" = Application.fetch_env!(:my_app, :key1)



  The given `opts` are merged into the existing configuration
  for the given `app`. Conflicting keys are overridden by the
  ones specified in `opts`. For example, the application
  configuration below

      config :logger,
        level: :warn,
        backends: [:console]

      config :logger,
        level: :info,
        truncate: 1024

  will have a final configuration for `:logger` of:

      [level: :info, backends: [:console], truncate: 1024]

  """
  def config(app, opts) when is_atom(app) and is_list(opts) do
