Clarify and link to config modules, closes #14533

Author: josevalim

lib/elixir/pages/mix-and-otp/config-and-releases.md

@@ -57,9 +57,11 @@ Configuration files provide a mechanism for us to configure the environment of a
 
   * `config/config.exs` — this file is read at build time, before we compile our application and before we even load our dependencies. This means we can't access the code in our application nor in our dependencies. However, it means we can control how they are compiled
 
-  * `config/runtime.exs` — this file is read after our application and dependencies are compiled and therefore it can configure how our application works at runtime. If you want to read system environment variables (via `System.get_env/1`) or any sort of external configuration, this is the appropriate place to do so
+  * `config/runtime.exs` — this file is read after our application and dependencies are compiled and therefore it can configure how our application works at runtime. If you want to read system environment variables (via `System.get_env/1`) or access external configuration, this is the appropriate place to do so
 
-For example, we can configure IEx default prompt to another value. Let's create the `config/runtime.exs` file with the following content:
+You can learn more about configuration in the `Config` and `Config.Provider` modules. For now, let's see an example.
+
+We can configure IEx default prompt to another value by creating a `config/runtime.exs` file with the following content:
 
 ```elixir
 import Config

lib/mix/lib/mix/tasks/release.ex

@@ -626,8 +626,8 @@ defmodule Mix.Tasks.Release do
 
   ### Runtime configuration
 
-  To enable runtime configuration in your release, all you need to do is
-  to create a file named `config/runtime.exs`:
+  To enable runtime configuration in your release, create a file named
+  `config/runtime.exs`:
 
       import Config
       config :my_app, :secret_key, System.fetch_env!("MY_APP_SECRET_KEY")