   the `RELEASE_TMP` environment variable, either explicitly or inside your
   `releases/RELEASE_VSN/env.sh` (or `env.bat` on Windows).
 
-  The `releases/RELEASE_VSN/env.sh` script can also be used to perform
-  limited runtime configuration via Erlang `-app` flags. For example, if
-  you want to make sure the Erlang Distribution listens only on a given
-  port known at runtime, you can set the following:
-
-      export ELIXIR_ERL_OPTIONS="-kernel inet_dist_listen_min $BEAM_PORT inet_dist_listen_max $BEAM_PORT"
-
-  Or for Windows, in your `releases/RELEASE_VSN/env.bat`:
-
-      set ELIXIR_ERL_OPTIONS=-kernel inet_dist_listen_min %BEAM_PORT% inet_dist_listen_max %BEAM_PORT%
-
-  See the "Customization" section to learn exactly how to provide a custom
-  `releases/RELEASE_VSN/env.sh` file.
-
   ### Config providers
 
   Releases also supports custom mechanisms, called config providers, to load

  their respective supervision trees will stop, one by one, in the
  opposite order that they were started.

  ## Options

  Here are the general options available to each release:

    * `:applications` - a keyword list that configures and adds new applications
      to the release. The key is the application name and the value is one of:

  can be achieved with config providers. See the `Config.Provider` for more
  information and a simple example.

  The following options can be set inside your releases key in your mix.exs
  to control how runtime configuration and config providers work:

    * `:runtime_config_path` - the path to your runtime configuration file.
